[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #32676 [Applications/Tor Browser]: Consider publishing a tarball with all Tor Browser langpacks
#32676: Consider publishing a tarball with all Tor Browser langpacks
-------------------------------------------------+-------------------------
Reporter: intrigeri | Owner: tbb-
| team
Type: enhancement | Status:
| needs_information
Priority: Medium | Milestone:
Component: Applications/Tor Browser | Version:
Severity: Normal | Resolution:
Keywords: AffectsTails, tbb-rbm, | Actual Points:
TorBrowserTeam201912R |
Parent ID: | Points:
Reviewer: gk | Sponsor:
-------------------------------------------------+-------------------------
Comment (by intrigeri):
Replying to [comment:6 gk]:
> So, how about scoping that feature to only release builds? Or if that's
really necessary to alpha builds in addition to that?
As far as I'm concerned, I think it's totally fine to start with release
builds only: it'll give us the expected benefits in the cases when it
matters most.
Then we'll see how much we miss it in the rarer cases when we include an
alpha, and we can get back to you if needed; meanwhile you'll also have
data/feelings about the cost of this extra tarball on your side. So I
prefer postponing this discussion about alphas to a time when we'll have
less hypothetical info to reason about :)
Should I try to update the patch to only trigger on release builds? Or is
it cheaper for you to do it yourself than to review an untested fixup
patch from me?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/32676#comment:7>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs