syncope-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ilgro...@apache.org
Subject svn commit: r1332265 - /incubator/syncope/site/release-process.html
Date Mon, 30 Apr 2012 15:54:06 GMT
Author: ilgrosso
Date: Mon Apr 30 15:54:06 2012
New Revision: 1332265

URL: http://svn.apache.org/viewvc?rev=1332265&view=rev
Log:
Publishing updated - but still draft - release process page

Modified:
    incubator/syncope/site/release-process.html

Modified: incubator/syncope/site/release-process.html
URL: http://svn.apache.org/viewvc/incubator/syncope/site/release-process.html?rev=1332265&r1=1332264&r2=1332265&view=diff
==============================================================================
--- incubator/syncope/site/release-process.html (original)
+++ incubator/syncope/site/release-process.html Mon Apr 30 15:54:06 2012
@@ -1,6 +1,6 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <!--
- | Generated by Apache Maven Doxia at Apr 26, 2012
+ | Generated by Apache Maven Doxia at Apr 30, 2012
  | Rendered using Apache Maven Fluido Skin 1.2.1
 -->
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
@@ -18,7 +18,7 @@
 
     
       <meta name="author" content="Apache Syncope Documentation Team" />
-    <meta name="Date-Revision-yyyymmdd" content="20120426" />
+    <meta name="Date-Revision-yyyymmdd" content="20120430" />
     <meta http-equiv="Content-Language" content="en" />
     
         </head>
@@ -53,7 +53,7 @@
       
                 
                     
-                  <li id="publishDate" class="pull-right">Last Published: 2012-04-26</li>
<li class="divider pull-right">|</li>
+                  <li id="publishDate" class="pull-right">Last Published: 2012-04-30</li>
<li class="divider pull-right">|</li>
               <li id="projectVersion" class="pull-right">Version: 1.0.0-incubating-SNAPSHOT</li>
             
                                   <li class="divider pull-right">|</li>
@@ -179,6 +179,70 @@ under the License. -->
       <a class="externalLink" href="http://maven.apache.org/developers/release/apache-release.html">http://maven.apache.org/developers/release/apache-release.html</a>.
     </p>
     
+    <div class="section"><h2>Prerequisites<a name="Prerequisites"></a></h2>
+      <div class="section"><h3>GPG<a name="GPG"></a></h3>
+        Install/Configure 
+        <tt>GPG</tt> - The artifacts that are deployed to the ASF central repository
need to
+        be signed. To do this you will need to have a public and private keypair. There is
a very good
+        <a class="externalLink" href="http://www.sonatype.com/people/2010/01/how-to-generate-pgp-signatures-with-maven/">guide</a>
that 
+        will walk you though this.
+      </div>
+
+      <div class="section"><h3>Apache Maven<a name="Apache_Maven"></a></h3>
+        <p>Install Apache Maven 3.0.3 or higher; we strongly
+          encourage our committers to install 
+          <a class="externalLink" href="http://maven.apache.org/download.html">Apache
Maven 3.0.4</a>.
+        </p>
+      
+        <p>As of Maven 2.1.0 you can now encrypt your servers passwords. We highly
recommend that you follow this
+          <a class="externalLink" href="http://maven.apache.org/guides/mini/guide-encryption.html">guide</a>
to set your master password and
+          use it to encrypt your ASF password in the next section.
+        </p>
+      </div>
+
+      <div class="section"><h3>ASF settings<a name="ASF_settings"></a></h3>
+        <p>Using the instructions from the previous step encrypt your Sonatype password
and add the following servers to
+          your 
+          <tt>~/.m2/settings.xml</tt> file. You may already have other servers
in this file. If not just create
+          the file.
+        </p>
+
+        <div class="source"><pre class="prettyprint">&lt;?xml version=&quot;1.0&quot;
encoding=&quot;UTF-8&quot;?&gt;
+&lt;settings&gt;
+  ...
+  &lt;servers&gt;
+    &lt;server&gt;
+      &lt;id&gt;apache.snapshots.https&lt;/id&gt;
+      &lt;username&gt;{put your ASF username here}&lt;/username&gt;
+      &lt;password&gt;{put your encrypted password here}&lt;/password&gt;
+    &lt;/server&gt;
+    &lt;server&gt;
+      &lt;id&gt;apache.releases.https&lt;/id&gt;
+      &lt;username&gt;{put your ASF username here}&lt;/username&gt;
+      &lt;password&gt;{put your encrypted password here}&lt;/password&gt;
+    &lt;/server&gt;
+  &lt;/servers&gt;
+  ...
+  &lt;profiles&gt;
+    &lt;profile&gt;
+      &lt;id&gt;apache&lt;/id&gt;
+      &lt;activation&gt;
+        &lt;activeByDefault&gt;false&lt;/activeByDefault&gt;
+      &lt;/activation&gt;
+      &lt;properties&gt;
+        &lt;mavenExecutorId&gt;forked-path&lt;/mavenExecutorId&gt;
+        &lt;gpg.keyname&gt;19FEA27D&lt;/gpg.keyname&gt;\
+        &lt;!-- optional --&gt;
+        &lt;gpg.passphrase&gt;your-gpg-passphrase&lt;/gpg.passphrase&gt;
+      &lt;/properties&gt;
+    &lt;/profile&gt;
+  &lt;/profiles&gt;
+  ...
+&lt;/settings&gt;
+        </pre></div>
+      </div>
+    </div>
+    
     <div class="section"><h2>Release steps<a name="Release_steps"></a></h2>
       
       <div class="section"><h3>Prepare the source for release<a name="Prepare_the_source_for_release"></a></h3>
