On 11 November 2015 at 23:16, Jimmy Berry <jimmy@boombatower.com> wrote:
This was a simple request and as I've seen many times on this list people get caught up on a lot of non-relevant side-topics. Especially given this heavily plays into power-users testing out new releases it should be considered.
But that's the point.. "testing out new releases" is done by testing the Alphas, Betas, and RC's we provide of that new release Testing the latest version of Software-Stack-A built against Leap 42.1 doesn't help anyone It doesn't help the development of Tumbleweed - Devel repos built against Tumbleweed do that. It doesn't help the development of Leap 42.1 - when we have Leap 42.2, we're going to be building it against a totally new base system (from SLE 12 SP2) So, encouraging people to build against Leap 42.1 leads to the following 1 People wasting time testing new versions of software that will almost-certainly never end up on Leap 42.1 2 Maintainers wasting time fixing build issues and debugging bugs that do not occur on Leap 42.1 and likely would not occur on 42.2 3 Sad users and Mailing List and Forum users wasting time trying to help people who broke their machines with wonderful combinations of software that would never work together (FOO from RepoA broken because of BAR from RepoB) 4 Some happy users who for a short while might be lucky enough to get something that works on their custom Leap 42.1 + Repo-of-their-choice I like 4, I absolutely hate outcomes 1-3. I therefore think it should be the responsibility of our maintainers to decide whether or not they can provide 4 without causing 1-3 by activating Leap 42.1 on their repositories Which is how they do things right now. I do not think increasing the pressure on maintainers to activate Leap 42.1 repos is a smart idea, because I do think that in the vast majority of cases, the problems with outcomes 1-3 are significantly worse than the benefits of outcome 4 *especially* when we have Tumbleweed which offers the latest of everything, as soon as it's been tested and confirmed to be working with the latest of everything else People need to realise that Tumbleweed is always going to be more reliable than whatever Frankenstein they can produce by taking Leap 42.1 and adding whatever cocktail of Devel repos they think they need. And if/when there are still issues on Tumbleweed, it's infinately easier for us to fix them, and prevent them happening again, with the Factory development process, than it is when they're taking Leap 42.1 and adding a cocktail of Devel repos. So yeah, I understand this seems like a simple request, but years of experience has taught us that the road requested leads to dragons, and should therefore best be avoided. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org