accumulo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1680443 - /accumulo/site/trunk/content/releasing.mdtext
Date Wed, 20 May 2015 02:51:48 GMT
Author: elserj
Date: Wed May 20 02:51:48 2015
New Revision: 1680443

ACCUMULO-3825 Update releasing document to be slightly more accurate and consumable.


Modified: accumulo/site/trunk/content/releasing.mdtext
--- accumulo/site/trunk/content/releasing.mdtext (original)
+++ accumulo/site/trunk/content/releasing.mdtext Wed May 20 02:51:48 2015
@@ -46,6 +46,21 @@ it was agreed upon to omit issues from p
 ## Create the candidate
+* `./assemble/ --create-release-candidate` to make the release candidate
+* `git tag $version $version-rcN` to create an RC tag from the actual tag
+* `git tag -d $version` make sure you don't accidentally push a "release" tag
+* `git push origin $version-rcN` push the RC tag
+* `git checkout -b $version-rcN-branch` save off the branch from the Maven release plugin
+* **VOTE**
+* *If vote fails*, fix the original branch and start over.
+* *If vote passes*, `git merge $version-rcN-branch` back into the original branch you released
+* `git tag -s $version-rcN $version` make a GPG-signed tag
+* `git push origin $version` push the signed tag.
+**Long-winded explanation**
 You should use the provided script assemble/ to create the release candidate. This
script is
 desirable as it activates all necessary maven profiles in addition to verifying that certain
 are met, like RPM signing availablilty and the ability to sign files using GPG. The --test
option can 
@@ -61,14 +76,6 @@ voting to occur on artifacts that cannot
 likely take at least 15 minutes, even on recent hardware), your current branch will be on
the "next" version 
 that you provided to the release plugin.
-This process is likely to fail because the maven-release-plugin is not configured to push
to the 
-remote repository automatically; however, this is (semi-)expected. At this point, you
-should have a local git tag for the release that you're creating. You should create a branch
-from the tag that was made by the release plugin which includes the _-rcN_ suffix. This way,
the branch name 
-will correctly identify which release candidate this is, while the contents of that tag will
have the correct 
-versions in the pom.xml files. This also ensure that the _release:perform_ goal of the release
plugin will
-work as intended.
 One unwanted side-effect of this approach is that after creating this branch, but *before
invoking release:perform*,
 you must edit the to add the _-rcN_ suffix to the value of scm.tag. Otherwise,
the release
 plugin will complain that it cannot find the branch for the release. With a successful invocation
of *mvn release:perform*,
@@ -92,11 +99,23 @@ If the vote passes, huzzah, you're almos
 using Nexus which you can do with the click of a button. This will trigger a process to get
the release
 out to all of the mirrors.
+## Copy artifacts to
+An SVN server is running at You need
to upload the release
+tarballs, the GPG signatures and checksum files to the correct directory (based on the release
number). If you
+are releasing a bug-fix release, be sure to delete the previous release in the same line
(e.g. if you release
+1.6.2, remove 1.6.1). The old tarballs removed from will still be preserved
 ## Update the Website
-After a successful vote, this website needs to be updated with the new artifacts. The downloads
page should
-be updated with the new information. A new minor release should replace the previous minor
release in the major
-version. The user manual should also be updated if changes were made to it.
+After a successful vote, this website needs to be updated with the new artifacts.
+  * Copy Accumulo User Manual (HTML version exists in >=1.7.0)
+  * Update downloads page
+  * Create release notes
+  * Remove previous bug-fix release (if applicable)
+  * Update examples README files
 ### Javadocs

View raw message