svn commit: r1589215 - /tomee/site/trunk/content/dev/release-tomee.mdtext

[an...@apache.org]

Author: andygumbrecht
Date: Tue Apr 22 17:19:47 2014
New Revision: 1589215

URL: http://svn.apache.org/r1589215
Log:
A better release check list - In progress.

Modified:
    tomee/site/trunk/content/dev/release-tomee.mdtext

Modified: tomee/site/trunk/content/dev/release-tomee.mdtext
URL: http://svn.apache.org/viewvc/tomee/site/trunk/content/dev/release-tomee.mdtext?rev=1589215&r1=1589214&r2=1589215&view=diff
==============================================================================
--- tomee/site/trunk/content/dev/release-tomee.mdtext (original)
+++ tomee/site/trunk/content/dev/release-tomee.mdtext Tue Apr 22 17:19:47 2014
@@ -70,7 +70,7 @@ Ensure your maven .m2/settings.xml corre
 
 ### Build the Release Tools
 
-Checkout the release tools from here [https://svn.apache.org/repos/asf/tomee/sandbox/release-tools]
+Checkout the release tools using SVN from here [https://svn.apache.org/repos/asf/tomee/sandbox/release-tools](https://svn.apache.org/repos/asf/tomee/sandbox/release-tools)
 
 Really read the README.mdtext and follow the instructions for building the 3rd party libraries.
 
@@ -80,12 +80,12 @@ Have a look at **run.sh** to see the ent
 
 Understand that the release tools are not polished, and you currently may have to edit source and re-compile.
 
-## Code Signing Setup
+### Code Signing Setup
 
 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:
 
- - [http://www.apache.org/dev/release-signing.html]
- - [http://maven.apache.org/developers/release/pmc-gpg-keys.html]
+ - [http://www.apache.org/dev/release-signing.html](http://www.apache.org/dev/release-signing.html)
+ - [http://maven.apache.org/developers/release/pmc-gpg-keys.html](http://maven.apache.org/developers/release/pmc-gpg-keys.html)
  
 However, the basic steps are:
 
@@ -95,7 +95,7 @@ However, the basic steps are:
 
 Once you have your key then you will need to append it to the key file here:
 
- - [http://www.apache.org/dist/openejb/KEYS]
+ - [http://www.apache.org/dist/openejb/KEYS](http://www.apache.org/dist/openejb/KEYS)
 
 That is best done as the file itself explains one you view it in a UTF-8 safe text editor.
 
@@ -105,12 +105,10 @@ That is best done as the file itself exp
  - Log in to people.apache.org
  - Make a backup of the remote KEYS file just in case
  - Overwrite the old /dist/openejb/KEYS file with your new one that now also contains your key.
- - Go to [http://pgp.mit.edu/] and add your ascii armoured key
+ - Go to [http://pgp.mit.edu/](http://pgp.mit.edu/) and add your ascii armoured key
  - Take note of your key fingerprint using **gpg --fingerprint <your name>**
- - Go to [https://id.apache.org], log in and fill OpenPGP Public Key Primary Fingerprint: with the value of your fingerprint.
+ - Go to [https://id.apache.org](https://id.apache.org), log in and fill OpenPGP Public Key Primary Fingerprint: with the value of your fingerprint.
  
+### Begin The Release Process
 
-
-
-
-follow steps in task
\ No newline at end of file
+Follow the steps in tasks - In progress...
\ No newline at end of file