FOray
| FOray Users |
| Module Users |
| Developers |
| Development Home | |
| View Repository | |
| Wiki | |
| Submit a Patch | |
| Development Blog | |
| Environment | |
| Extensions | |
| Testing | |
| FOrayFont | |
| Notes | |
| Encoding | |
| Planning | |
| FOrayFOTree | |
| Design Notes | |
| FOrayAreaTree | |
| Design Notes | |
| FOrayText | |
| Design Notes | |
| Layout | |
| General Layout | |
| ForayPS | |
| Design Notes | |
| ForayPDF | |
| Design Notes | |
| Administration | |
| Doc | |
| Release Mechanics | |
Powered By:
FOray Dev: Release Mechanics
Contents
This page is a checklist of things that should be done for each code release.
Before
- Make sure all tests pass.
- Make sure that org.foray.core.Application.getVersion() has the correct version number.
- Make sure that the build script build-common has the correct value for the property "version".
- Update the release notes. Commit, but don't publish yet.
- Lock the repository or at least make a note of the repository revision number which should be tagged: _________________.
Build
- Run the "distribution" target of the build script. The distributable output should be in build/distribution.
- The output should contain three files:
- foray-[version]-bin-all.zip
- foray-[version]-bin-modules.zip
- foray-[version]-src.zip
- Run the dist-test.sh shell script. This script looks for potential problems in the distribution files. If any problems are reported, fix them before proceeding.
- Unzip the "bin-all" distribution file, and run both the foray-test.bat batch file and foray-test.sh shell script to ensure basic runnability.
After
- Tag the repository, by copying the trunk revision to tags/rel_[revision], where [revision] is the id of the release being created, periods being converted to underscores. For example, for the 1.0 release, the trunk revision should be copied to "tags/rel_1_0". Enter the name of the tag here: _________________________.
- Unlock the repository, if it was locked above.
- Upload distribution file to sourceforge.
- Download releases and make sure downloaded files are identical to uploaded files.
- Publish website to get the new release notes updated.
- Announce the release at:
- The foray-announce (foray-announce at lists.sourceforge.net), foray-developer (foray-developer at lists.sourceforge.net), and foray-support (foray-support at lists.sourceforge.net) mailing lists.
- www.w3c.org
- www.xslfo.info
- Add "News" item to the SourceForge system announcing the release.
- Consider adding "News" item to the project home page.
- Update org.foray.core.Application.getVersion() and the build.common.xml "version" property to the next release level, with a "-dev" suffix.