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 GaryGregory: https://wiki.apache.org/commons/UsingNexus?action=diff&rev1=34&rev2=35 Comment: Update section "Publish the website" with link to SCM publishing docs. This will create the binary, source and javadoc jars and hashes and upload them. - The {{{-Prelease}}} flag ensures that the source and javadoc jars are created. - The {{{-Dgpg.skip}}} flag skips the signing phase; do not omit this as it might mislead users if a signed jar was deployed as a snapshot + The {{{-Prelease}}} flag ensures that the source and javadoc jars are created. The {{{-Dgpg.skip}}} flag skips the signing phase; do not omit this as it might mislead users if a signed jar was deployed as a snapshot The resulting snapshot will appear in the Nexus repository under: @@ -253, +252 @@ -DstagingSiteURL=scp://[...]/people.apache.org/builds/commons/compress/1.1/RC1 }}} The site should appear on the specified folder. Alternatively, you can stage the site in your ''public_html'' folder in your home directory on ''people.apache.org''. This can be done with the following command: + {{{ mvn site:stage-deploy -DstagingSiteURL=scp://people.apache.org/home/<ApacheID>/public_html/foo-1.2rc1 }}} - ==== Send Out The Vote ==== Below you find a vote template to save you some time ... @@ -313, +312 @@ * -e robots=off ignore robots.txt * --wait 10 wait between retrievals - Check the MD5/SHA hashes! This can be done for instance with the ''verify_sigs.sh'' script available under [[https://svn.apache.org/repos/private/committers/tools/releases]] (just check out from SVN and place the shell scripts in the ''bin'' folder below your home directory). + Check the MD5/SHA hashes! This can be done for instance with the ''verify_sigs.sh'' script available under https://svn.apache.org/repos/private/committers/tools/releases (just check out from SVN and place the shell scripts in the ''bin'' folder below your home directory). Also, change the group to commons and ensure that the files can be written by the group: + {{{ chgrp commons * chmod g+w * @@ -368, +368 @@ 1. Follow the links to the binaries and source directories. Check them in a similar manner. ===== Publish the website ===== + See https://commons.apache.org/site-publish.html - 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). 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 - }}} - 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 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. @@ -404, +389 @@ The actual release task is now complete, however there are some remaining steps to do some cleanup and to prepare the next development iteration. * '''Remove Obsolete Releases''': Unless old versions are especially required, remove them from the dist directory. This will cause the files to also be deleted from the mirrors and save them some diskspace as well as simplifying things for users. Note that the contents of the /www/www.apache.org/dist directory is regularly copied to /www/archive.apache.org/dist and from there transferred to host archive.apache.org. Deleting files from the standard distribution directories does ''not'' delete them from the archive dist directories so users will still be able to access old files even when they are not available from the mirrors. - * '''Update JIRA''': Mark the release as released in the JIRA project admin and CLOSE all issues RESOLVED in this release. Make sure the FIX VERSION for all issues closed with this release is set correctly to this version. If this has not already been done, create a JIRA version for the next release. + * '''Update JIRA''': Mark the release as released in the JIRA project admin and CLOSE all issues RESOLVED in this release. Make sure the FIX VERSION for all issues closed with this release is set correctly to this version. If this has not already been done, create a JIRA version for the next release. * '''Update DOAP file''': Update the component's [[http://projects.apache.org/guidelines.html|DOAP]] file with details of the released version: + {{{ <release> <Version> @@ -413, +399 @@ <created>yyyy-mm-dd</created> <revision>x.y.z</revision> </Version> - </release> + </release> }}} * '''Update changes.xml''': If the component uses the maven changes plugin to maintain its changelog, fill in the release date for the just released version and create a new release element for the next release. * '''Create the relase tag''': Copy the tag of the RC whose vote succeeded to the final release tag, e.g. + {{{ svn copy https://svn.apache.org/repos/asf/commons/proper/foo/tags/FOO_1.2RC1 https://svn.apache.org/repos/asf/commons/proper/foo/tags/FOO_1.2 -m "Tagging 1.2 release" --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
