Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

    • Build Repository (corresponding release branch)
    • Deploy target path (rsync) of both p2 and product task
    • Plan name
  1. Publish a few release candidates for testing. Test! One aspect of testing is to assign demo videos to everyone to walk through. Make sure to create tickets for them so that everyone records his findings somewhere.
  2. Proclaim a commit freeze on the release branch. Once all tickets are fixed, no one has any business pushing stuff into the release branch anymore!
  3. Update top-level update site. This is done by adding the new update site URL to compositeArtifacts.xml and compositeContent.xml. These two files are in /home/kieler/public_html/updatesite.
  4. Create a tag of the release.
  5. Publish release nodes and update download links in:
  6. Close the Jira version, set the new default version, and add a new version.
  7. Send the word out to the mailing list and do a release party!