openmeetings-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From solo...@apache.org
Subject svn commit: r1453460 - in /openmeetings/trunk/singlewebapp: docs/ReleaseGuide.html xdocs/ReleaseGuide.xml
Date Wed, 06 Mar 2013 18:11:23 GMT
Author: solomax
Date: Wed Mar  6 18:11:22 2013
New Revision: 1453460

URL: http://svn.apache.org/r1453460
Log:
Release: guide is updated

Modified:
    openmeetings/trunk/singlewebapp/docs/ReleaseGuide.html
    openmeetings/trunk/singlewebapp/xdocs/ReleaseGuide.xml

Modified: openmeetings/trunk/singlewebapp/docs/ReleaseGuide.html
URL: http://svn.apache.org/viewvc/openmeetings/trunk/singlewebapp/docs/ReleaseGuide.html?rev=1453460&r1=1453459&r2=1453460&view=diff
==============================================================================
--- openmeetings/trunk/singlewebapp/docs/ReleaseGuide.html (original)
+++ openmeetings/trunk/singlewebapp/docs/ReleaseGuide.html Wed Mar  6 18:11:22 2013
@@ -738,16 +738,20 @@ limitations under the License.
 					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
+					Create a TAG of the SVN tree that you would like to release<br />
+					Example:
+					<div class="xmlcode">
+						svn copy -r1453158 https://svn.apache.org/repos/asf/openmeetings/trunk/singlewebapp
\<br />
+							https://svn.apache.org/repos/asf/openmeetings/tags/2.1RC1 \<br />
+							-m "Release candidate 1"
+					</div>
 				</p>
                                                 <p>Get the source from your TAG: </p>
                                                 <div class="xmlcode">
-					svn checkout
-					https://svn.apache.org/repos/asf/openmeetings/$TREE/$BRANCHORTAG/
-					<br />
-					$TREE and $BRANCHORTAG should be replaced with your new TAG
+					svn checkout https://svn.apache.org/repos/asf/openmeetings/tags/$BRANCHORTAG/<br
/>
+					$BRANCHORTAG should be replaced with your new TAG
 				</div>
-                                                <p>Edit the file build.properties</p>
+                                                <p>Edit the file build.properties change</p>
                                                 <div class="xmlcode">
 					project.status=SNAPSHOT
 				</div>
@@ -763,27 +767,52 @@ limitations under the License.
                                                 <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
+					#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 &gt;apache-openmeetings-XXX-src.zip.md5
+				</div>
+                                                <div class="xmlcode">
+					#To create MD5 hashes On Ubuntu:<br />
+					for f in `ls -1 *.tar.gz *.zip`; do md5sum $f &gt; $f.md5; done<br />
 					<br />
-					md5 -r apache-openmeetings-XXX-src.zip &gt;
-					apache-openmeetings-XXX-src.zip.md5
+					#To check MD5 hashes On Ubuntu:<br />
+					for f in `ls -1 *.tar.gz *.zip`; do md5sum -c $f.md5; done
 				</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
+					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
+					#To create signatures On Ubuntu:<br />
+					for f in `ls -1 *.tar.gz *.zip`; do gpg --armor --output $f.asc --detach-sig $f; done<br
/>
 					<br />
-					scp apache-openmeetings-XXXX.zip
-					sebawagner@people.apache.org:~/public_html/
+					#To check signatures On Ubuntu:<br />
+					for f in `ls -1 *.tar.gz *.zip`; do gpg --verify $f.asc; done
+				</div>
+                                                <p>
+					Commit artifacts you have created with KEYS file to the
+					<tt>https://dist.apache.org/repos/dist/dev/openmeetings/</tt>
+					Proposed file structure for "Release Candidate 1" of 2.1 will be:
+				</p>
+                                                <div class="xmlcode">
+					2.1<br />
+					2.1/rc1<br />
+					2.1/rc1/src<br />
+					2.1/rc1/src/apache-openmeetings-2.1.0-src.zip<br />
+					2.1/rc1/src/apache-openmeetings-2.1.0-src.tar.gz<br />
+					2.1/rc1/src/apache-openmeetings-2.1.0-src.zip.md5<br />
+					2.1/rc1/src/apache-openmeetings-2.1.0-src.zip.asc<br />
+					2.1/rc1/src/apache-openmeetings-2.1.0-src.tar.gz.md5<br />
+					2.1/rc1/src/apache-openmeetings-2.1.0-src.tar.gz.asc<br />
+					2.1/rc1/bin<br />
+					2.1/rc1/bin/apache-openmeetings-2.1.0.zip<br />
+					2.1/rc1/bin/apache-openmeetings-2.1.0.tar.gz<br />
+					2.1/rc1/bin/apache-openmeetings-2.1.0.zip.md5<br />
+					2.1/rc1/bin/apache-openmeetings-2.1.0.zip.asc<br />
+					2.1/rc1/bin/apache-openmeetings-2.1.0.tar.gz.md5<br />
+					2.1/rc1/bin/apache-openmeetings-2.1.0.tar.gz.asc<br />
+					2.1/rc1/KEYS
 				</div>
                             </blockquote>
       </td></tr>
@@ -798,41 +827,25 @@ limitations under the License.
       <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 release
