0.19 release schedule
James Westby
jw+debian at jameswestby.net
Wed Jul 18 19:20:46 BST 2007
Hi all,
It looks like I'm "it" for 0.19.
This is my preferred release schedule for the next release. It gives
just over a month of open trunk on 0.19. This seems a little short,
would anybody like a couple more weeks?
All dates refer to the evening UTC. I'll use Tuesdays again as that
gives people a day or two after the weekend and suits me better anyway.
Option 1
* 14 Aug - Feature freeze
* 21 Aug - RC1
* 28 Aug - Release if RC1 shows no serious regressions.
This does mean that I will be unavailable for the weekend just before
RC1, but I hope that wont be too problematic. Perhaps I could delegate
for that weekend?
As for the changes that this release would contain, I would like it if
you could reply to this message and tell me what you hope to get merged
for this release, or at least what you will be spending time on.
One thing I would like to do is to bump the default format, at least to
dirstate-tags, but perhaps all the way to dirstate-with-subtree. I would
prefer the latter to do it in one go. Does anyone have any preference. I
believe that Martin said he had a branch with a changed default, and
there were some failing tests. I would like to get the change in this
week, one to get some testing of it from us, and two so that people know
what they will be aiming for with their new code.
As for current outstanding merge requests I can see the following as
needing a review:
http://bundlebuggy.aaronbentley.com/request/%3Cm24pk53b9j.fsf@free.fr%3E
Vincent's connection reuse changes. He is going on holiday soon, and
it would be good to some progress on it before he goes.
Everything else looks like it is ticking along ok, either waiting for
code changes, or with an recently updated merge request that I assume
people will get to soon.
As for bugs the following are marked critical
* 55149 documentation audit needed
- I am trying to work on this.
* 116598 bzr 0.14 cannot push via sftp/bzr+ssh to branch with WT4
* 121509 bzr check should verify last-changed fields and per file
knit parents.
* 124089 wsgi smart server chrooting does not manage additional
paths
* 124859 incorrect repository detected with symlink to a branch
And there are plenty of bugs marked high importance. I realise that
there is currently lots of work going on to try and sort out core data
structures, but the list of bugs appears to be slowing growing at the
moment. I don't want to designate a bugfix only merge week, but we have
a feature freeze week where we could accept bug fixes.
Thanks for your time,
James
--
James Westby -- GPG Key ID: B577FE13 -- http://jameswestby.net/
seccure key - (3+)k7|M*edCX/.A:n*N!>|&7U.L#9E)Tu)T0>AM - secp256r1/nistp256
More information about the bazaar
mailing list