Difference between revisions of "WTP Release 1.5 Shutdown Process"

From Eclipsepedia

Jump to: navigation, search
 
(2 intermediate revisions by 2 users not shown)
Line 7: Line 7:
 
# The bug must be serious, i.e. it is P1 or P2 priority, it is Blocking, Critical, or Major severity, it is a Hot Bug, or it is a serious usability problem.
 
# The bug must be serious, i.e. it is P1 or P2 priority, it is Blocking, Critical, or Major severity, it is a Hot Bug, or it is a serious usability problem.
 
# A fix must be available and attached to the bug, it must have limited scope, it must not cause ripples or regressions, and it must have been tested.
 
# A fix must be available and attached to the bug, it must have limited scope, it must not cause ripples or regressions, and it must have been tested.
# The component lead requests PMC approval by entering the keywork PMC in the status whiteboard field in bugzilla
+
# The component lead requests PMC approval by entering the keyword PMC in the status whiteboard field in bugzilla
 
# PMC members approve or reject the bug by adding comments to bugzilla, if 3 members approve and no members reject, then the bug is approved. If one or PMC members reject the fix, their concerns must be addressed and they must remove their objections.
 
# PMC members approve or reject the bug by adding comments to bugzilla, if 3 members approve and no members reject, then the bug is approved. If one or PMC members reject the fix, their concerns must be addressed and they must remove their objections.
 +
# Once approved, the keyword PMC in the status whiteboard will be changed to PMC_APPROVED (by Jeffrey Liu or a PMC member only) to make bugzilla queries easier and status easier to follow.
  
 
Since we are approaching our release date, we need to ensure that any remaining bugs are reviewed in a timely fashion, ideally within 24 hours. To track and expedite the process, we are doing the following:
 
Since we are approaching our release date, we need to ensure that any remaining bugs are reviewed in a timely fashion, ideally within 24 hours. To track and expedite the process, we are doing the following:
# The bugs requiring approval are summarized by [http://www.eclipse.org/webtools/people/liu.html Jeffrey Liu] in the [http://www.eclipse.org/webtools/plans/1.5/ramp-down-bugs-approval.html WTP 1.5 Bugs} page.
+
# The bugs requiring approval are summarized by [http://www.eclipse.org/webtools/people/liu.html Jeffrey Liu] in the [http://www.eclipse.org/webtools/plans/1.5/ramp-down-bugs-approval.php WTP 1.5 Bugs} page.
# An IRC channel has been created for component leads to discuss bugs with PMC members. PMC members will monitor this channel on a best effort basis and attempt to review bugs within 24 hours. The chat server is irc.freenode.net:6667, channel eclipsewtp.
+
# An [[IRC]] channel has been created for component leads to discuss bugs with PMC members. PMC members will monitor this channel on a best effort basis and attempt to review bugs within 24 hours. The chat server is irc.freenode.net:6667, channel eclipsewtp.
 
# A daily telecon will be held at 3:00 PM [http://www.timeanddate.com/worldclock/city.html?n=250 EDT]. [http://www.eclipse.org/webtools/people/liu.html Jeffrey Liu] will cancel this telecon if their are no bugs requiring PMC approval as of 2:00 PM [http://www.timeanddate.com/worldclock/city.html?n=250 EDT] each day. The [http://www.eclipse.org/webtools/development/status-telecons/index.html weekly status telecon] callin number will be used for these telecons.
 
# A daily telecon will be held at 3:00 PM [http://www.timeanddate.com/worldclock/city.html?n=250 EDT]. [http://www.eclipse.org/webtools/people/liu.html Jeffrey Liu] will cancel this telecon if their are no bugs requiring PMC approval as of 2:00 PM [http://www.timeanddate.com/worldclock/city.html?n=250 EDT] each day. The [http://www.eclipse.org/webtools/development/status-telecons/index.html weekly status telecon] callin number will be used for these telecons.

Latest revision as of 12:45, 7 June 2006

This page describes the procedures to follow for the shutdown of WTP 1.5. These procedures are in effect for the month of June. From now until WTP 1.5 is released, ALL bugs require PMC approval. Our final release candidate is planned for June 14. Only extremely serious bugs will be considered after that time.

To request approval for the release of a bug, the following conditions MUST be satisfied:

  1. The bug must be serious, i.e. it is P1 or P2 priority, it is Blocking, Critical, or Major severity, it is a Hot Bug, or it is a serious usability problem.
  2. A fix must be available and attached to the bug, it must have limited scope, it must not cause ripples or regressions, and it must have been tested.
  3. The component lead requests PMC approval by entering the keyword PMC in the status whiteboard field in bugzilla
  4. PMC members approve or reject the bug by adding comments to bugzilla, if 3 members approve and no members reject, then the bug is approved. If one or PMC members reject the fix, their concerns must be addressed and they must remove their objections.
  5. Once approved, the keyword PMC in the status whiteboard will be changed to PMC_APPROVED (by Jeffrey Liu or a PMC member only) to make bugzilla queries easier and status easier to follow.

Since we are approaching our release date, we need to ensure that any remaining bugs are reviewed in a timely fashion, ideally within 24 hours. To track and expedite the process, we are doing the following:

  1. The bugs requiring approval are summarized by Jeffrey Liu in the [http://www.eclipse.org/webtools/plans/1.5/ramp-down-bugs-approval.php WTP 1.5 Bugs} page.
  2. An IRC channel has been created for component leads to discuss bugs with PMC members. PMC members will monitor this channel on a best effort basis and attempt to review bugs within 24 hours. The chat server is irc.freenode.net:6667, channel eclipsewtp.
  3. A daily telecon will be held at 3:00 PM EDT. Jeffrey Liu will cancel this telecon if their are no bugs requiring PMC approval as of 2:00 PM EDT each day. The weekly status telecon callin number will be used for these telecons.