ctakes-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From james-mas...@apache.org
Subject svn commit: r1545846 - /ctakes/site/trunk/content/ctakes-release-guide.mdtext
Date Tue, 26 Nov 2013 21:28:09 GMT
Author: james-masanz
Date: Tue Nov 26 21:28:08 2013
New Revision: 1545846

URL: http://svn.apache.org/r1545846
Log:
CMS commit to ctakes by james-masanz

Modified:
    ctakes/site/trunk/content/ctakes-release-guide.mdtext

Modified: ctakes/site/trunk/content/ctakes-release-guide.mdtext
URL: http://svn.apache.org/viewvc/ctakes/site/trunk/content/ctakes-release-guide.mdtext?rev=1545846&r1=1545845&r2=1545846&view=diff
==============================================================================
--- ctakes/site/trunk/content/ctakes-release-guide.mdtext (original)
+++ ctakes/site/trunk/content/ctakes-release-guide.mdtext Tue Nov 26 21:28:08 2013
@@ -28,7 +28,7 @@ Move any existing open issues to the nex
 
  1. Send an email out to ctakes-dev@ with the intention of creating a release and that you
will be volunteering for the release manager role.
  2. Decide if you like to A) freeze any development in trunk until the release has been completed.
B) Create a branch that this release will be created from and development in trunk could continue.
- 3. If B) create a branch from trunk (such svn copy from trunk to branches/3.1.0).  Edit
the SVN connections info in the root pom.xml to the branch instead of trunk.  Continue with
the steps below as usual, but just work off the newly created branch instead of trunk.  Note:
It is the RM role to ensure that any fixes done in the branch are also done back in trunk.
+ 3. If B) create a branch from trunk (such svn copy from trunk to branches/3.1.1).  Edit
the SVN connections info in the root pom.xml to the branch instead of trunk.  Continue with
the steps below as usual, but just work off the newly created branch instead of trunk.  Note:
It is the RM role to ensure that any fixes done in the branch are also done back in trunk.
 
 
 Finally the release manager would trigger the release build, sign the generated artifacts
