Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[eclipse-pmc] Fwd: [platform-dev] Review practice

Looks like the charter of the TLP is totally out of date so it has to be updated.
McQ, as you're the PMC chair do you know how to drive a change in it and want to do it?

---------- Forwarded message ---------
From: <jkubitz-eclipse@xxxxxx>
Date: Thu, Mar 30, 2023 at 3:49 PM
Subject: Re: [platform-dev] Review practice
To: Eclipse platform general developers list. <platform-dev@xxxxxxxxxxx>

“The Committers of a Project or component decide which changes may be committed to the master code base of a Project or component respectively. Three +1 ('yes' votes) with no -1 ('no' votes or vetoes) are needed to approve a code change. Vetoes must be followed by an explanation for the veto within 24 hours or the veto becomes invalid. All votes are conducted via the developer mailing list associated with the Project or component.”



While we barely find a single reviewer I suggest to wait that 24h if anybody wants to review before merging without a single reviewer.

Further I suggest, that the PMC clarifies such rule and updates that document to the current practice to clearly state that reviewtools (like gerrit/github) can be used instead of mailing list.





platform-dev mailing list
To unsubscribe from this list, visit

Aleksandar Kurtakov
Red Hat Eclipse Team

Back to the top