0.8.3 bugfix release

[John Arbash Meinel]

Wouter van Heyst wrote:
> On Sun, Jun 18, 2006 at 02:00:56PM -0500, John Arbash Meinel wrote:

...

>>
>> I would love to get the tests passing on Win32 and OS X, and then
>> release an 0.8.3 with a bunch of our speed improvements and general
>> bugfixes.
> 
> Due to a Debian point of view I am used to point releases with minimal
> changes, but I wouldn't mind a compatible point release with speedups
> and no regressions.
> 
> Wouter van Heyst
> 
> 

Well, I can remember at least 3 or 4 simple bugs that have been squashed
that would be applicable to a point release. The problem is that I have
very little clue where and when they were exactly fixed.

If it is really important, we could spend the time to ferret out all of
these, and create an 0.8.3. Usually a point release means bug fixes, and
no new features.
So far, I don't think we have any real new features in bzr.dev over
bzr-0.8. Lots of improvements, but nothing that really changes the user
interface with the tool.
I do realize that I'm neck deep in bzr.dev, so I don't have a good grasp
on what has changed versus 0.8. I never use any of the releases. Which
has some downsides, but dogfooding does mean development bugs get
squashed rather quickly.

I really do like that there are people on this list who use the
releases, as it reminds us that we need to make a new release. :) I
think I do quite a bit of user support on this list, but I realize I
don't spend much time in IRC, or actually working with other people who
are using bzr. So I have a slightly skewed view of priorities.

I do believe that our long-term plans are to get a performance optimized
version of bzr into dapper, though it might actually be called 0.9.

Also, it might depend what you call bugfixes. Being slow can be seen as
a bug. :)

Just to give a general picture 0.8rc1 was at revno 1664, 0.8 was 1704,
1710 merged the rest of 0.8.x fixes
And we are now at revno 1791.

I count 9 fixes before revno 1730 that would be worthy of backporting.
(bzr info, ftp support, push only pushes ancestry, a couple "small
fixes" from Martin, etc). Not to mention my rather large set of
unicode/encoding fixes.

I'm not a good one to pick out what is worthy of backporting, versus
just creating a new release.
The only current regressions I know of are the DeprecationWarning
because all_revision_ids() is used in lots of places, and that some of
the Unicode tests fail on Mac.

John
=:->

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 254 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060618/03790220/attachment.pgp