commons-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From pste...@apache.org
Subject svn commit: r930759 - in /commons/proper/commons-site/trunk/src/site/xdoc/releases: prepare.xml release.xml
Date Sun, 04 Apr 2010 22:16:27 GMT
Author: psteitz
Date: Sun Apr  4 22:16:27 2010
New Revision: 930759

URL: http://svn.apache.org/viewvc?rev=930759&view=rev
Log:
Added reminder to make sure reviewers check sigs; fixed some errors.

Modified:
    commons/proper/commons-site/trunk/src/site/xdoc/releases/prepare.xml
    commons/proper/commons-site/trunk/src/site/xdoc/releases/release.xml

Modified: commons/proper/commons-site/trunk/src/site/xdoc/releases/prepare.xml
URL: http://svn.apache.org/viewvc/commons/proper/commons-site/trunk/src/site/xdoc/releases/prepare.xml?rev=930759&r1=930758&r2=930759&view=diff
==============================================================================
--- commons/proper/commons-site/trunk/src/site/xdoc/releases/prepare.xml (original)
+++ commons/proper/commons-site/trunk/src/site/xdoc/releases/prepare.xml Sun Apr  4 22:16:27
2010
@@ -227,7 +227,7 @@
     for the maven-changes-plugin in the pom:
     <pre>
     &lt;template>foo-release-notes.vm&lt;/template&lt;
-    &lt;templateDirectory&lt;templates&lt;/templateDirectory&gt; </pre>
</p>
+    &lt;templateDirectory&lt;templates&gt;/templateDirectory&gt; </pre>
</p>
     <p>
     and the Velocity template, <code>foo-release-notes.vm</code> needs to be
defined in
     <code>src/main/resources/templates.</code></p>
@@ -370,14 +370,14 @@
         </pre>
         <p>
         The NOTICE.txt must be distributed along with the LICENSE.txt.
-        Check that the distribution build correct adds this file
-        to the distributions.
+        Check that the distribution build correctly adds this file
+        to the distributions and that the copyright start and end dates are correct.
         </p>
     </subsection>
     <subsection name='Create the Release Candidate'>
         <p>
         Once all the preparations agreed in the release plan has been completed, create a
Release Candidate. 
-        Before taking the tag from which the release candidate will be taken, run the distribution
build
+        Before creating the tag from which the release candidate will be generated, run the
distribution build
         and double check that everything is still fine.
         </p>
         <p>
@@ -391,8 +391,8 @@
 		</p>
 	<pre>
 	  svn update trunk
-	  svn cp trunk tags/foo-1.2-rc1
-	  svn commit -m "Tagging foo-1.2 RC1" tags/foo-1.2-rc1 </pre>
+	  svn cp trunk tags/FOO_1_2_RC1
+	  svn commit -m "Tagging foo-1.2 RC1" tags/FOO_1_2_RC1 </pre>
         <p>
         Note that the "svn update" step is necessary in order to ensure that the directory
being
         copied does not have a mix of files at various revisions; even if the files haven't
changed
@@ -434,7 +434,6 @@
   release_path=~/foo-release </pre>
   <pre>
   # Generate the release artifacts and install them locally
-  mvn assembly:assembly
   mvn -Prc -DcreateChecksum=true install
   #
   # Copy the zips/tarballs and release notes to release directory
@@ -452,9 +451,8 @@
   # Copy maven artifacts
   cp -R ${repo_path} ${release_path}
   #
-  # Rename maven, site directories
+  # Rename maven directory
   mv ${release_path}/${version} ${release_path}/maven
-  mv ${release_path}/site ${release_path}/docs
   #
   # Delete tars/zips from maven subdirectory
   rm ${release_path}/maven/*.zip
@@ -488,7 +486,7 @@
     http://people.apache.org/~luckyrm/foo-1.2-RC1/
 
   Maven artifacts are here:
-    http://people.apache.org/~niallp/beanutils-1.8.3-rc1/m2/commons-beanutils/
+    http://people.apache.org/~luckyrm/foo-1.2-RC1/maven
 
   Details of changes since 1.1 are in the release notes:
     http://people.apache.org/~luckyrm/foo-1.2-RC1/RELEASE-NOTES.txt
@@ -552,10 +550,15 @@
         Note that binding the VOTEs recorded need to be clearly designated in the RESULT.
         This may be done by either stating only the binding votes (and indicating that to
be the case)
         or by adding <code>(non-binding)</code> to those which are not.
-        It is best practice to indicate how each person. 
+        It is best practice to indicate how each person voted. 
         This allows any mistakes to be caught and corrected early.
         If you do vote, please check the results to ensure that your vote has been correctly
tallied.
         </p>
+    <p>
+    During the course of the VOTE, make sure that one or more of the reviewers have verified
the signatures
+    and hash files included with the release artifacts.  If no one specifically mentions
having done that during
+    the VOTE, ask on the dev list and make sure someone does this before you proceed with
the release.
+    </p>
     </subsection>
   </section>
 

Modified: commons/proper/commons-site/trunk/src/site/xdoc/releases/release.xml
URL: http://svn.apache.org/viewvc/commons/proper/commons-site/trunk/src/site/xdoc/releases/release.xml?rev=930759&r1=930758&r2=930759&view=diff
==============================================================================
--- commons/proper/commons-site/trunk/src/site/xdoc/releases/release.xml (original)
+++ commons/proper/commons-site/trunk/src/site/xdoc/releases/release.xml Sun Apr  4 22:16:27
2010
@@ -37,19 +37,11 @@
     </p>
     <p>
     In particular, it is assumed:
-    <!-- TODO: make sure prepare.xml ensures the following are true -->
     <ul>
       <li>
-        The signed release candidate source and binary distributions are available in ~/public_html/commons-foo-1.2-RC3.
+        The signed release candidate source and binary distributions and release notes are
available
+        in ~/public_html/commons-foo-1.2-RC3.
       </li>
-      <!-- Make sure in prepare.xml then delete 
-      <li>
-        At least one reviewer has verified the hashes and signatures associated with the
release artifacts.
-      </li>
-      <li>
-        The release candidate was built from the tag, tags/foo-1.2-RC3.
-      </li>
-      -->
       <li>
         The maven artifacts associated with the release are available in ~/public_html/commons-foo-1.2-RC3/maven.
       </li>



Mime
View raw message