Re: [modeling-pmc] [SPAM PROBABLE]Modeling project ramp down policy and

[Kenn Hussey <kenn.hussey@xxxxxxxxx>]

All changes after RC1 must adhere to the ramp-down policy, i.e., they must receive the appropriate amount of review.

In theory, projects should only be fixing high priority issues during the release candidate phase, and the addition of new unit tests is most likely not "high priority". In practice, however, changes to non-functional areas of the code are probably fine, provided they are reviewed. The main idea behind the ramp-down policy is to communicate so that unintended breakages, especially where inter-project dependencies exist, don't occur.

Kenn

On Thu, May 19, 2011 at 6:02 AM, Grégoire Dupé <gdupe@xxxxxxxxxxxxxxxx> wrote:

Hello,

We need additional explanations about the Modeling project ramp down policy [1]:
 - Can we commit unit tests after RC1?
 - If we can, is the PMC approval required?

[1] http://wiki.eclipse.org/Modeling_Project_Ramp_Down_Policy

Regards,
Grégoire Dupé
_______________________________________________
modeling-pmc mailing list
modeling-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/modeling-pmc