Skip to content

Latest commit

 

History

History
167 lines (155 loc) · 17.8 KB

RELEASE.md

File metadata and controls

167 lines (155 loc) · 17.8 KB
Raw

Releng-Tasks 2.0

Eclipse Major Release Schedule

Previous Documentation

Milestone and RC Releases

Friday before release week:

  • Update I-builds to build on the milestone schedule (Twice daily at 06:00 EST and 18:00 EST except Thursday).
  • Create or update prerequisite issues for tracking ECF, EMF and Orbit
  • Send reminder email for upcoming milestone week to platform-releng-dev@eclipse.org, platform-dev@eclipse.org, eclipse-dev@eclipse.org and equinox-dev@eclipse.org
    • Example from 4.23 M1 but the usual schedule:
      • Monday: Last day of development.
      • Tuesday: Tests
      • Wednesday:
        • Fixes from Tuesday.
        • "New and Noteworthy entries due.
        • Release Candidate is built Wednesday evening at 6PM EST.
      • Thursday: Sign-Off
      • Friday:
        • Build delcared and released.
        • Make sure to mention that the Master branch will stay closed until the milestone is officially released.

Milestone Week

  • M2 Release
    • The M2 release is 'lightweight', meaning there is no announcement or signoff. No additional builds need to be run, just the daily I-build at 6PM EST. Thursdays build is promoted to simrel on friday (unless there are problems with Thursdays build, in which case promote Wednesdays) and the compiler is updated if necessary, but the promote and makevisible jobs don't need to be run.
  • Wednesday:
    • Verify that EMF, ECF and Orbit contributions have been included (if applicable).
    • Final release candidate build runs at 6PM EST.
    • Because of time zones, PST/EST might want to do Thursday's tasks EOD Wednesday after the release candidate has built.
  • Thursday:
  • Friday:
    • Promote the release candidate (if go).
      • Run the rename and promote job in Jenkins
        • DROP_ID: Release candidate build ID (make sure there is no space before or after the ID).
        • CHECKPOINT: M1 etc (blank for final releases)
        • SIGNOFF_BUG: Needs to be updated to sign-off issue (numeric part only)
        • TRAIN_NAME: Whenever the current GA release is planned for (formatted 4 digit year - 2 digit month, i.e 2022-06)
        • STREAM: 4.24.0 etc
        • DL_TYPE: S is used to promote I-builds.
        • After the build find and open the mail template artifact and have it ready.
      • Contribute to SimRel
        • If you have not already set up SimRel you can do so using Auto Launch here
        • Clone org.eclipse.simrel.build (Should have been done by the installer during set up, but make sure you have latest).
          1. Open simrel.aggr in Eclipse
          2. Change to the properties view
          3. Select Contribution:Eclipse > Mapped Repository
          4. Update the Location property to the "Specific repository for building against" in the mailtemplate.txt from promotion.
          5. Commit Simrel updates to Gerrit
            • Message should use year-month format, i.e "Simrel updates for Eclipse and Equinox for 2022-06 M1"
      • Make the build visible
        • Run the make visible job in Releng jenkins to make the promoted build visible on the download page.
        • Parameters should match Rename and Promote job
        • This should automatically run tag Eclipse release to tag the source code.
        • Tag Parameter should match stream version, i.e S4_24_0_M1 etc
      • Send email that the M1 build is available
        • Use the mail template from the promotion build artifacts in Jenkins to get the download urls.
      • For Milestone builds return the I-builds to the normal schedule.
    • Update ECJ compiler in the platform build (if it needs to be updated).
      • To find the new compiler version:
        • Go to the update site for the release candidate
        • Click plugins
        • Find org.eclipse.jdt.core.complier.batch_${ecjversion}.jar
      • Edit the copyAndDeployJDTCompiler job in Jenkins
        • Only JDT committers can run the job, but Releng/Platform committers can configure it
        • Update the default values of the versionfolder, buildid and ecjversion parameters.
        • Update the build triggers to schedule a build for the current date.
      • Finally update the cbi-ecj-version in eclipse.platform.releng.aggregator/eclipse-platform-parent/pom.xml
    • After RC1
      • Open an issue in eclipse.platform.releng.aggregator to enable the API Freeze Report for the current release.
        • Open buildproperties.txt
        • Comment out the empty FREEZE_PARAMS line and uncomment the line with the freeze arguments. Update freezeBaseURL with the RC1 build number.
        • Comment out the empty API_FREEZE_REF_LABEL line and update the version of the label to RC1.
      • Leave the I-builds running on the milestone schedule for RC2.
      • Comment on EMF, ECF and Orbit issues to ask for final release builds.

GA Releases

After RC2

RC2a Release

  • Sometimes there is a critical issue that requires a fix, if it's decided that one is needed then an RC2a (followed by RC2b, RC2c etc if necessary) is built from the maintenance branch and promoted using the RC2 process.
  • Create an issue to set the previous release version to RC2a and add it to the Preparation issue for the next version, then update all references to RC2 to the RC2a release.

Friday before GA Release

Publishing to Maven

Wednesday, GA Release