#2381 closed enhancement (duplicate)

create a tarball for beta-releases

Reported by: jg71 Owned by:
Priority: critical Milestone: undecided
Component: code Version: unknown
Keywords: testing, beta, tarball, release Cc:
Launchpad Bug:


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.

Change History (1)

comment:1 Changed at 2015-02-08T23:45:37Z by daira

  • Resolution set to duplicate
  • Status changed from new to closed

This doesn't require a separate ticket. Uploading of tarballs should be automatic on every commit to master. It currently isn't because of #2315.

Last edited at 2015-02-08T23:47:44Z by daira (previous) (diff)
Note: See TracTickets for help on using tickets.