continuum-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From br...@apache.org
Subject svn commit: r1427635 - in /continuum/site-publish: .htaccess development/release.html
Date Wed, 02 Jan 2013 03:41:55 GMT
Author: brett
Date: Wed Jan  2 03:41:55 2013
New Revision: 1427635

URL: http://svn.apache.org/viewvc?rev=1427635&view=rev
Log:
Site checkin for project Continuum

Removed:
    continuum/site-publish/.htaccess
Modified:
    continuum/site-publish/development/release.html

Modified: continuum/site-publish/development/release.html
URL: http://svn.apache.org/viewvc/continuum/site-publish/development/release.html?rev=1427635&r1=1427634&r2=1427635&view=diff
==============================================================================
--- continuum/site-publish/development/release.html (original)
+++ continuum/site-publish/development/release.html Wed Jan  2 03:41:55 2013
@@ -203,26 +203,13 @@ pageTracker._trackPageview();</script>
     </div>
     <div id="bodyColumn">
       <div id="contentBox">
-        <div class="section"><h2>Continuum Release Guidelines<a name="Continuum_Release_Guidelines"></a></h2><ul><li>Continuum
is versioned X.Y.Z -- Major.Minor.Build. The Major and Minor versions are set at the beginning
of a series, after which we use sequential build numbers starting with .0. For example, 1.3.0,
1.3.1, 1.3.2.</li><li>Ideally each version is tagged and built exactly once. The
Release Manager (RM) has discretion to re-build a version if something goes wrong during the
release process, but once a version has been made available for public download, that version
number may not be re-used.</li><li>During the vote, an additional qualifier is
determined. For example: 1.3.0 (M1) or 1.3.7 (GA). Respectively, these mean Milestone 1 and
General Availability. Qualifiers such as Alpha and Beta are also acceptable, as is RC (Release
Candidate).</li><li>If the vote does not pass, the qualifier may be reused. For
example, if 1.3.0 was meant to be Milestone 1 but does not
  get approved, 1.3.1 can become M1.</li><li>When releases are announced to the
community, the additional qualifier is used in addition to the version number. For example:
[ANN] Continuum 1.3.3 (Milestone 2) Release or [ANN] Continuum 1.3.6 (GA) Release</li><li>A
qualifier can be changed by calling a new vote. If we get to 1.3.8 (M5) and decide that it
has no problems and there's nothing else we want to add, we can simply re-label it GA and
update the website.</li><li>New features may be added to 1.3.x releases until
we reach GA, at which point only minor changes should be made.</li><li>If the
vote does not pass, the binaries should be removed from the download area, and the version
should be labeled &quot;test build&quot; on the release notes page.</li></ul></div><div
class="section"><h2>Continuum Release Preparation<a name="Continuum_Release_Preparation"></a></h2><ol
style="list-style-type: decimal"><li>Post to the dev list a few days before you plan
to do a Continuum relea
 se</li><li>Check for SNAPSHOT dependencies, including the Continuum parent POM</li><li>Update
<tt>continuum-docs/src/site/xdoc/release-notes.xml</tt><ul><li>Copy
and paste the html release notes from JIRA</li><li>Remove the first line with
the heading</li></ul></li><li>Make sure that you have the &quot;release&quot;
profile set in your <tt>settings.xml</tt> as shown below.<div class="source"><pre>&lt;profile&gt;
-  &lt;id&gt;release&lt;/id&gt;
-  &lt;properties&gt;
-    &lt;gpg.passphrase&gt;[GPG_PASS_PHRASE]&lt;/gpg.passphrase&gt;
-  &lt;/properties&gt;
-&lt;/profile&gt;</pre></div></li><li>Set your user credentials
for the stage repo in the <tt>&lt;servers</tt>&gt; section of your <tt>settings.xml</tt>
file.</li></ol></div><div class="section"><h2>Continuum Release
Process<a name="Continuum_Release_Process"></a></h2><p>By default,
the release will be staged in <tt>http://people.apache.org/builds/continuum/${version}/staging-repo</tt>.
If you want to stage it elsewhere, set the <tt>deploy.altRepository</tt> property
in your <tt>settings.xml</tt> file. For example:</p><div><pre>&lt;deploy.altRepository&gt;vmbuild.staging::default::http://vmbuild.apache.org/archiva/repository/staged-continuum/&lt;/deploy.altRepository&gt;</pre></div><p><i>Note:</i>
If using Archiva to deploy to, you will need to clear the deployment repository first</p><ol
style="list-style-type: decimal"><li>Check trunk is building correctly (including
Selenium tests) by running:<div><pre>mvn clean install -Pintegration</pre></div></li><li>Execute
<tt>mvn rel
 ease:prepare</tt> (check that it has been properly tagged. The tag name must be <tt>continuum-[VERSION]</tt>)</li><li>Then
