Daniel Holbert schrieb:
Would this mean that Beta-channel users would see some features appear
on release-day, and then disappear a couple weeks later, and then those
same features (plus maybe some new ones) would suddenly reappear on the
next release day, and then potentially disappear again? (etc)
Nothing would be day-wise here. Those things would on for for the first
half of the beta cycle and off for the second (or very similar), so
those users would alternate between the state every few weeks, not on a
daily or even single-weekly basis.
We once said that we wanted roughly 1:10:100:1000 ratios between the
channels, but what we have is roughly 1:1.2:25:1000 when counting only
the most-current versions on every channels (when counting the full
channels I think we're somewhere in the range of 1:2:40:1500 for desktop
- for Android we're something like 1:2:60:1100).
This means in practice that
1) Aurora is way too small to really see the impact of a lot of
problems, e.g. in web compat, as it basically doesn't really have a
wider impact in terms of users/testers than what Nightly has (the
channel is still good for localizing and stabilizing in general, just
not much for getting feedback "from the wild"), and
2) Beta is even too small to see how stability and edge-cases apply to
the general public.
Point 1 leads to what we are discussing here: We need to use the first
few weeks of Beta to get wider-impact testing of our code and some
feedback "from the wild".
Point 2 leads to us needing to stop ("0% throttle") updates on release
after we reach 10-20 million users, review stability and testing data
from the first few days, and often enough do point-releases to fix up
stability issues or regressions (like the recent issues with proxies or
remote profiles).
So, for the short term, I think those two outcomes (early-beta-flag and
throttling) are the right thing to do here as we need to get that
testing in time. For the longer run we IMHO need to think again about
how we can get more people on the Aurora and even Beta channels so that
we can get more of that testing earlier and spare us the complications
in early-beta or even early-release phases.
Robert Kaiser
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
