Ned Ludd wrote:
> Thank you for taking the time to put preXX doc this mail together.
> I find it personally inspiring and a reminder to watch how I/we handle
> bugs which is often easy to overlook.
Thanks for saying what I wanted to say Ned, I totally agree with you.
Regards,
--
Shyam Mani |
Daniel Drake wrote:
> Maybe we should consider alternatives. I quite like the NOTABUG
> resolution they have on the GNOME bugzilla.
I think this is a good idea. Shouldn't be too difficult to put this in /
replace INVALID with NOTABUG I guess.
Regards,
--
Shyam Mani | <[EMAIL PROTECTED]>
docs-t
Ciaran McCreesh wrote:
> On Sun, 12 Feb 2006 23:32:39 + Daniel Drake <[EMAIL PROTECTED]> wrote:
> | It may feel a little harsh to give someone a canned response just by
> | pasting a URL in the comment field, but curious readers will find his
> | faq.txt which explains nicely that we aren't e
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 [EMA
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
On Sun, 12 Feb 2006 23:32:39 + Daniel Drake <[EMAIL PROTECTED]> wrote:
| It may feel a little harsh to give someone a canned response just by
| pasting a URL in the comment field, but curious readers will find his
| faq.txt which explains nicely that we aren't evil/lazy, we just have
| a lot
On Mon, 13 Feb 2006 00:57:33 + (UTC) Ferris McCormick
<[EMAIL PROTECTED]> wrote:
| Well, the user did the work, too, and doesn't know that you did it
| (if I understand your case correctly). So the user deserves as much
| credit as you do.
What? No, that's silly. The one who does the work get
Thank you for taking the time to put preXX doc this mail together.
I find it personally inspiring and a reminder to watch how I/we handle
bugs which is often easy to overlook.
On Sun, 2006-02-12 at 21:11 +, Daniel Drake wrote:
> I wrote most of this a while ago but didn't get round to fin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 12 Feb 2006, Daniel Drake wrote:
Henrik Brix Andersen 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
Marien Zwart wrote:
I think this is too much effort, especially for small corrections. I
tend to fix them myself, commit with a message like "...based on an
ebuild from ... (bug #)" and comment on the bug like "Committed
with minor changes". It would probably be a good thing if I went into
a
Henrik Brix Andersen 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.
Do the above even if you already knew about the bug (i.e. you w
On Sun, Feb 12, 2006 at 09:11:33PM +, Daniel Drake wrote:
> I wrote most of this a while ago but didn't get round to finishing it.
> This seems appropriate at this time, so here it is :)
>
> Here are some small *suggestions* for how I think we can motivate users
> on Bugzilla to contribute m
Hi,
On Sun, Feb 12, 2006 at 09:11:33PM +, Daniel Drake wrote:
> 2. Be careful with INVALID resolutions
>
> The term invalid _is_ harsh in bugzilla context, so make sure you write
> a quick thankful-sounding comment to go with it.
>
> Maybe we should consider alternatives. I quite like the N
I wrote most of this a while ago but didn't get round to finishing it.
This seems appropriate at this time, so here it is :)
Here are some small *suggestions* for how I think we can motivate users
on Bugzilla to contribute more, and to contribute more often. I'm not
suggesting this be enforced
14 matches
Mail list logo
