Hi Eyad, eyadlorenzo@gmail.com writes:
Maybe I've not understood everything, but what about using the current workflow but with git branches?
This could be a second step indeed and is also something that we were thinking about.
People can PR to devel branch and it gets submitted as an SR to the devel project. Then the maintainer can PR devel -> factory and the SR gets submitted to factory.
This is problematic, as currently submissions to Factory are 100% reliant on checkers based on submit requests. However, with git based packages, submit requests cease to work. For that we would have to migrate all the tooling that currently runs the staging projects and checks the results to a git based workflow. This is on the roadmap, but it's a bit further in the future and depends on too many unknowns at the moment. The reliance of Factory submissions on submit requests is also the reason why the bot currently creates submit requests from pull requests: to allow all the tooling for release engineering to continue to work.
With this config: devel branch --> devel project factory branch --> factory
SR to devel projects should also be disallowed in this case, so that the only source of truth is git.
SRs to the devel project cease to work once you switch to scmsync anyway. OBS will report an error if you try to branch such a package. So this shouldn't be a problem. Cheers, Dan -- Dan Čermák <dcermak@suse.com> Software Engineer Development tools SUSE Software Solutions Germany GmbH Frankenstrasse 146 90461 Nürnberg Germany (HRB 36809, AG Nürnberg) Managing Director/Geschäftsführer: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman