From: Daniel Drake <dsd@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Bugzilla etiquette suggestions
Date: Mon, 13 Feb 2006 16:11:51 +0000 [thread overview]
Message-ID: <43F0AFC7.2000407@gentoo.org> (raw)
In-Reply-To: <pan.2006.02.13.09.50.19.347815@cox.net>
Duncan wrote:
> I'd /not/ really wish to encourage version bump requests "overnight".
> That's jumping the gun, and indeed, could encourage "first post" like
> behavior.
>
> What I'd do with such bugs is thank the user, but say next time, please
> give me a few days, at least a week (or whatever a dev feels comfortable
> with for that package, again, it'll vary) -- if it's /just/ a bump
> request.
That is precisely what was being discussed on the private list which
prompted me to finish off this post and publish it.
One point I was trying to make (as Mike and myself suggested on the
private list) is that if you *do* receive a bump request too soon after
release, then you ask the user nicely to wait 1 week (or whatever) after
release in the future before filing bump requests.
You should *also* leave the bug open until the ebuild is in portage,
then mark the bug as FIXED in the normal way, *and* you thank them by
name in the commit message.
By showing them some basic respect for the fact they were trying to
contribute, hopefully they will understand your position better and take
up your advice.
You can argue that that *may* encourage "overnight" bump requests (which
certainly isn't the intention), but in practice I think that won't
happen too much if you treat the contributor in the proper manner.
Daniel
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2006-02-13 16:10 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-12 21:11 [gentoo-dev] Bugzilla etiquette suggestions Daniel Drake
2006-02-12 21:43 ` Henrik Brix Andersen
2006-02-12 23:24 ` Daniel Drake
2006-02-13 0:57 ` Ferris McCormick
2006-02-13 8:09 ` Ciaran McCreesh
2006-02-13 9:50 ` [gentoo-dev] " Duncan
2006-02-13 16:11 ` Daniel Drake [this message]
2006-02-13 17:17 ` [gentoo-dev] " Duncan
2006-02-16 11:02 ` [gentoo-dev] " Michael Cummings
2006-02-13 10:51 ` [gentoo-dev] " Diego 'Flameeyes' Pettenò
2006-02-13 16:30 ` Daniel Drake
2006-02-12 22:53 ` [gentoo-dev] " Duncan
2006-02-12 23:39 ` Daniel Drake
2006-02-13 8:13 ` Ciaran McCreesh
2006-02-13 17:26 ` Richard Fish
2006-02-14 2:54 ` lnxg33k
2006-02-13 18:39 ` Simon Stelling
2006-02-13 18:49 ` Ciaran McCreesh
2006-02-13 19:00 ` Patrick McLean
2006-02-13 19:06 ` Marien Zwart
2006-02-13 19:07 ` Grobian
2006-02-13 19:21 ` Ciaran McCreesh
2006-02-13 19:29 ` Grobian
2006-02-13 20:02 ` Carsten Lohrke
2006-02-13 20:13 ` Grobian
2006-02-13 19:36 ` Diego 'Flameeyes' Pettenò
2006-02-14 13:03 ` [gentoo-dev] " Duncan
2006-02-14 13:18 ` Stephen P. Becker
2006-02-15 7:48 ` [gentoo-dev] " Duncan
2006-02-12 22:58 ` [gentoo-dev] " Marien Zwart
2006-02-12 23:32 ` Daniel Drake
2006-02-13 8:16 ` Ciaran McCreesh
2006-02-13 19:12 ` Donnie Berkholz
2006-02-13 4:06 ` Ned Ludd
2006-02-17 14:20 ` Shyam Mani
2006-02-17 14:11 ` Shyam Mani
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43F0AFC7.2000407@gentoo.org \
--to=dsd@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox