https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6419
--- Comment #13 from Kevin A. McGrail <[email protected]> 2010-07-21 16:15:08 EDT --- (In reply to comment #12) > (in reply to comment #11) > > Commits to trunk are CTR (Commit then review), no votes required (or rather, > only the one implied vote of the person committing it is required) but anyone > can notice a problem and veto it to have the commit reverted. > > Commits to branches are RTC, requiring three votes and no vetoes before > committing. > > Since only one vote is needed to commit to trunk, in general the committer who > is proposing a patch for branch commits to trunk at the same time that they > post the patch and call for votes for branch. > > Of course it can go somewhat differently if you are asking for opinions or > review before you are sure that you like your own proposal, or if the patch is > submitted by a non-committer and so doesn't even have one vote yet. > > But it is important to have the process such that it is difficult to > accidentally forget to commit something to trunk that has been committed to > branch. That has happened before with unfortunate results. Thanks for the detailed explanation. I will change my behavior with the trunk commits to be in line with this procedure. Regards, KAM -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
