Author: sebawagner
Date: Wed Aug 1 09:53:33 2012
New Revision: 1367901
URL: http://svn.apache.org/viewvc?rev=1367901&view=rev
Log:
Update release guide
Modified:
incubator/openmeetings/trunk/singlewebapp/docs/ReleaseGuide.html
incubator/openmeetings/trunk/singlewebapp/xdocs/ReleaseGuide.xml
Modified: incubator/openmeetings/trunk/singlewebapp/docs/ReleaseGuide.html
URL:
http://svn.apache.org/viewvc/incubator/openmeetings/trunk/singlewebapp/docs/ReleaseGuide.html?rev=1367901&r1=1367900&r2=1367901&view=diff
==============================================================================
--- incubator/openmeetings/trunk/singlewebapp/docs/ReleaseGuide.html (original)
+++ incubator/openmeetings/trunk/singlewebapp/docs/ReleaseGuide.html Wed Aug 1
09:53:33 2012
@@ -623,129 +623,195 @@ limitations under the License.
</td></tr>
<tr><td>
<blockquote>
+ <table border="0" cellspacing="0"
cellpadding="0" width="100%">
+ <tr><td bgcolor="#EFEFEF">
+ <font color="#000000" face="arial,helvetica,sanserif">
+ <a name="Required tools"><strong>Required tools</strong></a>
+ </font>
+ </td></tr>
+ <tr><td>
+ <blockquote>
<div>
- <p>To build a binary release of OpenMeetings
you need: </p>
- <ul>
- <li>Sun JDK6</li>
- <li>Apache ANT (minimum) 1.8.3</li>
- <li>
- SVN Command line client
(Subversion 1.7 required!)
- <a
href="http://subversion.apache.org/packages.html"; target="_BLANK"
rel="nofollow">http://subversion.apache.org/packages.html</a>
- </li>
- <li>A text editor</li>
- <li>You need to be online! The build
process actively downloads
- needed libraries and
dependencies.
- </li>
- </ul>
- </div>
- <p>
- Check that all files:
- <br />
- LICENSE, NOTICE, DISCLAIMER, CHANGELOG, README
- <br />
- are up to date and refer to the right version.
- </p>
+ <p>To build a binary release of
OpenMeetings you need: </p>
+ <ul>
+ <li>Sun JDK6</li>
+ <li>Apache ANT (minimum)
1.8.3</li>
+ <li>
+ SVN Command line client
(Subversion 1.7 required!)
+ <a
href="http://subversion.apache.org/packages.html"; target="_BLANK"
rel="nofollow">http://subversion.apache.org/packages.html</a>
+ </li>
+ <li>A text editor</li>
+ <li>You need to be online! The
build process actively downloads
+ needed libraries and
dependencies.
+ </li>
+ </ul>
+ </div>
+ </blockquote>
+ </td></tr>
+ <tr><td><br/></td></tr>
+ </table>
+ <table border="0"
cellspacing="0" cellpadding="0" width="100%">
+ <tr><td bgcolor="#EFEFEF">
+ <font color="#000000" face="arial,helvetica,sanserif">
+ <a name="Step1 - Prepare files"><strong>Step1 - Prepare
files</strong></a>
+ </font>
+ </td></tr>
+ <tr><td>
+ <blockquote>
+ <p>
+ Check that all files:
+ <br />
+ LICENSE, NOTICE, DISCLAIMER, CHANGELOG,
README
+ <br />
+ are up to date and refer to the right
version.
+ </p>
<p>
- Create a TAG of the SVN tree that you would
like to release
- </p>
+ Create a TAG of the SVN tree that you
would like to release
+ </p>
<p>Get the source from your
TAG: </p>
<div class="xmlcode">
- svn checkout
-
https://svn.apache.org/repos/asf/incubator/openmeetings/$TREE/$BRANCHORTAG/
- <br />
- $TREE and $BRANCHORTAG should be replaced with
your new TAG
- </div>
+ svn checkout
+
https://svn.apache.org/repos/asf/incubator/openmeetings/$TREE/$BRANCHORTAG/
+ <br />
+ $TREE and $BRANCHORTAG should be
replaced with your new TAG
+ </div>
<p>Edit the file
build.properties</p>
<div class="xmlcode">
- project.status=SNAPSHOT
- </div>
+ project.status=SNAPSHOT
+ </div>
<p>to</p>
<div class="xmlcode">
- project.status=RELEASE
- </div>
+ project.status=RELEASE
+ </div>
<p>Run the command: </p>
<div class="xmlcode">
- ant dist-release
- </div>
+ ant dist-release
+ </div>
<p>Test building the source on
windows and OSx or Linux</p>
<p>Test running the
binary's</p>
<p>Create MD5 checksums</p>
<div class="xmlcode">
- #On OSX you might use this command to make a
MD5 checksum and store
- it to a file
- <br />
- md5 -r apache-openmeetings-XXX-src.zip >
- apache-openmeetings-XXX-src.zip.md5
- </div>
- <p>
- Create signatures with the your KEY for every
file, the KEY must be
- available at:
- <br />
- <a
href="http://www.apache.org/dist/incubator/openmeetings/KEYS";>http://www.apache.org/dist/incubator/openmeetings/KEYS</a>
- </p>
+ #On OSX you might use this command to
make a MD5 checksum and store
+ it to a file
+ <br />
+ md5 -r apache-openmeetings-XXX-src.zip
>
+ apache-openmeetings-XXX-src.zip.md5
+ </div>
+ <p>
+ Create signatures with the your KEY for
every file, the KEY must be
+ available at:
+ <br />
+ <a
href="http://www.apache.org/dist/incubator/openmeetings/KEYS";>http://www.apache.org/dist/incubator/openmeetings/KEYS
+ </a>
+ </p>
<p>Upload the build artefacts
to your public_html in your home
- directory at people.apache.org
- </p>
+ directory at people.apache.org
+ </p>
<div class="xmlcode">
- #On OSX you might use this command to upload
the file
- <br />
- scp apache-openmeetings-XXXX.zip
- [email protected]:~/public_html/
- </div>
- <p>
- Send a "VOTE" to the developer mailing list
including links to
- release artefacts.
- <br />
- A VOTE always contains two parts:
- <br />
- Send an email to the developer mailing list
with the subject line:
- <br />
- [VOTE] Apache OpenMeetings x.xx Incubating
release
- <br />
- An example for such an email:
- <a
href="http://mail-archives.apache.org/mod_mbox/incubator-openmeetings-dev/201207.mbox/%3CCACeMiA9dXXMnxA3EhJVPGhpvO4z2cLNqHVP7uOhSHT8e_vHoFQ%40mail.gmail.com%3E";>example
Vote email</a>
- <br />
- Forward (Not CC) this Vote email to:
[email protected]
- <br />
- After the vote is over, send a "RESULT" email
to the list with the subject
- line:
- <br />
- [RESULT][VOTE] Apache OpenMeetings x.xx
Incubating release
- <br />
- An example for such an email:
- <a
href="http://mail-archives.apache.org/mod_mbox/incubator-openmeetings-dev/201207.mbox/%3CCACeMiA-ibo6fGCbnLjJX9H5H2kFGDVJRMfxPyMtzWzCWNi%2BpOg%40mail.gmail.com%3E";>example
Result email</a>
- <br />
- Forward (Not CC) this RESULT VOTE email to:
- [email protected]
- <br />
- <br />
- After the Vote was successful on the Developer
mailing list,
- you need
- organize a vote on the general list:
[email protected]
- <br />
- The vote on the general list has the same
process, first a VOTE
- email, then a RESULT" email.
- <br />
- You need at least 3 IPMC votes for the release.
You can summarize
- the IPMC votes from both votes (dev + general).
- </p>
- <p>If VOTEs positive: Upload
the release </p>
- <div class="xmlcode">
- The distribution upload location
(www.apache.org/dist)
- for all
- Apache projects is the /www/www.apache.org/dist
directory on
- people.apache.org. Each project (including the
Incubator) owns a
- directory within dist.
- </div>
- <p>
- Wait 24 hours (until all Apache mirrors have
synced the packages)
- and send an announcement to the mailing list +
blog and any other
- channel.
- </p>
- <p>
- Email announcements should have the subject
line:<br />
- [ANNOUNCE] Apache OpenMeetings x.xx
[Incubating] released
- </p>
+ #On OSX you might use this command to
upload the file
+ <br />
+ scp apache-openmeetings-XXXX.zip
+
[email protected]:~/public_html/
+ </div>
+ </blockquote>
+ </td></tr>
+ <tr><td><br/></td></tr>
+ </table>
+ <table border="0"
cellspacing="0" cellpadding="0" width="100%">
+ <tr><td bgcolor="#EFEFEF">
+ <font color="#000000" face="arial,helvetica,sanserif">
+ <a name="Step2 - VOTE and RESULT emails"><strong>Step2 - VOTE and
RESULT emails</strong></a>
+ </font>
+ </td></tr>
+ <tr><td>
+ <blockquote>
+ <p>
+ Send a "VOTE" to the developer mailing
list including links to
+ release artefacts.
+ <br />
+ A VOTE always contains two parts:
+ <br />
+ Send an email to the developer mailing
list with the subject line:
+ <br />
+ [VOTE] Apache OpenMeetings x.xx
Incubating release
+ <br />
+ An example for such an email:
+ <a
href="http://mail-archives.apache.org/mod_mbox/incubator-openmeetings-dev/201207.mbox/%3CCACeMiA9dXXMnxA3EhJVPGhpvO4z2cLNqHVP7uOhSHT8e_vHoFQ%40mail.gmail.com%3E";>example
Vote email</a>
+ <br />
+ Forward (Not CC) this Vote email to:
[email protected]
+ <br />
+ <br />
+ After the vote is over, send a "RESULT"
email to the list with the
+ subject line:
+ <br />
+ [RESULT][VOTE] Apache OpenMeetings x.xx
Incubating release
+ <br />
+ An example for such an email:
+ <a
href="http://mail-archives.apache.org/mod_mbox/incubator-openmeetings-dev/201207.mbox/%3CCACeMiA-ibo6fGCbnLjJX9H5H2kFGDVJRMfxPyMtzWzCWNi%2BpOg%40mail.gmail.com%3E";>example
Result email</a>
+ <br />
+ Forward (Not CC) this RESULT VOTE email
to:
+ [email protected]
+ <br />
+ <br />
+ After the Vote was successful on the
Developer mailing list,
+ you need organize a vote on the general
list:
+ [email protected]
+ <br />
+ The vote on the general list has the
same process, first a VOTE
+ email, then a RESULT email.
+ <br />
+ You need at least 3 IPMC votes for the
release. You can summarize
+ the IPMC votes from both votes (dev +
general).
+ </p>
+ </blockquote>
+ </td></tr>
+ <tr><td><br/></td></tr>
+ </table>
+ <table border="0"
cellspacing="0" cellpadding="0" width="100%">
+ <tr><td bgcolor="#EFEFEF">
+ <font color="#000000" face="arial,helvetica,sanserif">
+ <a name="Step3 - Distribute and announce"><strong>Step3 - Distribute
and announce</strong></a>
+ </font>
+ </td></tr>
+ <tr><td>
+ <blockquote>
+ <p>If VOTEs positive: Upload the release
</p>
+ <div class="xmlcode">
+ The distribution upload location
(www.apache.org/dist)
+ for all Apache projects is the
/www/www.apache.org/dist directory on
+ people.apache.org. Each project
(including the Incubator) owns a
+ directory within dist.
+ </div>
+ <p>
+ Our distribution directory is:
+ <br />
+
/www/www.apache.org/dist/incubator/openmeetings
+ <br />
+ each version should have a subfolder
within this directory matching the name of the release:
+ <br />
+ for example 2.0-incubating
+ </p>
+ <p>
+ Wait 24 hours (until all Apache mirrors
have synced the packages)
+ and send an announcement to the mailing
list + blog and any other
+ channel.
+ </p>
+ <p>
+ Email announcements should have the
subject line:
+ <br />
+ [ANNOUNCE] Apache OpenMeetings x.xx
[Incubating] released
+ </p>
+ <p>
+ Add a section to <a
href="downloads.html">downloads</a> website.
+ <br />
+ Make sure that the binary packages are
linked using the mirror URL as base path (<b>not</b> www.apache.org/dist):
+ <br />
+ Mirror URL: <a
href="http://www.apache.org/dyn/closer.cgi/incubator/openmeetings/";>http://www.apache.org/dyn/closer.cgi/incubator/openmeetings/</a>
+ </p>
+ </blockquote>
+ </td></tr>
+ <tr><td><br/></td></tr>
+ </table>
</blockquote>
</td></tr>
<tr><td><br/></td></tr>
Modified: incubator/openmeetings/trunk/singlewebapp/xdocs/ReleaseGuide.xml
URL:
http://svn.apache.org/viewvc/incubator/openmeetings/trunk/singlewebapp/xdocs/ReleaseGuide.xml?rev=1367901&r1=1367900&r2=1367901&view=diff
==============================================================================
--- incubator/openmeetings/trunk/singlewebapp/xdocs/ReleaseGuide.xml (original)
+++ incubator/openmeetings/trunk/singlewebapp/xdocs/ReleaseGuide.xml Wed Aug 1
09:53:33 2012
@@ -19,136 +19,167 @@
<section name="How to Build a Release of OpenMeetings">
- <div>
- <p>To build a binary release of OpenMeetings
you need: </p>
- <ul>
- <li>Sun JDK6</li>
- <li>Apache ANT (minimum) 1.8.3</li>
- <li>
- SVN Command line client
(Subversion 1.7 required!)
- <a
href="http://subversion.apache.org/packages.html"; target="_BLANK"
-
rel="nofollow">http://subversion.apache.org/packages.html</a>
- </li>
- <li>A text editor</li>
- <li>You need to be online! The build
process actively downloads
- needed libraries and
dependencies.
- </li>
- </ul>
- </div>
-
- <p>
- Check that all files:
- <br />
- LICENSE, NOTICE, DISCLAIMER, CHANGELOG, README
- <br />
- are up to date and refer to the right version.
- </p>
-
- <p>
- Create a TAG of the SVN tree that you would
like to release
- </p>
-
- <p>Get the source from your TAG: </p>
- <div class="xmlcode">
- svn checkout
-
https://svn.apache.org/repos/asf/incubator/openmeetings/$TREE/$BRANCHORTAG/
- <br />
- $TREE and $BRANCHORTAG should be replaced with
your new TAG
- </div>
-
- <p>Edit the file build.properties</p>
- <div class="xmlcode">
- project.status=SNAPSHOT
- </div>
- <p>to</p>
- <div class="xmlcode">
- project.status=RELEASE
- </div>
- <p>Run the command: </p>
- <div class="xmlcode">
- ant dist-release
- </div>
- <p>Test building the source on windows and OSx or
Linux</p>
- <p>Test running the binary's</p>
- <p>Create MD5 checksums</p>
- <div class="xmlcode">
- #On OSX you might use this command to make a
MD5 checksum and store
- it to a file
- <br />
- md5 -r apache-openmeetings-XXX-src.zip >
- apache-openmeetings-XXX-src.zip.md5
- </div>
- <p>
- Create signatures with the your KEY for every
file, the KEY must be
- available at:
- <br />
- <a
href="http://www.apache.org/dist/incubator/openmeetings/KEYS";>http://www.apache.org/dist/incubator/openmeetings/KEYS</a>
- </p>
- <p>Upload the build artefacts to your public_html in
your home
- directory at people.apache.org
- </p>
- <div class="xmlcode">
- #On OSX you might use this command to upload
the file
- <br />
- scp apache-openmeetings-XXXX.zip
- [email protected]:~/public_html/
- </div>
- <p>
- Send a "VOTE" to the developer mailing list
including links to
- release artefacts.
- <br />
- A VOTE always contains two parts:
- <br />
- Send an email to the developer mailing list
with the subject line:
- <br />
- [VOTE] Apache OpenMeetings x.xx Incubating
release
- <br />
- An example for such an email:
- <a
-
href="http://mail-archives.apache.org/mod_mbox/incubator-openmeetings-dev/201207.mbox/%3CCACeMiA9dXXMnxA3EhJVPGhpvO4z2cLNqHVP7uOhSHT8e_vHoFQ%40mail.gmail.com%3E";>example
Vote email</a>
- <br />
- Forward (Not CC) this Vote email to:
[email protected]
- <br />
- After the vote is over, send a "RESULT" email
to the list with the subject
- line:
- <br />
- [RESULT][VOTE] Apache OpenMeetings x.xx
Incubating release
- <br />
- An example for such an email:
- <a
-
href="http://mail-archives.apache.org/mod_mbox/incubator-openmeetings-dev/201207.mbox/%3CCACeMiA-ibo6fGCbnLjJX9H5H2kFGDVJRMfxPyMtzWzCWNi%2BpOg%40mail.gmail.com%3E";>example
Result email</a>
- <br />
- Forward (Not CC) this RESULT VOTE email to:
- [email protected]
- <br />
- <br />
- After the Vote was successful on the Developer
mailing list,
- you need
- organize a vote on the general list:
[email protected]
- <br />
- The vote on the general list has the same
process, first a VOTE
- email, then a RESULT" email.
- <br />
- You need at least 3 IPMC votes for the release.
You can summarize
- the IPMC votes from both votes (dev + general).
- </p>
- <p>If VOTEs positive: Upload the release </p>
- <div class="xmlcode">
- The distribution upload location
(www.apache.org/dist)
- for all
- Apache projects is the /www/www.apache.org/dist
directory on
- people.apache.org. Each project (including the
Incubator) owns a
- directory within dist.
- </div>
- <p>
- Wait 24 hours (until all Apache mirrors have
synced the packages)
- and send an announcement to the mailing list +
blog and any other
- channel.
- </p>
- <p>
- Email announcements should have the subject
line:<br/>
- [ANNOUNCE] Apache OpenMeetings x.xx
[Incubating] released
- </p>
+ <subsection name="Required tools">
+
+ <div>
+ <p>To build a binary release of
OpenMeetings you need: </p>
+ <ul>
+ <li>Sun JDK6</li>
+ <li>Apache ANT (minimum)
1.8.3</li>
+ <li>
+ SVN Command line client
(Subversion 1.7 required!)
+ <a
href="http://subversion.apache.org/packages.html"; target="_BLANK"
+
rel="nofollow">http://subversion.apache.org/packages.html</a>
+ </li>
+ <li>A text editor</li>
+ <li>You need to be online! The
build process actively downloads
+ needed libraries and
dependencies.
+ </li>
+ </ul>
+ </div>
+
+ </subsection>
+
+ <subsection name="Step1 - Prepare files">
+ <p>
+ Check that all files:
+ <br />
+ LICENSE, NOTICE, DISCLAIMER, CHANGELOG,
README
+ <br />
+ are up to date and refer to the right
version.
+ </p>
+
+ <p>
+ Create a TAG of the SVN tree that you
would like to release
+ </p>
+
+ <p>Get the source from your TAG: </p>
+ <div class="xmlcode">
+ svn checkout
+
https://svn.apache.org/repos/asf/incubator/openmeetings/$TREE/$BRANCHORTAG/
+ <br />
+ $TREE and $BRANCHORTAG should be
replaced with your new TAG
+ </div>
+
+ <p>Edit the file build.properties</p>
+ <div class="xmlcode">
+ project.status=SNAPSHOT
+ </div>
+ <p>to</p>
+ <div class="xmlcode">
+ project.status=RELEASE
+ </div>
+ <p>Run the command: </p>
+ <div class="xmlcode">
+ ant dist-release
+ </div>
+ <p>Test building the source on windows and OSx
or Linux</p>
+ <p>Test running the binary's</p>
+ <p>Create MD5 checksums</p>
+ <div class="xmlcode">
+ #On OSX you might use this command to
make a MD5 checksum and store
+ it to a file
+ <br />
+ md5 -r apache-openmeetings-XXX-src.zip >
+ apache-openmeetings-XXX-src.zip.md5
+ </div>
+ <p>
+ Create signatures with the your KEY for
every file, the KEY must be
+ available at:
+ <br />
+ <a
href="http://www.apache.org/dist/incubator/openmeetings/KEYS";>http://www.apache.org/dist/incubator/openmeetings/KEYS
+ </a>
+ </p>
+ <p>Upload the build artefacts to your
public_html in your home
+ directory at people.apache.org
+ </p>
+ <div class="xmlcode">
+ #On OSX you might use this command to
upload the file
+ <br />
+ scp apache-openmeetings-XXXX.zip
+
[email protected]:~/public_html/
+ </div>
+ </subsection>
+
+ <subsection name="Step2 - VOTE and RESULT emails">
+ <p>
+ Send a "VOTE" to the developer mailing
list including links to
+ release artefacts.
+ <br />
+ A VOTE always contains two parts:
+ <br />
+ Send an email to the developer mailing
list with the subject line:
+ <br />
+ [VOTE] Apache OpenMeetings x.xx
Incubating release
+ <br />
+ An example for such an email:
+ <a
+
href="http://mail-archives.apache.org/mod_mbox/incubator-openmeetings-dev/201207.mbox/%3CCACeMiA9dXXMnxA3EhJVPGhpvO4z2cLNqHVP7uOhSHT8e_vHoFQ%40mail.gmail.com%3E";>example
Vote email</a>
+ <br />
+ Forward (Not CC) this Vote email to:
[email protected]
+ <br />
+ <br />
+ After the vote is over, send a "RESULT"
email to the list with the
+ subject line:
+ <br />
+ [RESULT][VOTE] Apache OpenMeetings x.xx
Incubating release
+ <br />
+ An example for such an email:
+ <a
+
href="http://mail-archives.apache.org/mod_mbox/incubator-openmeetings-dev/201207.mbox/%3CCACeMiA-ibo6fGCbnLjJX9H5H2kFGDVJRMfxPyMtzWzCWNi%2BpOg%40mail.gmail.com%3E";>example
Result email</a>
+ <br />
+ Forward (Not CC) this RESULT VOTE email
to:
+ [email protected]
+ <br />
+ <br />
+ After the Vote was successful on the
Developer mailing list,
+ you need organize a vote on the general
list:
+ [email protected]
+ <br />
+ The vote on the general list has the
same process, first a VOTE
+ email, then a RESULT email.
+ <br />
+ You need at least 3 IPMC votes for the
release. You can summarize
+ the IPMC votes from both votes (dev +
general).
+ </p>
+
+ </subsection>
+
+ <subsection name="Step3 - Distribute and announce">
+ <p>If VOTEs positive: Upload the release </p>
+ <div class="xmlcode">
+ The distribution upload location
(www.apache.org/dist)
+ for all Apache projects is the
/www/www.apache.org/dist directory on
+ people.apache.org. Each project
(including the Incubator) owns a
+ directory within dist.
+ </div>
+ <p>
+ Our distribution directory is:
+ <br/>
+
/www/www.apache.org/dist/incubator/openmeetings
+ <br/>
+ each version should have a subfolder
within this directory matching the name of the release:
+ <br/>
+ for example 2.0-incubating
+ </p>
+ <p>
+ Wait 24 hours (until all Apache mirrors
have synced the packages)
+ and send an announcement to the mailing
list + blog and any other
+ channel.
+ </p>
+ <p>
+ Email announcements should have the
subject line:
+ <br />
+ [ANNOUNCE] Apache OpenMeetings x.xx
[Incubating] released
+ </p>
+ <p>
+ Add a section to <a
href="downloads.html">downloads</a> website.
+ <br/>
+ Make sure that the binary packages are
linked using the mirror URL as base path (<b>not</b> www.apache.org/dist):
+ <br/>
+ Mirror URL: <a
href="http://www.apache.org/dyn/closer.cgi/incubator/openmeetings/";>http://www.apache.org/dyn/closer.cgi/incubator/openmeetings/</a>
+ </p>
+ </subsection>
</section>
