Re: [tor-bugs] #33809 [Applications/Tor Browser]: Fast-Forward Tor Browser Versions

[Tor Bug Tracker & Wiki]

#33809: Fast-Forward Tor Browser Versions
--+--
 Reporter:  sysrqb|  Owner:  tbb-team
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #33808| Points:
 Reviewer:|Sponsor:
--+--

Comment (by boklm):

 This scheme, with the change suggested by brade (using an additional
 version part for the ${TB_PATCH}) sounds good to me for the releases. For
 the nightly builds however, I think this will make things more complicate
 for the script signing updates (#25102) which currently assumes that
 version numbers are based on the date.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #33809 [Applications/Tor Browser]: Fast-Forward Tor Browser Versions

[Tor Bug Tracker & Wiki]

#33809: Fast-Forward Tor Browser Versions
--+--
 Reporter:  sysrqb|  Owner:  tbb-team
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #33808| Points:
 Reviewer:|Sponsor:
--+--

Comment (by brade):

 This is an interesting idea. Mark and I wonder if we can just add another
 version part instead of multiplying the last part of the Firefox version
 by 100, e.g., Tor Browser based on Firefox 90.0 would use 90.0.0, the
 first TB patch would use 90.0.1, etc.  Another example: Tor Browser with a
 third patch and based on Firefox 91.0b1 would use 91.0b1.3.  We are not
 sure which scheme is the best choice, but it looks like Mozilla's version
 comparison code can handle any number of version parts.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #33809 [Applications/Tor Browser]: Fast-Forward Tor Browser Versions

[Tor Bug Tracker & Wiki]

#33809: Fast-Forward Tor Browser Versions
--+--
 Reporter:  sysrqb|  Owner:  tbb-team
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #33808| Points:
 Reviewer:|Sponsor:
--+--

Comment (by sysrqb):

 And I sent a mail about it, too.

 https://lists.torproject.org/pipermail/tbb-dev/2020-April/001063.html

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

[tor-bugs] #33809 [Applications/Tor Browser]: Fast-Forward Tor Browser Versions

[Tor Bug Tracker & Wiki]

#33809: Fast-Forward Tor Browser Versions
--+--
 Reporter:  sysrqb|  Owner:  tbb-team
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:  #33808
   Points:|   Reviewer:
  Sponsor:|
--+--
 Let's say in the future Tor Browser is based on Firefox 90.0, Tor Browser
 Beta is based on Firefox 91.0b1, and Tor Browser Nightly is based on
 92.0a1.

 I propose Tor Browser uses the following versioning schemes:
 Release: `${FF_MAJOR}`.`${FF_MINOR}`.`${PATCH}` (e.g. `90.0.1`)
 Beta: `${FF_MAJOR}`.`${FF_MINOR}`b`${PATCH}` (e.g. `91.0b101`)
 Nightly: `${FF_MAJOR}`.`${FF_MINOR}`a1 (i.e. `92.0a1`)

 Where `${PATCH}` is (`${FF_PATCH}`*100) + `${TB_PATCH}`), therefore we
 move the Firefox patch number into the third digit (hundreds) and we place
 the Tor Browser patch number in the first and second digits. (Initially, I
 began proposing (`${FF_PATCH}`*10), but what-if-we-need-11-releases?).
 That would be a sad month, but probably safe-than-sorry.

 I think we can re-use Firefox's alpha/nightly version number.

 The main advantage of this scheme is that the underlying Firefox version
 is immediately clear when looking at a Tor Browser version number.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs