Diego 'Flameeyes' Pettenò wrote:
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 [EMAIL PROTECTED], 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..
After contributing to the suggestions on -core I forgot to explain
myself very clearly on this point.
I'm not suggesting a mechanism for handling or encouraging "0-day" bump
requests - I'm giving a suggestion which I believe will help *reduce*
those requests.
By leaving a nice comment (asking that they give us a little more room
to breathe in future) *and* crediting the user, maybe they will take
your advice to heart.
It's not up to the user to know how closely the maintainer tracks the
upstream release (or even who the maintainer is in the first place), but
in general we prefer to be left for a week or so before being notified
via Gentoo bugzilla, right?
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).
OK - thats a good compromise if you can't afford to spend the full
amount of time guiding the user through it. I have never heard of your
maintainer guides before but will check them out now.
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 :)
Fair enough - I guess it depends on your workflow. Perhaps you could
just try this for a couple of bugs: reassign them to yourself and leave
the appropriate comments,then observing the users reaction. That way the
bug is hard to lose since it is on your "My Bugs" list.
Daniel
--
gentoo-dev@gentoo.org mailing list
