[tahoe-dev] calling all bugs! Please report to v1.6.1

Zooko O'Whielacronx zookog at gmail.com
Mon Feb 15 04:36:10 UTC 2010


Dear people of tahoe-dev:

David-Sarah wrote:

http://allmydata.org/trac/tahoe-lafs/ticket/948#comment:3

"We should probably put out a point release."

Okay, I agree, because as David-Sarah pointed out, #948 is a
regression in Tahoe-LAFS v1.6.0 compared to Tahoe-LAFS v1.5. (Only if
you use "tahoe backup", or more precisely if you try to view a
directory created by v1.6.0's "tahoe backup" which is tiny enough to
fit into a literal cap.)

So let us have a v1.6.1 release, fixing #948 and any other regressions
or easy, narrow, bug-fixes. How about if we release it next weekend?
Please be on the lookout for regressions in v1.6.0 compared to earlier
releases of Tahoe-LAFS and for any other specific, narrow bugs that we
might be able to fix this week.

I disagree with David-Sarah's suggestion of pulling in #778 -- that
one could surprise users. Let's commit #778 to trunk as soon as it
passes review after v1.6.1.

Looking at the timeline, there haven't been any potentially disruptive
patches committed to trunk since v1.6.0 except for this one:

http://allmydata.org/trac/tahoe-lafs/changeset/20100206054314-e27fb-72d19517773461d3461a7f227b9242d026899772

We'll probably need to comment-out that line to make the v1.6.1
release. (And maybe when we put that line back we'll do so with an
accompanying unit test!)

I created a Milestone to track tickets flagged as being relevant to v1.6.1:

http://allmydata.org/trac/tahoe-lafs/roadmap

Regards,

Zooko



More information about the tahoe-dev mailing list