From: "Diego 'Flameeyes' Pettenò" <flameeyes@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Bugzilla etiquette suggestions
Date: Mon, 13 Feb 2006 11:51:26 +0100 [thread overview]
Message-ID: <200602131151.27261@enterprise.flameeyes.is-a-geek.org> (raw)
In-Reply-To: <43EFC3BD.7080902@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2259 bytes --]
On Monday 13 February 2006 00:24, Daniel Drake wrote:
> 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.
This is a scenario quite good... if it wasn't that at least myself I see it
rarely :)
Rarely because if I see a bump, I'm already starting testing it usually.
Yesterday I finished amaroK's bump while I was eating dinner :P
In amaroK's case, anyway, there's no problem to know if it has relesed:
upstream releases always in time, providing packagers with candidates to
release, allowing to prepare stuff before actual release.. the release is
also broadcasted in their homepage, on #amarok@freenode, on KDE-Apps, on
kde-extra-gear mailing list, usually on Planet KDE, too....
Really, I don't need bugs to remember me to bump it.
Mostly the same for k3b.. it's released and then announced on kde-extra-gear,
KDE-Apps, SourceForge, ..
I can be very thankful if someone would let me know when ALSA gets released as
the upstream send mail to -announce once in a blue moon instead..
> That is a fair point, and if you can't afford to spend the time on it
> then I'm not complaining. However, there are situations where this can
> *save* you time.
I try to explain why I did some changes before committing or why I didn't use
a given fix usually, I also try to provide documentation of what I do and why
I do it that way (see maintainers' guides, that nobody else seems to want).
But really, if I get a bug for a thing to be fixed, I try to fix it right
away... sometimes if I don't have time in that moment I leave a comment
telling where or what to look for..not like there's always someone ready to
fix :)
If I start thinking "this bug I'll fix later and provide just pointers to
users, I'm sure I'm going to forget about it. I actually did that already :)
--
Diego "Flameeyes" Pettenò - http://dev.gentoo.org/~flameeyes/
Gentoo/ALT lead, Gentoo/FreeBSD, Video, AMD64, Sound, PAM, KDE
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-02-13 10:54 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
2006-02-13 17:17 ` [gentoo-dev] " Duncan
2006-02-16 11:02 ` [gentoo-dev] " Michael Cummings
2006-02-13 10:51 ` Diego 'Flameeyes' Pettenò [this message]
2006-02-13 16:30 ` [gentoo-dev] " 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=200602131151.27261@enterprise.flameeyes.is-a-geek.org \
--to=flameeyes@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