|
Last update : August 31 2002
Doc for : v1.4.1
About
What is Cactus ?
News
Changes
Features/Status
Goals
Roadmap/Todo
Contributors
Contributing
Cactus Users
Tested on ...
License
Downloads
Downloads
Documentation
How it works ?
Getting Started
Mock vs Container
Javadocs
FAQ
Howto Guides
Classpath Howto
Config Howto
Migration Howto
TestCase Howto
Jsp Howto
Runner Howto
Security Howto
Ant Howto
HttpUnit Howto
Sample Howto
EJB Howto
IDE Howto
Tomcat Howto
JUnitEE Howto
Support
Bug database
Mailing list
Misc.
Why the name ?
Logo Challenge
Resources
Test Coverage
Stats
Developers
CVS
Coding Conventions
Build results
Release Checklist
|
Release Checklist |
Checklist of tasks to perform for each release:
-
Ensure that the Cactus tests have been run on several application
servers and update the Tested On
page accordingly.
-
Ensure that the Todo page has no more items for the current version.
-
Ensure that the Cactus web site is up to date with the new release.
-
Ensure you have added a news item for the new Cactus release on
the News page.
-
Edit the
build.xml file for each Cactus subprojects and
modify the project.version Ant property so that it
reflects the version number for the release. Commit the changes.
-
CVS Checkout a clean copy of Cactus so that no local files are
included in the distribution and to verify it really works.
-
Make sure you turn Clover on (enable it in
build.properties ). Otherwise, test coverage reports will
not be generated on the Cactus web site.
-
Build the Cactus release for all Servlet APIs (
ant
release ). Note: Make sure you are connected to the internet
when building the releases as the documentation subproject needs the
CVS logs for the changes page.
-
Build the source release (
ant release.src ).
-
Install each delivered release on your local computer and try running
the Sample application tests for one application server.
-
(optional) Create a zipped packaged version of Ant containing all the
jars needed to build Cactus in its
lib/ directory. Name
it jakarta-cactus-ant-<version of
Ant>-<date>.zip .
-
Upload the Cactus releases (for all Servlet APIs and the source one)
and the zipped Ant distribution to
jakarta.apache.org ,
putting them in a
/www/jakarta.apache.org/builds/jakarta-cactus/release/<version>
directory.
-
Upload the Cactus website by running
ant -f
build-admin.xml deploy in the Cactus directory.
-
Tag the CVS HEAD with a new release tag named
CACTUS_<version>_RELEASE (ex:
CACTUS_14_RELEASE ).
-
Announce the release on the following locations (see below for the
announcement template):
-
Jakarta WebSite: Modify the Jakarta Website to contain the
announcement.
-
Cactus user mailing list: Send the announcement there with a
subject of
[Announce] Cactus <version> has been
released .
-
Jakarta Announcement mailing list
(
announcements@jakarta.apache.org ): Send the
announcement there with a subject of [Announce] Cactus
<version> has been released .
-
Prepare the next version by editing again the different Cactus
build.xml files and modifying the
project.version with the new development version
(for example after releasing 1.4, the new development version is
1.5dev).
|
Announcement template |
The Cactus project is pleased to announce the release of Version <version>
Cactus is a unit testing framework for testing server side java code.
<Some comment specific to this release>
Please check the Changes page (http://jakarta.apache.org/cactus/changes.html)
for a full list of the changes in version <version>. Existing users of
Cactus <version-1> can also check the Migration page
(http://jakarta.apache.org/cactus/howto_migration.html) which explains how to
migrate from the previous vesion to this new version.
For more information about Cactus, please visit: http://jakarta.apache.org/cactus/.
|
|
|
|