Page History

...

If the vote passed the following steps need to be performed:

Releasing

wget the artifcats from nexus to people server

In your home directory, perform:

wget -np -r https://repository.apache.org/content/repositories/orgapachecommons-098/org/apache/commons/commons-foo/1.1/

Check the MD5/SHA hashes!

Copy to dist

On people.apache.org, change directory to the distribution directory for your component:

cd /www/www.apache.org/dist/commons/foo/ 

Move source distributions, their detached signatures and md5 sums into position. All source versions live in the source subdirectory.

NOTE The Commons Parent pom currently attaches the assembly archives (the -bin* and -src* files) to the deploy phase, so they end up being copied to the Nexus staging repository. This is convenient for voting, as all the files are in the same place, but means that additional action needs to be taken to move the non-Maven files to the correct place.

wget the non-Maven artifacts from Nexus to people server

In your home directory, perform:

wget -np -r https://repository.apache.org/content/repositories/orgapachecommons-098/org/apache/commons/commons-foo/1.1/

Check the MD5/SHA hashes!

Copy to dist

On people.apache.org, change directory to the distribution directory for your component:

cd /www/www.apache.org/dist/commons/foo/ 

Move source distributions, their detached signatures and md5 sums into position. All source versions live in the source subdirectory.

mv ~/foo

mv ~/foo-1.2-RC3/commons-foo-1.2-src* source 

...

Recreate links to current distribution:
From committers/tools/releases in the ASF subversion repository, download the script "symlinks.sh" and install it in your home/bin directory. Make sure it is executable and your path includes your /bin subdirectory. From the top level distribution directory (/www/www.apache.org/dist/commons/foo/), execute

symlinks.sh 1.2

were where the argument is the number of your version.

Nexus

...

release

1. remove commons-compress-1.1-bin.* and commons-compress-1.1-src.* from nexus staging area
2. Promote
   

Test

Note that Nexus release is asynchronous - it may take a short while for the files to be copied to the release area of Nexus and for the status to be updated.

It may take a while for the Maven repo to be synchronised from Nexus. Sometimes the files don't all appear at once.

Test

Wait until the release files Wait until the release files are available from the main Apache web site (http://www.apache.org/dist/commons/foo/), then confirm things are good. Check the main directory:

...

On people.apache.org, verify that the directory has been updated, and that the file and directory permissions are correct (readable by all, not writeable by world, but group writeable). Also, ensure that the group is set to 'commons'. For example:

pwd commons.apache.org : ls -l compress
total 1366
drwxrwsr-x  5 niallp     commons      20 Aug 19 07:22 apidocs
-rw-rw-r--  1 grobmeier  commons   21050 Aug 19 09:19 changes-report.html
drwxrwsr-x  5 niallp     commons      98 Aug 19 07:22 cobertura
-rw-rw-r--  1 grobmeier  commons    7555 Aug 19 09:19 conventions.html

all, not writeable by world, but group writeable). Note that the files are transferred to the real web site only every few hours, so it may be a while before you see your changes appear. However if you set your webbrowser's HTTP proxy to 140.211.11.10 port 80 and access http://commons.apache.org/ you should be able to see the changes immediately.

...

Announce the availability of the new release. Please check that the mirrors have been updated with the new release before sending the announce. There is no need to check all mirrors, but it's worthwhile checking a few of them.

Please remember to give a brief description of your component. Please also remember to remind people about verifying the signatures. The subject should be something like \[ANNOUNCEMENT\] Foo 1.2 Released. Send this mail from your Apache account. Please spell check the document!

...