-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/01/16 13:30, Richard Brown wrote:
3. We dont bother submitting everything from devel projects. I see that a lot with the games repo, but I guess there are others containing useful software that is not in Factory for various reasons - - e.g. because we always want the latest version to be used everywhere and submitting maintenance-updates is not as easy as just telling people to use the extra repo.
I believe this to be a big problem. I support and want to strongly encourage any effort which decreases the diff between [Sum of Packages in Devel Projects] and [Sum of Packages in Tumbleweed]
Maybe we should do something similar to the old Greg-K-H Tumbleweed where we create an overlay repo that only contains leaf packages in their latest stable version but that builds for all released openSUSE+SLE versions. That does not overlap with https://build.opensuse.org/project/show/openSUSE:Backports:SLE-12
because it only contains packages that are in Factory.
I don't see how that fixes the issue. People need to submit their packages to Tumbleweed, submitting to some overlay repo is just going to be another step which people may or may not do, and I'd much rather see them take the steps to get their packages out of Devel hell and into our distributions properly.
I'm surprised I have to remind the grandfather of openQA that just because something builds, doesn't mean it works; Our history with GregKH-style Tumbleweed showed that overlays are not inherently more maintainable or reliable than Modern Tumbleweed style rolling releases. Assured Quality comes from testing, and right now Tumbleweed is tested, no Devel Repo (and I assume no overlay repo) is.
Those are leaf packages that are not very critical, so probably would not be covered by openQA even if they were in Factory. Yes, they might break once in a while, but since there is only one source-code (as opposed to differing versions for 13.1, 13.2, 42.1 and Factory), it would be a lot easier and faster to fix. The point is that there are probably fewer users and thus it makes sense to have a workflow that requires less effort for the maintainer. Or if we want to go without such a "Contrib" repo, and submit everything to Factory, we still want a Backports repo where we build all the new applications for older openSUSE versions, so that more people can use and test the new stuff. and I guess, if we really want to, we could still add a staging+openQA ontop of either such Contrib or Backports repo. Ciao Bernhard M. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlaWLFMACgkQSTYLOx37oWRhxgCgx7BuGlWltWM/YtA7QVZfMXeq Tj8AoI8Tk8w4EIt4fO9B29aebL82MBuA =wE4B -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org