Am 29.03.2017 um 02:47 schrieb James Mason:
Just to go a little bigger picture on your otherwise solid, and detailed, plan, I'd say:
In general, Leap should have the current Firefox ESR release by default, with the stable release as an alternative, to the extent it is manageable.
in https://lists.opensuse.org/opensuse-factory-mozilla/2017-03/msg00002.html I'm explaining what I already do with regards to packaging both variants with explanation about package names. I haven't thought about the implications caused by shipping both variants in one distribution and how to handle upgrades and going from A to B and back. But I explained that switching back and forth is probably a bad idea and I'm not sure how to make it save enough.
Tumbleweed should have the current Firefox (stable) release by default. ESR as an alternative (should always be available), as well as best effort to build beta and nightly. Failures in the substandard channels will give us a pretty good heads-up on upcoming maintenance nightmares ;-)
I'm mainly lagging behind nowadays but there are mozilla:beta and mozilla:alpha repositories which were used to provide betas and dev editions but not nightlies. I once wanted to build nightlies but OBS does not support what is required to do it server based and some things are breaking unnoticed as the patches are currently set up. So nightly is currently out of scope and I barely can provide betas but in this cycle I have them. So is there any feedback how transition from the current shipping model to the proposed one should look like assuming we want to implement it starting with 42.3? Wolfgang -- To unsubscribe, e-mail: opensuse-factory-mozilla+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory-mozilla+owner@opensuse.org