...
- All containers with a public download link are automatically tested by the Continous Integration system every time there is a code change:
- Open the CI page and click on the latest build
- First, check if the overall status is PASSED
- Then, click on the build and check for the command with
cat core/samples/java/containers.log
in it (on all threads). It should indicate status0
for all containers:
- For non-publicly-downloadable containers, tests need to be done on your computer. These include:
- JBoss 7.2.x, i.e. JBoss refers to as JBoss Enterprise Application Platform (EAP) version 6.1, and onwards
- Glassfish GlassFish 2.x
- JRun 4.x
- All versions of Orion/OC4J
- All versions of WebLogic
- All versions of WebSphere
...
- Follow the Releasing the Deployment guide in order to close the staging repository
- Send an e-mail to the Codehaus Cargo list so users can try out the new version. We typically leave the vote open for 72 hours.
- Once the developers/users also validate the version as being stable, follow the Releasing the Deployment guide in order to release the staging repository
Note: If the version was not stable, that same guide also explains how to drop it - Log onto Codehaus Cargo JIRA, release the current version and add the next version.
- Check that the Codehaus Cargo wiki is up to date. Specifically, perform the following updates:
- Modify the status on the home page about the delivery:
- Make sure the Containers list is complete.
- Make sure the Navigation page is completeMake sure the Javadocs for the Core Containers are complete.
- Make sure the documentation for each container is up to date.
Note: The source files (that you need to import using the Insert -> Wiki markup option in each container's page manually) are generated incore/documentation/target/[container's name].log
- Make sure the Containers with DataSource and Resource support is up to date.
Note: The source file (that you need to import using the Insert -> Wiki markup option manually) is generated incore/documentation/target/datasource.log
- Make sure the Project Structure is up to date.
Note: The source file (that you need to import using the Insert -> Wiki markup option manually) is generated incore/documentation/target/project-structure.log
- Modify the Home page to update the available version number, the release notes URL the checkbox is pointing to and the release date
- Modify the Maven2 Plugin Installation page to update the
SNAPSHOT
version - Create a blog post
- Export the wiki to a zipped HTML file (select all pages except for the Downloads (including all subsections) page) and add it the Downloads page
- Move the old version to the Archived Downloads page
- Remember to move the old documentation archive from the Downloads page to that page as well
- Modify the Downloads page to update the download links, available version number, documentation and release note links
- Modify the status on the home page about the delivery:
- Check that the Codehaus Cargo Web site is up to date. Specifically, perform the following updates:
- Go to the
generator
subdirectory of the codehaus-cargo.github.io repository and run amvn verify
command to generate the Web site - Download the source code of the tagged version in a temporary location and run a
mvn javadoc:aggregate
command to generate the API documentation - Move the
target/site/apidocs
folder to the root of the codehaus-cargo.github.io repository - Check in and push all changes, this will automatically update the Codehaus Cargo Web site
- Go to the
- Send an announcement email to Cargo mailing lists ... and to other relevant sites you know about. Mailing lists of some servers can also be interesting.
...