On 08/08/2008, at 1:04 AM, Jason van Zyl wrote:
We should be focusing on the release candidate in the short term.
Of course.
As far as 2.1 discussions so productive discussion will happen 1)
unless people have the necessary background, and 2) are given enough
time to prepare.
That's why I suggested it 4 days early, but that's fine.
I'm not really sure what background you think "people" are missing?
I just saw your commit that lists some 8 things to do before
discussing anything. That is back to front, first of all.
There's no value in sitting around waiting for some grand unified
plan, as was shown by attempts to do the same for maven-artifact in
May last year, and the Taxonomy in November last year. If you want to
come up with an extensive proposal or proposals, by all means, but
don't tie everything into a dependency on that. It takes time and it
has to evolve on the list.
Besides, there are more basic questions to answer first. Who says 2.1
has to be all that?
I have no time until next week for a couple hour discussion, and
people don't have enough information. I will send out another email
to setup some decent planning.
I wasn't looking for a planning session, just a sync up. I know
there's good stuff going on in mercury and the project builder off on
the side, but the real objectives for trunk aren't clear. Like I said,
if I'm going to spend time working on it, I want it to be meaningful.
I just suggested IRC since folks are usually around and it's a good
catalyst point. If we can do it on the ML, even better as far as I'm
concerned. I'll sleep in.
Essentially I was going to ask these questions:
* who's doing what now, where do they see it going, what help do they
need?
* what do people want to work on, and if that's something we all want,
where does it get done?
* where to next with trunk? It's clear we can't release trunk right
now, but I'd like to hear advice from John, yourself and others that
have done the work so far and are trying it as to whether we fix it,
rearchitect it from where it is, or something else.
Essentially - what is our collective vision for the next and future
releases of Maven?
Cheers,
Brett
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