execute <tt>mvn release:perform</tt></li><li>ssh to <tt>people.apache.org</tt>
and cd to <tt>/www/people.apache.org/builds/continuum/VERSION</tt>. Execute the
following commands to copy and rename the source and binary distributions.<div class="source"><pre>svn
cat http://svn.apache.org/repos/asf/continuum/project/release-script.sh &gt; ../release-script.sh
-sh ../release-script.sh VERSION STAGING_URL</pre></div></li><li>Stage
the site <tt>mvn site:stage-deploy -DstagingSiteURL=scp://people.apache.org/home/USERID/public_html/staging-sites/continuum/1.3.4</tt>
from the <tt>continuum-docs</tt> module of the release tag or <tt>target/checkout</tt>
directory</li><li>Call for a vote in the dev list and wait for 72 hours for the
vote results. 3 binding votes from PMC members are necessary for the release to be finalized.
<b><a class="externalLink" href="http://markmail.org/message/dhgdoz6aht6w5frl">Example</a></b></li><li>After
the vote has passed, copy the sources and binaries from <tt>people.apache.org</tt>
to <tt>/www/www.apache.org/dist/continuum</tt>.</li><li>To sync the
JARs to the central repository, execute:<div class="source"><pre>mvn stage:copy
-Dsource=&quot;[STAGE_REPO_URL]&quot;
+        <div class="section"><h2>Continuum Release Guidelines<a name="Continuum_Release_Guidelines"></a></h2><ul><li>Continuum
is versioned X.Y.Z -- Major.Minor.Build. The Major and Minor versions are set at the beginning
of a series, after which we use sequential build numbers starting with .0. For example, 1.3.0,
1.3.1, 1.3.2.</li><li>Ideally each version is tagged and built exactly once. The
Release Manager (RM) has discretion to re-build a version if something goes wrong during the
release process, but once a version has been made available for public download, that version
number may not be re-used.</li><li>During the vote, an additional qualifier is
determined. For example: 1.3.0 (M1) or 1.3.7 (GA). Respectively, these mean Milestone 1 and
General Availability. Qualifiers such as Alpha and Beta are also acceptable, as is RC (Release
Candidate).</li><li>If the vote does not pass, the qualifier may be reused. For
example, if 1.3.0 was meant to be Milestone 1 but does not
  get approved, 1.3.1 can become M1.</li><li>When releases are announced to the
community, the additional qualifier is used in addition to the version number. For example:
[ANN] Continuum 1.3.3 (Milestone 2) Release or [ANN] Continuum 1.3.6 (GA) Release</li><li>A
qualifier can be changed by calling a new vote. If we get to 1.3.8 (M5) and decide that it
has no problems and there's nothing else we want to add, we can simply re-label it GA and
update the website.</li><li>New features may be added to 1.3.x releases until
we reach GA, at which point only minor changes should be made.</li><li>If the
vote does not pass, the binaries should be removed from the download area, and the version
should be labeled &quot;test build&quot; on the release notes page.</li></ul></div><div
class="section"><h2>Continuum Release Preparation<a name="Continuum_Release_Preparation"></a></h2><ol
style="list-style-type: decimal"><li>Post to the dev list a few days before you plan
to do a Continuum relea
 se</li><li>Check for SNAPSHOT dependencies, including the Continuum parent POM</li><li>Update
