...
| Note |
|---|
Release may take up to 4 6 hours. Make sure you have time before you start |
| Note |
|---|
Sometimes, the maven-release-plugin has trouble releasing the core module (the compiler seems to fail). In order to release manually, follow these steps:
|
| Note |
Sometimes, you might get a message saying
|
...
- Follow the guide on closing a staging repository on Codehaus Nexus and releasing a closed staging repository on Codehaus Nexusin order to release the CARGO artifacts to Maven Central.
- Tip: If the staged version was not good, read the instructions for dropping a staging repository on Codehaus Nexus.
- Important: The artifacts cannot be taken back once they've reached Maven Central.
- Log onto Cargo JIRA, release the current version and add the next version.
- Check that the 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 complete
- Make sure the Javadocs for the Core Containers are complete
- Make sure the documentation for each container is up to date.
- The source files (that you need to import using the Insert -> Wiki markup option in each container's page manually) are generated in
core/documentation/target/[container's name].log. - If the web page in http://cargo.codehaus.org/ is not updated directly, add the ?nc=1 option to the end of the URL; for example http://cargo.codehaus.org/Jetty+7.x?nc=1
- The source files (that you need to import using the Insert -> Wiki markup option in each container's page manually) are generated in
- Make sure the Containers with DataSource and Resource supportis up to date.
- The source file (that you need to import using the Insert -> Wiki markup option manually) is generated in
core/documentation/target/datasource.log. - If the web page in http://cargo.codehaus.org/ is not updated directly, add the ?nc=1 option to the end of the URL; i.e. http://cargo.codehaus.org/DataSource+and+Resource+Support
- The source file (that you need to import using the Insert -> Wiki markup option manually) is generated in
- Make sure the Project Structureis up to date.
- The source file (that you need to import using the Insert -> Wiki markup option manually) is generated in
core/documentation/target/project-structure.log. - If the web page in http://cargo.codehaus.org/ is not updated directly, add the ?nc=1 option to the end of the URL; i.e. http://cargo.codehaus.org/Project+Structure?nc=1
- The source file (that you need to import using the Insert -> Wiki markup option manually) is generated in
- Modify the Home page to update the available version number and release date
- Modify the Maven2 Plugin Installation page to have the latest
SNAPSHOTversion in there - Create a blog post
- Export the wiki to a zipped HTML file (select all pages except for the Downloads (including all subsections) and News pages) 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 Home and Downloads pages page to update the download links, available version number, documentation and release note links
- Export the wiki to a zipped HTML file (select all pages except for the Downloads page) and add it the Downloads page
- Modify the status on the home page about the delivery:
- Send an announcement email to Cargo mailing lists ... and to other relevent sites you know about. Mailing lists of some servers can also be interesting.
- Create a blog post
| Info | ||
|---|---|---|
| ||
To insert content using Wiki Markup:
|
