lock_* API change

[Martin Pool]

On 14 May 2010 15:13, Russel Winder <russel at russel.org.uk> wrote:
> On Fri, 2010-05-14 at 19:26 +1200, Robert Collins wrote:
> [ . . . ]
>> Its entirely normal for trunk bzr and trunk plugin bzr-FOO to be out
>> of sync from time to time. We use this list to talk about things like
>> this. I don't know if Jelmer was caught by surprise or not - the merge
>> in question was up for a week or so - it wasn't rushed through in any
>> sense.
>
> Indeed.  I have full confidence in the management and development
> processes.  I guess the constructive point I was trying to make (but
> which probably got hidden by the moans) is that plugin developers may
> not be actively and attentively tracking the bzr.dev merge queue.  The
> question is whether there needs to be a way of flagging coming
> "breaking" API changes more widely.  Or perhaps I am missing stuff which
> everyone else knows of?

I think for large changes we often do an rfc thread which gives people
a chance to object.  For small changes that people do on the way to
something else adding a multi-day stall would not be economical.

-- 
Martin <http://launchpad.net/~mbp/>