On 05/09/2006, at 2:41 AM, Wendell Beckwith wrote:
That's a surprising admission sense I never would have
thought of maven development as being stalled. Thank goodness
Google gives
me a couple gigs for email otherwise I would have to dump email
every other
day it seems.
Well, the project is certainly moving along, but the work on the core
itself has been pushed down the list a little while we sorted out a
plan for documentation and getting some more stability from the plugins.
I just looked at the roadmap and there are 578 issues
combined between maven 2.0.5 and 2.1, approx. 41.2 issues per
listed dev
assignee. For 2 releases that's not an insane #. So from your
standpoint
we should just checkout the trunk and go to town submitting patches?
Sure! Just keep in touch with the list about what you are working on
it and ping us for feedback regularly. If there are eyeballs on it,
patches can get applied faster.
An important thing, even if it slows down the rate of progress, is to
improve the tests and docs along with each piece of work. It's
something we are definitely going to have to attend to as we pick up
work on it.
I was really spinning my wheels last week, but I've gotten past
that now and
opened the Jira issues. However, if I just blow off the docs now,
then I'm
repeating history. So, I'll start submitting patches for issues
that are
all ready in Jira. It can help me get better acclimated to how
you all
function.
Ok, great. Let us know if there's anything we can do to help you dive
in, and thanks for doing so!
Cheers,
Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
