Arnaud HERITIER wrote:
Also, it's a shame that we can't know if there's a patch.
It could also help us.
I try to use a filter to pick up the work "patch" or "diff" but it's not
100% accurate as you can't search for issues with attachments. I think
the best thing we can do in this case is push a value into a custom
field. The filter is here:
http://jira.codehaus.org/secure/IssueNavigator.jspa?mode=hide&requestId=11308
And if I can finish this little patch submission plugin it should be
able to poke a custom field:
http://svn.apache.org/viewcvs.cgi/maven/sandbox/issue/maven-submit-plugin/
So that we can at least try to accurately record the submission of a
patch on an issue and give it a higher ranking for priority in terms of
a developer looking at it.
--
jvz.
Jason van Zyl
jason at maven.org
http://maven.apache.org
People develop abstractions by generalizing from concrete examples.
Every attempt to determine the correct abstraction on paper without
actually developing a running system is doomed to failure. No one
is that smart. A framework is a resuable design, so you develop it by
looking at the things it is supposed to be a design of. The more examples
you look at, the more general your framework will be.
-- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
