Releasing

This documentation is defining every steps that needs to be accomplished when releasing Apache IvyDE.In this doc, the released version is denoted as $VERSION, so it HAVE to be replaced in the command line argument accordingly. There is also some $LOGIN which is referencing your login on the Apache machines.

Prepare

Jira

First in Jira make sure that no more issues are opened for the target release.

Release notes

Make sure the release notes and the annoucement are up to date. Look at doc/release-notes.html. Remove there anything which refers to a draft status.

Release branch

Some modifications of the branch are need to do the release. So a new branch is needed:

In order to keep the main dist area of a reasonable size, old releases should be removed. They will disapear from the main dist but will still be available via the archive. To do so, just use the svn rm command against the artifacts or folders to remove.

Deploy the updatesite

Annoucement

The annoucement should have been already prepared and reviewed by other committers. Its content can be found in doc/release-notes.html.

With that content, send a mail to announce@apache.org, ivy-user@ant.apache.org and dev@ant.apache.org with the title "[ANNOUNCE] Apache IvyDE $VERSION released", and with your apache email as sender (announce@ requires it).

Update the documentation

Update the table of content

The table of content needs to be updated so that the last documentation point to that new release.

First we need to update the external links. In svn/site/ivyde/sources/history:

Then svn update your working copy (to retrieve the new history branch).

Update the download page

In the page svn/site/ivyde/sources/download.html change every reference of the old version to the new one.

Deploy

All site editing being done, commit your changes.

And now let's generate the site and deploy it:

generate the part of the site for the new version:

ant generate-history -Dhistory.version=$VERSION

WARNING: that target is modifiying the toc.json in the imported branch so that the generated html have a proper version declared in the toc. You should not commit that change. Once the site has been generated, you may want to revert the changes so you won't commit it by mistake. (TODO: process to improve so we shouldn't worry).

generate the website with the new toc:

ant /all generate-site

you should verify that the site generated in target is OK. And once your happy with it, commit the changes in target (some svn add might be needed !)