Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Apache Wiki <wikidiffs@apache.org>
To: Apache Wiki <wikidiffs@apache.org>
Date: Thu, 19 Aug 2010 05:27:57 -0000
Message-ID: <20100819052757.66396.99338@eosnew.apache.org>
Subject: 
 =?utf-8?q?=5BCommons_Wiki=5D_Update_of_=22UsingNexus=22_by_ChristianGrobm?=
 =?utf-8?q?eier?=

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Commons Wiki" for c=
hange 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=3Ddiff&rev1=3D14&rev2=3D15

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

  =

  =3D=3D=3D=3D React to the Vote =3D=3D=3D=3D
  =

- If the vote passes, you can [[http://www.apache.org/dev/publishing-maven-=
artifacts.html#promote|Promote]] otherwise [[http://www.apache.org/dev/publ=
ishing-maven-artifacts.html#drop|Drop]] the repo and start again.
+ If the vote failed, you need to [[http://www.apache.org/dev/publishing-ma=
ven-artifacts.html#drop|Drop]] the repo and start again.
  =

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

+ =3D=3D=3D=3D Releasing =3D=3D=3D=3D
+ =

+ =3D=3D=3D=3D=3D wget the artifcats from nexus to people server =3D=3D=3D=
=3D=3D
+ =

+ In your home directory, perform: =

+ {{{
+ wget -np -r https://repository.apache.org/content/repositories/orgapachec=
ommons-098/org/apache/commons/commons-foo/1.1/
+ }}}
+ =

+ Check the MD5/SHA hashes!
+ =

+ =3D=3D=3D=3D=3D Copy to dist =3D=3D=3D=3D=3D
+ =

+ 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 po=
sition. 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 int=
o 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 "common=
s", for example:
+ =

+ {{{
+ -rw-rw-r--  1 userid   commons     203 Feb 21 23:45 commons-foo-1.2-src.t=
ar.gz.asc
+ }}}
+ =

+ =3D=3D=3D=3D=3D Update README =3D=3D=3D=3D=3D
+ The contents of the README.html are displayed at the bottom of the html s=
howing the directory listing. This document should be updated to reflect th=
e new release. If this document is not present, then copy one from an exist=
ing release directory and edit that.
+ Update the latest release number. Please also read through and correct an=
y mistakes you find and fix other items (eg. urls) which need updating.
+ Copy the revised README.html into the binary and source directories, repl=
acing any old versions.
+ =

+ =3D=3D=3D=3D=3D Update RELEASE-NOTES =3D=3D=3D=3D=3D
+ Replace the current RELEASE-NOTES.txt with the new release notes.
+  =

+ =3D=3D=3D=3D=3D Symbolic Links =3D=3D=3D=3D=3D
+ =

+ 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 s=
ure it is executable and your path includes your /bin subdirectory. From th=
e 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.
+ =

+ =3D=3D=3D=3D=3D Nexus relase =3D=3D=3D=3D=3D
+ =

+  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|P=
romote]]
+ =

+ =3D=3D=3D=3D=3D Test =3D=3D=3D=3D=3D
+ =

+ 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 co=
rrect.
+  1. Check the KEYS file
+  1. Check the RELEASE-NOTES.txt
+  1. Download and verify the current distributions, the following might he=
lp committers/tools/releases/verify_sigs.sh.
+  1. Follow the links to the binaries and source directories. Check them i=
n a similar manner.
+ =

+ =

+ =3D=3D=3D=3D=3D Publish the website =3D=3D=3D=3D=3D
+ =

+ Run the following to deploy the new component website:
+ {{{
+ mvn site:deploy
+ }}} =

+ =

+ On people.apache.org, verify that the directory has been updated, and tha=
t the file and directory permissions are correct (readable by all, not writ=
eable by world, but group writeable). Note that the files are transferred t=
o the real web site only every few hours, so it may be a while before you s=
ee 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 a=
ble to see the changes immediately.
+ =

+ =3D=3D=3D=3D=3D Send announcement =3D=3D=3D=3D=3D
+ =

+ Announce the availability of the new release.
+ =

+ Please remember to give a brief description of your component. Please als=
o remember to remind people about verifying the signatures. The subject sho=
uld 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 re=
lease artifacts are available on the mirrors.
+ =

+ The component website including the updated download page has been update=
d on the public site http://commons.apache.org/foo.
+ =

+ If the component publishes maven artifacts, these artifacts have been rep=
licated to the central maven repo at repo1.maven.org. (Clear your local rep=
o of the release artifacts and either activate the clirr report with the up=
dated version info or update a local project with a dependency to the new r=
elease version to get maven to try to download the release artifacts. Or ju=
st access repo1 using a web browser.)
+ The release announcement should go to (at least) the following mailing li=
sts:
+ =

+  * announce@apache.org
+  * dev@commons.apache.org
+  * user@commons.apache.org
+=20

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