>
> Putting it in JIRA is usually enough. Be prepared that it might take
> some time before a developer evaluates your patch. Developers usually
> work on one plugin at a time, fixing a bunch of issues. If you think
> that it's taking too long it is OK to ping the dev list for some attention.
I understand that, and I assume this plugin is not as high priority as
other plugins. Do you have an estimate of when this plugin will be
worked on again? I think you were the last developer to last work on
the plugin. I am only asking because I am interested in working on
MTAGLIST-15 and MTAGLIST-22, and I think both can be fixed with one
invasive patch. That being said, I was hopeing that MTAGLIST-20,
MTAGLIST-24, MTAGLIST-25, and MTAGLIST-26 could be patched to the
trunk (or tagged) before work on the other two begins.
> It is preferred if patches are against the current svn trunk. That makes
> them easier to apply for the developer. Also if one of the patches are
> rejected, for some reason, it is much easier if all the patches are
> separate. This can be a bit cumbersome for you as a contributor. One
> trick I used was to have one checkout of the code for each issue you
> want to create a patch for.
That makes sense.
Thanks.
-Nate
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
