Project Dawn or the end of Aurora

Sylvestre Ledru s at mozilla.com
Fri Mar 31 20:52:03 UTC 2017


I agree that we cannot afford to just close aurora and start nightly

We have been discussing about two options:

* reuse the org.mozilla.fennec_aurora to publish nightly instead.

I know this will add legacy and technological debt but this is fast and
"easy" to implement (generating apk with this id).

* reaching out to Google to know if they can use their super powers to
allow us to reuse the application to publish nightly with the current id

(which is, btw, already used by another uncontrolled account)

S



Le 31/03/2017 à 13:22, Kevin Brosnan a écrit :
> How are we handling Android? We won't be able to move users around.
> Most of my concern is around how we handle Aurora in the Play Store.
> We are locked into the ID org.mozilla.fennec_aurora
>  as I understand. I assume that we would do the opposite of what we
> are doing for desktop and rebrand Aurora in the Play Store as Nightly.
> The other option, abandon the 10k users on Aurora and then choose to
> upload Nightly to the Play Store seems poor as we will loose the 9k
> users that we gained by uploading to the Play Store. We would
> eventually get the users back but it took us 6 - 8 months to get to
> this point.
>
> Kevin
>
> On Fri, Mar 31, 2017 at 8:48 AM, Sylvestre Ledru <s at mozilla.com
> <mailto:s at mozilla.com>> wrote:
>
>     tl;dr The Aurora branch is going away in April.
>
>
>     What
>
>     In order to address the complexity and cycle length issues, the
>     release management team, in coordination with Firefox product
>     management and engineering, is going to remove the Aurora
>     stabilization phasefrom the cycle.
>
>
>     When
>
>
>     On April 17th, Firefox 55 will remain on Nightly. This means
>     Firefox 55 will remain on Nightly for two full cycles. On June
>     13th, Firefox 55 will migrate directly from Nightly to Beta.
>
>
>     Why
>
>     1.
>
>         As originally intended
>         <https://mozilla.github.io/process-releases/draft/development_overview/>,
>         Aurora was to be the first stabilization channel having a user
>         base 10x the size of Nightly so as to provide additional user
>         feedback. This original intent never materialized.
>
>     2.
>
>         The release cycle time has required that we subvert the model
>         regularly over the years by uplifting new features to meet
>         market requirements.
>
>
>     How
>
>      *
>
>         The stabilization cycle from Nightly to Release will be
>         shortened by 6-8 weeks.
>
>      *
>
>         A staged rollout mechanism, similar to what we do today with
>         Release, will be used for the first weeks of Beta.
>
>      *
>
>         Our engineering and release workflow will continue to have
>         additional checks and balances rolled out to ensure we ship a
>         high quality release.
>
>          o
>
>             We will focus on finding and fixing regressions during the
>             Nightly cycle and alleviate time pressure to ship to
>             reduce the 400-600 patches currently uplifted to Aurora.
>
>          o
>
>             A new feature will merge from Nightly to Beta only when
>             it’s deemed ready, based on pre-established criteria
>             determined by engineering, product, and product integrity.
>
>          o
>
>             Tooling such as static analysis, linters, and code
>             coverage will be integrated into the development process
>
>
>
>     Sylvestre
>
>
>
>
>     Go-live
>
>     	
>
>     Nightly
>
>     	
>
>     Aurora
>
>     	
>
>     Beta
>
>     	
>
>     Release
>
>
>     	
>     	
>     	
>     	
>
>     2017-03-07
>
>     	
>
>     55
>
>     	
>
>     54
>
>     	
>
>     53
>
>     	
>
>     52
>
>
>     	
>     	
>     	
>     	
>
>     2017-04-18
>
>     	
>
>     55
>
>     	
>     	
>
>     54
>
>     	
>
>     53
>
>
>     	
>     	
>     	
>     	
>
>     2017-06-13
>
>     	
>
>     56
>
>     	
>     	
>
>     55
>
>     	
>
>     54
>
>
>     	
>     	
>     	
>     	
>
>     2017-08-08
>
>     	
>
>     57
>
>     	
>     	
>
>     56
>
>     	
>
>     55
>
>
>     	
>     	
>     	
>     	
>
>     2017-10-10
>
>     	
>
>     58
>
>     	
>     	
>
>     57
>
>     	
>
>     56
>
>
>     	
>     	
>     	
>     	
>
>     2017-11-14
>
>     	
>
>     59
>
>     	
>     	
>
>     58
>
>     	
>
>     57
>
>
>     	
>     	
>     	
>     	
>
>     2018-01-09
>
>     	
>
>     60
>
>     	
>     	
>
>     59
>
>     	
>
>     58
>
>
>     -- 
>     You received this message because you are subscribed to the Google
>     Groups "sphilp-directs at mozilla.com
>     <mailto:sphilp-directs at mozilla.com>" group.
>     To unsubscribe from this group and stop receiving emails from it,
>     send an email to sphilp-directs+unsubscribe at mozilla.com
>     <mailto:sphilp-directs+unsubscribe at mozilla.com>.
>     To post to this group, send email to sphilp-directs at mozilla.com
>     <mailto:sphilp-directs at mozilla.com>.
>     To view this discussion on the web visit
>     https://groups.google.com/a/mozilla.com/d/msgid/sphilp-directs/93355eb5-c6eb-7a26-0163-30b6e3eccec9%40mozilla.com
>     <https://groups.google.com/a/mozilla.com/d/msgid/sphilp-directs/93355eb5-c6eb-7a26-0163-30b6e3eccec9%40mozilla.com?utm_medium=email&utm_source=footer>.
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/mobile-firefox-dev/attachments/20170331/f7eb6aef/attachment-0001.html>


More information about the mobile-firefox-dev mailing list