parallel/doc/release_new_version

= Notes on how to release new version =

== alpha/beta/production ==

Update documentation:

git blame
Unmodified beta since last version => production
Unmodified alpha since last version => beta
Modified => alpha

== Update version ==

=== configure.ac ===
configure.ac: AC_INIT([parallel], [20100422], [bug-parallel@gnu.org])

YYYYMMDD=`yyyymmdd`
perl -i -pe "s/20\d\d\d\d\d\d/$YYYYMMDD/" configure.ac

=== src/parallel ===

src/parallel: $Global::version = 20100422;

YYYYMMDD=`yyyymmdd`
perl -i -pe "/version/ and s/20\d\d\d\d\d\d/$YYYYMMDD/" src/parallel
perl -i -pe "/version/ and s/20\d\d\d\d\d\d/$YYYYMMDD/" src/sql
perl -i -pe "/version/ and s/20\d\d\d\d\d\d/$YYYYMMDD/" src/niceload

=== Autoconf/automake ===

rm -fr autom4te.cache aclocal.m4 config.h config.h.in config.log Makefile.in missing install-sh
rm -rf src/Makefile.in
autoreconf --install -W gnu
./configure
make -j && sudo make install

== Testsuite ==

cd testsuite; make

== Update NEWS ==

With the same things that goes in the announce mail

== Package ==

./configure
make dist
make dist-bzip2

== Test the package ==

YYYYMMDD=`yyyymmdd`
cp parallel-$YYYYMMDD.tar.bz2 /tmp
pushd /tmp
tar xjvf parallel-$YYYYMMDD.tar.bz2
cd parallel-$YYYYMMDD
./configure && make -j && sudo make -j install
pushd

== Upload ==

YYYYMMDD=`yyyymmdd`
cp doc/parallel.directive parallel-$YYYYMMDD.tar.bz2.directive
perl -i -pe "s/20\d\d\d\d\d\d/$YYYYMMDD/" parallel-*.tar.*directive
gpg --clearsign parallel-$YYYYMMDD.tar.bz2.directive

YYYYMMDD=`yyyymmdd`
gpg -b parallel-$YYYYMMDD.tar.bz2

YYYYMMDD=`yyyymmdd`
echo put parallel-$YYYYMMDD.tar.bz2{,.sig,*asc} | ncftp ftp://ftp-upload.gnu.org/incoming/ftp/
#echo put parallel-$YYYYMMDD.tar.bz2{,.sig,*asc} | ncftp ftp://ftp-upload.gnu.org/incoming/alpha/

== Update OpenSUSE build system ==

