Release process

Release process for ObjectLedge.

update ledge-reactor/xdocs/changes.xml
1. add entries from Jira changelog
update ledge-reactor/xdocs/releases.xml
1. copy existing session and do search/replace
update ledge-reactor/xdocs/roadmap.xml
1. fill in release date
2. fill in estimates about next release
update ledge-common/project.xml
project.xml and cvs madness (these could be automated with maven)
1. tag the HEAD revisions of all the files with RELEASE-<version>-ROOT marking release branching point
2. tag -b HEAD revisions of all the files with RELEASE-<version> creating the release branch
3. switch to the branch
4. edit project.xml files and set the <currentVersion> aproprietly
5. edit project.xml files and get rid of SNAPSHOT versions, replacing it with the current release version of modules released together, and a timestamped version otherwise
6. switch to the HEAD
7. edit project.xml files and increment versions
building the release (definetely could be automated with maven)
1. switch to the branch
2. build docs distribution from ledge-reactor
3. build source distribution
4. build binary distribution
5. upload the release
announcements
1. generate with maven
2. edit
3. send

Source release structure.

Archive contains subdirectories for each module, wich in turn contains all non .cvsignore ignored files and directories.
LICENSE.txt and README.txt are included in the root directory.

Documentation release structure.

Compressed multiproject docs from ledge-reactor - contain interlinked docs from all modules.

Binary release structure.

Archive contains directories for each deliverable type: jars, plugins, sources, wars. LICENSE.txt and README.txt are included in the root directory. Sources are zip archives containing java source files for each project that has them.

Source zips could be auto generated on a post hook to java:compile.