WTP Release Tasks

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 is intended as a living document.

Tasks for Major and Minor Releases

• The release should be tagged in all non-releng repositories.
• Maintenance branch may created for future adopter patch builds, but this is not typical with quarterly releases and 3 week milestones. Main development will continue in master for the next quarterly simultaneous release.
• A New Help for Old Friends page created, if required
• June releases typically line up for our mandatory Release Review, and necessitate prepared documentation

Tasks for All Releases (including Service Releases)

Deliverables

• March/September releases coincide with a new Java version: facets need updating
• Copy last RCx to R using WTP Publish job
• R-build GA'd on http://download.eclipse.org/webtools/downloads/, and email sent out declaring it
• EPP packages tested, signed-off on, and +1 sent to epp-dev mailing list

• Eclipse IDE for Java EE Developers: Chuck and Nitin (Java EE Smoke and also manual checks to general layout, preferences etc for changes from integrated features like m2e, oomph etc..)

• Composite site updated via WTP Publish Repo job. Repeat for latest 20xx-yy site
• Marketplace listings 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)
• IRC_FAQ updated

Web site updates

• Make sure packages/org.eclipse.epp.package.jee.feature/epp.website.xml in ssh://{USER}@git.eclipse.org:29418/epp/org.eclipse.epp.packages points to the correct New and Noteworthy
• /common.php (linking to Java EE package page and release train update site)
• /releases/index.html updated to point to newest release
• New release-specific landing page under /releases

• index.xml content -> appears on 3.9.3 page
• Provide link to a report showing Bugs fixed in the release

• New & Noteworthy appears on development/news and its URL listed in PMI
• News feed entry published in news.xml

download.eclipse.org, archive.eclipse.org, build.eclipse.org Site Updates

• Add new versions / remove old versions from: /shared/webtools/committers/buildbranches.php
• Add new versions / remove old versions from: /home/data/httpd/download.eclipse.org/webtools/downloads/buildbranches.php
• Move old releases from download.eclipse.org to archive.eclipse.org. If you don't have permission, open a bug.

• See WTP Retention Policy, then use WTP-Archive job

• Clean out old Jenkins workspaces / saved builds, old builds from http://build.eclipse.org/webtools/committers/, and old builds from http://download.eclipse.org/webtools/downloads/drops/

• Use WTP-Disk-Cleanup job

• Update releng files w/ new versions/dependencies:

• parent pom -> newer Eclipse Platform I build, etc.
• repositories pom -> controls default build stream value (e.g. 3.25), etc.
• dependencies.properties

Project Lead Tasks

Each project lead or a designated Committer 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
• Project metadata at https://projects.eclipse.org/projects/webtools updated for the release version
• Project metadata at https://projects.eclipse.org/projects/webtools created for the next release, with the New and Noteworthy URL populated

SCM Tagging script

1. Check out the webtools.releng.aggregator project & make sure you're up to date in all the submodules. Commit any updates.

• https://gist.github.com/nickboldt/4f5bf0ace88dcfd2b7f4779be23146f7

2. Check out all the projects listed below, then:

 TAG=R3_23
 for d in */; do echo $d; cd $d; git pull origin master; git tag ${TAG}; git push origin ${TAG}; cd ..; echo; done

Projects to tag include:

 webtools.releng.aggregator/
   webtools.releng/
   webtools.common/
   webtools.dali/
   webtools.javaee/
   webtools.jsdt/
   webtools.jsf/
   webtools.servertools/
   webtools.sourceediting/
   webtools.webservices/

Overall project + update site versions

• Once tags are created in the aggregator and releng projects, the following files should be bumped to the new 3.y+1 version:

 pom.xml
 publish/pom.xml
 webtools.repositories/pom.xml
 webtools.repositories/repository/pom.xml
 webtools.repositories/repositoryunittests/pom.xml

• For example:

for d in pom.xml publish/pom.xml webtools.repositories/pom.xml webtools.repositories/repository*/pom.xml; do \
  sed -i $d -r -e "s#3.23.0-SNAPSHOT#3.24.0-SNAPSHOT#g"; \
done

Elsewhere

• Make sure Eclipse/Installation reflects the current/new Eclipse Project release
• Make sure Simultaneous_Release points to the current or next release