commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Commons Wiki] Update of "UsingNexus" by ChristianGrobmeier
Date Thu, 19 Aug 2010 05:27:57 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification.

The "UsingNexus" page has been changed by ChristianGrobmeier.
The comment on this change is: added releasing section.
http://wiki.apache.org/commons/UsingNexus?action=diff&rev1=14&rev2=15

--------------------------------------------------

  
  ==== React to the Vote ====
  
- If the vote passes, you can [[http://www.apache.org/dev/publishing-maven-artifacts.html#promote|Promote]]
otherwise [[http://www.apache.org/dev/publishing-maven-artifacts.html#drop|Drop]] the repo
and start again.
+ If the vote failed, you need to [[http://www.apache.org/dev/publishing-maven-artifacts.html#drop|Drop]]
the repo and start again.
  
+ 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.
+ 
+ {{{
+ mv ~/foo-1.2-RC3/commons-foo-1.2-src* source 
+ }}}
+ 
+ Move the binary distributions, their detached signatures and md5 sums into position. All
binary versions live in the binaries subdirectory. 
+ 
+ {{{
+ mv ~/foo-1.2-RC3/commons-foo-1.2-bin* binaries
+ }}}
+ 
+ Double check the permissions for both binaries and source distributions. The file permissions
should be "-rw-rw-r--" and the group should be "commons", for example:
+ 
+ {{{
+ -rw-rw-r--  1 userid   commons     203 Feb 21 23:45 commons-foo-1.2-src.tar.gz.asc
+ }}}
+ 
+ ===== Update README =====
+ The contents of the README.html are displayed at the bottom of the html showing the directory
listing. This document should be updated to reflect the new release. If this document is not
present, then copy one from an existing release directory and edit that.
+ Update the latest release number. Please also read through and correct any mistakes you
find and fix other items (eg. urls) which need updating.
+ Copy the revised README.html into the binary and source directories, replacing any old versions.
+ 
+ ===== Update RELEASE-NOTES =====
+ Replace the current RELEASE-NOTES.txt with the new release notes.
+  
+ ===== Symbolic Links =====
+ 
+ Remove symbolic links to current distributions
+ 
+ {{{
+ rm commons-foo-current* 
+ }}}
+ 
+ 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 the argument is the number of your version.
+ 
+ ===== Nexus relase =====
+ 
+  1. remove commons-compress-1.1-bin.* and commons-compress-1.1-src.* from nexus staging
area
+  1. [[http://www.apache.org/dev/publishing-maven-artifacts.html#promote|Promote]]
+ 
+ ===== Test =====
+ 
+ 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:
+ 
+  1. Examine the directory listing page. At the bottom should be found the information you
entered into the README.html. Please check that this is correct.
+  1. Check the KEYS file
+  1. Check the RELEASE-NOTES.txt
+  1. Download and verify the current distributions, the following might help committers/tools/releases/verify_sigs.sh.
+  1. Follow the links to the binaries and source directories. Check them in a similar manner.
+ 
+ 
+ ===== Publish the website =====
+ 
+ Run the following to deploy the new component website:
+ {{{
+ mvn site:deploy
+ }}} 
+ 
+ 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).
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.
+ 
+ ===== Send announcement =====
+ 
+ Announce the availability of the new release.
+ 
+ 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!
+ 
+ Wait to send the release announcement until you have verified that the release artifacts
are available on the mirrors.
+ 
+ The component website including the updated download page has been updated on the public
site http://commons.apache.org/foo.
+ 
+ If the component publishes maven artifacts, these artifacts have been replicated to the
central maven repo at repo1.maven.org. (Clear your local repo of the release artifacts and
either activate the clirr report with the updated version info or update a local project with
a dependency to the new release version to get maven to try to download the release artifacts.
Or just access repo1 using a web browser.)
+ The release announcement should go to (at least) the following mailing lists:
+ 
+  * announce@apache.org
+  * dev@commons.apache.org
+  * user@commons.apache.org
+ 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message