Difference between revisions of "WTP Release Tasks"

Revision as of 11:18, 24 March 2018

For each WTP release, there are a few bookkeeping tasks unrelated to planning, development, and building, that also need tending to.

They should be recorded here so they're not forgotten. This document is a Draft.

Tasks for Major and Minor Releases

• Maintenance branch created and wtp-releng@ list notified. NOTE After Photon, this step may no longer be required if all development occurs in master only
• New Help for Old Friends page created, if required
• New and Noteworthy

• New content collected under NewAndNoteworthy

-> appears on releases/*/NewAndNoteworthy 

• index.xml -> appears on development/news/main.php

Tasks for All Releases (including Service Releases)

• R-build GA'd on http://download.eclipse.org/webtools/downloads/, and email sent out declaring it
• Marketplace listing version created/updated for these 3 listings (contact Nitin D. if you want edit privileges, but try to keep the mandatory features to a minimum)
• WTP_FAQ installation instructions updated (add versions/numbers/update sites)

• Web Site Updates:

• /common.php (linking to Java EE package page and release train update site)
• Release landing page created in /releases, what-is-fixed bug query included
• /releases/index.html updated
• News feed entry published in news.xml

• Update releng files w/ new versions/dependencies:

• build-preparation.sh
• parent pom
• dependencies.properties

Project Lead Tasks

Each project lead should perform these tasks for every release.

• Repositories tagged for the release
• Bugs triaged/retargeted out of the release
• Babel repo/branch set/updated for release
• Version value created in Bugzilla