> Checkout, for example:
> http://issues.apache.org/jira/browse/TAPESTRY-607

I was going to write yesterday in the bug that I have been looking at this issue, and it will be fixed by the end of the week. I've had it on my desktop for a while. Decided that it can wait for a while.

It just has a few related tricks that need to be addressed as well.

All the best,
-mb

Leonardo Quijano Vincenzi wrote:
Jesse Kuhnert escribió:

But since it's open source can't you just create a bug fix patch for
whatever you want fixed? It's incredibly hard to keep up with all of the bug submissions from people and still maintain some semblance of order in trying
to get your original goals accomplished.
Of course. I have a couple of patches / bug analysis submitted that no one has ever seen. It's no good to create patches if nobody's going to commit them, right? Or at least say "I don't like this, can you change this or that?".

Either that, or at the very least a junit test-case bug submission that
someone can quickly run to assert what you are saying...Otherwise it's
probably a pain in the ass to think about trying to go in and test what
someone says is a bug. That would be like doing exploratory surgery on a
patient without knowing wtf is wrong with them.
I usually do the exploratory surgery and try to tell where the bug is exactly. If someone wants to give me commiter access then I'd be glad to take all the other steps in the process. But since that's not usually the case, I get to the 'complaining' phase. Every project needs a commiter who is an administrator, not only a programmer. He doesn't have to get an MBA, just be aware of the growing issue list and check it out, ask for more detail, etc. It's simple.

Checkout, for example:

http://issues.apache.org/jira/browse/TAPESTRY-607

I don't know how to be more specific than that!
Of course, I can always patch myself the code. But forking for simple bugs it's just dumb. It's better to integrate these fixes to the main development code.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to