Skip to content

Release Instructions

reprogrammer edited this page Jun 18, 2012 · 1 revision

Update site

  1. Remove the following folders and files from edu.illinois.compositerefactorings.updatesite.
    • features/
    • plugins/
    • artifacts.jar
    • content.jar
    • logs.zip
  2. Open edu.illinois.compositerefactorings.updatesite/site.xml in Eclipse.
  3. Remove all the features listed in site.xml but not any categories.
  4. Select the compositerefactorings category in the Site Map. Then, press the Add Feature... button and select edu.illinois.compositerefactorings (1.0.0.qualifier) from the popped up dialog.
  5. Press the button Build.

Publish

  1. Install the new release of compositerefactorings from the local file system into fresh instances of Eclipse to make sure that it installs successfully.
  2. Check whether the update from an old version of compositerefactorings to the new one works.
  3. Copy the contents of the folder edu.illinois.compositerefactorings.updatesite into public_html/updates of the machine hosing the update site.
  4. Repeat the first two steps for the remote update site.

Change Log

Update the change log at the root of the repository by the changes made in the new release. We usually have an issue devoted to releasing a new version of compositerefactorings in which we keep track of the issues that are addressed in the new release. Use the release issue to update the change log. Then, close the release issue.

Tag

  1. Be careful not to delete any build.xml files. For some reason, the build script of the update site sometimes deletes some of the other build scripts.

  2. Commit the changes to the update site and change log. Use a commit message of the following form

     Released v<x>.<y>.<z>.<qualifier>
    
     This commit belongs to issue #<release-issue>.
    

In the above message, <x>, <y>, <z> and <qualifier> are parts of the version of the generated feature, and <release-issue> is the number of the issue devoted to this particular release of compositerefactorings.

  1. Push the commit to the remote repository.

  2. Tag the commit containing the new release using the following command.

     git tag v<x>.<y>.<z>.<qualifier> <commit-sha>
    

Push the created tag to the remote repository using the following command.

    git push --tags
Clone this wiki locally