On 14. Aug 2020, at 14:52, Neal Gompa <ngompa13@gmail.com> wrote:
That's part of Dirk's proposal though, at least on paper. To quote: "The package maintainers commit to handle primary architectures with care and test-build them in the development projects before submitting changes. The package maintainers commit to handle regressions quickly and in general accept bugreports for that platform and work on a resolution."
Sorry, no. Not going to work. There is no reasonable way to enforce that.
That being said, because *I* care, I actually *did* enable all architectures on the system:packagemanager:dnf[1] devel project a long time ago. But most devel projects will not do it. And the whole point of the staging workflow is so they don't need to.
[1]: https://build.opensuse.org/project/show/system:packagemanager:dnf
Even with Staging you can end up breaking packages, because the Stagings don't consider the entire tree of >10,000 packages. So you'll have to rely on maintainers reacting on notifications that their package doesn't build anymore.
This is what the staging workflow is for, and if the notifications aren't working, we need better communication.
Sorry Neal, but staging isn’t a panacea. I think all the architecture maintainers (regardless of status) feel that would be very nice if devel maintainers took more responsibility for their architectures. I like the fact the proposed policy defines responsibilities as clear as it does and I think adding more architectures to the distribution should be a burden shared by the whole project not just a select few. Staging is there as a firewall to stop things breaking the whole distro. The less they have to do the better. - signed, someone who’s learning to manage the stagings ;) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org