id summary reporter owner description type status priority milestone component version resolution keywords cc launchpad_bug 2381 create a tarball for beta-releases jg71 "if you expect folks to ""start testing things now"" like Brian said @ https://tahoe-lafs.org/pipermail/tahoe-dev/2015-January/009321.html let me tell you that folks def. need a tarball to cuddle with! I run a Slackware64-stable buildbot and everything looks peachy wrt the upcoming stable tahoe release but I cannot test code pulled manually from ""git trunk"" just by glueing a version number to it and running a system-wide test-install with it. (I shared such info on IRC but) I'll spare you the usual spoof of concept (pardon my russian) and demand: A tarball is needed the moment when you expect folks to tackle code in light of a release. " enhancement closed critical undecided code unknown duplicate testing, beta, tarball, release