Re: [gentoo-dev] Arches marking ebuilds stable before maintainer

[Donnie Berkholz]

Danny van Dyk said:
> 1. The ebuild maintainers should have the possibility to say: "ARCHs,
> feel free to mark stable. All major bugs that i know of are closed, only
> arch dependent bugs are left."

I definitely agree with this. Although there's no "official" mechanism for
this, perhaps there should be given the huge amounts of arguments that
have resulted from talking about it. Pending that, communication is all we
have to rely on, so we should at least rely on it rather than ignoring it.
The easiest way I can think of offhand from a package maintainer's POV is
a simple comment in the ebuild above the KEYWORDS line. Unfortunately some
people would never even see it if they're using ekeyword.

> 2. The arch maintainers should ask the package maintainers first before
> marking a package stable *before* the maintainer's approval. However,
> there are package maintainers that aren't on IRC all the time/that check
>  their dev-mails regularly, but probably only once or twice a week. In
> this case, arch maintainers should be allowed to just check bugs.g.o on
> major bugs and mark stable if the arch decides so.
>
> This is pretty much the way Donnie Berkholz proposed (Please correct me
> if I'm wrong), and in my eyes it's the only way that makes sense.

If you think about this, it's pretty similar to our security policy. When
the security team has the ability to "overrule" the package maintainer
holds a good parallel with when the arch maintainer could do the same.
Perhaps we can learn from that.

(Security guys, is that policy on the Web anywhere? I couldn't find it on
a quick browse.)

Thanks,
Donnie



--
gentoo-dev@g.o mailing list