@@ -206,7 +270,7 @@ under the License. -->
           </li>
           <li>
             Perform a full build and deploy the SNAPSHOT artifacts:
-            <div class="source"><pre class="prettyprint">mvn -P apache-release
clean deploy</pre></div>
+            <div class="source"><pre class="prettyprint">mvn -P all clean deploy</pre></div>
           </li>
         </ol>
       </div>
@@ -239,7 +303,7 @@ under the License. -->
           <li>
             Do a dry run of the 
             <tt>release:prepare</tt> step.
-            <div class="source"><pre class="prettyprint">mvn -Papache-release
release:prepare -DdryRun=true</pre></div>
+            <div class="source"><pre class="prettyprint">mvn release:prepare
-DdryRun=true</pre></div>
 
             The dry run will not commit any changes back to SVN and gives you the opportunity
to verify that the 
             release process will complete as expected.
@@ -288,7 +352,7 @@ gpg: Signature made ...</pre></div>
               </li>
               <li>
                 Once any failures or required updates have been committed to svn, rollback
the release prepare files:
-                <div class="source"><pre class="prettyprint">mvn -P apache-release
release:rollback</pre></div>
+                <div class="source"><pre class="prettyprint">mvn release:rollback</pre></div>
               </li>
             </ol>
           </li>
@@ -296,7 +360,7 @@ gpg: Signature made ...</pre></div>
             Run the 
             <tt>release:prepare</tt> step for real this time. You'll be prompted
for the same version information and 
             optionally your GPG passphrase again.
-            <div class="source"><pre class="prettyprint">mvn -P apache-release
release:prepare</pre></div>
+            <div class="source"><pre class="prettyprint">mvn release:prepare</pre></div>
           </li>
           <li>
             Backup (zip or tar) your local release candidate directory in case you need to
rollback the release after 
@@ -310,7 +374,7 @@ cd 1.0-rc1</pre></div>
       
       <div class="section"><h3>Perform the release<a name="Perform_the_release"></a></h3>
         This step will create a maven staging repository
-        <div class="source"><pre class="prettyprint">mvn -P apache-release release:perform</pre></div>
+        <div class="source"><pre class="prettyprint">mvn release:perform</pre></div>
         
         <ol style="list-style-type: decimal">
           <li>Verify the staged artifacts in the Nexus repository:
@@ -396,20 +460,20 @@ Vote will be open for 72 hours.
             </pre></div>
           </li>
           <li>
-            Create a DISCUSS email thread on syncope-dev@ for any vote questions, e.g.:
+            Create a <tt>DISCUSS</tt> email thread on <a class="externalLink"
href="mailto:syncope-dev@incubator.apache.org">syncope-dev</a> for any vote questions,
e.g.:
             <div><pre>
 To: syncope-dev@incubator.apache.org
 Subject: [DISCUSS] Apache Syncope &lt;version&gt;
 
-Discussion thread for vote on &lt;version&gt; release candidate, with SVN source
tag (r9999999).
+Discussion thread for vote on &lt;version&gt; release, with SVN source tag (r9999999).
 
 For more information on the release process, check out http://www.apache.org/dev/release.html
 
 Some of the things to check before voting are:
  - does &quot;mvn apache-rat:check&quot; pass on the source
- - can you build the contents of source-release.zip and svn tag
- - do all of the staged jars/zips contain the required LICENSE and NOTICE files
- - are all of the staged jars signed and the signature verifiable
+ - can you build the contents of source release (both .zip and .tar.gz) and SVN tag
+ - do all of the staged jars/wars/tar.gz/zips contain the required LICENSE and NOTICE files
+ - are all of the staged jars/wars/tar.gz/zips signed and the signature verifiable
  - is the signing key in the project's KEYS file and on a public server (i.e. http://www.apache.org/dist/incubator/syncope/)
             </pre></div>
           </li>
@@ -499,7 +563,7 @@ Some of the things to check before votin
           <ol style="list-style-type: decimal">
             <li>
               Restore the 0.1-rc1.tar.gz and run
-              <div class="source"><pre class="prettyprint">mvn -P apache-release
release:rollback</pre></div> 
+              <div class="source"><pre class="prettyprint">mvn release:rollback</pre></div>

               <i>or</i>:
               manually revert the versions in trunk to the prior version and commit
             </li>



Mime
View raw message