> Chrome has a six-week development cycle like Mozilla, but they only have one
> six-week beta delay between Canary and release. So Chrome can ship a new
> feature in 6-12 weeks compared to Mozilla's 12-18 weeks.
Having three pre-release populations on two branches instead of three
pre-release populations on three branches does have its scheduling advantages.
That being said, there isn't enough public information about Google's quality
standards, automated testing, pre-release population sizes/diversity, support
volume, third-party software integration issues (add-ons/plugins), etc to draw
conclusions about whether their situation is similar to Mozilla's.
That being said, I'm open to experimenting with release if there's a need to
get features out faster and we have organizational buy-in (engineering, QA,
localization, others). We can devise a plan where we'd easily fall back to the
normal train model without significant stress if faster doesn't work out.
-Alex
On Apr 25, 2013, at 1:20 PM, Chris Peterson <cpeter...@mozilla.com> wrote:
> On 4/25/13 8:20 AM, Robert Kaiser wrote:
>> 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.
>
> For comparison, Chrome's Aurora-like channel ("Dev") is just a weekly stable
> snapshot of their nightly Canary builds. [1]
>
> Chrome has a six-week development cycle like Mozilla, but they only have one
> six-week beta delay between Canary and release. So Chrome can ship a new
> feature in 6-12 weeks compared to Mozilla's 12-18 weeks.
>
> [1]
> http://www.chromium.org/getting-involved/dev-channel#TOC-How-do-I-choose-which-channel-to-use-
>
>
> chris p.
>
> _______________________________________________
> dev-platform mailing list
> dev-platform@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
