Release Process
This document will outline some common tasks that need to be accomplished when releasing a new version of PHPEclipse. Many of the items are pretty obvious, but some are requests from our user community. All are important in making a new releases of PHPEclipse consisting with other releases.
Release Steps
- Prepare Press Release Prepare a document that outlines the new release and the features or big bugs that are fixed. Make sure to give credit to all those that have contributed time in fixing bugs or validating the bugs/fixes. Also note any know issues, and when it's planned on them being fixed.
- Check that current version has tag.
Before starting anything make sure that trunk has been tagged from the previous release. Someone may not like this guide and do a release without tagging it. Releases are build from the tags... or so they should be. (ed_mann is responsible for the builds). - Merge branch into trunk.
If the release is coming for a branch you will need to merge the branch into trunk. (duh!). - Tag trunk
Once the merge from branch is done, if needed, tag trunk as the new release ie (1.3.0). - Build release from hudson.
Hudson has a project for releases. It will update our production Eclipse update site, and also build a src tar-ball. The src tar-ball is provided for the distributors that would like to compile PHPEclipse to include in their distribution. The src tar-ball will be uploaded to SourceForge?, but as of now you will need to manually include it in the project releases. Maybe this can be automated as well? Also this may update mirror sites that are mirroring PHPEclipse update site. This will start after we start signing our releases. Just noted here so i remember to do it and others bug me about it... maybe i should open a new ticket? - Issue Press Release
Once all the above has been completed issue the Press Release and watch the server get flooded with people updating to the latest and greatest release of PHPEclipse.
