[MPlayer-dev-eng] [POLICY] clarify conditions for functionality removal

[Oded Shimon]

On Fri, Feb 10, 2006 at 07:02:13PM +0100, Dominik 'Rathann' Mierzejewski wrote:
> On Friday, 10 February 2006 at 18:18, Diego Biurrun wrote:
> > On Thu, Feb 09, 2006 at 09:31:39PM +0100, Dominik 'Rathann' Mierzejewski wrote:
> > > On Thursday, 09 February 2006 at 02:08, The Wanderer wrote:
> > > > Diego Biurrun wrote:
> > > > >
> > > > >It *is* current practice.  No rules are set in stone.  Things are
> > > > >discussed on dev-eng until a consensus is reached.
> > > > 
> > > > I'd just like to note that that is not what the current form says, nor
> > > > is it what the old form said about "changing behaviour". No mention is
> > > > made of "consensus"; all it says is that discussion must take place, not
> > > > that the discussion must reach any particular conclusion first. Saying
> > > > "discussing it on the mplayer-dev-eng mailing list and receiving some
> > > > form of consensus approval" would avoid the problem.
> > > 
> > > Or just "... without being approved in a discussion on the mplayer-dev-eng
> > > mailing list".
> > 
> > Simple, clear, concise and I think it captures the spirit.  Please commit.
> > 
> > Thanks for this constructive contribution.
> 
> You're welcome, but... since Ivan has secretly reverted your last commit
> (so we're back at 1.24), I'd have to recommit yours and commit mine over
> that. Or should I do it in one go?

Seperate. admin -o should NEVER be used on old commits. Basically, if you 
commit them together, then all those who updated during the period before 
the admin -o will not be able to update to your version. You have to 
recommit the original commit that was reverted so everybody is in sync.

- ods15