Skip to content
Snippets Groups Projects
New look
  • View options
  • View options

    • Activity

    • All activity
    • Comments only
    • History only
    • Newest first
    • Oldest first
    • Karsten Loesing added SponsorZ component::applications/tor bundles/installation needs-triage owner::erinn priority::medium resolution::fixed severity::normal status::closed type::project labels
    • S
      Sebastian Hahn @sebastian

      There might be harddisk issues, in case we want to archive the builds. There are some issues where VMs can't talk directly to each other which we'd have to fix. Both seem entirely fixable tho, and definitely with sponsor money. Other than that, we should be able to propose that to a funder.

    • Karsten Loesing
      Karsten Loesing @karsten

      Replying to Sebastian:

      There might be harddisk issues, in case we want to archive the builds.

      How long would we want to keep a nightly build? Wouldn't it be sufficient to keep it until the next build is there?

      There are some issues where VMs can't talk directly to each other which we'd have to fix.

      Can you explain why VMs have to talk directly to each other for nightly builds? Which VMs are these, and what do you think is the problem? Would we want to wait to fix this until we have funding for nightly builds, or is this something we should fix anyway?

      Both seem entirely fixable tho, and definitely with sponsor money. Other than that, we should be able to propose that to a funder.

      Okay.

    • S
      Sebastian Hahn @sebastian

      Replying to karsten:

      Replying to Sebastian:

      There might be harddisk issues, in case we want to archive the builds.

      How long would we want to keep a nightly build? Wouldn't it be sufficient to keep it until the next build is there?

      At least a few weeks, until we've had the chance to check out what was actually wrong with it when we get a bug report

      There are some issues where VMs can't talk directly to each other which we'd have to fix.

      Can you explain why VMs have to talk directly to each other for nightly builds? Which VMs are these, and what do you think is the problem? Would we want to wait to fix this until we have funding for nightly builds, or is this something we should fix anyway?

      Well, the build VMs don't have a webserver for obvious reasons, but they need to be able to get the packages to a place that can sign them, and then they need to be able to get them to a place with a webserver. Without that, we would build nightlies, but not do anything with them.

    • Roger Dingledine
      Roger Dingledine @arma

      #1869 (closed) sure looks related here (and abandoned).

    • Karsten Loesing
      Karsten Loesing @karsten

      Switching from using milestones to keywords for sponsor deliverables. See #6365 (moved) for details.

      Trac:
      Keywords: N/A deleted, SponsorZ added
      Milestone: Sponsor Z: March 1, 2013 to N/A

    • E
      Erinn Clark @erinn

      Trac:
      Keywords: N/A deleted, needs-triage added

    • C
      cass @cass

      This ticket is tagged SponsorZ, but it looks like progress stalled two years ago---and possibly the need has been covered in other ways.

      Is this still a thing that needs funding?

      Trac:
      Sponsor: N/A to N/A
      Reviewer: N/A to N/A
      Severity: N/A to Normal

    • Georg Koppen
      Georg Koppen @gk

      We have nightly builds for all of our Tor Browser stuff over at: http://f4amtbsowhix7rrf.onion

      Trac:
      Status: new to closed
      Resolution: N/A to fixed

    • Trac closed