#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 gk):
Replying to [comment:6 cypherpunks]:
> > And, yes, we *are* using the ticket in the release process.
> s/ticket/tag
Thanks, fixed.
> > At the end there is no guarantee that things tagged with `tbb-
backport` get backported.
> They should be re-tagged or cleared out of it every major stable update.
And that should be documented and used as part of the release process.
They do get cleared out with every major stable update and I just amended
the text on the hacking document.
> > Oh, and I updated
https://trac.torproject.org/projects/tor/wiki/doc/TorBrowser/Hacking
accordingly so that our use of `tbb-backport` is documented there.
> The hyperlink
https://trac.torproject.org/projects/tor/query?status=!closed&keywords
=~tbb-backport is a search query which lists `tbb-backported` too. That's
why it cannot be used.
Yeah, I added a better link
> Could you backport #32493 to get parity with tba?
It does not seem like we do this for the upcoming stable release and the
next regular stable one is 9.5.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/34055#comment:7>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online