Return-Path: X-Original-To: apmail-ctakes-commits-archive@www.apache.org Delivered-To: apmail-ctakes-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AF59810A41 for ; Tue, 26 Nov 2013 21:41:05 +0000 (UTC) Received: (qmail 97923 invoked by uid 500); 26 Nov 2013 21:41:05 -0000 Delivered-To: apmail-ctakes-commits-archive@ctakes.apache.org Received: (qmail 97898 invoked by uid 500); 26 Nov 2013 21:41:05 -0000 Mailing-List: contact commits-help@ctakes.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ctakes.apache.org Delivered-To: mailing list commits@ctakes.apache.org Received: (qmail 97887 invoked by uid 99); 26 Nov 2013 21:41:05 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Nov 2013 21:41:05 +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; Tue, 26 Nov 2013 21:41:02 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id 85DDE238890B for ; Tue, 26 Nov 2013 21:40:41 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r888199 - in /websites/staging/ctakes/trunk: cgi-bin/ content/ content/ctakes-release-guide.html Date: Tue, 26 Nov 2013 21:40:41 -0000 To: commits@ctakes.apache.org From: buildbot@apache.org X-Mailer: svnmailer-1.0.9 Message-Id: <20131126214041.85DDE238890B@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Author: buildbot Date: Tue Nov 26 21:40:41 2013 New Revision: 888199 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:40:41 2013 @@ -1 +1 @@ -1545846 +1545851 Propchange: websites/staging/ctakes/trunk/content/ ------------------------------------------------------------------------------ --- cms:source-revision (original) +++ cms:source-revision Tue Nov 26 21:40:41 2013 @@ -1 +1 @@ -1545846 +1545851 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:40:41 2013 @@ -201,7 +201,8 @@ to https://dist.apache.org/repos/dist/re Once the release hits:

update cTAKES' DOAP file -
Note once you update the DOAP file, it might take overnight for the change to be seen. Refer to http://markmail.org/message/cinxrqjfm3wuxtmb

Note once you update the DOAP file, it might take overnight for the change to be seen. +

@@ -218,10 +219,15 @@ Once the release hits:

Sending Announcement Email

Wait for versions to hit the mirrors (hint: keep checking http://www.apache.org/dyn/closer.cgi/ctakes until you see something). -Once release hits send announcement email to announce@a.o and dev@ctakes and user@ctakes. 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.

Wait for versions to hit the mirrors (hint: keep checking http://www.apache.org/dyn/closer.cgi/ctakes until you see something).

Once release hits send announcement email to announce@a.o and dev@ctakes and user@ctakes. +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. +It's even easier then the instructions there as it will recognize your email address and default to Apache settings.

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 to verify new component(s) were added there, so users can report issues to the appropriate component.

After announce, if the release included a new component, +it's a good idea to check the list of cTAKES components within JIRA +to verify new component(s) were added there, so users can report issues to the appropriate component.