On 02/04/14 21:22, Mike Gilbert wrote: > On Wed, Apr 2, 2014 at 12:52 PM, Samuli Suominen <ssuomi...@gentoo.org> wrote: >> The "30 days maintainer time out" stabilization policy isn't working >> when package has multiple SLOTs, because >> the bugs are filed for only latest SLOT, where as some packages require >> stabilization in sync at both SLOTs >> >> Option 1: >> >> Either revert the whole policy, and never CC arches on unanswered bugs >> when the package has a maintainer, >> and let him do it when he finds the time himself, and if that doesn't >> happen, wait until it's dropped to maintainer-needed@ >> >> Option 2: >> >> Or, the person who is CCing the arches in 30 days timeout, needs to make >> sure the bug covers all SLOT at the same time >> >> >> The status quo no longer allows me to maintain stable version of >> dev-libs/girara, app-text/zathura*, and the issue needs >> to be addressed, see http://bugs.gentoo.org/502714 for what inspired >> this mail >> >> - Samuli >> > If you want to prevent packages from being "timed out", just leave a
That would require me to take action on the STABLEREQ, which I don't want to do if I see someone requesting it stable only because it's newer version, see below: > comment on the bug saying so. If you don't even have time to do that > within a 30 day window, why are you the maintainer? It's like we handle stabilization for Xfce, we collect enough xfce-base/ and xfce-extra/ packages together to form a longer list, to avoid bothering arch teams unnecessarily constantly This time it's app-text/zathura-meta and it's dependencies, multiple packages, we'd like to wait there are enough plugins, and form a list And this time the package even had 3 maintainers, 2 gentoo developers and one proxy, in metadata.xml, yet none of us managed to intervene in time to prevent the SLOT breakage[1] done by arches without our consent [1] Stabilizing headers, but not the library, causing the .h not to match the .so, causing every reverse dependency of the library to break > > Another option would be to add some kind of notation to metadata.xml. > That could work
