Mailing-List: contact commits-help@ctakes.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ctakes.apache.org
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: svn commit: r1524353 -
 /ctakes/site/trunk/content/ctakes-release-guide.mdtext
Date: Wed, 18 Sep 2013 09:51:33 -0000
To: commits@ctakes.apache.org
From: james-masanz@apache.org
Message-Id: <20130918095133.A65062388900@eris.apache.org>

Author: james-masanz
Date: Wed Sep 18 09:51:33 2013
New Revision: 1524353

URL: http://svn.apache.org/r1524353
Log:
CMS commit to ctakes by james-masanz

Modified:
    ctakes/site/trunk/content/ctakes-release-guide.mdtext

Modified: ctakes/site/trunk/content/ctakes-release-guide.mdtext
URL: http://svn.apache.org/viewvc/ctakes/site/trunk/content/ctakes-release-guide.mdtext?rev=1524353&r1=1524352&r2=1524353&view=diff
==============================================================================
--- ctakes/site/trunk/content/ctakes-release-guide.mdtext (original)
+++ ctakes/site/trunk/content/ctakes-release-guide.mdtext Wed Sep 18 09:51:33 2013
@@ -121,8 +121,20 @@ For example, if the VOTE for RCX passes 
    -m "Copying tag of accepted RC for the release to final actual release tag"
 </pre>
 
+### Update documentation
+Wait for versions to hit the mirrors (hint: keep checking http://www.apache.org/dyn/closer.cgi/ctakes until you see something).
+Once the release hits:
+
+ * update the [archive page](http://ctakes.apache.org/roadmap.html) with information about the previous release.
+ * update any site or Wiki pages that mention the "latest release" or "current release".
+ * verify the latest install guides are linked where appropriate.
+
 ### 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.
   [1]: http://www.apache.org/dev/publishing-maven-artifacts.html
-  [2]: https://docs.sonatype.org/display/Repository/How+To+Generate+PGP+Signatures+With+Maven
\ No newline at end of file
+  [2]: https://docs.sonatype.org/display/Repository/How+To+Generate+PGP+Signatures+With+Maven
+
+### 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](https://issues.apache.org/jira/browse/ctakes#selectedTab=com.atlassian.jira.plugin.system.project%3Acomponents-panel) to verify new component(s) were added there, so users can report issues to the appropriate component.
+