svn commit: r906533 - in /websites/staging/tomee/trunk: cgi-bin/ content/ content/dev/release-tomee.html

[bu...@apache.org]

Author: buildbot
Date: Tue Apr 22 17:20:02 2014
New Revision: 906533

Log:
Staging update by buildbot for tomee

Modified:
    websites/staging/tomee/trunk/cgi-bin/   (props changed)
    websites/staging/tomee/trunk/content/   (props changed)
    websites/staging/tomee/trunk/content/dev/release-tomee.html

Propchange: websites/staging/tomee/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Apr 22 17:20:02 2014
@@ -1 +1 @@
-1589213
+1589215

Propchange: websites/staging/tomee/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Apr 22 17:20:02 2014
@@ -1 +1 @@
-1589213
+1589215

Modified: websites/staging/tomee/trunk/content/dev/release-tomee.html
==============================================================================
--- websites/staging/tomee/trunk/content/dev/release-tomee.html (original)
+++ websites/staging/tomee/trunk/content/dev/release-tomee.html Tue Apr 22 17:20:02 2014
@@ -208,7 +208,7 @@ svn delete -m "Delete test dir" https://
 
 <h3>Build the Release Tools</h3>
 
-<p>Checkout the release tools from here [https://svn.apache.org/repos/asf/tomee/sandbox/release-tools]</p>
+<p>Checkout the release tools using SVN from here <a href="https://svn.apache.org/repos/asf/tomee/sandbox/release-tools">https://svn.apache.org/repos/asf/tomee/sandbox/release-tools</a></p>
 
 <p>Really read the README.mdtext and follow the instructions for building the 3rd party libraries.</p>
 
@@ -218,13 +218,13 @@ svn delete -m "Delete test dir" https://
 
 <p>Understand that the release tools are not polished, and you currently may have to edit source and re-compile.</p>
 
-<h2>Code Signing Setup</h2>
+<h3>Code Signing Setup</h3>
 
 <p>If this is your first release then you will have to ensure that you have a code signing key prepared on the machine from which you perform the release. The process is quite intense. You can find information here:</p>
 
 <ul>
-<li>[http://www.apache.org/dev/release-signing.html]</li>
-<li>[http://maven.apache.org/developers/release/pmc-gpg-keys.html]</li>
+<li><a href="http://www.apache.org/dev/release-signing.html">http://www.apache.org/dev/release-signing.html</a></li>
+<li><a href="http://maven.apache.org/developers/release/pmc-gpg-keys.html">http://maven.apache.org/developers/release/pmc-gpg-keys.html</a></li>
 </ul>
 
 <p>However, the basic steps are:</p>
@@ -238,7 +238,7 @@ svn delete -m "Delete test dir" https://
 <p>Once you have your key then you will need to append it to the key file here:</p>
 
 <ul>
-<li>[http://www.apache.org/dist/openejb/KEYS]</li>
+<li><a href="http://www.apache.org/dist/openejb/KEYS">http://www.apache.org/dist/openejb/KEYS</a></li>
 </ul>
 
 <p>That is best done as the file itself explains one you view it in a UTF-8 safe text editor.</p>
@@ -250,12 +250,14 @@ svn delete -m "Delete test dir" https://
 <li>Log in to people.apache.org</li>
 <li>Make a backup of the remote KEYS file just in case</li>
 <li>Overwrite the old /dist/openejb/KEYS file with your new one that now also contains your key.</li>
-<li>Go to [http://pgp.mit.edu/] and add your ascii armoured key</li>
+<li>Go to <a href="http://pgp.mit.edu/">http://pgp.mit.edu/</a> and add your ascii armoured key</li>
 <li>Take note of your key fingerprint using <strong>gpg --fingerprint <your name></strong></li>
-<li>Go to [https://id.apache.org], log in and fill OpenPGP Public Key Primary Fingerprint: with the value of your fingerprint.</li>
+<li>Go to <a href="https://id.apache.org">https://id.apache.org</a>, log in and fill OpenPGP Public Key Primary Fingerprint: with the value of your fingerprint.</li>
 </ul>
 
-<p>follow steps in task</p>
+<h3>Begin The Release Process</h3>
+
+<p>Follow the steps in tasks - In progress...</p>