On Sat, 2019-05-18 at 16:28 +0930, Simon Lees wrote:

Hi All,

Stemming from the discussion on opensuse-factory, While we really don't want to add new leap builds to every project in obs maybe its worth having a script we run when we think that Leap releases reach a usable state that enables leap builds for every project listed as a factory development project. This should make sure all the main ones get enabled and it isn't really waisting obs resources as its pretty easy to argue that they should be enabled in most places (I guess d:l:p with its backports is the notable exception).

I'm not sure - At least all *:Factory devel projects are clearly not targetting Leap and are DEVELOPMENT projects (not production projects) There are currently 214 registered devel project of which 20 contain the string 'factory' (case insensitive), 11 are devel:languages:python:*, then there is Base:System which claims already in the prj description that it is not meant to be enabled for non-Factory builds. And that's just the 'exceptions' I know without looking up anything. OTOH: if we start auto-enabling repos for new releases we also have to balance this by auto-removing (or at least disabling) repos (in a timely manner) of eol distros.

So for example when Leap 15.2 reaches a milestone like the core is now building we then enable all the devel repos to make it easy for maintainers to spot issues.

Aren't the maintainers that actually care about said project to be avaialble for Leap most likely enabling it while Leap is even in flux? That's the moment you can still influence the base on top after all. Cheers, Dominique