FYI,
I trust that project leads generally know what's best for their projects
and for their downstream users, so I see no general need to police or
review their decisions.
Regards,
Ed
On 12/06/2013 12:42 PM, Sven Efftinge wrote:
Ed,
comments inline
On Jun 12, 2013, at 11:47 AM, Ed Willink <[email protected]
<mailto:[email protected]>> wrote:
Doesn't it need PMC approvals before being resolved as fixed?
No, we don't follow that policy anymore.
From the yet to be superseded
http://wiki.eclipse.org/Modeling_Project_Ramp_Down_Policy/Helios
* After RC3
<http://wiki.eclipse.org/Helios#Milestones_and_Release_Candidates>:
Two additional Committers and at least 2 PMC members must review
and vote +1 after reviewing the bug for appropriateness and risk.
Two additional committers have reviewed the change.
I don't see why votes from the PMC would help.
After reviewing the commit myself, I see quite a lot of new lines and
control flow changes in core code, but the bug description reads as a
UI inelegance rather than a killer. So IMHO not really appropriate
for RC4.
It's an important missing compiler analysis. I don't think UI is
mentioned at all.
Regards,
Sven
_______________________________________________
cross-project-issues-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
