Daniel Drake posted <[EMAIL PROTECTED]>, excerpted below, on Sun, 12 Feb 2006 23:24:45 +0000:
> Henrik Brix Andersen wrote: [Danial Drake wrote...] >>> 3. Always record contributions by name >>> >>> If you commit something in response to a bug report that has been filed, >>> always thank the user by full name (and bug number) in the ChangeLog and >>> commit message. >>> >>> This also applies for [...] version bump requests/submissions. Might >>> sound pointless for 'trivial' reports/requests but it is important to >>> credit the user if they have gone to the trouble of filing a bug. >> >> I don't really get this part. Why should I give credit to someone else >> for providing a fix for a bug which I already fixed myself locally? > > Maybe not if you have already done the work. I was thinking more of the > scenario, upstream does a release. You are on the mailing list so you > know about the new version. You decide you'll bump it in portage > tomorrow. > > Overnight, someone files a request for a version bump. Maybe they attach > a new ebuild or state that the existing one needs bumping. > > Even though you knew about it, I was suggesting that you credit the user > for filing the bug. I don't recall where I read it, but it sounded reasonable to me then, and deals with a possible issue, so I'll repeat it. Somewhere I read a recommendation for bump requests, addressed to users thinking of making one, suggesting that they give the devs a week or two to do the bump themselves, as they likely know about it because they are following the list for that app, since they are the Gentoo maintainer for it, and just need time to get something worked up and tested locally. If after two weeks, the bump isn't in portage, /then/ it's time to post the bug about it. Now, two weeks may be a bit long, but I'd say a week, anyway, of course depending on the app (something big like gcc or gnome/kde bumps would be different, but they are often in the tree even before the package is publicly released and sources publicly available -- good job!). 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. If I take over a week (or whatever), then maybe I need reminding, so let me know! OTOH, if the bug includes "I tried bumping the last ebuild to use the new sources and it worked fine", or "... and it broke at <whatever>", that's far more valuable than just a bump request, and I'd treat it so. (In fact, that sounds like possible AT/HT material, maybe ultimately leading to a new dev, to me.) -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman in http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html -- gentoo-dev@gentoo.org mailing list
