-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[Releng] Publish Nightly app to Production track instead of nightly track #12208
[Releng] Publish Nightly app to Production track instead of nightly track #12208
Comments
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? |
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. |
Everything is so confusing and messy😡 |
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 |
Nightlies have NEVER been here to be used as primary browser by users. 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. 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? |
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.
There was Firefox / Firefox Beta on one hand and Firefox Preview / Firefox Preview Beta on the other hand.
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.)
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. |
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
The text was updated successfully, but these errors were encountered: