incubator-ctakes-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r850737 - in /websites/staging/ctakes/trunk: cgi-bin/ content/ content/ctakes/ctakes-release-guide.html
Date Fri, 15 Feb 2013 20:08:42 GMT
Author: buildbot
Date: Fri Feb 15 20:08:41 2013
New Revision: 850737

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/ctakes-release-guide.html

Propchange: websites/staging/ctakes/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Feb 15 20:08:41 2013
@@ -1 +1 @@
-1445887
+1446751

Propchange: websites/staging/ctakes/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Feb 15 20:08:41 2013
@@ -1 +1 @@
-1445887
+1446751

Modified: websites/staging/ctakes/trunk/content/ctakes/ctakes-release-guide.html
==============================================================================
--- websites/staging/ctakes/trunk/content/ctakes/ctakes-release-guide.html (original)
+++ websites/staging/ctakes/trunk/content/ctakes/ctakes-release-guide.html Fri Feb 15 20:08:41
2013
@@ -87,9 +87,14 @@
     <p>We follow the standard ASF release process. 
 One of the committers would volunteer to play the release manager role for a given release.

 A few days will be spent on stabilizing the cTAKES development trunk, improving its documentation
and test coverage. 
-When the code base is in a satisfactory state a tag would be created under https://svn.apache.org/repos/asf/incubator/ctakes/tags.<br
/>
 The maven release plug-in (mvn release:prepare/perform) is recommended for this purpose (See
details below).</p>
-<p>Open JIRA issues will be reviewed and rearranged accordingly. Many of the issues
will get resolved during this process and the remaining few will be accordingly prioritized
and scheduled for a future release. The unit tests and integration tests will be used extensively
during this critical period to keep the development in its most stable form.</p>
+<p>Open JIRA issues will be reviewed and rearranged accordingly. Many of the issues
will get resolved during this process and the remaining few will be accordingly prioritized
and scheduled for a future release. The unit tests and integration tests will be used extensively
during this critical period to keep the development in its most stable form.
+Move any existing open issues to the next release.</p>
+<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.0.0-incubating).
 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 of 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>
 <ol>
@@ -105,13 +110,50 @@ The maven release plug-in (mvn release:p
 <li>$mvn release:prepare -DdryRun={false} -Dresume={false} -DautoVersionSubmodules=true</li>
 </ol>
 <p>Release: 3.0.0-incubating</p>
-<p>Tag: ctakes-3.0.0-incubating</p>
+<p>Tag: ctakes-3.0.0-incubating-rc1</p>
 <p>Next Dev Release: 3.1.0-incubating-SNAPSHOT</p>
 <ol>
 <li>$mvn release:perform</li>
 <li>[If need to revert] $ mvn release:rollback  (Works if you didn't do a release:clean
yet)</li>
 </ol>
-<p>This will place the artifacts to the ASF Nexus area for staging for voting.</p>
+<p>This will place the artifacts to the ASF Nexus area for staging for voting.</p>
+<h3 id="prepare-the-rc-for-a-vote">Prepare the RC for a VOTE</h3>
+<p>Send an email like the following with the subject line: [VOTE} Release Apache cTAKES
<version> to ctakes-dev@
+<pre>
+Hi,
+This is a call for a vote on releasing the following candidate as Apache cTAKES 3.0.0-incubating.
This will be our first release.</p>
+<p>CTAKES-136 - Remove models and binary from the src and bin dist</p>
+<p>For more detailed information on the changes/release notes, please visit:
+https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313621&amp;version=12322969</p>
+<p>The release was made using the cTAKES release process documented here: http://incubator.apache.org/ctakes/ctakes-release-guide.html</p>
+<p>The candidate is available at:
+http://people.apache.org/~chenpei/ctakes-3.0.0-incubating/rc7/target/apache-ctakes-3.0.0-incubating-src.tar.gz
/.zip</p>
+<p>The binary is:
+http://people.apache.org/~chenpei/ctakes-3.0.0-incubating/rc7/target/apache-ctakes-3.0.0-incubating-bin.tar.gz
/.zip</p>
+<p>The tag to be voted on:
+http://svn.apache.org/repos/asf/incubator/ctakes/tags/ctakes-3.0.0-incubating-rc7/</p>
+<p>The MD5 checksum of the tarball can be found at:
+http://people.apache.org/~chenpei/ctakes-3.0.0-incubating/rc7/target/apache-ctakes-3.0.0-incubating-src.tar.gz.md5
/.zip.md5</p>
+<p>The signature of the tarball can be found at:
+http://people.apache.org/~chenpei/ctakes-3.0.0-incubating/rc7/target/apache-ctakes-3.0.0-incubating-src.tar.gz.asc
/.zip.asc</p>
+<p>Apache cTAKES' KEYS file, containing the PGP keys used to sign the release:
+http://svn.apache.org/repos/asf/incubator/ctakes/tags/ctakes-3.0.0-incubating-rc7/KEYS</p>
+<p>Please vote on releasing these packages as Apache cTAKES 3.0.0-incubating. The vote
is open for at least the next 72 hours.
+Only votes from Incubator 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.</p>
+<p>[ ] +1 Release the packages as Apache cTAKES 3.0.0-incubating [ ] -1 Do not release
the packages because...
+Thanks!
+Pei
+P.S. Here is my +1.
+</pre></p>
+<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>
+<h3 id="publishing-artifacts-to-dist">Publishing artifacts to dist</h3>
+<ol>
+<li>mvn release:perform</li>
+<li>commit the artifacts to https://dist.apache.org/repos/dist/release/incubator/ctakes/<release></li>
+</ol>
+<h3 id="send-announcement-email">Send Announcement Email</h3>
+<p>Wait for versions to hit the mirrors (hint: keep checking http://www.apache.org/dyn/closer.cgi/oodt
until you see something).
+Once release hits send announcement email to announce@a.o and ctakes-dev@ and ctakes-user@.
This needs to be done from your @apache.org email address or the email will bounce from the
announce list. Gmail forwarding can help here and is a snap to set up (http://gmailblog.blogspot.com/2009/07/send-mail-from-another-address-without.html).
It's even easier then the instructions there as it will recognize your email address and default
to Apache settings.</p>
   </div>
  
  <div id="footera">



Mime
View raw message