Re: [proposal] Handling of contested changes near release finalization
> "Contested changes of non-critical functional severity should not
> be backported during a release candidate cycle which is likely to
> result in a final release. A change is "contested" not only by a
> -1 veto in STATUS, but by negative feedback from a committer in any
This leaves me wondering a couple of things.
1) _Why_ is a -1 not the correct way to contest a change late in the
release cycle? What makes it necessary to allow other methods to do
the same thing?
2) Does this change the old policy, "if it didn't happen on the list,
it didn't happen"? By saying "any forum" you seem to include IRC
channels and who knows what else.
Received on Tue Sep 5 22:59:52 2006
This is an archived mail posted to the Subversion Dev