cayenne-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r979469 - in /websites/staging/cayenne/trunk/content: ./ dev/release-guide.html
Date Thu, 04 Feb 2016 16:14:42 GMT
Author: buildbot
Date: Thu Feb  4 16:14:42 2016
New Revision: 979469

Log:
Staging update by buildbot for cayenne

Modified:
    websites/staging/cayenne/trunk/content/   (props changed)
    websites/staging/cayenne/trunk/content/dev/release-guide.html

Propchange: websites/staging/cayenne/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Feb  4 16:14:42 2016
@@ -1 +1 @@
-1700374
+1728502

Modified: websites/staging/cayenne/trunk/content/dev/release-guide.html
==============================================================================
--- websites/staging/cayenne/trunk/content/dev/release-guide.html (original)
+++ websites/staging/cayenne/trunk/content/dev/release-guide.html Thu Feb  4 16:14:42 2016
@@ -105,12 +105,23 @@
 
 <hr>
 <div id="content">
-       <p>This page describes the steps that a Cayenne Release Manager needs to
+       <style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
> .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink
{ visibility: visible }</style>
+<p>This page describes the steps that a Cayenne Release Manager needs to
 perform to prepare a release. The specifics of Cayenne release process is
 that we are publishing both downloadable assemblies and Maven artifacts, so
 we have to build and publish things twice. Both forms of Cayenne release
 are also available for evaluation during the vote.</p>
-<h2 id="prerequisites">Prerequisites</h2>
+<h2 id="prerequisites">Prerequisites<a class="headerlink" href="#prerequisites"
title="Permanent link">&para;</a></h2>
 <ul>
 <li>A release manager must have his public key appended to the KEYS file
 checked in to source control and the key published on one of the public key servers.
@@ -118,22 +129,21 @@ More info can be found at <a href="http:
 <li>Make sure "apache-releases" repository is configured in
 <em>~/.m2/settings.xml</em> and an appropriate password is setup. See <a href="http://www.apache.org/dev/publishing-maven-artifacts.html">this
page</a>
  for details.</li>
+<li>As Cayenne has modules which require Java 1.8, you should use Java 1.8 to perform
the release.</li>
 </ul>
-<h2 id="preparing-sources">Preparing Sources</h2>
+<h2 id="preparing-sources">Preparing Sources<a class="headerlink" href="#preparing-sources"
title="Permanent link">&para;</a></h2>
 <ul>
 <li>Edit UPGRADE-NOTES.txt if there is anything to add there.</li>
-<li>
-<p>Check Sources Compliance with <a href="http://creadur.apache.org/rat/">RAT</a>.
To run RAT,
+<li>Check Sources Compliance with <a href="http://creadur.apache.org/rat/">RAT</a>.
To run RAT,
 download the distro and unpack it somewhere. You can run it directly, or use a convenience
script available at the root of Cayenne 
-source. Then read the report and fix any issues.</p>
-<div class="codehilite"><pre><span class="n">cd</span> <span class="n">cayenne</span>
+source. Then read the report and fix any issues.<div class="codehilite"><pre><span
class="n">cd</span> <span class="n">cayenne</span>
 <span class="o">./</span><span class="nb">rat</span><span class="p">.</span><span
class="n">sh</span> <span class="o">~/</span><span class="n">Desktop</span><span
class="o">/</span><span class="n">apache</span><span class="o">-</span><span
class="nb">rat</span><span class="o">-</span>0<span class="p">.</span>9<span
class="o">/</span><span class="n">apache</span><span class="o">-</span><span
class="nb">rat</span><span class="o">-</span>0<span class="p">.</span>9<span
class="p">.</span><span class="n">jar</span>  <span class="o">&gt;</span>
<span class="n">report</span><span class="p">.</span><span class="n">txt</span>
 </pre></div>
 
 
 </li>
 </ul>
-<h2 id="tagging-the-repo-and-releasing-maven-artifacts">Tagging the Repo and Releasing
Maven Artifacts</h2>
+<h2 id="tagging-the-repo-and-releasing-maven-artifacts">Tagging the Repo and Releasing
Maven Artifacts<a class="headerlink" href="#tagging-the-repo-and-releasing-maven-artifacts"
title="Permanent link">&para;</a></h2>
 <ul>
 <li>
 <p>Create a Git tag and Create Maven Staging Repository:</p>
@@ -154,7 +164,7 @@ be used by the people voting on Cayenne.
 <a href="https://repository.apache.org/content/repositories/orgapachecayenne-052/">https://repository.apache.org/content/repositories/orgapachecayenne-052/</a>
</p>
 </li>
 </ul>
