Remy Maucherat wrote:
Mladen Turk wrote:
Remy Maucherat wrote:
To give an idea, "tis" could mean:
- API changing patches (any protected or above signature change)
- code changes in the critical path (for example, code which gets
executed on each HTTP request)
Fine.
- any other commit for which a committer asks for the RTC procedure
should be rollbacked if it hinders concurrent work, and go through the
RTC procedure
This looks like a conditional veto that can be voted over. Perfect!
IIUC it means that instead veto one asks for a vote (+3 votes), right?
Looks like RTC on demand, that would require some sort of lazy consensus.
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
This could get clarified a little bit more. I don't think asking for
review is vetoing a patch, as there's no need to revert in most cases
(one case would be a pending tag, or if it somehow causes immediate
development conflicts). However, if a patch doesn't attract enough
votes, or doesn't pass the +3 margin (if that's what gets accepted), it
is considered vetoed and needs to be reverted.
this wouldn't work, the community is simply too small, we barely get
enough vote to get a 5.5 release out the door as it is.
Filip
Rémy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
