[CONF] Apache ActiveMQ > Release Guide
Title: Message Title
Robbie Gemmell edited a page
Release Guide
...
Verify the to-be-released version identifier exists in the META-INF/spring.schemas mappings file AND activemq-osgi/src/main/resources/META-INF/spring.schemas file, if not add it and commit. It should contain:
Code Block
http\://activemq.apache.org/schema/core/activemq-core-${pom.version}.xsd=activemq.xsd
Verify headers with rat
Code Block
mvn -e apache-rat:check
grep -e ' !?' target/rat.txt -- will show any files without licenses
Do a release dry run to check for problems
Code Block
mvn release:prepare -DdryRun=true
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:
Code Block
mvn release:clean
Prepare the release
Code Block
mvn release:prepare
This will create the tag in git and leave various stuff around locally to direct the perform phase.
Make a local copy of the release configuration in case something goes wrong
Code Block
cd ..
cp -r activemq-release activemq-release-prepared
cd activemq-release
Perform the release to the staging repo
Code Block
mvn release:perform
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 put stuff and how to sign it.
Close the staging repository Quote from the Maven release guide for Apache projects
Login to https://repository.apache.org 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.
See the image in the original guide for more info.
Verify staged artifacts Quote from the original guide
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. Note the repository URL, you will need this in your vote email.
Build the site from the tag that release:perform checked out into target/checkout in the previous step. Note that the -Prelease profile is needed to specify the profile in settings.xml that configures the staging location.
Code Block
cd target/checkout
mvn site -Prelease
Populate the Javadocs site in svn
No Format
svn co https://svn.apache.org/repos/infra/websites/production/activemq/content
cd content/maven
mkdir
#copy over apidocs folder that was created by the site plugin to /apidocs
svn add
svn rm apidocs
ln -s /apidocs apidocs
svn add apidocs
# and commit once it looks good.
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:
No Format
svn co https://dist.apache.org/repos/dist/dev/activemq/activemq/
cd activemq
./prepare-release.sh
# Example: ./prepare-release.sh https://repository.apache.org/content/repositories/orgapacheactivemq-1149 5.15.1
svn add
and commit once it looks good.
Call a vote on the dev list, listing the great new features of the release.
After ... the vote passes
Promote the release (i.e. release the staging repository): login to https://repository.apache.org, navigate to the staging repository and click the "release" button.
After it passes, copy Copy the staged release files from the SVN dist dev folder to the SVN dist release folder: https://dist.apache.org/repos/dist/release/activemq/
No Format
svn cp -m "add files for activemq-" https://dist.apache.org/repos/dist/dev/activemq/activemq/ https://dist.apache.org/repos/dist/release/activemq/
# 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
Populate the schema site in svn
No Format
svn co https://svn.apache.org/repos/infra/websites/production/activemq/content
cd content/schema/core
curl --remote-name-all
[CONF] Apache ActiveMQ > Release Guide
Title: Message Title
Robbie Gemmell edited a page
Release Guide
...
Verify the to-be-released version identifier exists in the META-INF/spring.schemas mappings file AND activemq-osgi/src/main/resources/META-INF/spring.schemas file, if not add it and commit. It should contain:
Code Block
http\://activemq.apache.org/schema/core/activemq-core-${pom.version}.xsd=activemq.xsd
Verify headers with rat
Code Block
mvn -e apache-rat:check
grep -e ' !?' target/rat.txt -- will show any files without licenses
Do a release dry run to check for problems
Code Block
mvn release:prepare -DdryRun=true
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:
Code Block
mvn release:clean
Prepare the release
Code Block
mvn release:prepare
This will create the tag in git and leave various stuff around locally to direct the perform phase.
Make a local copy of the release configuration in case something goes wrong
Code Block
cd ..
cp -r activemq-release activemq-release-prepared
cd activemq-release
Perform the release to the staging repo
Code Block
mvn release:perform
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 put stuff and how to sign it.
Close the staging repository Quote from the Maven release guide for Apache projects
Login to https://repository.apache.org 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.
See the image in the original guide for more info.
Verify staged artifacts Quote from the original guide
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. Note the repository URL, you will need this in your vote email.
Build the site from the tag that release:perform checked out into target/checkout in the previous step. Note that the -Prelease profile is needed to specify the profile in settings.xml that configures the staging location.
Code Block
cd target/checkout
mvn site -Prelease
Populate the Javadocs site in svn
No Format
svn co https://svn.apache.org/repos/infra/websites/production/activemq/content
cd content/maven
mkdir
#copy over apidocs folder that was created by the site plugin to /apidocs
svn add
svn rm apidocs
ln -s /apidocs apidocs
svn add apidocs
# and commit once it looks good.
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:
No Format
svn co https://dist.apache.org/repos/dist/dev/activemq/activemq/
cd activemq
./prepare-release.sh
# Example: ./prepare-release.sh https://repository.apache.org/content/repositories/orgapacheactivemq-1149 5.15.1
svn add
and commit once it looks good.
Call a vote on the dev list, listing the great new features of the release.
After it passes, promote the release (i.e. release the staging repository): login to https://repository.apache.org, navigate to the staging repository and click the "release" button.
After it passes, copy the staged release files from the SVN dist dev folder to the SVN dist release folder: https://dist.apache.org/repos/dist/release/activemq/
No Format
svn cp -m "add files for activemq-" https://dist.apache.org/repos/dist/dev/activemq/activemq/ https://dist.apache.org/repos/dist/release/activemq/
# 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
No Format
*** 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 ;cd
curl
[CONF] Apache ActiveMQ > Release Guide
Title: Message Title
Robbie Gemmell edited a page
Release Guide
...
Verify the to-be-released version identifier exists in the META-INF/spring.schemas mappings file AND activemq-osgi/src/main/resources/META-INF/spring.schemas file, if not add it and commit. It should contain:
Code Block
http\://activemq.apache.org/schema/core/activemq-core-${pom.version}.xsd=activemq.xsd
Verify headers with rat
Code Block
mvn -e apache-rat:check
grep -e ' !?' target/rat.txt -- will show any files without licenses
Do a release dry run to check for problems
Code Block
mvn release:prepare -DdryRun=true
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:
Code Block
mvn release:clean
Prepare the release
Code Block
mvn release:prepare
This will create the tag in git and leave various stuff around locally to direct the perform phase.
Make a local copy of the release configuration in case something goes wrong
Code Block
cd ..
cp -r activemq-release activemq-release-prepared
cd activemq-release
Perform the release to the staging repo
Code Block
mvn release:perform
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 put stuff and how to sign it.
Close the staging repository Quote from the Maven release guide for Apache projects
Login to https://repository.apache.org 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.
See the image in the original guide for more info.
Verify staged artifacts Quote from the original guide
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. Note the repository URL, you will need this in your vote email.
Build the site from the tag that release:perform checked out into target/checkout in the previous step. Note that the -Prelease profile is needed to specify the profile in settings.xml that configures the staging location.
Code Block
cd target/checkout
mvn site -Prelease
Populate the Javadocs site in svn
No Format
svn co https://svn.apache.org/repos/infra/websites/production/activemq/content
cd content/maven
mkdir
#copy over apidocs folder that was created by the site plugin to /apidocs
svn add
svn rm apidocs
ln -s /apidocs apidocs
svn add apidocs
# and commit once it looks good.
Download Stage the official releasearchives (src and bin) from the staging repository and prepare them for upload to the Apache dev SVN repo where the official release is staged A script exists that can do this release preparation for you in the Git repo here. If you don't want to use the script the process is fairly simple:
Download the source bundle from the staging site along with it's signature and checksum files.
Download the binary bundles (tar.gz and zip) from the staging site along with their signature and checksum files.
Check the downloaded files using the md5 and or sha1 checksums, then discard the sha1 files.
Check the signatures for all the downloaded files using "gpg --verfiy" or the like.
Update the md5 files by amending them with the actual filename they are associated with, this make validation easier for end users.
Create a new sha512 checksum file for each release artifact using the sha512sum command.
Upload the newly prepared official release artifacts to the dev site artifacts in the SVN dist dev area for folks to test and vote on, using the helper script already in the repo:
No Format
svn co https://dist.apache.org/repos/dist/dev/activemq/activemq/
cd activemq
mkdir ;cd./prepare-release.sh
[CONF] Apache ActiveMQ > Release Guide
Title: Message Title
Christopher L. Shannon edited a page
Release Guide
...
Verify the to-be-released version identifier exists in the META-INF/spring.schemaschemas mappings file AND activemq-osgi/src/main/resources/META-INF/spring.schemas file, if not add it and commit. It should contain:
Code Block
http\://activemq.apache.org/schema/core/activemq-core-${pom.version}.xsd=activemq.xsd
Verify headers with rat
Code Block
mvn -e apache-rat:check
grep -e ' !?' target/rat.txt -- will show any files without licenses
Do a release dry run to check for problems
Code Block
mvn release:prepare -DdryRun=true
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:
Code Block
mvn release:clean
Prepare the release
Code Block
mvn release:prepare
This will create the tag in git and leave various stuff around locally to direct the perform phase.
Make a local copy of the release configuration in case something goes wrong
Code Block
cd ..
cp -r activemq-release activemq-release-prepared
cd activemq-release
Perform the release to the staging repo
Code Block
mvn release:perform
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 put stuff and how to sign it.
Close the staging repository Quote from the Maven release guide for Apache projects
Login to https://repository.apache.org 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.
See the image in the original guide for more info.
Verify staged artifacts Quote from the original guide
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. Note the repository URL, you will need this in your vote email.
Build the site from the tag that release:perform checked out into target/checkout in the previous step. Note that the -Prelease profile is needed to specify the profile in settings.xml that configures the staging location.
Code Block
cd target/checkout
mvn site -Prelease
Populate the Javadocs site in svn
No Format
svn co https://svn.apache.org/repos/infra/websites/production/activemq/content
cd content/maven
mkdir
#copy over apidocs folder that was created by the site plugin to /apidocs
svn add
svn rm apidocs
ln -s /apidocs apidocs
svn add apidocs
# and commit once it looks good.
Call a vote on the dev list, listing the great new features of the release.
After it passes, promote the release (i.e. release the staging repository): login to https://repository.apache.org, navigate to the staging repository and click the "release" button
replicate the contents of mvn apache-activemq/ directory to the dist website on people.apache.org using svn
No Format
ssh [apacheId]@people.apache.org
svn co https://dist.apache.org/repos/dist/release/activemq/
cd activemq
mkdir ;cd
curl --remote-name-all -f https://repository.apache.org/content/repositories/releases/org/apache/activemq/activemq-parent//activemq-parent-{.pom,-source-release.zip}{.asc,.asc.md5,.asc.sha1,.sha1,.md5,}
curl --remote-name-all -f https://repository.apache.org/content/repositories/releases/org/apache/activemq/apache-activemq//apache-activemq-{.pom,-bin.tar.gz,-bin.zip}{.asc,.asc.md5,.asc.sha1,.sha1,.md5,}
svn add .
and commit once it looks good.
Populate the schema site in svn
No Format
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//activemq-spring-{-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
[CONF] Apache ActiveMQ > Release Guide
Title: Message Title
Christopher L. Shannon edited a page
Release Guide
...
Verify the to-be-released version identifier exists in the META-INF/spring.schema mappings file, if not add it and commit. It should contain:
Code Block
http\://activemq.apache.org/schema/core/activemq-core-${pom.version}.xsd=activemq.xsd
Verify headers with rat
Code Block
mvn -e apache-rat:check
grep -e ' !?' target/rat.txt -- will show any files without licenses
Do a release dry run to check for problems
Code Block
mvn release:prepare -DdryRun=true
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:
Code Block
mvn release:clean
Prepare the release
Code Block
mvn release:prepare
This will create the tag in git and leave various stuff around locally to direct the perform phase.
Make a local copy of the release configuration in case something goes wrong
Code Block
cd ..
cp -r activemq-release activemq-release-prepared
cd activemq-release
Perform the release to the staging repo
Code Block
mvn release:perform
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 put stuff and how to sign it.
Close the staging repository Quote from the Maven release guide for Apache projects
Login to https://repository.apache.org 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.
See the image in the original guide for more info.
Verify staged artifacts Quote from the original guide
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. Note the repository URL, you will need this in your vote email.
Build the site from the tag that release:perform checked out into target/checkout in the previous step. Note that the -Prelease profile is needed to specify the profile in settings.xml that configures the staging location.
Code Block
cd target/checkout
mvn site -Prelease
Populate the Javadocs site in svn
No Format
svn co https://svn.apache.org/repos/infra/websites/production/activemq/content
cd content/maven
mkdir
#copy over apidocs folder that was created by the site plugin to /apidocs
svn add
svn rm apidocs
ln -s /apidocs apidocs
svn add apidocs
# and commit once it looks good.
Call a vote on the dev list, listing the great new features of the release.
After it passes, promote the release (i.e. release the staging repository): login to https://repository.apache.org, navigate to the staging repository and click the "release" button
replicate the contents of mvn apache-activemq/ directory to the dist website on people.apache.org using svn
No Format
ssh [apacheId]@people.apache.org
svn co https://dist.apache.org/repos/dist/release/activemq/
cd activemq
mkdir ;cd
curl --remote-name-all -f https://repository.apache.org/content/repositories/releases/org/apache/activemq/activemq-parent//activemq-parent-{.pom,-source-release.zip}{.asc,.asc.md5,.asc.sha1,.sha1,.md5,}
curl --remote-name-all -f https://repository.apache.org/content/repositories/releases/org/apache/activemq/apache-activemq//apache-activemq-{.pom,-bin.tar.gz,-bin.zip}{.asc,.asc.md5,.asc.sha1,.sha1,.md5,}
svn add .
and commit once it looks good.
Populate the schema site in svn
No Format
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//activemq-spring-{-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
[CONF] Apache ActiveMQ > Release Guide
Title: Message Title
Christopher L. Shannon edited a page
Release Guide
...
Verify the to-be-released version identifier exists in the META-INF/spring.schema mappings file, if not add it and commit. It should contain:
Code Block
http\://activemq.apache.org/schema/core/activemq-core-${pom.version}.xsd=activemq.xsd
Verify headers with rat
Code Block
mvn -e apache-rat:check
grep -e ' !?' target/rat.txt -- will show any files without licenses
Do a release dry run to check for problems
Code Block
mvn release:prepare -DdryRun=true
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:
Code Block
mvn release:clean
Prepare the release
Code Block
mvn release:prepare
This will create the tag in git and leave various stuff around locally to direct the perform phase.
Make a local copy of the release configuration in case something goes wrong
Code Block
cd ..
cp -r activemq-release activemq-release-prepared
cd activemq-release
Perform the release to the staging repo
Code Block
mvn release:perform
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 put stuff and how to sign it.
Close the staging repository Quote from the Maven release guide for Apache projects
Login to https://repository.apache.org 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.
See the image in the original guide for more info.
Verify staged artifacts Quote from the original guide
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. Note the repository URL, you will need this in your vote email.
Stage Build the maven generated sitesite from the tag that release:perform checked out into target/checkout in the previous step. Note that the -Prelease profile is needed to specify the profile in settings.xml that configures the staging location. Build the site from the tag that release:perform checked out into target/checkout in the previous step.
Code Block
cd target/checkout
mvn site site:deploy -Prelease
This will copy to the staging.siteURL set up in your settings.xml release profile.Populate the Javadocs site in svn
No Format
svn co https://svn.apache.org/repos/infra/websites/production/activemq/content
cd content/maven
mkdir
#copy over apidocs folder that was created by the site plugin to /apidocs
svn add
svn rm apidocs
ln -s /apidocs apidocs
svn add apidocs
# and commit once it looks good.
Call a vote on the dev list, listing the great new features of the release.
After it passes, promote the release (i.e. release the staging repository): login to https://repository.apache.org, navigate to the staging repository and click the "release" button
replicate the contents of mvn apache-activemq/ directory to the dist website on people.apache.org using svn
No Format
ssh [apacheId]@people.apache.org
svn co https://dist.apache.org/repos/dist/release/activemq/
cd activemq
mkdir ;cd
curl --remote-name-all https://repository.apache.org/content/repositories/releases/org/apache/activemq/activemq-parent//activemq-parent-{.pom,-source-release.zip}{.asc,.asc.md5,.asc.sha1,.sha1,.md5,}
curl --remote-name-all https://repository.apache.org/content/repositories/releases/org/apache/activemq/apache-activemq//apache-activemq-{.pom,-bin.tar.gz,-bin.zip}{.asc,.asc.md5,.asc.sha1,.sha1,.md5,}
svn add .
and commit once it looks good.
Populate the schema site in svn
No Format
svn co https://svn.apache.org/repos/infra/websites/production/activemq/content
cd content/schema/core
curl --remote-name-all
[CONF] Apache ActiveMQ Release Guide
Arthur Naseef edited the page:
Release Guide
...
Verify the to-be-released version identifier exists in the META-INF/spring.schema mappings file, if not add it and commit. It should contain:
Code Block
http\://activemq.apache.org/schema/core/activemq-core-${pom.version}.xsd=activemq.xsd
Verify headers with rat
Code Block
mvn -e apache-rat:check
grep -e ' !?' target/rat.txt -- will show any files without licenses
Do a release dry run to check for problems
Code Block
mvn release:prepare -DdryRun=true
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:
Code Block
[CONF] Apache ActiveMQ Release Guide
Arthur Naseef edited the page:
Release Guide
...
Verify the to-be-released version identifier exists in the META-INF/spring.schema mappings file, if not add it and commit. It should contain:
Code Block
http\://activemq.apache.org/schema/core/activemq-core-${pom.version}.xsd=activemq.xsd
Verify headers with rat
Code Block
mvn -e apache-rat:check
grep -e ' !?' target/rat.txt -- will show any files without licenses
Do a release dry run to check for problems
Code Block
mvn release:prepare -DdryRun=true
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:
Code Block
[CONF] Apache ActiveMQ Release Guide
Gary Tully edited the page:
Release Guide
...
Verify the to-be-released version identifier exists in the META-INF/spring.schema mappings file, if not add it and commit. It should contain:
Code Block
http\://activemq.apache.org/schema/core/activemq-core-${pom.version}.xsd=activemq.xsd
Verify headers with rat
Code Block
mvn -e apache-rat:check
grep -e ' !?' target/rat.txt -- will show any files without licenses
Do a release dry run to check for problems
Code Block
mvn release:prepare -DdryRun=true
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:
Code Block
[CONF] Apache ActiveMQ Release Guide
Arthur Naseef edited the page: Release Guide ... Perform a release in JIRA and create a new release version in JIRA. Move unresolved issues to the next release first, in a bulk (do not send email) update You might also want to search for resolved/closed issues with no fix version just in case Create a download page for the release in the WIKI similar like the ActiveMQ 5.3.0 Release; also update the main Download page as appropriate Update the Xml Reference page with a link to the HTML and XSD Update latest release link on home page Change the links for the prior release to reference the archive (athttp://archive.apache.org/dist/activemq/); otherwise, users will not be able to locate the older release for download Update QuickLinks and JavaDocs pages Mail the dev user lists Post a news entry on the WIKI tweet Have a beer! View Online Like View Changes Stop watching space Manage Notifications This message was sent by Atlassian Confluence 5.0.3, Team Collaboration Software
[CONF] Apache ActiveMQ Release Guide
Arthur Naseef edited the page: Release Guide ... Before you deploy anything to the maven repository using Maven 2, you should configure your ~/.m2/settings.xml file 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. Code Block xml settings ... servers server idapache.snapshots.https/id usernamedejanb/username /server !-- To publish a website of some part of Maven -- server idapache.website/id usernamedejanb/username filePermissions664/filePermissions directoryPermissions775/directoryPermissions /server !-- To stage a release of some part of Maven -- server idapache.releases.https/id usernamedejanb/username /server !-- To stage a website of some part of Maven -- server idstagingSite/id !-- must match hard-coded repository identifier in site:stage-deploy -- usernamedejanb/username filePermissions664/filePermissions directoryPermissions775/directoryPermissions /server /servers ... /settings 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 Code Block umask 2 Other shell initialization files may interfere with this setting but if this is the