-<h2 id="releasing-downloadable-assemblies">Releasing Downloadable Assemblies</h2>
+<h2 id="releasing-downloadable-assemblies">Releasing Downloadable Assemblies<a class="headerlink"
href="#releasing-downloadable-assemblies" title="Permanent link">&para;</a></h2>
 <ul>
 <li>
 <p>Switch to the release tag created above.</p>
@@ -175,7 +185,7 @@ below, although release evaluators shoul
  and other kinds of testing.</em> </p>
 <div class="codehilite"><pre><span class="n">mvn</span> <span
class="n">clean</span> <span class="n">install</span> <span class="o">-</span><span
class="n">Passembly</span><span class="p">,</span><span class="n">generic</span>
<span class="o">-</span><span class="n">Dmaven</span><span class="p">.</span><span
class="n">test</span><span class="p">.</span><span class="n">skip</span><span
class="p">=</span><span class="n">true</span>
 
-# <span class="n">You</span> <span class="n">will</span> <span
class="n">need</span> <span class="n">to</span> <span class="n">do</span>
<span class="n">this</span> <span class="n">on</span> <span class="n">OS</span>
<span class="n">X</span><span class="p">,</span> <span class="n">and</span>
<span class="n">use</span> <span class="n">at</span> <span class="n">least</span>
<span class="n">Java</span> 1<span class="p">.</span>7
+# <span class="n">You</span> <span class="n">will</span> <span
class="n">need</span> <span class="n">to</span> <span class="n">do</span>
<span class="n">this</span> <span class="n">on</span> <span class="n">OS</span>
<span class="n">X</span><span class="p">,</span> <span class="n">and</span>
<span class="n">use</span> <span class="n">at</span> <span class="n">least</span>
<span class="n">Java</span> 1<span class="p">.</span>8
 <span class="n">mvn</span> <span class="n">clean</span> <span
class="n">install</span> <span class="o">-</span><span class="n">Passembly</span><span
class="p">,</span><span class="n">mac</span> <span class="o">-</span><span
class="n">Dmaven</span><span class="p">.</span><span class="n">test</span><span
class="p">.</span><span class="n">skip</span><span class="p">=</span><span
class="n">true</span>
 
 # <span class="n">You</span> <span class="n">will</span> <span
class="n">need</span> <span class="n">to</span> <span class="n">do</span>
<span class="n">this</span> <span class="n">on</span> <span class="n">Windows</span>
@@ -202,7 +212,7 @@ work ("-u" option can be omitted if you
 <li>Assemblies, signature and checksum files are committed to the special SVN repo
   used for staging development releases: <a href="https://dist.apache.org/repos/dist/dev/cayenne/">https://dist.apache.org/repos/dist/dev/cayenne/</a>.
Use a separate folder for each release. For more info on this repository check <a href="http://apache.org/dev/release.html#upload-ci">the
infrastructure docs</a>.</li>
 </ul>
-<h2 id="voting">Voting</h2>
+<h2 id="voting">Voting<a class="headerlink" href="#voting" title="Permanent link">&para;</a></h2>
 <ul>
 <li>The vote is started on the dev mailing list.</li>
 <li>All committers are encouraged to vote on releases. Committer votes will
@@ -223,7 +233,7 @@ main jar passes some basic tests.
 running them manually or verifying that Hudson has run those tests against
 the equivalent source). </li>
 </ul>
-<h2 id="publishing-the-release">Publishing the Release</h2>
+<h2 id="publishing-the-release">Publishing the Release<a class="headerlink" href="#publishing-the-release"
title="Permanent link">&para;</a></h2>
 <ul>
 <li>
 <p>Publish Maven artifacts. Go back to <a href="https://repository.apache.org/">https://repository.apache.org/</a>,
@@ -238,7 +248,7 @@ select the staging repo and click "Relea
 
 </li>
 </ul>
-<h2 id="after-the-release">After the release</h2>
+<h2 id="after-the-release">After the release<a class="headerlink" href="#after-the-release"
title="Permanent link">&para;</a></h2>
 <ul>
 <li>
 <p>Delete a previous version of Cayenne release of the same branch from the dist server.

@@ -266,7 +276,7 @@ add any new features</li>
 <li>Send a notification email to announceATapache.org</li>
 <li>Update <a href="http://en.wikipedia.org/wiki/Apache_Cayenne">http://en.wikipedia.org/wiki/Apache_Cayenne</a></li>
 </ul>
-<h2 id="reference">Reference:</h2>
+<h2 id="reference">Reference:<a class="headerlink" href="#reference" title="Permanent
link">&para;</a></h2>
 <ul>
 <li>Apache release publishing:
 <a href="http://www.apache.org/dev/release-publishing.html">http://www.apache.org/dev/release-publishing.html</a></li>



Mime
View raw message