Skip to main content
Jump to: navigation, search

OCL/Dev/Releng/Quiet Week

< OCL
Revision as of 05:54, 10 September 2019 by Ed.willink.me.uk (Talk | contribs) (Final Release Day)

In this wiki entry we explain the releng bits that may be done during the quiet week, particularly to the Eclipse OCL project. You may find some general information about the quite week in the Simultaneous Release Final Daze documentation (Juno, for the time of writing).

The main purpose of the quite week activities is preparing the downloadable zips and the release p2 repository in its final location so that they are properly mirrored across the different mirror servers prior to the final release date, taking into account that the content can't be available for download until that date. The releng tasks to be done are explained in two blocks, the tasks during the Quite Week and those tasks which must be done the Final Release Day.

Quiet Week

The following are the Eclipse OCL usual releng tasks to be accomplished during the quiet week.

Hide the new release in the downloads web page

Prior to prepare the downloadable zips of the imminent release in the downloads area, we should ensure that it's not available for downloading. To do that you must follow the following steps:

   note: see the hidden.txt file history to find examples of previous modifications
  • Commit and push the change to the remote repository

Prepare the downloadable zips area

The former practice contributed the final RC-build to SimRel and performed a number of manual rename activities once the build was successful and ready to be published. These manual activities are hard now that the remote access to build.eclipse.org is more restricted.

There is now no need to prepare a downloads area. Just perform an R-build with an alias of the release name. Do this as late as practical before the final SimREl build so that the R-build can be contributed to the SimRel aggregator.

Archive old releases

Older download ZIPs are moved to archive:

  • Edit the /mdt/downloads/extras-ocl.php file to add the redirections for archived releases
  • Copy the releases to archive
cd ~/downloads/modeling/mdt/ocl/downloads/drops
mv 5.0.5 /home/data/httpd/archive.eclipse.org/modeling/mdt/ocl/downloads/drops

*Make sure the archive is useable For each new archived R folder that doesn't have an index.php

cp ../../3.1.0/R201106061427/index.php .

The default Eclipse Foundation archive.eclipse.org 404 page has a "Show Directory Contents." that provides similar/better functionality than the traditional project index.php.

Older P2 repos are moved to archive:

  • Copy the repo to archive
cd ~/downloads/modeling/mdt/ocl/updates/releases
ant -f /shared/modeling/tools/promotion/manage-composite.xml remove -Dchild.repository=5.0.5
mv 5.0.5 /home/data/httpd/archive.eclipse.org/modeling/mdt/ocl/updates/releases
cd /home/data/httpd/archive.eclipse.org/modeling/mdt/ocl/updates/releases
ant -f /shared/modeling/tools/promotion/manage-composite.xml add -Dchild.repository=5.0.5

Prepare the releases p2 repository

The former practice contributed the final RC-build to SimRel and performed a number of manual rename activities once the build was successful and ready to be published. These manual activities are hard now that the remote access to build.eclipse.org is more restricted.

There is now no need to prepare a releases area. Just perform an R-build with an alias of the release name. Do this as late as practical before the final SimREl build so that the R-build can be contributed to the SimRel aggregator.

Update the Help Info Center

The Help Info Center is now populated automatically.

With every release a bugzilla is created so that every project can publish where the doc plugin is located in the new release repository. We will usually need to keep an eye to the cross-project-issues mailing list to catch the proper bugzilla up (Following the cross-project dot inbox @at eclipse dot org bugzilla account may also help). In the corresponding Juno release bugzilla 379598 , you may find different examples about how to provide the required information.

Final Release Day

The R-build is automatically published, so no immediate action is required.

Update Eclipse Market Entry

The Eclipse OCL entry in the Eclipse MarketPlace requires to be updated with the final R-build:

Eclipse OCL at Market Place

Next Version

The Eclipse OCL entry in the Eclipse MarketPlace requires to be updated with the final R-build: The project should be moved onto the next release number by editing the many version numbers in MANIFEST.MF, pom.xml, feature.xml. Once this has been debugged using a local Tycho build, the Promoter job can be re-enabled.

Announcement

Remember to announce the new release in our public forum.

Back to the top