[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):
> And, yes, we *are* using the ticket in the release process.
s/ticket/tag
> 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.
> 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.
Could you backport #32493 to get parity with tba?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/34055#comment:6>
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