[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[pde-dev] 3.5 RC4 Reminder... one more week to go!
|
We're getting close to releasing Eclipse 3.5! Just one more RC to go!
Our primary focus should be on documentation and SERIOUS DEFECTS only.
As a reminder, here are the rules of engagement that we need to follow:
Fix approvalComponent lead plus one other component lead must approve all work on a component. In addition, any component lead can veto a change with cause. No changes are to be released without associated bug report tagged 3.5RC4 including risk assessment and prior approvals. (Ongoing changes to component documentation do not require special approval.)
API change approval
PMC must approve all API changes. No changes are to be released without prior approval and associated bug report. Send the request for approval to the eclipse pmc mailing list. If a change is made to API to make it binary compatible with 3.4, technically this is still an API change, and thus it should be treated in the same way as any other API change requests.
Notification requirements
Two additional committers must check all code changes prior to release. Person who reported bug should mark the bug as verified once they have retested.
Thanks for everyone's hard work!