and host them on Apache Nexus & Maven Central. A release vote will be called urging all
those interested to review the packs and provide feedback. Upon receiving the necessary number
of votes, the artifacts will be uploaded to the appropriate servers for distribution.
@@ -39,7 +39,7 @@ Finally the release manager would trigge
  2. Setup your PGP keys: [https://docs.sonatype.org/display/Repository/How+To+Generate+PGP+Signatures+With+Maven][2]
 
 ### Preparing a Release using Maven 
-Note: Using 3.1.0 as an example
+Note: Using 3.1.1 as an example
 
 It may prompt you to enter your PGP passphrase and SVN password multiple times for each module.
 Just enter them in- as passing them in thru the CLI is found to be insecure.
 
@@ -47,11 +47,11 @@ It may prompt you to enter your PGP pass
  2. $mvn release:clean
  3. $mvn release:prepare -DdryRun={false} -Dresume={false} -DautoVersionSubmodules=true
 
-Release: 3.1.0
+Release: 3.1.1
 
-Tag: ctakes-3.1.0-rc1
+Tag: ctakes-3.1.1
 
-Next Dev Release: 3.1.1-SNAPSHOT
+Next Dev Release: 3.1.2-SNAPSHOT
 
 ### Changes for the release
 Update ctakes-distribution/RELEASE_NOTES.html and check in change into trunk or the branch
for the release if using a branch
@@ -63,7 +63,7 @@ This will place the artifacts to the ASF
 
  1. $mvn release:perform<br>
       For example:<br>
- <code>mvn release:perform -DconnectionUrl=scm:svn:https://svn.apache.org/repos/asf/ctakes/tags/ctakes-3.1.2</code>
+ <code>mvn release:perform -DconnectionUrl=scm:svn:https://svn.apache.org/repos/asf/ctakes/tags/ctakes-3.1.1</code>
  2. [If need to revert] $ mvn release:rollback  (Works if you didn't do a release:clean yet)
  3. log into [apache's nexus area](https://repository.apache.org)
  4. [close the staging respository](https://docs.sonatype.org/display/Repository/Closing+a+Staging+Repository)
@@ -79,44 +79,49 @@ Send an email like the following to dev@
 with the subject line:  [VOTE] Release Apache cTAKES <version> 
 
 <pre>
+
 Hi,
-This is a call for a vote on releasing the following candidate as Apache cTAKES 3.1.0. This
will be our first release as a TLP.
+
+This is a call for a vote on releasing the following candidate as Apache cTAKES 3.1.1.
 
 For more detailed information on the changes/release notes, please visit:
-https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313621&version=12322969
+https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313621&version=UPDATE_VERSION_ID_HERE
 
 The release was made using the cTAKES release process documented here: http://ctakes.apache.org/ctakes-release-guide.html
 
 The candidate is available at:
-https://dist.apache.org/repos/dist/dev/ctakes/ctakes-3.1.0/apache-ctakes-3.1.0-src.tar.gz
/.zip
+https://dist.apache.org/repos/dist/dev/ctakes/ctakes-3.1.1/apache-ctakes-3.1.1-src.tar.gz
/.zip
 
-The binary is:
-https://dist.apache.org/repos/dist/dev/ctakes/ctakes-3.1.0/apache-ctakes-3.1.0-bin.tar.gz
/.zip
 
 The tag to be voted on:
-http://svn.apache.org/repos/asf/ctakes/tags/ctakes-3.1.0-rc7/
+http://svn.apache.org/repos/asf/ctakes/tags/ctakes-3.1.1/
 
 The MD5 checksum of the tarball can be found at:
-https://dist.apache.org/repos/dist/dev/ctakes/ctakes-3.1.0/apache-ctakes-3.1.0-src.tar.gz.md5
/.zip.md5
+https://dist.apache.org/repos/dist/dev/ctakes/ctakes-3.1.1/apache-ctakes-3.1.1-src.tar.gz.md5
/.zip.md5
 
 The signature of the tarball can be found at:
-https://dist.apache.org/repos/dist/dev/ctakes/ctakes-3.1.0/apache-ctakes-3.1.0-src.tar.gz.asc
/.zip.asc
+https://dist.apache.org/repos/dist/dev/ctakes/ctakes-3.1.1/apache-ctakes-3.1.1-src.tar.gz.asc
/.zip.asc
 
 Apache cTAKES' KEYS file, containing the PGP keys used to sign the release:
 https://dist.apache.org/repos/dist/dev/ctakes/KEYS
 
-Please vote on releasing these packages as Apache cTAKES 3.1.0. The vote is open for at least
the next 72 hours.
+Please vote on releasing these packages as Apache cTAKES 3.1.1. The vote is open for at least
the next 72 hours.
 Only votes from the cTAKES PMC are binding, but folks are welcome to check the release candidate
and voice their approval or disapproval. The vote passes if at least three binding +1 votes
are cast.
 
-[ ] +1 Release the packages as Apache cTAKES 3.1.0 
+[ ] +1 Release the packages as Apache cTAKES 3.1.1 
 [ ] -1 Do not release the packages because...
+
+Also note that the convenience binary is:
+https://dist.apache.org/repos/dist/dev/ctakes/ctakes-3.1.1/apache-ctakes-3.1.1-bin.tar.gz
/.zip
+
 Thanks!
-Pei
+(name here)
+
 P.S. Here is my +1.
-</pre>
 
-If VOTE passes with 3+ cTAKES PMC votes, move onto next step. If VOTE does not pass, repeat
steps 3-on until it does
+</pre>
 
+If VOTE passes with 3+ cTAKES PMC votes and majority approval, move onto next step. (See
http://www.apache.org/foundation/voting.html#ReleaseVotes) If VOTE does not pass, repeat steps
3-on until it does
 
 ### Publishing Artifacts to dist
 Move the artifacts from Dev to Dist
@@ -164,4 +169,4 @@ Once release hits send announcement emai
   [2]: https://docs.sonatype.org/display/Repository/How+To+Generate+PGP+Signatures+With+Maven
 
 ### Post-announce
-After announce, if the release included a new component, it's a good idea to check the [list
of cTAKES components within JIRA](https://issues.apache.org/jira/browse/ctakes#selectedTab=com.atlassian.jira.plugin.system.project%3Acomponents-panel)
to verify new component(s) were added there, so users can report issues to the appropriate
component.
\ No newline at end of file
+After announce, if the release included a new component, it's a good idea to check the [list
of cTAKES components within JIRA](https://issues.apache.org/jira/browse/ctakes#selectedTab=com.atlassian.jira.plugin.system.project%3Acomponents-panel)
to verify new component(s) were added there, so users can report issues to the appropriate
component.



Mime
View raw message