[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Monotone-devel] Release recommendations?

From: Timothy Brownawell
Subject: Re: [Monotone-devel] Release recommendations?
Date: Wed, 06 Feb 2008 06:23:26 -0600

On Wed, 2008-02-06 at 11:41 +0100, Richard Levitte wrote:
> Hello,
> I'm thinking of making a release pretty soon, but I'm wondering if
> there's any opinion on what should be included.  There are a few
> interesting development efforts going on, such as encapsulation and
> policy-branches, and the question is if we should wait for them to
> become part of the main branch or not.

Eh, I wasn't aware that releases are that big of a deal that we'd want
to delay/cancel one for something other than lack of time or some
horrible bug.

> Pros: policy branches have been one of the primarly requested changes,
> and finally having them in a release would be a good thing.

Having them in the release would probably scare everyone away. ;)

> Cons: policy branches are currently not tested at all (well, except
> for the test cases), and there's really no saying what the effects
> will be in the longer run...

There is exactly *one* test that actually uses the policy branch stuff,
added yesterday. All the others haven't been changed, so they just check
that current behavior is preserved in you don't have any projects

It's also very nearly impossible to recover from getting multiple heads
in you highest-level policy branches (the one referenced in
$confdir/projects/$prefix). This will definitely have to be fixed (this
particular problem actually shouldn't be that hard), and I'd guess that
other things like this will come up as well.


Free (experimental) public monotone hosting:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]