Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse-dev] RC3 Rules Reminder

One extra detail.  Reviews for test changes and doc changes do not need the 3 person review.

Tom



Inactive hide details for Daniel Megert ---05/23/2014 06:19:29 AM---The rules for committing code are getting tighter: - Two adDaniel Megert ---05/23/2014 06:19:29 AM---The rules for committing code are getting tighter: - Two additional committers and a component lead

From: Daniel Megert <daniel_megert@xxxxxxxxxx>
To: "General development mailing list of the Eclipse project." <eclipse-dev@xxxxxxxxxxx>, eclipse-releng@xxxxxxxxxxx
Date: 05/23/2014 06:19 AM
Subject: [eclipse-dev] RC3 Rules Reminder
Sent by: eclipse-dev-bounces@xxxxxxxxxxx





The rules for committing code are getting tighter: 

- Two additional committers and a component lead must +1 your bug report (3 people who are not the one making the change).
 
- Every planned fix must be announced on the platform-releng-dev@xxxxxxxxxxx mailing list.
 
- An API change needs to get PMC approval.
 

This needs to happen before committing the fix, nit afterwards.
 

For all the details see:
http://www.eclipse.org/eclipse/development/plans/freeze_plan_4_4.php#FixPassAfterRC2. 

Thanks for your cooperation!
 
Dani
_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipse-dev

GIF image


Back to the top