keyword expansion and post_commit hook in 2.0 (was Re: DRAFT 2.0.0 ANNOUNCEMENT)

[Martin Pool]

2009/9/26 Stephen J. Turnbull <stephen at xemacs.org>:

> AIUI from the thread I'm responding to, the earlier implementation of
> this feature which was never released has been abandoned, and this is
> a different implementation, not a "bug fix".

If true that's disturbing and different from the policy we are trying
to follow in 2.0.

But the change (4600 on bzr.2.0) really is just adding a hook and
calling it, and I think it is reasonably safe.  Or are there other
changes here?

>  > [In micro releases, we want] to evaluate things through the eyes of
>  > a user who really dislikes surprises or disruptions.
>
> I think you vastly underestimate just how picky such users can be.
> You're running a substantial risk with little gain that I can see.
>
> Specifically, IIRC, 2.1 is targeted for late October.  Given that
> schedule, I really don't see a loss to users in saying "sorry, we
> promised this for 2.0, but you'll have to wait a couple weeks and
> accept any additional features we've added to 2.1", and a definite
> gain in reduced maintenance effort because fewer patches need to be
> created/ported and tested in 2.0.x.

Actually 2.1.0 is scheduled for February next year
<https://edge.launchpad.net/bzr/+series> but 2.1.0b1 is next week.  So
any changes we decide not to merge to 2.0, will be available to people
in a beta release within a month, but only in a six-month release in
up to six months.

-- 
Martin <http://launchpad.net/~mbp/>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: r4660.diff
Type: text/x-diff
Size: 4398 bytes
Desc: not available
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20090927/227a0b54/attachment-0002.bin