Author: onealj
Date: Thu Feb  2 00:50:28 2017
New Revision: 1781339

URL: http://svn.apache.org/viewvc?rev=1781339&view=rev
Log:
add shell code to move artifacts from staging dist.apache.org repo to release 
dist.apache.org repo

Modified:
    poi/site/src/documentation/release-guide.txt

Modified: poi/site/src/documentation/release-guide.txt
URL: 
http://svn.apache.org/viewvc/poi/site/src/documentation/release-guide.txt?rev=1781339&r1=1781338&r2=1781339&view=diff
==============================================================================
--- poi/site/src/documentation/release-guide.txt (original)
+++ poi/site/src/documentation/release-guide.txt Thu Feb  2 00:50:28 2017
@@ -160,32 +160,68 @@ find . -name "*.asc" -exec gpg --no-secm
 
  (IV) After the vote:
 
-In the release area of the dist repo:
+Deploy the artifacts from the staging area 
(https://dist.apache.org/repos/dist/dev/poi/)
+to the release area of the dist repo:
     https://dist.apache.org/repos/dist/release/poi/release/   (FINAL)
-    https://dist.apache.org/repos/dist/release/poi/dev/       (Alpha/Beta)
-Remove the previous release
+    https://dist.apache.org/repos/dist/release/poi/dev/       (Beta)
 
-Next, svn move the files from the /dist/dev/ area to the appropriate
-/dist/release/ area
+Perform a sparse checkout of the dist repo to move artifacts in the staging 
area to the beta or final release area
+In the following example, replace FIXME3.16-beta2-RC1 or FIXME3.16-beta2 with 
the version you are releasing
 
-FIXME: The release directory structure has changed.
-The commands need to be updated
-example:
-$ svn rm -m "remove the previous release" \
-    https://dist.apache.org/repos/dist/release/poi/dev/src \
-    https://dist.apache.org/repos/dist/release/poi/dev/bin
-
-$ svn mv -m "move staging files to the release area" \
-    https://dist.apache.org/repos/dist/dev/poi/bin \
-    https://dist.apache.org/repos/dist/dev/poi/src/  \
-    https://dist.apache.org/repos/dist/release/poi/dev/
+For a beta release:
+{code}
+svn checkout https://dist.apache.org/repos/dist/ --depth immediates
+svn update --set-depth immediates dist/dev/poi/
+svn update --set-depth infinity   dist/dev/poi/FIXME3.16-beta2-RC1/
+svn update --set-depth infinity   dist/release/poi/
+svn rm dist/release/poi/dev/src/* dist/release/poi/dev/bin/* 
dist/release/poi/dev/maven/
+svn mv dist/dev/poi/FIXME3.16-beta2-RC1/poi-src-* dist/release/poi/dev/src/
+svn mv dist/dev/poi/FIXME3.16-beta2-RC1/poi-bin-* dist/release/poi/dev/bin/
+svn mv dist/dev/poi/FIXME3.16-beta2-RC1/maven/ dist/release/poi/dev/
+svn mv dist/dev/poi/FIXME3.16-beta2-RC1/RELEASE-NOTES.txt 
dist/release/poi/dev/RELEASE-NOTES-FIXME3.16-beta2.txt
+# regular (non-svn) copy so that these text files retain their revision history
+cp dist/release/poi/dev/RELEASE-NOTES-FIXME3.16-beta2.txt 
dist/release/poi/dev/RELEASE-NOTES.txt
+cp dist/dev/poi/KEYS dist/release/poi/KEYS
+svn checkin dist/ -m "deploy 3.16-beta2 release artifacts from staging area"
+{code}
+
+For a final release:
+{code}
+svn checkout https://dist.apache.org/repos/dist/ --depth immediates
+svn update --set-depth immediates dist/dev/poi/
+svn update --set-depth infinity   dist/dev/poi/FIXME3.16-RC1/
+svn update --set-depth infinity   dist/release/poi/
+svn rm dist/release/poi/release/src/* dist/release/poi/release/bin/* 
dist/release/poi/release/maven/
+svn mv dist/dev/poi/FIXME3.16-RC1/poi-src-* dist/release/poi/release/src/
+svn mv dist/dev/poi/FIXME3.16-RC1/poi-bin-* dist/release/poi/release/bin/
+svn mv dist/dev/poi/FIXME3.16-RC1/maven/ dist/release/poi/release/
+svn mv dist/dev/poi/FIXME3.16-RC1/RELEASE-NOTES.txt 
dist/release/poi/dev/RELEASE-NOTES-FIXME3.16.txt
+# regular (non-svn) copy so that these text files retain their revision history
+cp dist/release/poi/dev/RELEASE-NOTES-FIXME3.16.txt 
dist/release/poi/dev/RELEASE-NOTES.txt
+cp dist/dev/poi/KEYS dist/release/poi/KEYS
+svn checkin dist/ -m "deploy 3.16 release artifacts from staging area"
+{code}
+
+
+And remove any old releases from the staging area
+
+{code}
+svn rm https://dist.apache.org/repos/dist/dev/poi/FIXME3.16-beta1-RC1 -m 
"remove old release from staging area"
+{code}
 
+You should get an email from the Apache Reporter Service 
([email protected])
+at your Apache email address.
+The email instructions will ask you to log on to 
https://reporter.apache.org/addrelease.html?poi
+and add your release data (version and date) to the database.
 
 Log into https://repository.apache.org/ and go to the "Staging Repositories" 
area.
-Find the "orgapachepoi" entry, check it has the right content, then Close the 
repository.
-When that completes, Release it.
+Find the "orgapachepoi" entry, check it has the right content, then Close the 
repository
+(it was probably already closed by release-prep3).
+Select all artifacts and Release (and Automatically Drop) them.
+Refresh to verify that the artifacts are no longer in the Staging Repositories 
area.
 
-2. Wait for the distributions to appear on your favourite mirror
+2. Wait for the distributions to appear on your favourite mirror (anywhere 
from 3-24 hours)
+   Maven Central: 
https://search.maven.org/#search|ga|1|g%3A%22org.apache.poi%22
 
 3. Wait for the maven artifacts to appear on Maven Central, and ensure
    they work:
@@ -247,8 +283,10 @@ ant update-download -Dversion.id="3.15-b
 7. Don't forget to upload the latest version of the site and javadocs
 
 8. Send announcements:
- - to poi-user and poi-dev lists
- - to [email protected]
+From: your @apache.org e-mail address
+To: [email protected], [email protected], [email protected], and 
[email protected]
+Subject: Apache POI 3.16-beta2 released
+Body: 
 
 Note, announcements should be sent from your @apache.org e-mail address.
 
@@ -256,6 +294,7 @@ Note, announcements should be sent from
    next -dev version. Also close the n-2 -dev version to new bugs.
 
 10. If this is a final release, add it to the DOAP file too
+  https://svn.apache.org/repos/asf/poi/trunk/doap_POI.rdf
 
 11. Delete directory that held RC.
 



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to