Steve Dibb wrote:
Ciaran McCreesh wrote:
On Mon, 30 Oct 2006 22:33:26 +0100 Jakub Moc <[EMAIL PROTECTED]> wrote:
| Ciaran McCreesh napsal(a):
| > | What on earth are you talking about here? And why almost 6 months
| > | is not enough for someone to respond on a bug with a simple
| > | "we'll only support newer versions and don't care about MySQL
| > | 4.0.x any more, go drop it"?
| > | > Priorities. The arch teams could be too busy dealing with
other bugs
| > that matter more or too busy dealing with noise bugs.
| | Sorry, taking 1 minute to respond on a bug after being poked for a
| couple of months is not a matter of priorities, but mere politeness
| and common sense. Seriously, you can't work productively with other
| people if they can't be bothered to write one sentence for months.
There are an awful lot of bugs requiring an awful lot of attention...
That does bring up an interesting question though -- at what point do
you just ignore the arch and move on so that development can continue?
I suppose if you had a nasty security verbump you needed to release, you
could keyword it yourself, but for everything else, what's the best way
to handle those if you are perpetually ignored?
Steve
I picked a random e-mail to reply to. I don't maintain that many
packages (maybe 10 or so?). But if I have a bug (particularly a sec bug
as in this case) and you haven't stablized it after five months then
I'll probably just nuke the ebuild and drop your keywords and then
change the bug title to "$arch got it's keywords dropped". Now of
course I'd probably e-mail your alias a couple of times letting on that
this is my evil plan and to please try and get to my bug.
As an arch team you may not like it; and yeah it kind of sucks. If you
want your keyword back there will still be a bug open for it and the
arch team can always keyword it themselves.
You can ask that we make a good faith attempt to not break the arch
trees, and I think thats an acceptable request. But eventually I'm
going to give up waiting on you.
--
gentoo-dev@gentoo.org mailing list
