Skip to content
This repository has been archived by the owner on Feb 20, 2023. It is now read-only.

[Releng] Publish Nightly app to Production track instead of nightly track #12208

Closed
liuche opened this issue Jul 2, 2020 · 7 comments · Fixed by mozilla-releng/scriptworker-scripts#243
Assignees

Comments

@liuche
Copy link
Contributor

liuche commented Jul 2, 2020

As part of the Nightly channel consolidation, we switched the org.mozilla.fenix to publish the Nightly app.

However, I forgot that you can't return a Production app back to "in-development", so while we are pushing Nightly builds to the org.mozilla.fenix channel, they are landing on the Nightly track -- but need to be on the Production track to be published.

We need to update our automation so that 1) we publish directly to the Production track, 2) automatically publish that release (because for nightly releases we should not require relman to publish each release).

┆Issue is synchronized with this Jira Task

@github-actions github-actions bot added the needs:triage Issue needs triage label Jul 2, 2020
@liuche liuche removed the needs:triage Issue needs triage label Jul 2, 2020
@liuche
Copy link
Contributor Author

liuche commented Jul 2, 2020

Bugzilla for manual updates by relman on weekdays: https://bugzilla.mozilla.org/show_bug.cgi?id=1650180

@JohanLorenzo if you don't get a fix for this tomorrow, would someone else on your team be able to pick it up?

@ghost
Copy link

ghost commented Jul 3, 2020

Communication is what's lacking from your end to the users. Inform the users who are using the Fenix "production" channel that the app is transitioning to use the "Nightly" channel and give them enough time. Play Store page for Firefox Preview already lists the Nightly channel and with a Nightly version updated already!

When asked for the communication, developers lock the threads. And accuse the users who are helping that they made incorrect assumptions about several versions of Firefox on the Play Store (perhaps, if you communicated a little better, you won't have to do that)!

You might also mark this comment as "off-topic" but I don't want to file another issue on this repository. That's why I'm putting it here.

@sheikh-azharuddin
Copy link

Everything is so confusing and messy😡
Mozilla is forcing to move to Firefox preview(Firefox nightly now) from Firefox preview nightly and Firefox nightly....but what about the data???? You don't have sync features for collection and top sites...so if I move I will loose everything...plus I have to login again to all sites...how fair is this? There must be some way to export data or migrate data to the new Firefox nightly

@sheikh-azharuddin
Copy link

sheikh-azharuddin commented Jul 3, 2020

Also if Firefox preview nightly will be removed why it is still being updated in below link??? Last updated 29mins ago...!

https://firefox-ci-tc.services.mozilla.com/tasks/index/project.mobile.fenix.v2.nightly/latest

@Dunexus
Copy link

Dunexus commented Jul 3, 2020

Nightlies have NEVER been here to be used as primary browser by users.
The goal of nightlies is to test features before they go to production channel. There is only one production channel, Firefox <org.mozilla.firefox>, not Preview, Beta, Nightly.

The transition period between Fennec and Fenix needed to have two distinct life cycle (main, beta and nightly) as Fenix couldn't replace Fennec before Fenix been considered features ready and stable enough by Firefox Mobile team.
This may be confusing but there was no other way to have both living during development phase.

Currently, this update channel issues is been addressed, see #12207 (comment)

@ghost
Copy link

ghost commented Jul 3, 2020

Nightlies have NEVER been here to be used as primary browser by users.
The goal of nightlies is to test features before they go to production channel. There is only one production channel, Firefox <org.mozilla.firefox>, not Preview, Beta, Nightly.

The transition period between Fennec and Fenix needed to have two distinct life cycle (main, beta and nightly) as Fenix couldn't replace Fennec before Fenix been considered features ready and stable enough by Firefox Mobile team.
This may be confusing but there was no other way to have both living during development phase.

Currently, this update channel issues is been addressed, see #12207 (comment)

I know the situation all too well. And why they needed those separate channels. But this is no way to handle it. Currently there are at least 3 different versions of Nightly. And a few weeks ago there were seemingly 2 Beta/ production channels were floating around in the guise of an experiment (this caused real trouble, and how many users do you think have installed the "beta" version instead of the "production" version and vice-versa?! And are now stuck on the "Beta" channel, for who knows how long). And now they're switching Fenix production channel to Nightly overnight! This muct be some sort of joke with users. And not to mention they accuse us the users of wrongly assuming which versions were what who try to help others in deciding what versions to install. If they communicate we wouldn't have to "assume" or "guess".

They lock the threads when asked for communication from them! This is not how "Open development environment" where developers and users equally try to contribute in there capacity!

Developers please stop experimenting with users. That's what I'm asking! And communicate if possible, maybe?

@Dunexus
Copy link

Dunexus commented Jul 3, 2020

Currently there are at least 3 different versions of Nightly.

They are transitionning from the old Firefox Nightly <org.mozilla.fennec_aurora>, Fenix Nightly<org.mozilla.fenix.nightly> and Fenix <org.mozilla.fenix> to using only <org.mozilla.fenix> as new Firefox Nightly.
The in-app message was supposed to help but there was a bug leading to the wrong play store page.
Again, nightly is not supposed to be a stable version, when using it you should be open minded and prepared to such bugs.

And a few weeks ago there were seemingly 2 Beta/ production channels were floating around in the guise of an experiment

There was Firefox / Firefox Beta on one hand and Firefox Preview / Firefox Preview Beta on the other hand.
The Preview label was clear about the last two being a preview of the rework of Firefox in active development.

this caused real trouble, and how many users do you think have installed the "beta" version instead of the "production" version and vice-versa?!

The "beta" label clearly means it is not production. Beta programs are available on the play store for so many apps (chrome, google maps, etc.)

And now they're switching Fenix production channel to Nightly overnight

This is wrong, they switch nightly channel from the old one to firefox preview nightly, it should not affect users using versions other than nightly.
The production channel hasn't been changed (still <org.mozilla.firefox>) nor updated to Fenix yet.

@data-sync-user data-sync-user changed the title [Releng] Publish Nightly app to Production track instead of nightly track FNX3-15215 ⁃ [Releng] Publish Nightly app to Production track instead of nightly track Aug 11, 2020
@data-sync-user data-sync-user changed the title FNX3-15215 ⁃ [Releng] Publish Nightly app to Production track instead of nightly track FNX-13248 ⁃ [Releng] Publish Nightly app to Production track instead of nightly track Aug 11, 2020
@data-sync-user data-sync-user changed the title FNX-13248 ⁃ [Releng] Publish Nightly app to Production track instead of nightly track FNX2-15083 ⁃ [Releng] Publish Nightly app to Production track instead of nightly track Aug 11, 2020
@liuche liuche closed this as completed Aug 18, 2020
@data-sync-user data-sync-user changed the title FNX2-15083 ⁃ [Releng] Publish Nightly app to Production track instead of nightly track [Releng] Publish Nightly app to Production track instead of nightly track May 19, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
5 participants