You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by bu...@apache.org on 2017/09/19 20:23:08 UTC
svn commit: r1018384 - in /websites/production/activemq/content:
cache/main.pageCache release-guide.html
Author: buildbot
Date: Tue Sep 19 20:23:08 2017
New Revision: 1018384
Log:
Production update by buildbot for activemq
Modified:
websites/production/activemq/content/cache/main.pageCache
websites/production/activemq/content/release-guide.html
Modified: websites/production/activemq/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/activemq/content/release-guide.html
==============================================================================
--- websites/production/activemq/content/release-guide.html (original)
+++ websites/production/activemq/content/release-guide.html Tue Sep 19 20:23:08 2017
@@ -37,6 +37,7 @@
<script src='http://activemq.apache.org/styles/highlighter/scripts/shCore.js' type='text/javascript'></script>
<script src='http://activemq.apache.org/styles/highlighter/scripts/shBrushJava.js' type='text/javascript'></script>
<script src='http://activemq.apache.org/styles/highlighter/scripts/shBrushXml.js' type='text/javascript'></script>
+ <script src='http://activemq.apache.org/styles/highlighter/scripts/shBrushBash.js' type='text/javascript'></script>
<script type="text/javascript">
SyntaxHighlighter.defaults['toolbar'] = false;
@@ -82,7 +83,7 @@
<tr>
<td valign="top" width="100%">
<div class="wiki-content maincontent"><p>How to create and announce an ActiveMQ release. This release is based on <a shape="rect" class="external-link" href="http://maven.apache.org/developers/release/apache-release.html">General guide for releasing Maven-based project at Apache </a>, so be sure to check it out before continuing and meet all prerequisites.</p><h2 id="ReleaseGuide-Maven2Setup">Maven 2 Setup</h2><p>Before you deploy anything to the maven repository using Maven 2, you should configure your ~/.m2/settings.xml file<br clear="none"> so that the file permissions of the deployed artifacts are group writeable. If you do not do this, other developers will not able to overwrite your SNAPSHOT releases with newer versions.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: xml; gutter: false; theme: Default" style="font-size:12px;"><settings>
+<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;"><settings>
...
<servers>
@@ -118,7 +119,7 @@
<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">umask 2
</pre>
</div></div><p>Other shell initialization files may interfere with this setting but if this is the only umask setting it appears to work. Instructions for other shells would be welcome.</p><h3 id="ReleaseGuide-Additionallocalconfigurationforusingreleaseandstagingplugins.">Additional local configuration for using release and staging plugins.</h3><p>To effectively use the release and staging plugins you need some information about where the staging will happen and signing information for gpg. Your ~/.m2/settings.xml should contain a profile like this:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: xml; gutter: false; theme: Default" style="font-size:12px;"><settings>
+<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;"><settings>
<profiles>
<profile>
<id>apache-release</id>
@@ -166,8 +167,25 @@ svn rm apidocs
ln -s <version>/apidocs apidocs
svn add apidocs
# and commit once it looks good.</pre>
-</div></div></li><li>Call a vote on the dev list, listing the great new features of the release.</li><li>After it passes, promote the release (i.e. release the staging repository): login to<span style="color: rgb(112,112,112);"> </span><a shape="rect" class="external-link" href="https://repository.apache.org/">https://repository.apache.org</a>, navigate to the staging repository and click the "release" button</li><li><p>replicate the contents of mvn apache-activemq/<version> directory to the dist website on people.apache.org using svn</p><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>ssh [apacheId]@people.apache.org
+</div></div></li><li>Download the official release archives (src and bin) from the staging repository and prepare them for upload to the Apache <a shape="rect" class="external-link" href="https://dist.apache.org/repos/dist/dev/activemq/">dev</a> SVN repo where the official release is staged<br clear="none">A script exists that can do this release preparation for you in the Git repo <a shape="rect" class="external-link" href="https://raw.githubusercontent.com/apache/activemq/master/etc/scripts/prepare-release.sh" rel="nofollow">here</a>.  If you don't want to use the script the process is fairly simple:<ol><li>Download the source bundle from the staging site along with it's signature and checksum files.</li><li>Download the binary bundles (tar.gz and zip) from the staging site along with their signature and checksum files.</li><li>Check the downloaded files using the md5 and or sha1 checksums, then discard the sha1 files.</li><li>Check the signatures for all the downloaded files
using "gpg --verfiy" or the like.</li><li>Update the md5 files by amending them with the actual filename they are associated with, this make validation easier for end users.</li><li>Create a new sha512 checksum file for each release artifact using the sha512sum command.</li></ol></li><li><p>Upload the newly prepared official release artifacts to the dev site</p><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
+<pre>svn co https://dist.apache.org/repos/dist/dev/activemq/
+cd activemq
+mkdir <version>;cd <version>
+<Copy prepared artifacts to this folder
+svn add .
+and commit once it looks good.</pre>
+</div></div></li><li>Call a vote on the dev list, listing the great new features of the release.</li><li>After it passes, promote the release (i.e. release the staging repository): login to<span style="color: rgb(112,112,112);"> </span><a shape="rect" class="external-link" href="https://repository.apache.org/">https://repository.apache.org</a>, navigate to the staging repository and click the "release" button. </li><li><p>Migrate the staged release files from the SVN dev folder to the SVN release folder: <a shape="rect" class="external-link" href="https://dist.apache.org/repos/dist/release/activemq/">https://dist.apache.org/repos/dist/release/activemq/</a></p><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
+<pre>svn co https://dist.apache.org/repos/dist/release/activemq/
+cd activemq
+mkdir <version>;cd <version>
+
+<copy files from the https://dist.apache.org/repos/dist/dev/activemq/ directory to the ./release/activemq directory>
+
+and commit once it looks good.</pre>
+</div></div><p> </p><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
+<pre>*** Deprecated Remove once the above is fully worked out ***
+
+ssh [apacheId]@people.apache.org
svn co https://dist.apache.org/repos/dist/release/activemq/
cd activemq
mkdir <version>;cd <version>