[tahoe-dev] Tahoe-LAFS v1.9.0 for Ubuntu Oneiric!? Re: when do patches need to be finished in order to get into v1.9.0?

[Zooko O'Whielacronx]

   "If it weren't for the last minute, nothing would ever get done."


Brian and everyone:

The feature freeze for Ubuntu Oneiric Ocelot (11.10) is August 11:

https://wiki.ubuntu.com/OneiricReleaseSchedule

It would be pretty cool to maintain our tradition of having a new
major release of Tahoe-LAFS in each new release of Ubuntu.

http://tahoe-lafs.org/trac/tahoe-lafs/wiki/OSPackages

http://packages.ubuntu.com/search?keywords=tahoe-lafs&searchon=names&suite=all&section=all

 * lucid (utils): Secure distributed filesystem [universe]
   1.6.1-0ubuntu2: all
 * maverick (utils): Secure distributed filesystem [universe]
   1.7.1-0ubuntu1: all
 * natty (utils): Secure distributed filesystem [universe]
   1.8.2-0ubuntu1: all

And hopefully:

 * oneiric (utils): Secure distributed filesystem [universe]
   1.9.0-0ubuntu1: all

It might take around a week after we release Tahoe-LAFS v1.9 before
the Ubuntu folks upload it into Ubuntu, so that would suggest that we
have a deadline of about August 4 if we want Tahoe-LAFS v1.9 in
Oneiric.

And for some reason it usually takes about two weeks of effort to
finalize a Tahoe-LAFS release even after we are done making changes to
it, which suggests that we should set ourselves a deadline of stopping
making changes to v1.9 around July 21 -- less than two weeks from
today.

Setting such a deadline might preclude getting Kevan's MDMF patches
(#393) into v1.9, and those patches are long-awaited and very
valuable. Are we faced with the choice of getting v1.9.0 into Oneiric
vs. getting the MDMF patches into v1.9?

Well, let's see how much progress we can make on #393 in the next few
days! :-) One of the major next steps is to merge Kevan's #1382
patches and Brian's #1363 patches. I started doing that at the Summit,
and I'm pleased with my progress so far. I'll try to make further
progress on that tonight.

There are many other patches that are close to being committable to
trunk, including my #1385 and, of course, all of the review-needed
tickets: http://tahoe-lafs.org/trac/tahoe-lafs/query?status=!closed&keywords=~review-needed
.

Everyone reading this can help by having a stab at a review-needed
ticket! Start here:

http://tahoe-lafs.org/trac/tahoe-lafs/wiki/PatchReviewProcess

Even if you just start this process and then say "Oh dear I don't
understand what any of these are about -- I give up", we would still
like to hear that you tried. Maybe we can find a ticket for you that
you *can* review, or maybe this will tell us that we need to modify
our review process. In any case I would be interested to hear if you
looked at the instructions for how to review and the list of patches
needing review.

Regards,

Zooko

http://tahoe-lafs.org/trac/tahoe-lafs/ticket/393# implement MDMF
http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1363# refactor
storage_client.py, use IServer objects instead of rrefs
http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1382# immutable peer
selection refactoring and enhancements
http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1385# stop respecting the
pre-v1.3.0 configuration files