bzr 0.7 release candidate

[John Arbash Meinel]

A.J. Rossini wrote:
> On 1/9/06, Robey Pointer <robey at lag.net> wrote:
> 
>>On 8 Jan 2006, at 20:10, Martin Pool wrote:
>>
>>
>>>A couple of people have suggested that we move towards time-based
>>>releases for bzr.  I propose to start making releases candidates on
>>>around the first of each month.
>>
>>+1 :)
>>
>>robey
> 
> 
> My only concern is that I'm using bzr VERY actively (since about 0.4)
> to try multiple projects -- it works great, and I'm happy with the
> "feature-based" release tendency.   If those features could be broken
> down into monthly steps (one can argue this is a "good thing") then
> +1.
> 
> If just for the sake of releasing, with a medium/high probably of
> increased instability, -1.

Well, I think we are also starting to focus on maintaining
compatibility. One of the proposals we are going to be working with, is
that sometime after Feb, we are going to maintain compatible interfaces
for 6 months since they show up in a release, either that or 6 months
from the time they are deprecated.

> 
> (one could ask why I'm using alpha/beta software -- but the point is
> that right now, it's "the right interface" for what I need for these
> projects).
> 
> 
> best,
> -tony

I understand your concern for stability. I also know that the time
between 0.6 and 0.7 was far too long. The main bzr.dev tree is actually
fairly stable, since things have to make it through a double check
before they get added there. (And test cases should always pass in
bzr.dev, and hopefully any of the integration branches.).

I think a more often release cycle will mean people don't have to grab
bzr.dev when something gets updated.

John
=:->
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060109/c5a739d9/attachment.pgp