On Tue, 2007-04-17 at 14:56 -0400, Doug Goldstein wrote:
I would like to take this time to note and re-affirm the proper bug
assignment policy and have it noted somewhere officially in Gentoo Policy.
Bugs that are created for the purpose of getting arches to keyword or
stabilize a particular
I would like to take this time to note and re-affirm the proper bug
assignment policy and have it noted somewhere officially in Gentoo Policy.
Bugs that are created for the purpose of getting arches to keyword or
stabilize a particular package should initially be assigned to the
herd/maintainer
On Tue, 17 Apr 2007 14:56:58 -0400
Doug Goldstein [EMAIL PROTECTED] wrote:
I would like to take this time to note and re-affirm the proper bug
assignment policy and have it noted somewhere officially in Gentoo
Policy.
Bugs that are created for the purpose of getting arches to keyword or
On Tue, 17 Apr 2007 14:56:58 -0400
Doug Goldstein [EMAIL PROTECTED] wrote:
Once all but the last arch has keyworded said package, it is
acceptable and proper for a bug wrangler and/or maintainer/herd to
re-assign the bug to the last remaining arch and they remove that
arch from CC. They should
Ned Ludd wrote:
On Tue, 2007-04-17 at 14:56 -0400, Doug Goldstein wrote:
I would like to take this time to note and re-affirm the proper bug
assignment policy and have it noted somewhere officially in Gentoo Policy.
Bugs that are created for the purpose of getting arches to keyword or
Stefan Schweizer wrote:
In my opinion the last architecture should also remove the old ebuild
they have just made obsolete by stabling/keywording the new version,
since they commit to the directory anyway.
This might be good, but also bad. I usually let the older stable version
linger in our
