svn commit: r960015 - in /websites/staging/taverna/trunk: cgi-bin/ content/ content/community/releasing.html

[bu...@apache.org]

Author: buildbot
Date: Wed Jul 29 13:17:38 2015
New Revision: 960015

Log:
Staging update by buildbot for taverna

Modified:
    websites/staging/taverna/trunk/cgi-bin/   (props changed)
    websites/staging/taverna/trunk/content/   (props changed)
    websites/staging/taverna/trunk/content/community/releasing.html

Propchange: websites/staging/taverna/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Jul 29 13:17:38 2015
@@ -1 +1 @@
-1693253
+1693256

Propchange: websites/staging/taverna/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Jul 29 13:17:38 2015
@@ -1 +1 @@
-1693253
+1693256

Modified: websites/staging/taverna/trunk/content/community/releasing.html
==============================================================================
--- websites/staging/taverna/trunk/content/community/releasing.html (original)
+++ websites/staging/taverna/trunk/content/community/releasing.html Wed Jul 29 13:17:38 2015
@@ -493,7 +493,7 @@ verify its <em>Content</em>.</p>
 <p>You can leave the staging repository <em>Open</em> until you have released all the
 projects that will form part of this <em>[VOTE]</em>, e.g. you can deploy both
 <code>taverna-maven-parent</code> and <code>taverna-language</code> using the same staging repository.</p>
-<p>When all artifacts to be deployed are in the staging repository, tick the box
+<p><strong>Important</strong> - When all artifacts to be deployed are in the staging repository, tick the box
 next to it and click <em>Close</em>.</p>
 <p><strong>DO NOT CLICK RELEASE YET</strong> - the release candidate must pass <em>[VOTE]</em> emails
 on both dev@taverna and general@incubator before we release.</p>