missing feedback (Re: [kde-announce] Announcing KDE 3.2)

Christian Loose christian.loose at hamburg.de
Thu Feb 5 20:32:52 GMT 2004


Am Donnerstag, 5. Februar 2004 20:34 schrieb Aaron Seigo:
> On February 5, 2004 11:12, Christian Loose wrote:
> > So my real question is, how should this be handled when one stumbles over
> > one of those patches? Just test and commit it? What do the other app
> > maintainers think?
>
> if it's an obvious bug fix, it's probably cool.

Okay.

> but many of the patches alter behaviour or add features, and those are best 
> passed on to the maintainers and/or discussed on the appropriate mailing 
> list(s).

That's what I find strange. When I attach a patch to the wish the maintainer 
gets a mail, right? So why do I have to send him the patch again? 

I'm being so pedantic about this, because I told a few people on kde-devel in 
the past that when they don't want to see their patches get overlooked they 
should attach it to a bug report. This of course doesn't make sense when the 
maintainer chooses to ignore the bugzilla messages.

When you tell me to just send it always directly to the maintainer, I'm fine 
with that (even when there are some maintainers that choose to ignore those 
mails too).

>
> to help that process go better, we could certainly use a few ppl doing bug
> triage

I wish I had more time besides working on Cervisia. :-(

Thanks for the feedback!

Christian





More information about the kde-core-devel mailing list