Author: andygumbrecht
Date: Mon May 12 13:13:47 2014
New Revision: 1593961
URL: http://svn.apache.org/r1593961
Log:
release-tomee.mdtext
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=1593961&r1=1593960&r2=1593961&view=diff
==============================================================================
--- tomee/site/trunk/content/dev/release-tomee.mdtext (original)
+++ tomee/site/trunk/content/dev/release-tomee.mdtext Mon May 12 13:13:47 2014
@@ -1,8 +1,8 @@
-# Releasing TomEE
+#Releasing TomEE
This document is aimed at guiding a release manager through the general
release process. You will need either a Linux, Mac, or failing that a Linux
Virtual on Win.
-### Preparation of The Branch
+###Preparation of The Branch
Run **ant -f rat.xml > report.txt** on trunk to ensure all licences are in
place.
@@ -22,7 +22,7 @@ Basically search for the following line
An SVN trigger must be added afterwards. This can only be done by someone with
admin permissions, such as any PMC chair or an Infra team member.
Just drop an email to *[email protected]*
-### Create a TCK Branch
+###Create a TCK Branch
Branch the TCK using the same version as the release branch from here:
@@ -40,7 +40,7 @@ Run **ant -f rat.xml > report.txt** on t
- Review the report.txt and update/add missing headers until clean.
- *Tip*, search for **Unapproved licenses:**.
-### Check SVN Authentication
+###Check SVN Authentication
Pre-authenticate svn repositories to ensure your credentials are cached before
using any tools.
@@ -51,7 +51,7 @@ Pre-authenticate svn repositories to ens
svn mkdir -m "Create test dir"
https://dist.apache.org/repos/dist/dev/tomee/testdir
svn delete -m "Delete test dir"
https://dist.apache.org/repos/dist/dev/tomee/testdir
-### Prepare Maven Authentication
+###Prepare Maven Authentication
Ensure your maven .m2/settings.xml correct, and be aware that the tools
currently require a clear text password:
@@ -83,7 +83,7 @@ Ensure your maven .m2/settings.xml corre
</repository>
</repositories>
-### 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:
@@ -113,7 +113,7 @@ Just follow the instructions there on ho
- Take note of your key fingerprint using **gpg --fingerprint <your name>**
- 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.
-### Build the Release Tools
+###Build the 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)
@@ -125,7 +125,7 @@ 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.
-### Site Staging
+###Site Staging
For some of the release steps you will need to provide documentation on the
site. Checkout the site here:
@@ -147,7 +147,7 @@ Once you are happy with the staging you
[https://cms.apache.org/tomee/publish](https://cms.apache.org/tomee/publish)
-### Begin The Release Process
+###Begin The Release Process
Ensure TCK is passing all tests, and if so create an SVN tag from the branch.
@@ -195,7 +195,7 @@ Update trunk versions. How you do this i
Create the next version iterations in JIRA.
-### Rolling Out The Preview
+###Rolling Out The Preview
Note: Before running anything below ensure you either have:
@@ -222,7 +222,9 @@ Votes are generally managed and identifi
If the vote fails then discuss, fix and re-roll.
-TCK test vote binaries
+###Voted Binaries
+
+Once the vote has passed then release the binaries on Nexus:
[https://repository.apache.org/index.html#welcome](https://repository.apache.org/index.html#welcome)
###Blog
