You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@tomee.apache.org by bu...@apache.org on 2014/04/22 18:51:21 UTC
svn commit: r906527 - in /websites/staging/tomee/trunk: cgi-bin/ content/
content/dev/release-tomee.html
Author: buildbot
Date: Tue Apr 22 16:51:21 2014
New Revision: 906527
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 16:51:21 2014
@@ -1 +1 @@
-1589180
+1589203
Propchange: websites/staging/tomee/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Apr 22 16:51:21 2014
@@ -1 +1 @@
-1589180
+1589203
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 16:51:21 2014
@@ -130,11 +130,14 @@
<h1>Releasing TomEE</h1>
-<pre><code>This document is aimed at guiding a release manager through the general release process.
+<pre><code>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.
</code></pre>
+<h2>Preparation of The Branch</h2>
+
<p>Run <strong>ant -f rat.xml > report.txt</strong> on trunk to ensure all licences are in place.
-* Review the report.txt and update/add missing headers until clean. <em>Tip</em>, search for <strong>Unapproved licenses:</strong>.</p>
+ - Review the report.txt and update/add missing headers until clean.
+ - <em>Tip</em>, search for <strong>Unapproved licenses:</strong> at the beginning the report for a list.</p>
<p>Branch the version to release and ensure it builds and passes all tests.</p>
@@ -142,14 +145,17 @@
<p>Update the TCK branch to point to the version branch.</p>
-<pre><code>\tck-1.?\plus.properties
-\tck-1.?\pom.xml
-\tck-1.?\webprofile-plus.properties
-\tck-1.?\webprofile.properties
+<pre><code>\tckbranch\plus.properties
+\tckbranch\pom.xml
+\tckbranch\webprofile-plus.properties
+\tckbranch\webprofile.properties
</code></pre>
<p>Run <strong>ant -f rat.xml > report.txt</strong> on the branch.
-* Review the report.txt and update/add missing headers until clean. <em>Tip</em>, search for <strong>Unapproved licenses:</strong>.</p>
+ - Review the report.txt and update/add missing headers until clean.
+ - <em>Tip</em>, search for <strong>Unapproved licenses:</strong>.</p>
+
+<h2>Check SVN</h2>
<p>Pre-authenticate svn repositories to ensure your credentials are cached before using any tools.</p>
@@ -161,7 +167,7 @@ svn mkdir -m "Create test dir" https://d
svn delete -m "Delete test dir" https://dist.apache.org/repos/dist/dev/tomee/testdir
</code></pre>
-<p>Ensure you have code signing set up [http://www.apache.org/dev/release-signing.html]</p>
+<h2>Prepare Maven Authentication</h2>
<p>Ensure your maven settings.xml correct, and be aware that the tools currently require a clear text password:</p>
@@ -184,16 +190,18 @@ svn delete -m "Delete test dir" https://
</server>
<profiles>
-<profile>
-...
- <repositories>
- <repository>
- <id>apache.dist.https</id>
- <url>https://dist.apache.org/repos/dist</url>
- </repository>
- </repositories>
+ <profile>
+ ...
+ <repositories>
+ <repository>
+ <id>apache.dist.https</id>
+ <url>https://dist.apache.org/repos/dist</url>
+ </repository>
+ </repositories>
</code></pre>
+<h2>Build the Release Tools</h2>
+
<p>Checkout the release tools from here [https://svn.apache.org/repos/asf/tomee/sandbox/release-tools]</p>
<p>Really read the README.mdtext and follow the instructions for building the 3rd party libraries.</p>
@@ -202,12 +210,38 @@ svn delete -m "Delete test dir" https://
<p>Have a look at <strong>run.sh</strong> to see the entry point.</p>
-<p>Understand that the release tools are not polished, and you currently may have to edit source and compile.</p>
+<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>
-<p>http://www.apache.org/dist/openejb/KEYS
-find / > /dev/null</p>
+<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>
-<p>cat KEYS /home/yourname/public_html/AD3424SD.asc > KEYS2</p>
+<ul>
+<li>[http://www.apache.org/dev/release-signing.html]</li>
+<li>[http://maven.apache.org/developers/release/pmc-gpg-keys.html]</li>
+</ul>
+
+<p>However, the basic steps are:
+ - Create a key using <strong>gpg --gen-key</strong>, using size 4096 and answering the questions that command issues.
+ - During the process you will have to generate random entropy, this is best achieved in another console and issuing the command <strong>find / > /dev/null</strong> and waiting a minute.
+ - List the keys using <strong>gpg --list-keys</strong> and take note of the name</p>
+
+<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>
+</ul>
+
+<p>That is best done as the file itself explains one you view it in a UTF-8 safe text editor.
+ - Save the KEYS file on your local machine and import it using <strong>gpg --import KEYS</strong>
+ - Then create the new KEYS file using <strong>(gpg --list-sigs <your name> && gpg --armor --export <your name>) >> KEYS</strong>
+ - Check that the new KEYS file contains your key.
+ - 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
+ - Take note of your key fingerprint using <strong>gpg --fingerprint <your name></strong>
+ - Go to [https://id.apache.org], log in and fill OpenPGP Public Key Primary Fingerprint: with the value of your fingerprint.</p>
<p>follow steps in task</p>