cd ~/privat/parallel/packager/obs
# Update version number
em home:tange/parallel/parallel.spec
find home:tange/parallel/* -type f | grep -v parallel.spec | parallel -Xj1 osc rm {}
# This should not create new files
osc up home:tange/parallel/
make
# Update versionsnummeret from 20110422-2 to YYYYMMDD-1
# Reload build-status:
https://build.opensuse.org/package/show?package=parallel&project=home%3Atange
# Check that one .deb (Debian 5.0) and one .rpm (CentOS) end with 'succeeded'

== Download and test ==

YYYYMMDD=`yyyymmdd`
pushd /tmp
rm -rf parallel-${YYYYMMDD}*
wget http://ftp.gnu.org/gnu/parallel/parallel-$YYYYMMDD.tar.bz2
#wget http://alpha.gnu.org/gnu/parallel/parallel-$YYYYMMDD.tar.bz2
tar xjvf parallel-$YYYYMMDD.tar.bz2
cd parallel-$YYYYMMDD
./configure
make -j && sudo make -j install
pushd

== Update website ==

http://www.gnu.org/software/parallel/
http://www.gnu.org/software/parallel/man.html
http://www.gnu.org/software/parallel/sql.html
http://www.gnu.org/software/parallel/sem.html
http://www.gnu.org/software/parallel/niceload.html

pod2html src/parallel.pod > ../parallel-web/parallel/man.html
pod2html src/sql > ../parallel-web/parallel/sql.html
pod2html src/niceload.pod > ../parallel-web/parallel/niceload.html
pod2html src/sem.pod > ../parallel-web/parallel/sem.html
pushd ../parallel-web/parallel
cvs up
cvs ci
pushd

== Commit released version ==

git diff
git commit -a

== Update Savannah ==

Content from release mail:

cat doc/release_new_version | klipper-stdin
https://savannah.gnu.org/news/submit.php?group=parallel
https://savannah.gnu.org/news/approve.php?group=parallel

# No longer updated. Too long and too buggy
# doc/pod2savannah_publicinfo src/parallel | klipper-stdin
# https://savannah.gnu.org/project/admin/editgroupinfo.php?group=parallel

== Update Freshmeat ==

http://freshmeat.net/projects/parallel/releases/new

== Update Twitter ==

New version of #GNU Parallel released. See what is new in this release
http://nd.gd/2j Watch the intro video http://nd.gd/039

https://savannah.gnu.org/news/?group=parallel

# Obsolete: Now use @GnuParallel
# # Only 350 requests per hour: 1 tweet = 3 requests
# # 119 tweets/hour = sleep 30 per tweet (40 to be safe)
# # The above is not enough.
# # Went over the limit at number 132 (sleep 40)
# # https://support.twitter.com/entries/15364-about-twitter-limits-update-api-dm-and-following
# # says 250 direct msg per day = 86400/250 = sleep 345
# cat twitters | grep -iv removed |
#   parallel -j1 sleep 354\; echo @{} You have shown interest in GNU Parallel. \
#   New version: http://nd.gd/2j This is the last message: Follow @GnuParallel \
#  '|' ttytter



== Send announce ==

http://groups.google.com/group/comp.unix.shell/post
Newsgroups: comp.unix.shell,comp.unix.admin

https://lists.gnu.org/mailman/admindb/bug-parallel
https://lists.gnu.org/mailman/admindb/parallel

<<<<<
from:tange@gnu.org
to:parallel@gnu.org, bug-parallel@gnu.org, info-gnu@gnu.org, bug-directory@gnu.org
cc:Sandro Cazzaniga <kharec@mandriva.org>,
   Tim Cuthbertson <tim3d.junk@gmail.com>, Ludovic Courtès
   <ludo@gnu.org>, Markus Ammer <mkmm@gmx-topmail.de>, Pavel Nuzhdin
   <pnzhdin@gmail.com>, Phil Sung <psung@alum.mit.edu>, Michael
   Shigorin <mike@altlinux.org>, Andrew McFague <amcfague@wgen.net>,
   Steven M. Christensen <sunfreeware@gmail.com>, Chris Howey
   <howeyc@gmail.com>, Fethican Coşkuner <fethicanc@gmail.com>,
   Rogério Brito <rbrito@ime.usp.br>, Koen Vervloesem
   <koen@vervloesem.eu>, R. Tyler Croy <tyler@monkeypox.org>,
   kerick@shiftedbit.net, Christian Faulhammer <fauli@gentoo.org>,
   Ryoichiro Suzuki <ryoichiro.suzuki@gmail.com>, Jesse Alama
   <jesse.alama@gmail.com>

Subject: GNU Parallel 20111222 ('Hitchens') released

GNU Parallel 20111122 ('Hitchens') has been released. It is
available for download at: http://ftp.gnu.org/gnu/parallel/

This is a bugfix release with no new features. Probably a good release
for stable long-term use.

New in this release:

* Interview in Hacker Public Radio.
  http://hackerpublicradio.org/eps.php?id=0860

* Bug fixes and man page updates.


= About GNU Parallel =

GNU Parallel is a shell tool for executing jobs in parallel using one
or more computers. A job is can be a single command or a small script
that has to be run for each of the lines in the input. The typical
input is a list of files, a list of hosts, a list of users, a list of
URLs, or a list of tables. A job can also be a command that reads from
a pipe. GNU Parallel can then split the input and pipe it into
commands in parallel.

If you use xargs and tee today you will find GNU Parallel very easy to
use as GNU Parallel is written to have the same options as xargs. If
you write loops in shell, you will find GNU Parallel may be able to
replace most of the loops and make them run faster by running several
jobs in parallel. GNU Parallel can even replace nested loops.

GNU Parallel makes sure output from the commands is the same output as
you would get had you run the commands sequentially. This makes it
possible to use output from GNU Parallel as input for other programs.

You can find more about GNU Parallel at:
http://www.gnu.org/s/parallel/

Watch the intro video on
http://www.youtube.com/playlist?list=PL284C9FF2488BC6D1 or at
http://tinyogg.com/watch/TORaR/ and http://tinyogg.com/watch/hfxKj/

When using GNU Parallel for a publication please cite:

O. Tange (2011): GNU Parallel - The Command-Line Power Tool, ;login:
The USENIX Magazine, February 2011:42-47.


= About GNU SQL =

GNU sql aims to give a simple, unified interface for accessing
databases through all the different databases' command line
clients. So far the focus has been on giving a common way to specify
login information (protocol, username, password, hostname, and port
number), size (database and table size), and running queries.

The database is addressed using a DBURL. If commands are left out you
will get that database's interactive shell.

When using GNU SQL for a publication please cite:

O. Tange (2011): GNU SQL - A Command Line Tool for Accessing Different
Databases Using DBURLs, ;login: The USENIX Magazine, April 2011:29-32.


= About GNU Niceload =

GNU niceload slows down a program when the computer load average (or
other system activity) is above a certain limit. When the limit is
reached the program will be suspended for some time. If the limit is a
soft limit the program will be allowed to run for short amounts of
time before being suspended again. If the limit is a hard limit the
program will only be allowed to run when the system is below the
limit.

>>>>>