Release Suggestions
This is a list of suggested tasks one might perform when preparing for a release.
Check Quality of Artifacts
- Run
ant clean test
- Check that Solr works on the latest versions of Jetty, Tomcat, and Resin.
- Make sure the src/maven artifact templates are in sync with the dependencies in the Ant build file.
- Make sure the Ant sign-artifacts target is in sync with all of the artifacts that are created. All released artifacts should be signed.
- Run RAT on the source
|
ant rat-sources
| http://incubator.apache.org/rat/| | | see https://issues.apache.org/jira/browse/SOLR-762|
- Check that we include all pertinent license files and that NOTICE.txt is in order.
- Check that release tgz/zip files looks ok - e.g. uncompress them, run example, work through the steps of the tutorial, ensure that the javadocs are readable, etc...
- Check if documentation needs an update, update release date in CHANGES.txt and add any necessary notes on upgrading.
Misc Housekeeping
- Start a new section in CHANGES.txt
- Is your Key in the KEYS file? |
| see people.apache.org:/www/www.apache.org/dist/lucene/solr/KEYS and http://www.apache.org/dev/release-signing.html|
JIRA Housekeeping
- Double Check that there are no remaining unresolved Jira issues with the upcoming version number listed as the Fix version
- Double Check that there are no Fixed Jira issues missing a Fix Version that should be marked as Fixed in this release.
- Mark the version as released in Jira (noting the release date)
- Create the next version in Jira (if it doesn't already exist)
- Go to Jira and find all issues that were Fixed in the release you just made, whose Status is Resolved, and do a bulk change to close all of these issues. |
| Uncheck the box that says "send an email for these changes"|
Publicity
- update FreshMeat |
| Yonik owns the project on Freshmeat, he may need to do this one|
- TheServerSide blurb
- Blog away!