Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "WTP PMC Defect Review"
| Line 4: | Line 4: | ||
==== Developer obtains component lead approval, fixes defect, and attachs patch to the defect. ==== | ==== Developer obtains component lead approval, fixes defect, and attachs patch to the defect. ==== | ||
| + | |||
==== Developer gets component review and puts "PMC" in the Status Whiteboard field. Developer also adds documentation about the fix and why it is a mustfix. ==== | ==== Developer gets component review and puts "PMC" in the Status Whiteboard field. Developer also adds documentation about the fix and why it is a mustfix. ==== | ||
| + | |||
==== PMC members review and vote. A single negative vote will reject a defect and a minimum of two positive votes is required for approval. It will be incumbent on the PMC to do anything possible to perform reviews within 24 hours. If the bug is approved, the Status Whiteboard is updated to "PMC_approved" by release lead. If the bug is rejected, it will be updated to "PMC_rejected" and the code should not be released for a build. ==== | ==== PMC members review and vote. A single negative vote will reject a defect and a minimum of two positive votes is required for approval. It will be incumbent on the PMC to do anything possible to perform reviews within 24 hours. If the bug is approved, the Status Whiteboard is updated to "PMC_approved" by release lead. If the bug is rejected, it will be updated to "PMC_rejected" and the code should not be released for a build. ==== | ||
| + | |||
==== If approval is given, the developer may then release the code and component lead can tag for a build. ==== | ==== If approval is given, the developer may then release the code and component lead can tag for a build. ==== | ||
Revision as of 12:15, 29 January 2007
Contents
- 1 WTP PMC Defect Review
- 1.1 Developer obtains component lead approval, fixes defect, and attachs patch to the defect.
- 1.2 Developer gets component review and puts "PMC" in the Status Whiteboard field. Developer also adds documentation about the fix and why it is a mustfix.
- 1.3 PMC members review and vote. A single negative vote will reject a defect and a minimum of two positive votes is required for approval. It will be incumbent on the PMC to do anything possible to perform reviews within 24 hours. If the bug is approved, the Status Whiteboard is updated to "PMC_approved" by release lead. If the bug is rejected, it will be updated to "PMC_rejected" and the code should not be released for a build.
- 1.4 If approval is given, the developer may then release the code and component lead can tag for a build.
WTP PMC Defect Review
As the end of a release cycle nears, WTP needs to add some governance in order to maintain stability and quality in the face of the upcoming deadline. To this end, a PMC review process will occur. The basic steps to this process are: