On 9/18/06, Jörg Schaible <[EMAIL PROTECTED]> wrote:
jerome lacoste wrote on Thursday, September 14, 2006 11:24 PM:
> On 9/14/06, John Taylor <[EMAIL PROTECTED]> wrote:
>> Hi all,
>> Apologies for what is probably a FAQ, but can anyone give me an
>> approx timescale for the 2.0.5 release?
>
> I haven't followed closely lately but I would say 'When it's done'.
>
>> Just knowing whether it's imminent,
>> weeks or months away would help me decide whether to invest in
>> finding workarounds to some of the issues in 2.0.4.
>
> THere were about 180 issues targeted to it last time I checked. So
> probably not tomorrow nor in the next weeks.
And some of them have been open since 1.0 and postponed from version to version
... so that's not the real issue ;-)
>> I'm really hoping that 2.0.5 will fix the problems with site
>> deployment, particularly http://jira.codehaus.org/browse/MSITE-138
>> and http://jira.codehaus.org/browse/MSITE-25 (a real problem for
>> windows users).
>
> You will probably have to find work-arounds.
> Such as
> - backport the plugin patches
> - or use maven 2.0.5-snapshot
> - or fix maven 2.0.5 issues to help fasten the release :)
Well, some bugs already have been fixed and it will need a new Maven release to roll them
out (MNG-1245 and all those dependend on it). Especially in large organizations it is not
really an option to tell every developer to install a snapshot library into their Maven
installation nor will such a thing pass any QA process. Fact is, that creating non-final
EJBs, WARs, EARs, etc. in multi-module builds will produce unusable artifacts. So a
"release often release fast" strategy would definitely be welcome.
I completely agree. In fact building plugins now requires maven 2.0.5
and this made me put a pause on working on mojo plugins: I want to use
a stable build with known shortcomings, and not depend on a moving
development platform.
But my understanding is that Jira is the official release plan tool,
so unless someone decides to cut a new release and to triage issues,
we're left with the current issue list, right?
Jerome
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
