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:
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.
Component Lead sends a note to email@example.com with a link to the defect. (You must be a member of this list to send mail to it.)
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.
- Back to WTP Build Process and Procedures
- Back to Web Tools Wiki Home