Return-Path: X-Original-To: apmail-incubator-ctakes-commits-archive@minotaur.apache.org Delivered-To: apmail-incubator-ctakes-commits-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 736AEE938 for ; Wed, 20 Feb 2013 18:03:04 +0000 (UTC) Received: (qmail 40947 invoked by uid 500); 20 Feb 2013 18:03:04 -0000 Delivered-To: apmail-incubator-ctakes-commits-archive@incubator.apache.org Received: (qmail 40917 invoked by uid 500); 20 Feb 2013 18:03:04 -0000 Mailing-List: contact ctakes-commits-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ctakes-dev@incubator.apache.org Delivered-To: mailing list ctakes-commits@incubator.apache.org Received: (qmail 40909 invoked by uid 99); 20 Feb 2013 18:03:04 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Feb 2013 18:03:04 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Feb 2013 18:03:03 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id 454512388A5E for ; Wed, 20 Feb 2013 18:02:44 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit 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 -0000 To: ctakes-commits@incubator.apache.org From: buildbot@apache.org X-Mailer: svnmailer-1.0.8-patched Message-Id: <20130220180244.454512388A5E@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Author: buildbot Date: Wed Feb 20 18:02:43 2013 New Revision: 851318 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 Wed Feb 20 18:02:43 2013 @@ -1 +1 @@ -1447941 +1448324 Propchange: websites/staging/ctakes/trunk/content/ ------------------------------------------------------------------------------ --- cms:source-revision (original) +++ cms:source-revision Wed Feb 20 18:02:43 2013 @@ -1 +1 @@ -1447941 +1448324 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 2013 @@ -95,7 +95,7 @@ Move any existing open issues to the nex

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.

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.

Preparing your environment

Preparing your Environment

Read: http://www.apache.org/dev/publishing-maven-artifacts.html
Setup your PGP keys: https://docs.sonatype.org/display/Repository/How+To+Generate+PGP+Signatures+With+Maven
[If need to revert] $ mvn release:rollback (Works if you didn't do a release:clean yet)

This will place the artifacts to the ASF Nexus area for staging for voting.

Prepare the RC for a VOTE

Preparing the RC for a VOTE

Send an email like the following with the subject line: [VOTE} Release Apache cTAKES to ctakes-dev@

 Hi,
@@ -145,12 +145,20 @@ Pei
 P.S. Here is my +1.

If VOTE passes with 3+ cTAKES PMC votes, move onto next step. If VOTE does not pass, repeat steps 3-on until it does

Publishing artifacts to dist

Publishing Artifacts to dist

mvn release:perform
commit the artifacts to https://dist.apache.org/repos/dist/release/incubator/ctakes/

Send Announcement Email

Creating Final Tag from RC Tag after VOTE Passes

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"
+

Sending Announcement Email

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.