<tt>continuum-docs/src/site/xdoc/release-notes.xml</tt><ul><li>Copy
and paste the html release notes from JIRA</li><li>Remove the first line with
the heading</li></ul></li></ol></div><div class="section"><h2>Continuum
Release Process<a name="Continuum_Release_Process"></a></h2><p>The
release will be staged in <a class="externalLink" href="https://archiva-repository.apache.org/archiva/repository/continuum-releases/">https://archiva-repository.apache.org/archiva/repository/continuum-releases/</a>.
You will need to set your user credentials for the Archiva repository in the <tt>&lt;servers</tt>&gt;
section of your <tt>settings.xml</tt> file, under the <tt>archiva-repository.releases</tt>
server ID.</p><ol style="list-style-type: decimal"><li>Check trunk is building
correctly (including Selenium tests) by running:<div><pre>mvn clean install -Pintegration</pre></div></li><li>Execute
<tt>
 mvn release:prepare</tt> (check that it has been properly tagged. The tag name must
be <tt>continuum-[VERSION]</tt>)</li><li>Then execute <tt>mvn
release:perform</tt></li><li>Copy the release artifacts from the Archiva
repository to the Continuum distribution testing area ~~ TODO: expand with instructions for
pubsub</li><li>Stage the site <tt>mvn -Ptag site-deploy</tt> from
the <tt>continuum-docs</tt> module of the release tag or <tt>target/checkout</tt>
directory</li><li>Call for a vote in the dev list and wait for 72 hours for the
vote results. 3 binding votes from PMC members are necessary for the release to be finalized.
<b><a class="externalLink" href="http://markmail.org/message/dhgdoz6aht6w5frl">Example</a></b>.
</li><li>After the vote has passed, copy the sources and binaries to the production
Continuum distribution area ~~ TODO: expand with instructions for pubsub</li><li>Remove
versions that no longer need to be downloaded from mirrors ~~ TODO: expand with instruct
 ions for pubsub</li><li>To sync the JARs to the central repository, execute:<div
class="source"><pre>mvn stage:copy -Dsource=&quot;[STAGE_REPO_URL]&quot;
      -Dtarget=&quot;scp://[APACHE_USERNAME]@people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository&quot;
-     -Dversion=1.3.4 -DrepositoryId=apache.releases</pre></div><p><b>Note:</b>
Do not use Maven 2.0.9 because it has a bug when performing <tt>mvn stage:copy</tt></p><p><b>Note:</b>
You can also use scpexe:// especially if you are building from another machine using SSH agent
forwarding</p></li><li>Execute fix permissions scripts. Login to <tt>people.apache.org</tt><div
class="source"><pre>/www/people.apache.org/repo/m2-snapshot-repository/fix-permissions.sh</pre></div></li><li>Publish
the docs with <tt>mvn site-deploy</tt> from the <tt>continuum-docs</tt>
module from the release tag</li><li>Update the Continuum site at <tt>https://svn.apache.org/repos/asf/continuum/site/</tt>
with the versions and release notes URL and run <tt>mvn site-deploy</tt>. Below
is the list of pages that you need to update:<ul><li><tt>src/site/xdoc/index.xml</tt></li><li><tt>src/site/apt/known-issues.apt</tt></li><li><tt>src/site/apt/download.apt</tt></li><li><tt>src/site/apt/changelog.apt</tt></li
 ><li><tt>src/site/resources/.htaccess</tt> - update <tt>Redirect
