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:55:00 UTC
svn commit: r906528 - in /websites/staging/tomee/trunk: cgi-bin/ content/
content/dev/release-tomee.html
Author: buildbot
Date: Tue Apr 22 16:55:00 2014
New Revision: 906528
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:55:00 2014
@@ -1 +1 @@
-1589203
+1589205
Propchange: websites/staging/tomee/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Apr 22 16:55:00 2014
@@ -1 +1 @@
-1589203
+1589205
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:55:00 2014
@@ -133,11 +133,14 @@
<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>
+<h3>Preparation of The Branch</h3>
-<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> at the beginning the report for a list.</p>
+<p>Run <strong>ant -f rat.xml > report.txt</strong> on trunk to ensure all licences are in place.</p>
+
+<ul>
+<li>Review the report.txt and update/add missing headers until clean.</li>
+<li><em>Tip</em>, search for <strong>Unapproved licenses:</strong> at the beginning the report for a list.</li>
+</ul>
<p>Branch the version to release and ensure it builds and passes all tests.</p>
@@ -151,11 +154,14 @@
\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>
+<p>Run <strong>ant -f rat.xml > report.txt</strong> on the branch.</p>
+
+<ul>
+<li>Review the report.txt and update/add missing headers until clean.</li>
+<li><em>Tip</em>, search for <strong>Unapproved licenses:</strong>.</li>
+</ul>
-<h2>Check SVN</h2>
+<h3>Check SVN</h3>
<p>Pre-authenticate svn repositories to ensure your credentials are cached before using any tools.</p>
@@ -167,9 +173,9 @@ 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>
-<h2>Prepare Maven Authentication</h2>
+<h3>Prepare Maven Authentication</h3>
-<p>Ensure your maven settings.xml correct, and be aware that the tools currently require a clear text password:</p>
+<p>Ensure your maven .m2/settings.xml correct, and be aware that the tools currently require a clear text password:</p>
<pre><code><server>
<id>apache.snapshots.https</id>
@@ -200,7 +206,7 @@ svn delete -m "Delete test dir" https://
</repositories>
</code></pre>
-<h2>Build the Release Tools</h2>
+<h3>Build the Release Tools</h3>
<p>Checkout the release tools from here [https://svn.apache.org/repos/asf/tomee/sandbox/release-tools]</p>
@@ -221,10 +227,13 @@ svn delete -m "Delete test dir" https://
<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>However, the basic steps are:</p>
+
+<ul>
+<li>Create a key using <strong>gpg --gen-key</strong>, using size 4096 and answering the questions that command issues.</li>
+<li>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.</li>
+<li>List the keys using <strong>gpg --list-keys</strong> and take note of the name</li>
+</ul>
<p>Once you have your key then you will need to append it to the key file here:</p>
@@ -232,16 +241,19 @@ svn delete -m "Delete test dir" https://
<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>That is best done as the file itself explains one you view it in a UTF-8 safe text editor.</p>
+
+<ul>
+<li>Save the KEYS file on your local machine and import it using <strong>gpg --import KEYS</strong></li>
+<li>Then create the new KEYS file using <strong>(gpg --list-sigs <your name> && gpg --armor --export <your name>) >> KEYS</strong></li>
+<li>Check that the new KEYS file contains your key.</li>
+<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>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>
+</ul>
<p>follow steps in task</p>