-					<br />
+					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 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: private@incubator.apache.org
-					<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 release
+					Forward (Not CC) this Vote email to: private@openmeetings.apache.org<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 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:
-					private@incubator.apache.org
-					<br />
-					<br />
-					After the Vote was successful on the Developer mailing list,
-					you
-					need organize a vote on the general list:
-					general@incubator.apache.org
-					<br />
-					The vote on the general list has the same process, first a VOTE
-					email, then a RESULT email.
+					Forward (Not CC) this RESULT VOTE email to: private@openmeetings.apache.org<br />
 					<br />
+					After the Vote was successful on the Developer mailing list, you
+					need organize a vote on the general list: general@incubator.apache.org<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>

Modified: openmeetings/trunk/singlewebapp/xdocs/ReleaseGuide.xml
URL: http://svn.apache.org/viewvc/openmeetings/trunk/singlewebapp/xdocs/ReleaseGuide.xml?rev=1453460&r1=1453459&r2=1453460&view=diff
==============================================================================
--- openmeetings/trunk/singlewebapp/xdocs/ReleaseGuide.xml (original)
+++ openmeetings/trunk/singlewebapp/xdocs/ReleaseGuide.xml Wed Mar  6 18:11:22 2013
@@ -118,13 +118,11 @@
 
 				<p>Get the source from your TAG: </p>
 				<div class="xmlcode">
-					svn checkout
-					https://svn.apache.org/repos/asf/openmeetings/tags/$BRANCHORTAG/
-					<br />
+					svn checkout https://svn.apache.org/repos/asf/openmeetings/tags/$BRANCHORTAG/<br
/>
 					$BRANCHORTAG should be replaced with your new TAG
 				</div>
 
-				<p>Edit the file build.properties</p>
+				<p>Edit the file build.properties change</p>
 				<div class="xmlcode">
 					project.status=SNAPSHOT
 				</div>
@@ -140,11 +138,15 @@
 				<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
+					#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>
+				<div class="xmlcode">
+					#To create MD5 hashes On Ubuntu:<br />
+					for f in `ls -1 *.tar.gz *.zip`; do md5sum $f > $f.md5; done<br/>
+					<br/>
+					#To check MD5 hashes On Ubuntu:<br />
+					for f in `ls -1 *.tar.gz *.zip`; do md5sum -c $f.md5; done
 				</div>
 				<p>
 					Create signatures with the your KEY for every file, the KEY must be available at:<br
/>
@@ -152,57 +154,66 @@
 						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 sebawagner@people.apache.org:~/public_html/
+					#To create signatures On Ubuntu:<br />
+					for f in `ls -1 *.tar.gz *.zip`; do gpg --armor --output $f.asc --detach-sig $f; done<br/>
+					<br/>
+					#To check signatures On Ubuntu:<br />
+					for f in `ls -1 *.tar.gz *.zip`; do gpg --verify $f.asc; done
+				</div>
+				
+				<p>
+					Commit artifacts you have created with KEYS file to the
+					<tt>https://dist.apache.org/repos/dist/dev/openmeetings/</tt>
+					Proposed file structure for "Release Candidate 1" of 2.1 will be:
+				</p>
+				<div class="xmlcode">
+					2.1<br />
+					2.1/rc1<br />
+					2.1/rc1/src<br />
+					2.1/rc1/src/apache-openmeetings-2.1.0-src.zip<br />
+					2.1/rc1/src/apache-openmeetings-2.1.0-src.tar.gz<br />
+					2.1/rc1/src/apache-openmeetings-2.1.0-src.zip.md5<br />
+					2.1/rc1/src/apache-openmeetings-2.1.0-src.zip.asc<br />
+					2.1/rc1/src/apache-openmeetings-2.1.0-src.tar.gz.md5<br />
+					2.1/rc1/src/apache-openmeetings-2.1.0-src.tar.gz.asc<br />
+					2.1/rc1/bin<br />
+					2.1/rc1/bin/apache-openmeetings-2.1.0.zip<br />
+					2.1/rc1/bin/apache-openmeetings-2.1.0.tar.gz<br />
+					2.1/rc1/bin/apache-openmeetings-2.1.0.zip.md5<br />
+					2.1/rc1/bin/apache-openmeetings-2.1.0.zip.asc<br />
+					2.1/rc1/bin/apache-openmeetings-2.1.0.tar.gz.md5<br />
+					2.1/rc1/bin/apache-openmeetings-2.1.0.tar.gz.asc<br />
+					2.1/rc1/KEYS
 				</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 release
-					<br />
+					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 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: private@incubator.apache.org
-					<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 release
+					Forward (Not CC) this Vote email to: private@openmeetings.apache.org<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 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:
-					private@incubator.apache.org
-					<br />
-					<br />
-					After the Vote was successful on the Developer mailing list,
-					you
-					need organize a vote on the general list:
-					general@incubator.apache.org
-					<br />
-					The vote on the general list has the same process, first a VOTE
-					email, then a RESULT email.
+					Forward (Not CC) this RESULT VOTE email to: private@openmeetings.apache.org<br />
 					<br />
+					After the Vote was successful on the Developer mailing list, you
+					need organize a vote on the general list: general@incubator.apache.org<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">



Mime
View raw message