Permanent /docs/current http://continuum.apache.org/docs/1.0.1/</tt> to the latest released
GA version</li></ul></li><li>Remove versions that no longer need to
be downloaded from the mirror from <tt>/www/www.apache.org/dist/continuum</tt></li><li>Publish
the reference docs (<tt>mvn site-deploy</tt> from the release tag. You may have
to exclude the <tt>continuum-webapp</tt> module to do this, and will require <tt>MAVEN_OPTS=-Xmx256m</tt></li><li>Update
JIRA to indicate the version is released</li><li>Send out an announcement of the
release</li></ol></div><div class="section"><h2>Verifying a
Release<a name="Verifying_a_Release"></a></h2><p>Download the uploaded
files via wget:</p><div class="source"><pre> wget http://people.apache.org/builds/continuum/1.3.4/source/apache-continuum-1.3.4-src.tar.gz</pre></div><p>Verify
the signatures:</p><div class="source"><pre> gpg -v apache-continuum-1.3.4-src.zip.asc</pre></di
 v><p>Verify the checksums:</p><div class="source"><pre> md5sum
apache-continuum-1.3.4-src.zip
+     -Dversion=1.3.4 -DrepositoryId=apache.releases</pre></div><p><b>Note:</b>
You can also use scpexe:// especially if you are building from another machine using SSH agent
forwarding</p></li><li>Execute fix permissions scripts. Login to <tt>people.apache.org</tt><div
class="source"><pre>/www/people.apache.org/repo/m2-snapshot-repository/fix-permissions.sh</pre></div></li><li>Update
the Continuum site at <tt>https://svn.apache.org/repos/asf/continuum/site/</tt>
with the versions and release notes URL and run <tt>mvn site-deploy</tt>. Below
is the list of pages that you need to update:<ul><li><tt>src/site/xdoc/index.xml</tt></li><li><tt>src/site/apt/known-issues.apt</tt></li><li><tt>src/site/apt/download.apt</tt></li><li><tt>src/site/apt/changelog.apt</tt></li></ul></li><li>Publish
the reference docs (<tt>mvn site site:stage scmpublish:publish-scm</tt> from the
release tag or previous <tt>target/checkout</tt> directory.</li><li>Update
JIRA to indicate the version is released
 </li><li>Send out an announcement of the release to users@continuum.apache.org,
and announce@apache.org (for GA releases). This must be sent from your @apache.org address.</li></ol></div><div
class="section"><h2>Verifying a Release<a name="Verifying_a_Release"></a></h2><p>Download
the uploaded files via wget:</p><!-- TODO: adjust for pubsub --><div class="source"><pre>
wget http://people.apache.org/builds/continuum/1.3.4/source/apache-continuum-1.3.4-src.tar.gz</pre></div><p>Verify
the signatures:</p><div class="source"><pre> gpg -v apache-continuum-1.3.4-src.zip.asc</pre></div><p>Verify
the checksums:</p><div class="source"><pre> openssl md5 apache-continuum-1.3.4-src.zip
  cat apache-continuum-1.3.4-src.zip.md5
 
- sha1sum apache-continuum-1.3.4-src.zip
- cat apache-continuum-1.3.4-src.zip.sha1</pre></div></div><div class="section"><h2>Publishing
a release<a name="Publishing_a_release"></a></h2><p>Tally the vote
and reply on the vote thread. I prefer not to change the subject line as it breaks threading
in some clients.</p><p>Copy the distribution files over to /www/www.apache.org/dist/continuum</p><div
class="source"><pre>cp /www/people.apache.org/builds/continuum/1.3.4/apache-continuum-1.3.4-bin*
/www/www.apache.org/dist/continuum/binaries/
-cp /www/people.apache.org/builds/continuum/1.3.4/apache-continuum-1.3.4.war* /www/www.apache.org/dist/continuum/binaries/
-cp /www/people.apache.org/builds/continuum/1.3.4/apache-continuum-1.3.4-src* /www/www.apache.org/dist/continuum/source/
-cp /www/people.apache.org/builds/continuum/1.3.4/apache-continuum-buildagent-1.3.4-bin* /www/www.apache.org/dist/continuum/binaries/
-cp /www/people.apache.org/builds/continuum/1.3.4/apache-continuum-buildagent-1.3.4.war* /www/www.apache.org/dist/continuum/binaries/</pre></div><p>Promote
the staged repository contents</p><div class="source"><pre>mvn stage:copy
-Dsource=&quot;http://people.apache.org/builds/continuum/1.3.4/staging-repo&quot;
\
--Dtarget=&quot;scp://people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository&quot;
\
--Dversion=1.3.4 \
--DtargetRepositoryId=apache.releases</pre></div><p><b>Note:</b>
This copies <b>everything</b> in the staging repo, even if you specify a version</p><p>Update
the <tt>index.xml</tt> and <tt>downloads.apt</tt> pages on the main
site</p><p>Publish the versioned reference docs (<tt>mvn site-deploy</tt>
from a checkout of the tag)</p><p>Publish the top-level website</p><p>Announce
the release on the dev and user lists</p><p>Optionally announce on the Apache
announcements list (only for major versions?)</p><p>Remove old releases from /www/www.apache.org/dist
(make sure to remove them from <tt>downloads.apt</tt> or the links will be broken)</p><p>Open
a bottle of champagne ! :-)</p></div><div class="section"><h2>Releasing
the parent POM<a name="Releasing_the_parent_POM"></a></h2><p>Check
out the source from <tt>https://svn.apache.org/repos/asf/continuum/parent</tt></p><ul><li><tt>mvn
release:prepare</tt> (verify that it has been properly tagged)</li><li><tt>mvn
release:perform</tt>
  (verify that it has been deployed correctly in the staging repo)</li><li>Update
the parent POM version in Continuum at <tt>https://svn.apache.org/repos/asf/continuum/trunk</tt>
(or in the branch)</li><li>Change the parent POM version to the <tt>continuum-parent</tt>
version that has just been released</li><li>Commit the changes made</li></ul></div>
+ openssl sha1 apache-continuum-1.3.4-src.zip
+ cat apache-continuum-1.3.4-src.zip.sha1</pre></div></div><div class="section"><h2>Releasing
the parent POM<a name="Releasing_the_parent_POM"></a></h2><p>Check
out the source from <tt>https://svn.apache.org/repos/asf/continuum/parent</tt></p><ul><li><tt>mvn
release:prepare</tt> (verify that it has been properly tagged)</li><li><tt>mvn
release:perform</tt> (verify that it has been deployed correctly in the staging repo)</li><li>Conduct
a vote (or do it in conjunction with a Continuum release)</li><li>Update the parent
POM version in Continuum at <tt>https://svn.apache.org/repos/asf/continuum/trunk</tt>
(or in the branch), in the site at <tt>https://svn.apache.org/repos/asf/continuum/site</tt>,
and the skin at <tt>https://svn.apache.org/repos/asf/continuum/skin/trunk</tt>
to change the parent POM version to the <tt>continuum-parent</tt> version that
has just been released</li><li>Commit the changes made</li></ul></div><div
class="section"><h2>Releasing the Site Skin<a name="Re
 leasing_the_Site_Skin"></a></h2><p>Check out the source from <tt>https://svn.apache.org/repos/asf/continuum/skin/trunk</tt></p><ul><li><tt>mvn
release:prepare</tt> (verify that it has been properly tagged)</li><li><tt>mvn
release:perform</tt> (verify that it has been deployed correctly in the staging repo)</li><li>Conduct
a vote (or do it in conjunction with a Continuum release)</li><li>Update the <tt>site.xml</tt>
in Continuum at <tt>https://svn.apache.org/repos/asf/continuum/trunk</tt> and
in the site at <tt>https://svn.apache.org/repos/asf/continuum/site</tt></li><li>Commit
the changes made</li></ul></div>
       </div>
     </div>
     <div class="clear">



Mime
View raw message