This is an automated email from the ASF dual-hosted git repository.
asf-gitbox-commits pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/activemq-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new bbf398c0b Automatic Site Publish by Buildbot
bbf398c0b is described below
commit bbf398c0b516322350d3c872498664b3444c6142
Author: buildbot <[email protected]>
AuthorDate: Mon Aug 3 17:52:06 2026 +0000
Automatic Site Publish by Buildbot
---
.../classic/documentation/release-guide.html | 279 ++++++++++-----------
1 file changed, 139 insertions(+), 140 deletions(-)
diff --git a/output/components/classic/documentation/release-guide.html
b/output/components/classic/documentation/release-guide.html
index 7125feb44..b7e90dd61 100644
--- a/output/components/classic/documentation/release-guide.html
+++ b/output/components/classic/documentation/release-guide.html
@@ -96,51 +96,35 @@
<p>How to create and announce an ActiveMQ release. This release is based on <a
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="maven-2-setup">Maven 2 Setup</h2>
+<h2 id="maven-setup">Maven Setup</h2>
-<p>Before you deploy anything to the maven repository using Maven 2, you
should configure your ~/.m2/settings.xml file<br />
+<p>Before you deploy anything to the maven repository using Maven, you should
configure your ~/.m2/settings.xml file<br />
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="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code><settings>
...
<servers>
<server>
<id>apache.snapshots.https</id>
- <username>dejanb</username>
- </server>
- <!\-\- To publish a website of some part of Maven -->
- <server>
- <id>apache.website</id>
- <username>dejanb</username>
- <filePermissions>664</filePermissions>
- <directoryPermissions>775</directoryPermissions>
+ <username>user</username>
+ <password>password</password>
</server>
- <!\-\- To stage a release of some part of Maven -->
<server>
<id>apache.releases.https</id>
- <username>dejanb</username>
- </server>
- <!\-\- To stage a website of some part of Maven -->
- <server>
- <id>stagingSite</id> <!-- must match hard-coded
repository identifier in site:stage-deploy -->
- <username>dejanb</username>
- <filePermissions>664</filePermissions>
- <directoryPermissions>775</directoryPermissions>
+ <username>user</username>
+ <password>password</password>
</server>
</servers>
...
</settings>
</code></pre></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>
-
-<p>umask 2</p>
-
-<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="additional-local-configuration-for-using-release-and-staging-plugins">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="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code><settings>
<profiles>
<profile>
@@ -156,147 +140,162 @@ so that the file permissions of the deployed artifacts
are group writeable. If y
<h2 id="creating-the-activemq-release">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>
+<p>If the release is the first one on a new series, you might want to create a
branch for the series:</p>
+
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>git branch activemq-a.b.x main
+git push origin activemq-a.b.x
+</code></pre></div></div>
<ol>
- <li>Verify the to-be-released version identifier exists in the <a
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.schemas</a>
mappings file AND <a
href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=blob;f=activemq-osgi/src/main/resources/META-INF/spring.schemas;hb=HEAD";>activemq-osgi/src/main/resources/META-INF/spring.schemas</a>
file, if not add it and commit. It shoul [...]
- <div class="language-plaintext highlighter-rouge"><div
class="highlight"><pre
class="highlight"><code>http://activemq.apache.org/schema/core/activemq-core-${pom.version}.xsd=activemq.xsd
-</code></pre></div> </div>
- </li>
- <li>Verify headers with <a
href="http://incubator.apache.org/rat/apache-rat-plugin/usage.html";>rat</a>
- <div class="language-plaintext highlighter-rouge"><div
class="highlight"><pre class="highlight"><code>mvn -e apache-rat:check
-grep -e ' !?????' target/rat.txt -- will show any files without licenses
-</code></pre></div> </div>
- </li>
- <li>Do a release dry run to check for problems
- <div class="language-plaintext highlighter-rouge"><div
class="highlight"><pre class="highlight"><code>mvn release:prepare -DdryRun=true
-</code></pre></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="language-plaintext highlighter-rouge"><div
class="highlight"><pre class="highlight"><code>mvn release:clean
-</code></pre></div> </div>
- </li>
- <li>Prepare the release
- <div class="language-plaintext highlighter-rouge"><div
class="highlight"><pre class="highlight"><code>mvn release:prepare
-</code></pre></div> </div>
- <p>This will create the tag in git and leave various stuff around locally
to direct the perform phase.</p>
- </li>
- <li>Make a local copy of the release configuration in case something goes
wrong
- <div class="language-plaintext highlighter-rouge"><div
class="highlight"><pre class="highlight"><code>cd ..
-cp -r activemq-release activemq-release-prepared
-cd activemq-release
-</code></pre></div> </div>
- </li>
- <li>Perform the release to the staging repo
- <div class="language-plaintext highlighter-rouge"><div
class="highlight"><pre class="highlight"><code>mvn release:perform
-</code></pre></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 />
-put stuff and how to sign it.</p>
- </li>
- <li>
- <p>Close the staging repository<br />
-Quote from the <a
href="http://maven.apache.org/developers/release/apache-release.html";>Maven
release guide for Apache projects</a></p>
+ <li>As ActiveMQ protects branches, you have to create a release branch based
on the branch you want to release:</li>
+</ol>
- <blockquote>
- <p>Login to <a
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 [...]
- </blockquote>
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>git branch release/a.b.c activemq-a.b.x
+git push origin release/a.b.c
+</code></pre></div></div>
- <p>See the image in the original guide for more info.</p>
+<ol>
+ <li>[Optional] You can do a verification build on the <code
class="language-plaintext highlighter-rouge">activemq-a.b.c</code> branch:</li>
+</ol>
+
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>mvn verify
+</code></pre></div></div>
+
+<p>Especially, it should not complain about missing license header (rat) and
the build should pass without error.</p>
+
+<ol>
+ <li>You can now go on the release branch and prepare the release:</li>
+</ol>
+
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>git checkout release/a.b.c
+mvn release:prepare -Papache-release,deploy
+</code></pre></div></div>
+
+<p>This create the RC tag.</p>
+
+<ol>
+ <li>Now we can stage the release:</li>
+</ol>
+
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>mvn release:perform -Papache-release,deploy
+</code></pre></div></div>
+
+<p>It creates a staging repository on Nexus
(https://repository.apache.org).</p>
+
+<ol>
+ <li>
+ <p>You can close the staging repository on Nexus. Go on
https://repository.apache.org, in the Staging Repositories menu and close the
ActiveMQ staging repository.</p>
</li>
<li>
- <p>Verify staged artifacts<br />
-Quote from the <a
href="http://maven.apache.org/developers/release/apache-release.html";>original
guide</a></p>
-
- <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 />
-Note the repository URL, you will need this in your vote email.</p>
- </blockquote>
+ <p>Now, you can stage the release artifacts on Dist:</p>
</li>
- <li>Build the site from the tag that release:perform checked out into
target/checkout in the previous step.<br />
-Note that the -Prelease profile is needed to specify the profile in
settings.xml that configures the staging location.
- <div class="language-plaintext highlighter-rouge"><div
class="highlight"><pre class="highlight"><code>cd target/checkout
-mvn site -Prelease
-</code></pre></div> </div>
+</ol>
+
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>svn co
https://dist.apache.org/repos/dist/dev/activemq/activemq
+cd activemq
+./prepare-release.sh <nexus-staging-repo-url> <version>
+svn add <version>
+svn commit
+</code></pre></div></div>
+
+<ol>
+ <li>
+ <p>Create the pre-release on GitHub
(https://github.com/apache/activemq/releases/new) using the corresponding tags
and using “Apache ActiveMQ a.b.c” as release title.</p>
</li>
- <li>Populate the Javadocs site in svn
- <code class="language-plaintext highlighter-rouge">
- svn co
https://svn.apache.org/repos/infra/websites/production/activemq/content
- cd content/maven
- mkdir <version>
- #copy over apidocs folder that was created by the site plugin to
<version>/apidocs
- svn add <version>
- svn rm apidocs
- ln -s <version>/apidocs apidocs
- svn add apidocs
- # and commit once it looks good.
- </code></li>
<li>
- <p>Stage the official release artifacts in the SVN dist dev area for folks
to test and vote on, using the helper script already in the repo:
- <code class="language-plaintext highlighter-rouge">
- svn co https://dist.apache.org/repos/dist/dev/activemq/activemq/
- cd activemq
- ./prepare-release.sh <nexus-staging-repo-url> <version>
- # Example: ./prepare-release.sh
https://repository.apache.org/content/repositories/orgapacheactivemq-1149 5.15.1
- svn add <version>
- </code>
- and commit once it looks good.</p>
+ <p>Call a vote on the dev mailing list, with this template:</p>
</li>
- <li>Call a vote on the dev list, listing the great new features of the
release.</li>
</ol>
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>Subject: [VOTE] Apache ActiveMQ 6.2.7 release (rcN)
+
+Hi everyone,
+
+I propose Apache ActiveMQ a.b.c (rcN) release for your vote.
+
+This release includes:
+- ...
+
+You can review the Pre-Release Notes for details:
+https://github.com/apache/activemq/releases/tag/activemq-a.b.c
+
+Staging Maven Repository:
+https://repository.apache.org/content/repositories/orgapacheactivemq-xxxx/
+
+Staging Dist Repository:
+https://dist.apache.org/repos/dist/dev/activemq/activemq/a.b.c/
+
+Git tag:
+https://github.com/apache/activemq/tree/activemq-a.b.c
+
+Please vote to approve this release:
+[ ] +1 Approve the release
+[ ] 0 I don't care
+[ ] -1 Don't approve the release (please provide specific comment)
+
+This vote will be open for at least 72 hours.
+
+Thanks!
+Regards
+</code></pre></div></div>
+
<h2 id="after-the-vote-passes">After the vote passes</h2>
<ol>
- <li>Promote the release (i.e. release the staging repository): login to<a
href="https://repository.apache.org/";>https://repository.apache.org</a>,
navigate to the staging repository and click the “release” button. </li>
- <li>Copy the staged release files from the SVN dist dev folder to the SVN
dist release folder: <a
href="https://dist.apache.org/repos/dist/release/activemq/";>https://dist.apache.org/repos/dist/release/activemq/</a>
- <div class="language-plaintext highlighter-rouge"><div
class="highlight"><pre class="highlight"><code>svn cp -m "add files for
activemq-<version>"
https://dist.apache.org/repos/dist/dev/activemq/activemq/<version>
https://dist.apache.org/repos/dist/release/activemq/<version>
-# Example: svn cp -m "add files for activemq-5.15.1"
https://dist.apache.org/repos/dist/dev/activemq/activemq/5.15.1
https://dist.apache.org/repos/dist/release/activemq/5.15.1
-</code></pre></div> </div>
+ <li>
+ <p>Promote the release on Nexus (https://repository.apache.org).</p>
</li>
- <li>Populate the schema site in svn
- <div class="language-plaintext highlighter-rouge"><div
class="highlight"><pre class="highlight"><code>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,}
-for i in activemq-spring-5.9.0*; do mv -- "$i" "${i//spring/core}"; done;
-svn add activemq-core-5.9.0*
-svn rm activemq-core.xsd
-ln -s activemq-core-5.9.0.xsd activemq-core.xsd
-svn add activemq-core.xsd
-# and commit once it looks good.
-</code></pre></div> </div>
+ <li>
+ <p>Promote the release on Dist:</p>
</li>
- <li>Continue with the Announcing section below</li>
- <li>Created a in progress wiki page for the next release</li>
- <li>Remove any releases from the dist site that are no longer supported and
update the wiki page for that release to point to the archives for
downloads.</li>
</ol>
-<h2 id="announcing-the-activemq-release">Announcing the ActiveMQ Release</h2>
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>svn mv
https://dist.apache.org/repos/dist/dev/activemq/activemq/<version>
https://dist.apache.org/repos/dist/release/activemq/
+</code></pre></div></div>
<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>
+ <p>Change the release on GitHub removing the pre-release tag
(https://github.com/apache/activemq/releases/edit/activemq-a.b.c).</p>
</li>
- <li>Create a download page for the realease by adding a file in <code
class="language-plaintext highlighter-rouge">src/_releases/</code> and name the
file with its version converted to an integer - for example the file for 5.16.1
should be name <code class="language-plaintext
highlighter-rouge">activemq-5016001-release.md</code>. The Front Matter must
include <code class="language-plaintext highlighter-rouge">version</code>,
<code class="language-plaintext highlighter-rouge">release_no [...]
- <div class="language-plaintext highlighter-rouge"><div
class="highlight"><pre class="highlight"><code>---
-version: 5.16.1
-release_notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12347027
-release_date: Jan 20, 2021
-title: ActiveMQ 5.16.1 Release
----
-Apache ActiveMQ was released on . It fully supports JDK 9+ at runtime and
includes several resolved [issues]() and bug fixes.
-</code></pre></div> </div>
+ <li>
+ <p>Update the website with release:</p>
</li>
- <li>If necessary, update the current versions by editing the <code
class="language-plaintext highlighter-rouge">5x</code> list in <code
class="language-plaintext
highlighter-rouge">src/_data/current_releases.yml</code>. The latest patch
release published in <code class="language-plaintext
highlighter-rouge">src/_releases/</code> for the major.minor versions in the
list will automatically be included on the <a
href="https://activemq.apache.org/components/classic/download/";>download page
[...]
- <li>Update the <a href="xml-reference">Xml Reference</a> page with a link to
the HTML and XSD</li>
- <li>Update <a href="quicklinks">QuickLinks</a> and <a
href="docs">JavaDocs</a> pages</li>
- <li>Mail the <a href="mailto:[email protected]";>dev</a> & <a
href="mailto:[email protected]";>user</a> lists</li>
- <li><a
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!</li>
</ol>
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>git clone https://github.com/apache/activemq-website
+cd activemq-website/src/_classic_releases
+vi classic-0a-0b-0c.md
+git add
+git commit -a
+git push
+</code></pre></div></div>
+
+<ol>
+ <li>Announce the release on the dev mailing list and
[email protected]:</li>
+</ol>
+
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>Subject: [ANNOUNCE] Apache ActiveMQ a.b.c has been
released!
+
+The ActiveMQ team is pleased to announce the Apache ActiveMQ a.b.c release.
+
+<Quickly describe the release>
+
+You view find the details on the Release page:
+https://activemq.apache.org/components/classic/download/classic-0a-0b-0c
+
+And also more details on the Release Notes:
+https://github.com/apache/activemq/releases/tag/activemq-a.b.c
+
+You can download ActiveMQ a.b.c here:
+https://activemq.apache.org/components/classic/download/
+
+Enjoy!
+
+Regards
+--
+The Apache ActiveMQ team
+</code></pre></div></div>
+
</div>
</div>
</div>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
