Return-Path:
- 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 ~/public_html/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. - [Note: the source must have been moved already, otherwise the following command will - also be applied to the source files.] -
- mv ~/public_html/foo-1.2-RC3/commons-foo-1.2* 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 + The distribution area of commons releases is populated from + https://dist.apache.org/repos/dist/release/commons/ + via svnpubsub. In order to publish the release, you must move the distributions files + fromdev
torelease
. + +You can perform multiple
+svn mv
operations (with or without local + working copies) or you can use svnmucc, + for example:+ svnmucc -U https://dist.apache.org/repos/dist \ + mv dev/commons/foo/RELEASE-NOTES.txt release/commons/foo \ + mv dev/commons/foo/binaries/commons-foo-1.2-bin.tar.gz release/commons/foo/binaries \ + mv dev/commons/foo/binaries/commons-foo-1.2-bin.tar.gz.asc release/commons/foo/binaries \ + mv dev/commons/foo/binaries/commons-foo-1.2-bin.tar.gz.md5 release/commons/foo/binaries \ + mv dev/commons/foo/binaries/commons-foo-1.2-bin.tar.gz.asc release/commons/foo/binaries \ + mv dev/commons/foo/binaries/commons-foo-1.2-bin.zip release/commons/foo/binaries \ + mv dev/commons/foo/binaries/commons-foo-1.2-bin.zip.asc release/commons/foo/binaries \ + mv dev/commons/foo/binaries/commons-foo-1.2-bin.zip.md5 release/commons/foo/binaries \ + mv dev/commons/foo/binaries/commons-foo-1.2-bin.zip.asc release/commons/foo/binaries \ + mv dev/commons/foo/source/commons-foo-1.2-src.tar.gz release/commons/foo/source \ + mv dev/commons/foo/source/commons-foo-1.2-src.tar.gz.asc release/commons/foo/source \ + mv dev/commons/foo/source/commons-foo-1.2-src.tar.gz.md5 release/commons/foo/source \ + mv dev/commons/foo/source/commons-foo-1.2-src.tar.gz.asc release/commons/foo/source \ + mv dev/commons/foo/source/commons-foo-1.2-src.zip release/commons/foo/source \ + mv dev/commons/foo/source/commons-foo-1.2-src.zip.asc release/commons/foo/source \ + mv dev/commons/foo/source/commons-foo-1.2-src.zip.md5 release/commons/foo/source \ + mv dev/commons/foo/source/commons-foo-1.2-src.zip.asc release/commons/foo/source \ + -m "Publish commons-foo 1.2 Release"-
The README must be https://dist.apache.org/repos/dist/release/commons/foo/README.html
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.
-
Check KEYS file
Check the KEYS
file located in the main release directory. This should contain all the
@@ -101,85 +104,22 @@
that it contains the public key you've used to sign these releases. The KEYS
file
gives instructions on how to do this.
- Symbolic Links
- These are no longer to be used, so please
- do not use symbolic links in mirrored directories!
- Update RELEASE-NOTES
- Replace the current RELEASE-NOTES.txt
with the new release notes.
-
- mv ~/public_html/foo-1.2-RC3/RELEASE-NOTES.txt . --
- Download maven-metadata.xml for commons foo from repo1.maven.org. This file is located in the top-level
- directory for the component. The file should contain a versioning
element, similar to the following:
-
- <versioning> - <release>1.1</release> - <versions> - <version>1.0</version> - <version>1.1</version> - </versions> - <lastUpdated>20091011214529</lastUpdated> - </versioning>- -
- Create a version
element for 1.2, update the release
version and update
- the date in the lastUpdated
element:
-
- <versioning> - <release>1.2</release> - <versions> - <version>1.0</version> - <version>1.1</version> - <version>1.2</version> - </versions> - <lastUpdated>20100401214529</lastUpdated> - </versioning>- -
- Create the hash files, maven-metadata.xml.sha1 and maven-metadata.xml.md5 for the updated metadata file. - If you do not have openssl or another suitable utility installed locally, you can upload the edited - maven-metadata.xml file to people.apache.org and use the following commands to create these files: -
- md5 -q maven-metadata.xml > maven-metadata.xml.md5 - sha1 -q maven-metadata.xml > maven-metadata.xml.sha1- -
- Your Maven artifacts (jar and pom files with hashes and signatures) should be placed in
- /www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/commons/commons-foo/1.2/
on
- people.apache.org. This assumes that your component has been migrated to use the org.apache.commons groupId.
- If the component still uses commons-foo as its groupId, the deployment location should be
- /www/people.apache.org/repo/m2-ibiblio-rsync-repository/commons-foo/commons-foo/1.2. If your RC directory
- includes a "maven" subdirectory including the maven artifacts, you can move the maven artifacts using
- the following commands (assuming the org.apache.commons groupId):
-
- mkdir /www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/commons/commons-foo/1.2 - chgrp commons ~/public_html/foo-1.2-RC3/maven/* - chmod g+w ~/public_html/foo-1.2-RC3/maven/* - mv ~/public_html/foo-1.2-RC3/maven/* /www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/commons/commons-foo/1.2- -
- Double-check permissions on the newly created directory and the deployed files. Also double-check that all - of the artifacts have hashes and signature files associated with them. -
-
- The updated maven-metadata.xml
and its sha1 and md5 hashes should be placed in the directory
- above the deployed artifacts
- (/www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/commons/commons-foo
if
- org.apache.commons is the groupId).
-
Login to the Nexus web interface, select your staging repository and + promote it.
The files placed here will be mirrored (after some delay) to the public distribution repository on http://repo1.maven.org/maven2/.
Copy the release candidate tag in subversion to a name without RC in its name.
+
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.
@@ -207,7 +147,7 @@
Announce the availability of the new release.
@@ -237,7 +177,7 @@That's it! The release is out there - but there is still some tidying up to be done.
@@ -265,9 +205,10 @@ 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 + Note that the contents of the http://www.apache.org/dist directory is regularly copied to + http://archive.apache.org/dist. + Deleting files from the standard distribution directories + on https://dist.apache.org/repos/dist/release/commons/ 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. @@ -281,7 +222,7 @@<release> <Version>