Author: buildbot
Date: Wed Jan 21 21:21:32 2015
New Revision: 937152
Log:
Production update by buildbot for activemq
Modified:
websites/production/activemq/content/cache/main.pageCache
websites/production/activemq/content/download.html
websites/production/activemq/content/javadocs.html
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/download.html
==============================================================================
--- websites/production/activemq/content/download.html (original)
+++ websites/production/activemq/content/download.html Wed Jan 21 21:21:32 2015
@@ -72,11 +72,7 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2 id="Download-LatestReleases">Latest
Releases</h2><div class="sectionColumnWrapper"><div class="sectionMacro"><div
class="sectionMacroRow"><div class="columnMacro"
style="width:20%;min-width:20%;max-width:20%;"><div
style="padding-right:20px;float:left;">
-<p><img class="confluence-embedded-image confluence-external-resource"
src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"
data-image-src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></p></div></div><div
class="columnMacro" style="width:80%;min-width:80%;max-width:80%;"><div
style="min-height:200px">
-
-<p>The latest stable release is the <a shape="rect"
href="activemq-5100-release.html">ActiveMQ 5.10.0 Release</a></p>
-</div></div></div></div></div><h2 id="Download-Gettingpastreleases">Getting
past releases</h2><p>See the <a shape="rect"
href="download-archives.html">Download Archives</a> for all time
releases.</p><p></p><h2 id="Download-ReleasesInProgress">Releases In
Progress</h2>
+<div class="wiki-content maincontent"><h2 id="Download-LatestReleases">Latest
Releases</h2><div class="sectionColumnWrapper"><div class="sectionMacro"><div
class="sectionMacroRow"><div class="columnMacro"
style="width:20%;min-width:20%;max-width:20%;"><div
style="padding-right:20px;float:left;"><p><img class="confluence-embedded-image
confluence-external-resource"
src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"
data-image-src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></p></div></div><div
class="columnMacro" style="width:80%;min-width:80%;max-width:80%;"><div
style="min-height:200px"><p>The latest stable release is the <a shape="rect"
href="activemq-5101-release.html">ActiveMQ 5.10.1
Release</a></p></div></div></div></div></div><h2
id="Download-Gettingpastreleases">Getting past releases</h2><p>See the <a
shape="rect" href="download-archives.html">Download Archives</a> for all time
releases.</p><p>
</p><h2 id="Download-ReleasesInProgress">Releases In Progress</h2>
<p>The following releases are currently in progress</p>
<h3 id="Download-SNAPSHOTBinaries">SNAPSHOT Binaries</h3><p>The current
development of Apache ActiveMQ can be downloaded as binaries from the Apache
Maven snapshot repository.<br clear="none"> The binaries is located at <a
shape="rect" class="external-link"
href="https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/apache-activemq/">https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/apache-activemq/</a>.</p><h2
id="Download-MavenRepositories">Maven Repositories</h2><p>All ActiveMQ
releases are available from the <a shape="rect" class="external-link"
href="https://repository.apache.org/content/repositories/releases/org/apache/activemq/">Maven
central repository</a>.</p><p>If you want to run against a more recent
SNAPSHOT, use the repositories listed below:</p><h3
id="Download-MavenRepositories.1">Maven Repositories</h3><div
class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1"
rowspan="1" class="confluen
ceTh"><p>Repository</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>Apache ActiveMQ SNAPSHOTS</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect"
class="external-link"
href="https://repository.apache.org/content/repositories/snapshots/">https://repository.apache.org/content/repositories/snapshots/</a></p></td></tr></tbody></table></div></div>
Modified: websites/production/activemq/content/javadocs.html
==============================================================================
--- websites/production/activemq/content/javadocs.html (original)
+++ websites/production/activemq/content/javadocs.html Wed Jan 21 21:21:32 2015
@@ -72,27 +72,7 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2
id="JavaDocs-JavaDocsforApacheActiveMQ">JavaDocs for Apache ActiveMQ</h2>
-
-<p>Versioned JavaDocs for Apache ActiveMQ could be found at </p>
-
-<p><a shape="rect" class="external-link"
href="http://activemq.apache.org/maven/">http://activemq.apache.org/maven/</a>x.y.z/apidocs/index.html
kind of url, where <em>x.y.z</em> is broker version you're looking for.</p>
-
-<p>For example <a shape="rect" class="external-link"
href="http://activemq.apache.org/maven/5.8.0/apidocs/index.html">http://activemq.apache.org/maven/5.8.0/apidocs/index.html</a>
contains JavaDocs for <strong>5.8.0</strong>.</p>
-
-<h2 id="JavaDocs-OtherJavaDocs">Other JavaDocs</h2>
-
-<ul><li><a shape="rect" class="external-link"
href="http://java.sun.com/j2ee/1.4/docs/api/javax/jms/package-summary.html"
rel="nofollow">JMS API</a></li></ul>
-
-
-<h2 id="JavaDocs-CMSandC++Documentation">CMS and C++ Documentation</h2>
-
-<ul><li><a shape="rect" class="external-link"
href="http://activemq.apache.org/cms/">CMS and ActiveMQ-CPP</a></li></ul>
-
-
-<h2 id="JavaDocs-NMSandC#Documentation">NMS and C# Documentation</h2>
-
-<ul><li><a shape="rect" class="external-link"
href="http://activemq.apache.org/nms/">NMS API</a></li></ul></div>
+<div class="wiki-content maincontent"><h2
id="JavaDocs-JavaDocsforApacheActiveMQ">JavaDocs for Apache
ActiveMQ</h2><p>Versioned JavaDocs for Apache ActiveMQ could be found
at</p><p><a shape="rect" class="external-link"
href="http://activemq.apache.org/maven/">http://activemq.apache.org/maven/</a>x.y.z/apidocs/index.html
kind of url, where <em>x.y.z</em> is broker version you're looking
for.</p><p>For example <a shape="rect" class="external-link"
href="http://activemq.apache.org/maven/5.10.0/apidocs/index.html">http://activemq.apache.org/maven/5.10.0/apidocs/index.html</a>
contains JavaDocs for <strong>5.10.0</strong>.</p><h2
id="JavaDocs-OtherJavaDocs">Other JavaDocs</h2><ul><li><a shape="rect"
class="external-link"
href="http://java.sun.com/j2ee/1.4/docs/api/javax/jms/package-summary.html"
rel="nofollow">JMS API</a></li></ul><h2
id="JavaDocs-CMSandC++Documentation">CMS and C++ Documentation</h2><ul><li><a
shape="rect" class="external-link" href="http://activemq.apache.org/cms/">CMS
and ActiveMQ-CPP</a></li></ul><h2 id="JavaDocs-NMSandC#Documentation">NMS and
C# Documentation</h2><ul><li><a shape="rect" class="external-link"
href="http://activemq.apache.org/nms/">NMS API</a></li></ul></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/activemq/content/release-guide.html
==============================================================================
--- websites/production/activemq/content/release-guide.html (original)
+++ websites/production/activemq/content/release-guide.html Wed Jan 21 21:21:32
2015
@@ -82,16 +82,8 @@
<tbody>
<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">
-<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[
-<settings>
+<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">
+<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[<settings>
...
<servers>
@@ -123,22 +115,11 @@ so that the file permissions of the depl
...
</settings>
]]></script>
-</div></div>
-
-<p>It is also essential that you configure your umask to 2 on
people.apache.org for non-interactive login. If your shell is tcsh you can
edit .cshrc to include</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-umask 2
+</div></div><p>It is also essential that you configure your umask to 2 on
people.apache.org for non-interactive login. If your shell is tcsh you can edit
.cshrc to include</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[umask 2
]]></script>
-</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">
-<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[
-<settings>
+</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">
+<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[<settings>
<profiles>
<profile>
<id>apache-release</id>
@@ -150,70 +131,34 @@ umask 2
...
</settings>
]]></script>
-</div></div>
-
-
-<h2 id="ReleaseGuide-CreatingtheActiveMQRelease">Creating the ActiveMQ
Release</h2>
-
-<p>The release plugin will prompt for a release version, tag and next release
version. Use a three digit release version of the form: 5.x.x and for the tag
use a string of the form: activemq-5.x.x. The next version string should use
the two digit from: 5.x-SNAPSHOT as this can be consistent for future SNAPSHOT
releases.</p>
-<ol><li>Verify the to-be-released version identifier exists in the <a
shape="rect" class="external-link"
href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=blob;f=activemq-spring/src/main/resources/META-INF/spring.schemas;hb=HEAD">META-INF/spring.schema</a>
mappings file, if not add it and commit. It should contain:
- <div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+</div></div><h2 id="ReleaseGuide-CreatingtheActiveMQRelease">Creating the
ActiveMQ Release</h2><p>The release plugin will prompt for a release version,
tag and next release version. Use a three digit release version of the form:
5.x.x and for the tag use a string of the form: activemq-5.x.x. The next
version string should use the two digit from: 5.x-SNAPSHOT as this can be
consistent for future SNAPSHOT releases.</p><ol><li><p>Verify the
to-be-released version identifier exists in the <a shape="rect"
class="external-link"
href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=blob;f=activemq-spring/src/main/resources/META-INF/spring.schemas;hb=HEAD">META-INF/spring.schema</a>
mappings file, if not add it and commit. It should contain:</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[http\://activemq.apache.org/schema/core/activemq-core-${pom.version}.xsd=activemq.xsd]]></script>
-</div></div></li><li>Verify headers with <a shape="rect" class="external-link"
href="http://incubator.apache.org/rat/apache-rat-plugin/usage.html">rat</a>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-mvn -e apache-rat:check
+</div></div></li><li><p>Verify headers with <a shape="rect"
class="external-link"
href="http://incubator.apache.org/rat/apache-rat-plugin/usage.html">rat</a></p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[mvn -e apache-rat:check
grep -e ' !?????' target/rat.txt -- will show any files without
licenses
]]></script>
-</div></div></li><li>Do a release dry run to check for problems
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-mvn release:prepare -DdryRun=true
-]]></script>
-</div></div>
-Check that you are happy with the results. The poms for the proposed tags will
be in pom.xml.tag. When you like the results, clean up:
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-mvn release:clean
-]]></script>
-</div></div></li><li>Prepare the release
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-mvn release:prepare
-]]></script>
-</div></div>
-This will create the tag in git and leave various stuff around locally to
direct the perform phase.</li><li>Make a local copy of the release
configuration in case something goes wrong
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-cd ..
+</div></div></li><li><p>Do a release dry run to check for problems</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[mvn release:prepare -DdryRun=true
+]]></script>
+</div></div><p>Check that you are happy with the results. The poms for the
proposed tags will be in pom.xml.tag. When you like the results, clean
up:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[mvn release:clean
+]]></script>
+</div></div></li><li><p>Prepare the release</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[mvn release:prepare
+]]></script>
+</div></div><p>This will create the tag in git and leave various stuff around
locally to direct the perform phase.</p></li><li><p>Make a local copy of the
release configuration in case something goes wrong</p><div class="code panel
pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[cd ..
cp -r activemq-release activemq-release-prepared
cd activemq-release
]]></script>
-</div></div></li><li>Perform the release to the staging repo
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-mvn release:perform
-]]></script>
-</div></div>
-This uses both the activemq release profile which directs building source
jars, javadoc jars, and signing everything, and also the settings release
profile that says where to<br clear="none">
-put stuff and how to sign it.</li><li>Close the staging repository<br
clear="none">
-Quote from the <a shape="rect" class="external-link"
href="http://maven.apache.org/developers/release/apache-release.html">Maven
release guide for Apache projects</a>
-<blockquote><p> Login to <a shape="rect" class="external-link"
href="https://repository.apache.org">https://repository.apache.org</a> using
your Apache LDAP credentials. Click on "Staging". Then click on "maven" in the
list of repositories. In the panel below you should see an open repository that
is linked to your username and ip. Right click on this repository and select
"Close". This will close the repository from future deployments and make it
available for others to view. If you are staging multiple releases together,
skip this step until you have staged everything. Enter the name and version of
the artifact being released in the "Description" field and then click "Close".
This will make it easier to identify it later.</p></blockquote>
-See the image in the original guide for more info.</li><li>Verify staged
artifacts<br clear="none">
-Quote from the <a shape="rect" class="external-link"
href="http://maven.apache.org/developers/release/apache-release.html">original
guide</a>
-<blockquote>
-<p>If you click on your repository, a tree view will appear below. You can
then browse the contents to ensure the artifacts are as you expect them. Pay
particular attention to the existence of *.asc (signature) files. If the you
don't like the content of the repository, right click your repository and
choose "Drop". You can then rollback your release and repeat the process.<br
clear="none">
-Note the repository URL, you will need this in your vote
email.</p></blockquote></li><li>Stage the maven generated site<br clear="none">
-Note that the -Prelease profile is needed to specify the profile in
settings.xml that configures the staging location.<br clear="none">
-Build the site from the tag that release:perform checked out into
target/checkout in the previous step.
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-cd target/checkout
+</div></div></li><li><p>Perform the release to the staging repo</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[mvn release:perform
+]]></script>
+</div></div><p>This uses both the activemq release profile which directs
building source jars, javadoc jars, and signing everything, and also the
settings release profile that says where to<br clear="none"> put stuff and how
to sign it.</p></li><li>Close the staging repository<br clear="none"> Quote
from the <a shape="rect" class="external-link"
href="http://maven.apache.org/developers/release/apache-release.html">Maven
release guide for Apache projects</a><blockquote><p>Login to <a shape="rect"
class="external-link"
href="https://repository.apache.org">https://repository.apache.org</a> using
your Apache LDAP credentials. Click on "Staging". Then click on "maven" in the
list of repositories. In the panel below you should see an open repository that
is linked to your username and ip. Right click on this repository and select
"Close". This will close the repository from future deployments and make it
available for others to view. If you are staging multiple releases together,
skip thi
s step until you have staged everything. Enter the name and version of the
artifact being released in the "Description" field and then click "Close". This
will make it easier to identify it later.</p></blockquote>See the image in the
original guide for more info.</li><li>Verify staged artifacts<br clear="none">
Quote from the <a shape="rect" class="external-link"
href="http://maven.apache.org/developers/release/apache-release.html">original
guide</a><blockquote><p>If you click on your repository, a tree view will
appear below. You can then browse the contents to ensure the artifacts are as
you expect them. Pay particular attention to the existence of *.asc (signature)
files. If the you don't like the content of the repository, right click your
repository and choose "Drop". You can then rollback your release and repeat the
process.<br clear="none"> Note the repository URL, you will need this in your
vote email.</p></blockquote></li><li><p>Stage the maven generated site<br
clear="none
"> Note that the -Prelease profile is needed to specify the profile in
settings.xml that configures the staging location.<br clear="none"> Build the
site from the tag that release:perform checked out into target/checkout in the
previous step.</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[cd target/checkout
mvn site site:deploy -Prelease
]]></script>
-</div></div>
-This will copy to the staging.siteURL set up in your settings.xml release
profile.</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</li><li>replicate the
contents of mvn apache-activemq/<version> directory to the dist website
on people.apache.org
-<div class="preformatted panel" style="border-width: 1px;"><div
class="preformattedContent panelContent">
+</div></div><p>This will copy to the staging.siteURL set up in your
settings.xml release profile.</p></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</li><li><p>replicate the contents of mvn
apache-activemq/<version> directory to the dist website on
people.apache.org</p><div class="preformatted panel" style="border-width:
1px;"><div class="preformattedContent panelContent">
<pre>ssh [apacheId]@people.apache.org
mdir siteUpdate;cd siteUpdate
curl --remote-name-all
https://repository.apache.org/content/repositories/releases/org/apache/activemq/activemq-parent/<version>/activemq-parent-<version>{.pom,-source-release.zip}{.asc,.asc.md5,.asc.sha1,.sha1,.md5,}
@@ -222,8 +167,7 @@ mkdir /www/www.apache.org/dist/activemq/
mv * /www/www.apache.org/dist/activemq/apache-activemq/<version>
chmod -R g+w /www/www.apache.org/dist/activemq/apache-activemq/<version>
</pre>
-</div></div></li><li>Populate the schema site in svn
-<div class="preformatted panel" style="border-width: 1px;"><div
class="preformattedContent panelContent">
+</div></div></li><li><p>Populate the schema site in svn</p><div
class="preformatted panel" style="border-width: 1px;"><div
class="preformattedContent panelContent">
<pre>svn co
https://svn.apache.org/repos/infra/websites/production/activemq/content
cd content/schema/core
curl --remote-name-all
https://repository.apache.org/content/repositories/releases/org/apache/activemq/activemq-spring/<version>/activemq-spring-<version>{-schema.html,.xsd}{.asc,.asc.md5,.asc.sha1,.sha1,.md5,}
@@ -233,14 +177,7 @@ svn rm activemq-core.xsd
ln -s activemq-core-5.9.0.xsd activemq-core.xsd
and commit once it looks good.
</pre>
-</div></div></li><li>Continue with the Announcing section
below</li><li>Created a in progress wiki page for the next release</li></ol>
-
-
-<h2 id="ReleaseGuide-AnnouncingtheActiveMQRelease">Announcing the ActiveMQ
Release</h2>
-
-<ol><li>Perform a release in JIRA and create a new release version in JIRA.
- <ol><li>Move unresolved issues to the next release first, in a bulk (do
not send email) update</li><li>You might also want to search for
resolved/closed issues with no fix version just in case</li></ol>
- </li><li>Create a download page for the release in the WIKI similar
like the <a shape="rect" href="activemq-530-release.html">ActiveMQ 5.3.0
Release</a></li><li>Update the <a shape="rect" href="xml-reference.html">Xml
Reference</a> page with a link to the HTML and XSD</li><li>Update latest
release link on home page</li><li>Update <a shape="rect"
href="quicklinks.html">QuickLinks</a> and <a shape="rect"
href="javadocs.html">JavaDocs</a> pages</li><li>Mail the <a shape="rect"
class="external-link" href="mailto:[email protected]"
rel="nofollow">dev</a> & <a shape="rect" class="external-link"
href="mailto:[email protected]" rel="nofollow">user</a>
lists</li><li><a shape="rect" class="external-link"
href="http://cwiki.apache.org/confluence/pages/viewrecentblogposts.action?key=ACTIVEMQ">Post</a>
a news entry on the WIKI</li><li>tweet</li><li>Have a beer! <img
class="emoticon emoticon-smile"
src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8
580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/smile.png"
data-emoticon-name="smile" alt="(smile)"></li></ol></div>
+</div></div></li><li>Continue with the Announcing section
below</li><li>Created a in progress wiki page for the next release</li></ol><h2
id="ReleaseGuide-AnnouncingtheActiveMQRelease">Announcing the ActiveMQ
Release</h2><ol><li>Perform a release in JIRA and create a new release version
in JIRA.<ol><li>Move unresolved issues to the next release first, in a bulk (do
not send email) update</li><li>You might also want to search for
resolved/closed issues with no fix version just in
case</li></ol></li><li>Create a download page for the release in the WIKI
similar like the <a shape="rect" href="activemq-530-release.html">ActiveMQ
5.3.0 Release</a>; also update the main <a shape="rect"
href="download.html">Download</a> page as appropriate</li><li>Update the <a
shape="rect" href="xml-reference.html">Xml Reference</a> page with a link to
the HTML and XSD</li><li>Update latest release link on home page</li><li>Update
<a shape="rect" href="quicklinks.html">QuickLinks</a> and <a shape="rect" h
ref="javadocs.html">JavaDocs</a> pages</li><li>Mail the <a shape="rect"
class="external-link" href="mailto:[email protected]"
rel="nofollow">dev</a> & <a shape="rect" class="external-link"
href="mailto:[email protected]" rel="nofollow">user</a>
lists</li><li><a shape="rect" class="external-link"
href="http://cwiki.apache.org/confluence/pages/viewrecentblogposts.action?key=ACTIVEMQ">Post</a>
a news entry on the WIKI</li><li>tweet</li><li>Have a beer! <img
class="emoticon emoticon-smile"
src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/smile.png"
data-emoticon-name="smile" alt="(smile)"></li></ol></div>
</td>
<td valign="top">
<div class="navigation">