Skip to main content
Jump to: navigation, search

Difference between revisions of "CDT/ProjectLeadNotes"

< CDT
Line 1: Line 1:
 
== Preparing for a release ==
 
== Preparing for a release ==
# Create a release record well in advance to announce the release.  This is done while logged in, from the [https://projects.eclipse.org/projects/tools.cdt project page] . 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.  This is done while logged in, from the [https://projects.eclipse.org/projects/tools.cdt project page] . 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 complete and ready for review.
+
* About 2 months before the release, probably around but before RC1, make sure the corresponding release record is properly complete and ready for review.
# Deal with IP. Now that we only accept contribution through Gerrit, there really shouldn't be much to do.
+
* Deal with IP. Now that we only accept contribution through Gerrit, there really shouldn't be much to do.
## Run the bugzilla checker for iplog: https://www.eclipse.org/projects/tools/ip_contribution_review.php?id=tools.cdt
+
*# Run the bugzilla checker for iplog: https://www.eclipse.org/projects/tools/ip_contribution_review.php?id=tools.cdt
## Address recommendations which are probably patches that were posted on bugzilla and then moved to Gerrit. In that case mark the patches as iplog-
+
*# Address recommendations which are probably patches that were posted on bugzilla and then moved to Gerrit. In that case mark the patches as iplog-
## Generate the IPLog. Got to the [https://projects.eclipse.org/projects/tools.cdt project page] and while logged in, use "Committer Tools" on the right to "Generate IPLog (project)"
+
*# Generate the IPLog. Got to the [https://projects.eclipse.org/projects/tools.cdt project page] and while logged in, use "Committer Tools" on the right to "Generate IPLog (project)"
## Review the IPLog created.  There shouldn't be much to change, if anything at all.
+
*# Review the IPLog created.  There shouldn't be much to change, if anything at all.
## Submit the IPLog using the button at the bottom of the IPLog page.
+
*# Submit the IPLog using the button at the bottom of the IPLog page.
# Request Tools PMC approval for the release by sending an email to "tools-pmc at eclipse.org" of the form
+
* Request Tools PMC approval for the release by sending an email to "tools-pmc at eclipse.org" of the form
 
  Title: PMC approval requested for CDT 8.6.0
 
  Title: PMC approval requested for CDT 8.6.0
 
   
 
   
Line 25: Line 25:
 
  [1] https://wiki.eclipse.org/CDT/User/NewIn86
 
  [1] https://wiki.eclipse.org/CDT/User/NewIn86
  
# Schedule a release review.  From the release review page e.g., [https://projects.eclipse.org/projects/tools.cdt/releases/8.6.0/review review for 8.6], there should be a green link at the top that says "Schedule a review".  Once pressed the review will be made public but an email must be sent to the EMO like this:
+
* Schedule a release review.  From the release review page e.g., [https://projects.eclipse.org/projects/tools.cdt/releases/8.6.0/review review for 8.6], there should be a green link at the top that says "Schedule a review".  Once pressed the review will be made public but an email must be sent to the EMO like this:
 
  Title: Please schedule CDT's 8.6.0 Release Review
 
  Title: Please schedule CDT's 8.6.0 Release Review
 
  Hi,
 
  Hi,

Revision as of 10:45, 19 January 2015

Preparing for a release

  • Create a release record well in advance to announce the release. This is done while logged in, from the project page . 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 complete 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.cdt
    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. Got to the project page and while logged in, use "Committer Tools" on the right to "Generate IPLog (project)"
    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.
  • Request Tools PMC approval for the release by sending an email to "tools-pmc at eclipse.org" of the form
Title: PMC approval requested for CDT 8.6.0

Dear PMC Members,

We'd like PMC approval for the CDT 8.6.0 minor release that is scheduled to coincide with Eclipse Luna SR2.  The release contains both bug fixes and new features [1].

https://projects.eclipse.org/projects/tools.cdt/releases/8.6.0/review

The project's IP Log has been submitted and is awaiting approval.

Regards,

Marc

[1] https://wiki.eclipse.org/CDT/User/NewIn86
  • Schedule a release review. From the release review page e.g., review for 8.6, there should be a green link at the top that says "Schedule a review". Once pressed the review will be made public but an email must be sent to the EMO like this:
Title: Please schedule CDT's 8.6.0 Release Review
Hi,

could we schedule a release review [1] for CDT's next minor release scheduled to coincide with Luna SR2, on Feb 27th, 2015?  PMC approval has been requested [2]

[1] https://projects.eclipse.org/projects/tools.cdt/reviews/8.6.0-release-review
[2] https://dev.eclipse.org/mhonarc/lists/tools-pmc/msg02944.html

Thanks

Marc

Back to the top