ctakes-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r851318 - in /websites/staging/ctakes/trunk: cgi-bin/ content/ content/ctakes/ctakes-release-guide.html
Date Wed, 20 Feb 2013 18:02:44 GMT
Author: buildbot
Date: Wed Feb 20 18:02:43 2013
New Revision: 851318

Staging update by buildbot for ctakes

    websites/staging/ctakes/trunk/cgi-bin/   (props changed)
    websites/staging/ctakes/trunk/content/   (props changed)

Propchange: websites/staging/ctakes/trunk/cgi-bin/
--- cms:source-revision (original)
+++ cms:source-revision Wed Feb 20 18:02:43 2013
@@ -1 +1 @@

Propchange: websites/staging/ctakes/trunk/content/
--- cms:source-revision (original)
+++ cms:source-revision Wed Feb 20 18:02:43 2013
@@ -1 +1 @@

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 Wed Feb 20 18:02:43
@@ -95,7 +95,7 @@ Move any existing open issues to the nex
 <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
 <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>
+<h3 id="preparing-your-environment">Preparing your Environment</h3>
 <li>Read: <a href="http://www.apache.org/dev/publishing-maven-artifacts.html">http://www.apache.org/dev/publishing-maven-artifacts.html</a></li>
 <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>
@@ -116,7 +116,7 @@ Move any existing open issues to the nex
 <li>[If need to revert] $ mvn release:rollback  (Works if you didn't do a release:clean
 <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>
+<h3 id="preparing-the-rc-for-a-vote">Preparing 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@
@@ -145,12 +145,20 @@ Pei
 P.S. Here is my +1.
 <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>
+<h3 id="publishing-artifacts-to-dist">Publishing Artifacts to dist</h3>
 <li>mvn release:perform</li>
 <li>commit the artifacts to https://dist.apache.org/repos/dist/release/incubator/ctakes/<release></li>
-<h3 id="send-announcement-email">Send Announcement Email</h3>
+<h3 id="creating-final-tag-from-rc-tag-after-vote-passes">Creating Final Tag from RC
Tag after VOTE Passes</h3>
+<p>For example, if the VOTE for RCX passes for release A.B.C
+ svn copy \
+   https://svn.apache.org/repos/asf/incubator/ctakes/tags/ctakes-A.B.C-incubating-rcX  \
+   https://svn.apache.org/repos/asf/incubator/ctakes/tags/ctakes-A.B.C-incubating      \
+   -m "Copying tag of accepted RC for the release to final actual release tag"
+<h3 id="sending-announcement-email">Sending 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>

View raw message