[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #26050 [Applications/Tor Browser]: achieve update "watershed" for ESR60-based Tor Browser
#26050: achieve update "watershed" for ESR60-based Tor Browser
--------------------------------------------+--------------------------
Reporter: mcs | Owner: tbb-team
Type: defect | Status: new
Priority: Very High | Milestone:
Component: Applications/Tor Browser | Version:
Severity: Normal | Resolution:
Keywords: ff60-esr, TorBrowserTeam201805 | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
--------------------------------------------+--------------------------
Changes (by boklm):
* status: needs_information => new
Comment:
If we switch from `update_3` to `update_4`, I think the list of things we
should do before the 8.0 release are:
- adding a symlink `update_4/release -> update_3/release`, so that
update_4 URLs start working.
- tell external tools such as torbrowser-launcher or gettor to switch to
update_4 URLs
And then when releasing 8.0.1:
- remove the `update_4/release -> update_3/release` symlink, put the 8.0.1
release in `update_4/release` and keep 8.0 in `update_3/release`.
- add a redirect `update_3/downloads.json -> update_4/downloads.json`
- add a redirect `update_3/release/Linux_x86_64-gcc3/x/en-US ->
update_4/release/Linux_x86_64-gcc3/x/en-US` (which is the URL used by
torbrowser-launcher)
As an alternative, maybe we can avoid an `update_3 -> update_4` change,
and instead redirect the update pings where the version number starts with
`7.` to a different directory updating users to 8.0. In that case the list
of things to do before releasing version 8.0.1 would be:
- teach the update_responses script to add redirects for `7.*` versions in
the .htaccess file to a different directory, for instance
`update_pre_8.0`.
And when releasing 8.0.1:
- copy `update_3/release` (containing the 8.0 update) to
`update_pre_8.0/release`, and then update `update_3/release` normally.
So unless I'm missing something, it seems staying with `update_3` and
redirecting old versions to a different directory would be more simple
than switching from `update_3` to `update_4`.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/26050#comment:4>
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