[tahoe-dev] plans for tahoe-1.3.0 release

[zooko]

On Feb 8, 2009, at 9:33 AM, Aleksandr Milewski wrote:

> On Feb 7, 2009, at 1:27 PM, Zooko O'Whielacronx wrote:
>>
>>    * figure out why dreid and Andrzej Falout are both reporting  
>> bad performance from the prod grid
>
> Unless you find something significant and low-risk in a day or so,  
> I'm going to argue vigorously for pushing this to 1.3.1.

Yeah, it seems like dreid's and Andrzej's problems are not indicative  
of something that we can improve in 1.3.  Thanks for the feedback!   
I'll release Tahoe-1.3.0 as soon as possible.  Here's my current list:

from the Roadmap [1]:

http://allmydata.org/trac/tahoe/ticket/556 # prepend 'application- 
version' with the name of this particular application
http://allmydata.org/trac/tahoe/ticket/596 # storage servers should  
announce that they support over-read

Those two should be easy.

http://allmydata.org/trac/tahoe/ticket/535 # "recursion depth  
exceeded" failure during t=manifest of large directory tree
http://allmydata.org/trac/tahoe/ticket/538 # add get_version() method  
to Referenceable objects, describe our versioning scheme

Those two are fixed (by Brian) but, if I understand correctly,  
incompletely tested.  I'm waiting for Brian to say what to do with  
those tickets.

http://allmydata.org/trac/tahoe/ticket/566 # host tahoe dependencies  
on a tahoe grid

This isn't really a blocker for 1.3.0 release -- we can continue to  
upload more binary packages of dependencies after tagging 1.3.0.

from my blog [2]:

* remove the cygwin buildbot from the list of supported platforms,  
move it to a new list of unsupported platforms, report this issue to  
twisted and cygwin via bug reports with minimal test cases ; //or//  
fix the cygwin buildslave.  (I contributed a small test script which  
shows the problem over on //** [[twisted #3529|http:// 
twistedmatrix.com/trac/ticket/3529]]: closing stdout in a child  
process on cygwin means that process doesn't receive bytes from stdin  
anymore. I think.//.)
* remove Dan's ~ArchLinux buildbot from the list of supported  
platforms, //or// fix it.  (I sent Dan, Chris Galvan, and Brian mail  
about that behavior.)

I guess the fastest way to deal with this is to move these two  
machines to a list of "unsupported platforms" and release 1.3.0 and  
then worry about them.  :-)  Fortunately people other than me are  
looking these failures (Dan, hopefully Chris Galvan).

* clean up the repairer tests -- probably comment many of them out  
since they are written to test a repairer that discriminates among  
servers on upload, probably add a verify run after the remaining ones  
so that it is judging more carefully the state of the shares after  
repair instead of just judging the repairer's report

This one is actual coding work, that I am best suited to do.  I'll  
prioritize this one in the hopes that someone else will do the others  
on this list.  :-)

Regards,

Zooko

[1] http://allmydata.org/trac/tahoe/query? 
status=assigned&status=new&status=reopened&group=status&milestone=1.3.0
[2] http://zooko.com/log