Quoting Stephan Kulow
Hi,
I have a new topic ;)
As the bootstraping of openSUSE:42 is almost done (already looking forward to do the same from scratch with openSUSE:$NEWNAME) I wonder how we go from there.
I would like simple (to enforce) submission rules. So submission from openSUSE:Factory or SUSE:SLE-12:Update only (:Update overshadows SLE-12:GA, so it has all sle12 packages). Then we would test compile the submissions in a staging project light (in IRC we did some brain storming and Staging:adi:<NR> was the best suggestion so far) to see if the submitted packages compile in 42 and accept.
I think this is a fair 'first rule', but I can imagine exceptions, like 'just changed build flags', changed feature set which we would want in :42, but the package in TW might have progressed much more than just that. Shouldn't the package from SUSE:SLE-12:Update be 'automatically' considered for :42? I guess a bot submitting those changes should do as well (if something was good for SLE, it should be good for :42 - unless it reverts something that moved already a bit further ahead) As a practical example for where an exception of submissions only from TW might be needed: Xorg in :42 is currently at version 1.15.2, Tumbleweed is at 1.17.1 yet, I need X configured with --enable-systemd-logind; this corresponds to Submit request https://build.opensuse.org/request/show/287362 that was done against TW 4 months ago. Alternatively, of course, the SLE package might receive an 'update' with the new build flags; but that sounds very unrealistic as an update. Sadly, with OBS, it is not possible to 'cherry pick' such changes, so whoever is going to submit that fix for TW needs to have a way to except from 'only submissions from openSUSE:Factory' are allowed. And I'm sure there are more such cases where we'd see small variations, but the TW version diverged too much already. Cheers, Dominiqu -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org