Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Trace Compass/ReleasePreparation"

(Created page with "== Preparing for a release == * Create a release record well in advance to announce the release. Go to the [https://projects.eclipse.org/projects/tools.tracecompass project p...")
 
Line 1: Line 1:
 +
== Simultaneous release ==
 +
* Be aware for the release schedule for the simultaneous release. For that follow important dates on the simultaneous release wiki, e.g. https://wiki.eclipse.org/Mars/Simultaneous_Release_Plan
 +
* Create milestones update site for the simultaneous release before M1 build
 +
*# Login to build.eclipse.org
 +
*# goto to sub-directory downloads/tracecompass
 +
*# if needed, create directory <release-name>/milestones, e.g. mkdir neon/milestones
 +
*# goto sub-directory <release-name>/milestones
 +
*# create milestone directory, e.g. mkdir m1
 +
*# copy update site conntent to milestone directory (e.g. m1)
 +
*# copy compositeArtifacts.xml and compositeContent.xml from previous release (e.g. mars)
 +
*# update both files for current milestone build (e.g. <child location="m1"/>)
 +
 
== Preparing for a release ==
 
== Preparing for a release ==
 
* Create a release record well in advance to announce the release.  Go to the [https://projects.eclipse.org/projects/tools.tracecompass project page] and while logged in, use "Committer Tools"-> "Create new release" on the right. This can be done even before the preceding release is done.  It is used to indicate our intention.
 
* Create a release record well in advance to announce the release.  Go to the [https://projects.eclipse.org/projects/tools.tracecompass project page] and while logged in, use "Committer Tools"-> "Create new release" on the right. This can be done even before the preceding release is done.  It is used to indicate our intention.

Revision as of 11:46, 23 June 2015

Simultaneous release

  • Be aware for the release schedule for the simultaneous release. For that follow important dates on the simultaneous release wiki, e.g. https://wiki.eclipse.org/Mars/Simultaneous_Release_Plan
  • Create milestones update site for the simultaneous release before M1 build
    1. Login to build.eclipse.org
    2. goto to sub-directory downloads/tracecompass
    3. if needed, create directory <release-name>/milestones, e.g. mkdir neon/milestones
    4. goto sub-directory <release-name>/milestones
    5. create milestone directory, e.g. mkdir m1
    6. copy update site conntent to milestone directory (e.g. m1)
    7. copy compositeArtifacts.xml and compositeContent.xml from previous release (e.g. mars)
    8. update both files for current milestone build (e.g. <child location="m1"/>)

Preparing for a release

  • Create a release record well in advance to announce the release. Go to the project page and while logged in, use "Committer Tools"-> "Create new release" on the right. This can be done even before the preceding release is done. It is used to indicate our intention.
  • About 2 months before the release, probably around but before RC1, make sure the corresponding release record is properly completed and ready for review.
  • Deal with IP. Now that we only accept contribution through Gerrit, there really shouldn't be much to do.
    1. Run the bugzilla checker for iplog: https://www.eclipse.org/projects/tools/ip_contribution_review.php?id=tools.tracecompass
    2. Address recommendations which are probably patches that were posted on bugzilla and then moved to Gerrit. In that case mark the patches as iplog-
    3. Generate the IPLog. Go to the project page and while logged in, use "Committer Tools" -> "Generate IPLog (project)" on the right to generate the IPLog.
    4. Review the IPLog created. There shouldn't be much to change, if anything at all.
    5. Submit the IPLog using the button at the bottom of the IPLog page.
    6. Once the IP team finishes the review they will send an email with the approved iplog attached. Save it under something like 1.0-approvedIPLog.html and attach it to the review material on the review page e.g., https://projects.eclipse.org/projects/tools.tracecompass/releases/1.0.0/review
  • Prepare the New&Noteworthy page, e.g. https://wiki.eclipse.org/Trace_Compass/News/NewIn10
  • Request Tools PMC approval for the release by sending an email to "tools-pmc at eclipse.org" of the form
Title: PMC Approval for Trace Compass 1.0
 
 Dear PMC Members,
 
 We'd like PMC approval for the Trace Compass 1.0 major release that is scheduled to coincide with Eclipse Mars.  The release contains bug fixes, new features and API changes [1].
 
 http://projects.eclipse.org/projects/tools.tracecompass/releases/1.0.0/review
 
 The project's IP Log has been submitted and is awaiting approval.
 
 Regards,
 Bernd

[1] https://wiki.eclipse.org/Trace_Compass/News/NewIn10

  • Schedule a release review. From the release review page e.g., review for 1.0.0, there should be a green link at the top that says "Schedule a review". Once pressed the review will be available but to make it public an email must be sent to the EMO (emo at eclipse.org) like this:
Title: Please schedule Trace Compass's 1.0.0 Release Review
Hi,

could we schedule a release review [1] for Trace Compass's next major release scheduled to coincide with Mars , on June 24th, 2015? PMC approval has been requested [2]

[1] http://projects.eclipse.org/projects/tools.tracecompass/releases/1.0.0/review
[2] <Add link to email on Trace Compass mailing list that request PMC approval>

Thanks

Bernd

Back to the top