Re: [tor-bugs] #33184 [Applications/Tor Browser]: Support for Fenix

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#33184: Support for Fenix
--------------------------------------+--------------------------
 Reporter:  sisbell                   |          Owner:  tbb-team
     Type:  enhancement               |         Status:  new
 Priority:  Medium                    |      Milestone:
Component:  Applications/Tor Browser  |        Version:
 Severity:  Normal                    |     Resolution:
 Keywords:  tbb-mobile, Android       |  Actual Points:
Parent ID:                            |         Points:
 Reviewer:                            |        Sponsor:
--------------------------------------+--------------------------

Comment (by gk):

 Here come some release cycle notes I collected that should help us
 determine which combinations of components we want to base our nightly and
 release builds on:

 The release cycle for mozilla-* code is 4 weeks which means 3 weeks 3
 betas each and one week with 3 rcs (affects GeckoView)

 For Fenix we have beta and nightly versions with geckoview on
 beta/nightly. In particular Mozilla builds

 a) nightly:    geckoBeta/fenixNightly and geckoNightly/fenixNightly (only
 latter is published to Google Play)
 b) beta:       geckoBeta/fenixBeta
 c) production: geckoBeta/fenixProducion

 (Yes, the release version of GeckoView is currently not used it seems)

 android-components used on Fenix `master` is updated daily by a bot to the
 latest nightly version

 geckoview used on android-components' `master` is updated daily by a bot
 to the latest nightly version and to the latest beta every 2-4 days (I
 suspect that corresponds to the 3 betas each week above)

 See: `docs/contribute/merge_day.md` for what happens during merge days in
 the android-components repository.

 How does branching and release tagging for Fenix currently look like?

 4.3 release
   - branching off 1 week before release
 (`7f1ef17d8b4b6aa5381819ef7a7ab822668b05c1` merge-base with `master`), no
 beta releases before that and android-components got pinned to a stable
 version for release on first beta which got out 3 days before the final
 release
 4.2 release
   - branching off 1 day before release
 (`301f56d144754e6c26f7e390952f35287185dfd4` merge-base with `master`), no
 beta releases before that and android-components got pinned to a stable
 for release on first beta which got out 1 days before the final release

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/33184#comment:8>
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