Here is the release process for Lyo. General information on the Eclipse release process is documented at http://wiki.eclipse.org/Development_Resources/HOWTO/Release_Reviews.
Important: This must be done at least 3 weeks before your release date!
- Make sure the Lyo project plans page is current.
- Make sure the release date is set in the project metadata at https://projects.eclipse.org/projects/technology.lyo/releases
- Review and submit the IP log: http://www.eclipse.org/projects/ip_log.php?projectid=technology.lyo
- Put together release review documentation for the release. Look at the Lyo project plans for examples.
- Subscribe to the technology-pmc and lyo-dev mailing lists (if you're not already), otherwise your review request email will bounce!
- Send an email to the email@example.com, firstname.lastname@example.org, and email@example.com requesting the release review. Here is an example: http://dev.eclipse.org/mhonarc/lists/lyo-dev/msg00436.html
When the IP log and release review are approved, you can publish the release. (In the future, we should look at using the Maven release plugin to make this easier.)
Important: Once you publish a release version to repo.eclipse.org, you cannot overwrite it.
Builds are published to repo.eclipse.org from Hudson. If you really need to delete a published release artifact from repo.eclipse.org (not recommended), email Thanh Ha.
Here are the steps to publish a release:
- Remove the SNAPSHOT qualifier from the version numbers in every pom.xml.
- Commit and push the change.
- Update the configuration for Hudson builds for lyo-oslc4j-nightly, lyo-server-nightly, and lyo-client-nightly. These builds have scripts with the version number in them that need to change.
- Run the builds. This will push the binaries to repo.eclipse.org.
- Update the Lyo packaging build, lyo-oslc4j-packaging.
- Run the packaging builds to creates the ZIPs for the downloads page.
- Download the files from the packaging build workspace. Make sure they look right and include the appropriate licenses. Testing the bits is a good idea :)
- Use SFTP to upload the files to build.eclipse.org for the downloads page.
- Update the project homepage and download pages at ssh://<your-id>@git.eclipse.org/gitroot/www.eclipse.org/lyo.git
Yay! The build is public! Now let's tag it and ready development for the next release.
- Create a tag for the release in git (in each Lyo git repository). For instance,
git tag -a 2.0 -m "Lyo 2.0" git push origin 2.0
- Add the next version number with a SNAPSHOT qualifier to every POM file.
- Commit and push the changes.
You're done! That was easy, wasn't it?