ctakes-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r888197 - in /websites/staging/ctakes/trunk: cgi-bin/ content/ content/ctakes-release-guide.html
Date Tue, 26 Nov 2013 21:28:24 GMT
Author: buildbot
Date: Tue Nov 26 21:28:24 2013
New Revision: 888197

Log:
Staging update by buildbot for ctakes

Modified:
    websites/staging/ctakes/trunk/cgi-bin/   (props changed)
    websites/staging/ctakes/trunk/content/   (props changed)
    websites/staging/ctakes/trunk/content/ctakes-release-guide.html

Propchange: websites/staging/ctakes/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Nov 26 21:28:24 2013
@@ -1 +1 @@
-1545385
+1545846

Propchange: websites/staging/ctakes/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Nov 26 21:28:24 2013
@@ -1 +1 @@
-1545385
+1545846

Modified: websites/staging/ctakes/trunk/content/ctakes-release-guide.html
==============================================================================
--- websites/staging/ctakes/trunk/content/ctakes-release-guide.html (original)
+++ websites/staging/ctakes/trunk/content/ctakes-release-guide.html Tue Nov 26 21:28:24 2013
@@ -92,7 +92,7 @@ Move any existing open issues to the nex
 <ol>
 <li>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.</li>
 <li>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.</li>
-<li>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.</li>
+<li>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.</li>
 </ol>
 <p>Finally the release manager would trigger the release build, sign the generated
artifacts and host them on Apache Nexus &amp; 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.</p>
 <h3 id="preparing-your-environment">Preparing your Environment</h3>
@@ -101,16 +101,16 @@ Move any existing open issues to the nex
 <li>Setup your PGP keys: <a href="https://docs.sonatype.org/display/Repository/How+To+Generate+PGP+Signatures+With+Maven">https://docs.sonatype.org/display/Repository/How+To+Generate+PGP+Signatures+With+Maven</a></li>
 </ol>
 <h3 id="preparing-a-release-using-maven">Preparing a Release using Maven</h3>
-<p>Note: Using 3.1.0 as an example</p>
+<p>Note: Using 3.1.1 as an example</p>
 <p>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.</p>
 <ol>
 <li>$svn co https://svn.apache.org/repos/asf/ctakes/trunk ctakes</li>
 <li>$mvn release:clean</li>
 <li>$mvn release:prepare -DdryRun={false} -Dresume={false} -DautoVersionSubmodules=true</li>
 </ol>
-<p>Release: 3.1.0</p>
-<p>Tag: ctakes-3.1.0-rc1</p>
-<p>Next Dev Release: 3.1.1-SNAPSHOT</p>
+<p>Release: 3.1.1</p>
+<p>Tag: ctakes-3.1.1</p>
+<p>Next Dev Release: 3.1.2-SNAPSHOT</p>
 <h3 id="changes-for-the-release">Changes for the release</h3>
 <p>Update ctakes-distribution/RELEASE_NOTES.html and check in change into trunk or
the branch for the release if using a branch</p>
 <h3 id="performing-the-build-from-the-tag">Performing the build from the tag</h3>
@@ -119,7 +119,7 @@ Move any existing open issues to the nex
 <ol>
 <li>$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></li>
+ <code>mvn release:perform -DconnectionUrl=scm:svn:https://svn.apache.org/repos/asf/ctakes/tags/ctakes-3.1.1</code></li>
 <li>[If need to revert] $ mvn release:rollback  (Works if you didn't do a release:clean
yet)</li>
 <li>log into <a href="https://repository.apache.org">apache's nexus area</a></li>
 <li><a href="https://docs.sonatype.org/display/Repository/Closing+a+Staging+Repository">close
the staging respository</a></li>
@@ -132,43 +132,49 @@ Move any existing open issues to the nex
 <p>Send an email like the following to dev@ctakes.apache.org
 with the subject line:  [VOTE] Release Apache cTAKES <version> </p>
 <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>
 
-<p>If VOTE passes with 3+ cTAKES PMC votes, move onto next step. If VOTE does not pass,
repeat steps 3-on until it does</p>
+<p>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</p>
 <h3 id="publishing-artifacts-to-dist">Publishing Artifacts to dist</h3>
 <p>Move the artifacts from Dev to Dist
 For example:



Mime
View raw message