> 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
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 eve
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? (e
On Fri 19 Apr 2013 04:27:22 PM PDT, Asa Dotzler wrote:
> On 4/19/2013 4:04 PM, Robert O'Callahan wrote:
>> On Sat, Apr 20, 2013 at 10:34 AM, Asa Dotzler wrote:
>>
>>> That would be great -- if we had a significantly larger Aurora
>>> population..
>>> Right now, the only way to get anything close
On Sat, Apr 20, 2013 at 11:27 AM, Asa Dotzler wrote:
> I don't think it's that black and white. PDF.js and our new Cookie policy
> are both user facing features and web compat concerns that need a crap ton
> of compat testing.
Hmm, PDF.js yes, maybe click to play too.
But for cookie policy, Sh
On 4/19/2013 4:04 PM, Robert O'Callahan wrote:
On Sat, Apr 20, 2013 at 10:34 AM, Asa Dotzler wrote:
That would be great -- if we had a significantly larger Aurora population..
Right now, the only way to get anything close to decent "did we break the
web" testing is on our Beta channel.
I
On Sat, Apr 20, 2013 at 10:34 AM, Asa Dotzler wrote:
> That would be great -- if we had a significantly larger Aurora population.
> Right now, the only way to get anything close to decent "did we break the
> web" testing is on our Beta channel.
>
I think Daniel was concerned about user-visible
On 4/19/2013 3:17 PM, Daniel Holbert wrote:
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
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)
This seems like it co
Johnathan and I also spoke about this last week, and we were going to sync up
with Gavin to work out details and find an owner for channel-specific
preference enables/disables. We'd only discussed having Nightly-only, up to
Aurora, and up to Beta. Up to early beta is a good addition.
Let me set
Lukas Blakk schrieb:
* Releng automation to switch/edit mozconfigs for earlier betas to check for
this flag
I think it would be good if we wouldn't have to rely on releng there, as
this again introduces the factor of someone possibly forgetting to do
this. Ideally this should be fully automa
On Apr 18, 2013, at 1:18 PM, Gregory Szorc wrote:
>
> I think this is a good idea. I've wanted it for a while as well. I've even
> already filed a build config bug to support it:
> https://bugzilla.mozilla.org/show_bug.cgi?id=853071.
>
> What we don't have are specific and common use cases th
On 04/18/13 04:03 PM, Lukas Blakk wrote:
> Hello,
>
> I'm following up on an action from our Firefox 20 Post-Mortem where it was
> discussed that it would be helpful to have a way to pref on a set of features
> that want to be in early Beta builds to garner feedback and audience reach
> but sho
On 4/18/13 1:03 PM, Lukas Blakk wrote:
Hello,
I'm following up on an action from our Firefox 20 Post-Mortem where it was
discussed that it would be helpful to have a way to pref on a set of features
that want to be in early Beta builds to garner feedback and audience reach but
should not ship
14 matches
Mail list logo
