On Mon, 29 Jan 2007 08:15:18 +0100 (MET) Christian Faulhammer <[EMAIL PROTECTED]> wrote:
> Ciaran McCreesh <[EMAIL PROTECTED]>: > > > On Sun, 28 Jan 2007 19:17:35 +0100 (MET) Christian Faulhammer > > <[EMAIL PROTECTED]> wrote: > > | As we all notice from time to time, amd64 team is lacking behind a > > | bit, due to various reasons. a) manpower, b) a lot of keywording. > > | Java team asked arch teams if they object when Java team marks > > stable | generation-2 ebuilds on their own, due to the long time it > > takes and | to the amount of ebuilds to be stabilised. > > | So, maybe we can discuss here another helping hand for amd64. Devs > > | that work with a given software (not necessarily the maintainer) on > > | amd64 architecture and when there is a keywording bug open, then > > said | devs can keyword the ebuild. For a short period of time this > > could be | allowed to all devs. > > | Any objections? > > Why not just extend the amd64 team to include people who will only > > work on Java stuff? Other arch teams have no problems with developers > > being onboard only for a few particular packages. > > Because it was meant for every package and I only talk about > keywording ~amd64, not stabling. The latter is handled by the team in > a timely manner, but keywording is put aside (it leads to even more > stabling, once it is keyworded). Java was only mentioned, as they came > up with an idea to help amd64 in special and arch teams in general. AFAIK that has been the (unofficial?) policy of the AMD64 team for as long as I can remember. Marius -- gentoo-dev@gentoo.org mailing list
