[rfc] Fix committed/released distinction

[Martin Pool]

On 8 April 2011 15:47, Andrew Cowie <andrew at operationaldynamics.com> wrote:
> On Fri, 2011-04-08 at 14:48 +1000, Martin Pool wrote:
>> - we need to run a script to flip things to released when that becomes
>> true (not built in to lp but obviously automatable)
> ...
>> I think we should not worry about refiling existing bugs, but rather
>> just do this from this point on.
>
> That'd be a shame; your project has a large bug database and it'd be a
> long time if ever, before enough old bugs are the new "fixed-released"
> instead of the old meaning of "fixed-released".

Hm.  We release every month off trunk.  So anything currently actually
only committed but marked fixreleased will in fact become
really-fixreleased in less than a month.  Probably more like a week,
if we change the policy today.

Note that we only use fixreleased when something is landed to trunk or
a series branch, not just an alleged fix in a branch somewhere, which
would be inprogress.

On the non trunk series the releases are less frequent and thus the
lag would be longer.

> I'm not so naive as to think that "if you can script one part, surely
> you can script the other" but I think you would reduce confusion in your
> team and in those working with you if you were able to.

It may be a bit tricky because we're pulling things back out of what
should be a terminal state, but yes, it's possible.

Martin