[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #34055 [Applications/Tor Browser]: Use and document 'tbb-backport' in the release process
#34055: Use and document 'tbb-backport' in the release process
--------------------------------------+--------------------------
Reporter: cypherpunks | Owner: tbb-team
Type: defect | Status: closed
Priority: Medium | Milestone:
Component: Applications/Tor Browser | Version:
Severity: Normal | Resolution: fixed
Keywords: TorBrowserTeam202004 | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
--------------------------------------+--------------------------
Comment (by cypherpunks):
Replying to [comment:10 gk]:
> Replying to [comment:9 cypherpunks]:
> > BTW, what's wrong with with the variant in the comment:description for
you?
>
> Nothing.
Then it's not clear why you don't use it.
> > `tbb-backport` doesn't seem to be documented in
https://gitweb.torproject.org/tor-browser-
spec.git/tree/processes/ReleaseProcess
>
> Yes, because that document describes the process for getting a release
out *once all patches have landed*. Considerations about which patch
should actually get backported for which release happen before that.
Thanks for the clarification. It seems we need ReleasePreparationProcess
document ;)
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/34055#comment:11>
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