On Sat, Dec 30, 2000 at 01:20:26AM -0800, Mr.Bad wrote:
> Wow! That doesn't seem really appropriate at all... It's a change in
> behavior, not a bug fix, and it's pretty much untested.
>
> It seems like it makes more sense to hold this kind of thing for the
> next release rather than putting it in stable. BTW, I volunteered to
> manage this branch -- could I get a chance to do so?
Ok, I'm sorry - I misunderstood.
My understanding is that changes intended for 0.3.7 go in the stable
branch, and things intended for 0.4 go in the development branch. Is
this what you had in mind?
If so, are you asserting that only bugfixes should go in the stable
branch, and thus there will be no functionality improvements in releases
before 0.4? That doesn't seem right.
It is true that this change is a change in functionality, however its
effects are well understood and there is unanimous agreement among the
developers (AFAIK) that we should implement it as soon as possible. I
have done some testing on my local machine (by manually editing my
datastore) and it seems fine.
Also, when you say you want to "manage" the branch - what does that
mean? Does it mean that you need to agree to every commit to that
branch (since that would *really* create a bottleneck particluarly if
you went on holidays or something)?
Ian.
PGP signature
