You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Ben Walding <be...@walding.com> on 2003/06/11 01:45:06 UTC
RC1 release plans
After the scathing blame-storming attack by Nick (just kidding), we've
decided to prepare for a Maven RC1 release.
You can track progress on our attempt to get everything ready for an RC1
via JIRA. All bugs attached to MAVEN-401 will be processed prior to the
release OR I will mail to the user / dev lists if I remove dependent
issues (highly unlikely).
If you have something that positively must be fixed you have one of
three choices
1) Find a compliant committer who will fix the problem for you. No
guarantees.
2) ***BEST PLAN*** Submit a tested patch and then find a committer who
will apply the patch and test it
3) Submit an issue and hope someone takes notice. No guarantees.
Changes to core functionality will probably not be considered at this
stage as we just want to clean up what we have, run it for a few days
and then release it.
Please note: If it's not logged in JIRA, the problem does not exist.
By all means post to the dev list to find out if it is known and listed
somewhere else, but ultimately, don't expect that mailing to the dev
list will get it fixed. IT MUST BE PUT INTO JIRA.
(Committers: Can you funnel changes to the MAVEN-401 dependant issues
through me please - Under NO circumstances unlink issues from MAVEN-401)
We'll be looking to lock down for release end of this week with an
internal release after the weekend and a public release mid week (all
things permitting).
Cheers,
Ben
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: RC1 release plans
Posted by Ben Walding <be...@walding.com>.
MAVEN-442 is now linked. You just have to fix it now :)
I believe Jason is working on resolving the reactor memory leak, you
might want to check in with him at some point.
Brett Porter wrote:
> Hi Ben,
>
> Can you add MAVEN-442 to the RC1 bug? It also breaks a lot of reactor
> based builds.
>
> Sorry, I haven't come up with a fix for either 442 or 472 yet, but I'm
> working on it. I've posted my research on 472 to the issue in JIRA.
>
> Cheers,
> Brett
>
> Ben Walding wrote:
>
>> (Committers: Can you funnel changes to the MAVEN-401 dependant issues
>> through me please - Under NO circumstances unlink issues from MAVEN-401)
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: RC1 release plans
Posted by Brett Porter <bp...@f2network.com.au>.
Hi Ben,
Can you add MAVEN-442 to the RC1 bug? It also breaks a lot of reactor
based builds.
Sorry, I haven't come up with a fix for either 442 or 472 yet, but I'm
working on it. I've posted my research on 472 to the issue in JIRA.
Cheers,
Brett
Ben Walding wrote:
> (Committers: Can you funnel changes to the MAVEN-401 dependant issues
> through me please - Under NO circumstances unlink issues from MAVEN-401)
>
--
Web Developer
f2 network ~ everything essential
02 8596 4437
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: RC1 release plans
Posted by Emmanuel Venisse <ev...@ifrance.com>.
There are no patches. We must do it with explanations on dev eclipse site.
----- Original Message -----
From: <di...@multitask.com.au>
To: "Maven Developers List" <de...@maven.apache.org>
Sent: Wednesday, July 02, 2003 5:31 PM
Subject: Re: RC1 release plans
> Are there patches for Maven-473? I couldn't see one...
> --
> dIon Gillard, Multitask Consulting
> Blog: http://blogs.codehaus.org/people/dion/
> Work: http://www.multitask.com.au
>
>
> Wes Isberg <we...@california.com> wrote on 11/06/2003 10:42:48 AM:
>
> > Sorry, newbie protocol question wrt
> >
> > > 3) Submit an issue and hope someone takes notice. No guarantees.
> >
> > I'd like to find a committer for Maven-473, but I assume that
> > one should not email committers directly and that this mailing
> > list is not the place to plead for attention (as I've just done).
> >
> > So...
> >
> > Any committers interested in Maven-473? (doh! I did it again!)
> >
> > http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-473
> >
> > Should non-committers do something other than mail this list
> > to find committers?
> >
> > Thanks -
> > Wes
> >
> >
> > Ben Walding wrote:
> >
> > > After the scathing blame-storming attack by Nick (just kidding), we've
>
> > > decided to prepare for a Maven RC1 release.
> > >
> > > You can track progress on our attempt to get everything ready for an
> RC1
> > > via JIRA. All bugs attached to MAVEN-401 will be processed prior to
> the
> > > release OR I will mail to the user / dev lists if I remove dependent
> > > issues (highly unlikely).
> > >
> > > If you have something that positively must be fixed you have one of
> > > three choices
> > > 1) Find a compliant committer who will fix the problem for you. No
> > > guarantees.
> > > 2) ***BEST PLAN*** Submit a tested patch and then find a committer who
>
> > > will apply the patch and test it
> > > 3) Submit an issue and hope someone takes notice. No guarantees.
> > >
> > > Changes to core functionality will probably not be considered at this
> > > stage as we just want to clean up what we have, run it for a few days
> > > and then release it.
> > >
> > > Please note: If it's not logged in JIRA, the problem does not exist.
> > > By all means post to the dev list to find out if it is known and
> listed
> > > somewhere else, but ultimately, don't expect that mailing to the dev
> > > list will get it fixed. IT MUST BE PUT INTO JIRA.
> > >
> > >
> > > (Committers: Can you funnel changes to the MAVEN-401 dependant issues
> > > through me please - Under NO circumstances unlink issues from
> MAVEN-401)
> > >
> > > We'll be looking to lock down for release end of this week with an
> > > internal release after the weekend and a public release mid week (all
> > > things permitting).
> > >
> > > Cheers,
> > >
> > >
> > > Ben
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
>
_____________________________________________________________________
Envie de discuter en "live" avec vos amis ? Télécharger MSN Messenger
http://www.ifrance.com/_reloc/m la 1ère messagerie instantanée de France
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: RC1 release plans
Posted by di...@multitask.com.au.
Are there patches for Maven-473? I couldn't see one...
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Work: http://www.multitask.com.au
Wes Isberg <we...@california.com> wrote on 11/06/2003 10:42:48 AM:
> Sorry, newbie protocol question wrt
>
> > 3) Submit an issue and hope someone takes notice. No guarantees.
>
> I'd like to find a committer for Maven-473, but I assume that
> one should not email committers directly and that this mailing
> list is not the place to plead for attention (as I've just done).
>
> So...
>
> Any committers interested in Maven-473? (doh! I did it again!)
>
> http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-473
>
> Should non-committers do something other than mail this list
> to find committers?
>
> Thanks -
> Wes
>
>
> Ben Walding wrote:
>
> > After the scathing blame-storming attack by Nick (just kidding), we've
> > decided to prepare for a Maven RC1 release.
> >
> > You can track progress on our attempt to get everything ready for an
RC1
> > via JIRA. All bugs attached to MAVEN-401 will be processed prior to
the
> > release OR I will mail to the user / dev lists if I remove dependent
> > issues (highly unlikely).
> >
> > If you have something that positively must be fixed you have one of
> > three choices
> > 1) Find a compliant committer who will fix the problem for you. No
> > guarantees.
> > 2) ***BEST PLAN*** Submit a tested patch and then find a committer who
> > will apply the patch and test it
> > 3) Submit an issue and hope someone takes notice. No guarantees.
> >
> > Changes to core functionality will probably not be considered at this
> > stage as we just want to clean up what we have, run it for a few days
> > and then release it.
> >
> > Please note: If it's not logged in JIRA, the problem does not exist.
> > By all means post to the dev list to find out if it is known and
listed
> > somewhere else, but ultimately, don't expect that mailing to the dev
> > list will get it fixed. IT MUST BE PUT INTO JIRA.
> >
> >
> > (Committers: Can you funnel changes to the MAVEN-401 dependant issues
> > through me please - Under NO circumstances unlink issues from
MAVEN-401)
> >
> > We'll be looking to lock down for release end of this week with an
> > internal release after the weekend and a public release mid week (all
> > things permitting).
> >
> > Cheers,
> >
> >
> > Ben
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Re: RC1 release plans
Posted by Wes Isberg <we...@california.com>.
Sorry, newbie protocol question wrt
> 3) Submit an issue and hope someone takes notice. No guarantees.
I'd like to find a committer for Maven-473, but I assume that
one should not email committers directly and that this mailing
list is not the place to plead for attention (as I've just done).
So...
Any committers interested in Maven-473? (doh! I did it again!)
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-473
Should non-committers do something other than mail this list
to find committers?
Thanks -
Wes
Ben Walding wrote:
> After the scathing blame-storming attack by Nick (just kidding), we've
> decided to prepare for a Maven RC1 release.
>
> You can track progress on our attempt to get everything ready for an RC1
> via JIRA. All bugs attached to MAVEN-401 will be processed prior to the
> release OR I will mail to the user / dev lists if I remove dependent
> issues (highly unlikely).
>
> If you have something that positively must be fixed you have one of
> three choices
> 1) Find a compliant committer who will fix the problem for you. No
> guarantees.
> 2) ***BEST PLAN*** Submit a tested patch and then find a committer who
> will apply the patch and test it
> 3) Submit an issue and hope someone takes notice. No guarantees.
>
> Changes to core functionality will probably not be considered at this
> stage as we just want to clean up what we have, run it for a few days
> and then release it.
>
> Please note: If it's not logged in JIRA, the problem does not exist.
> By all means post to the dev list to find out if it is known and listed
> somewhere else, but ultimately, don't expect that mailing to the dev
> list will get it fixed. IT MUST BE PUT INTO JIRA.
>
>
> (Committers: Can you funnel changes to the MAVEN-401 dependant issues
> through me please - Under NO circumstances unlink issues from MAVEN-401)
>
> We'll be looking to lock down for release end of this week with an
> internal release after the weekend and a public release mid week (all
> things permitting).
>
> Cheers,
>
>
> Ben
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: RC1 release plans
Posted by Jason van Zyl <ja...@zenplex.com>.
On Tue, 2003-06-10 at 19:45, Ben Walding wrote:
>
> (Committers: Can you funnel changes to the MAVEN-401 dependant issues
> through me please - Under NO circumstances unlink issues from MAVEN-401)
I assigned myself 473 if you want to link that into the 401 series of
deps.
> Ben
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
--
jvz.
Jason van Zyl
jason@zenplex.com
http://tambora.zenplex.org
In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
-- Jacques Ellul, The Technological Society
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: RC1 release plans
Posted by Tim Anderson <tm...@netspace.net.au>.
Any chance of MAVEN-474 "war plugin doesn't support lists of
includes/excludes"
(http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-474)
getting included in the next release?
Thanks,
Tim
> -----Original Message-----
> From: Ben Walding [mailto:ben@walding.com]
> Sent: Wednesday, 11 June 2003 9:45 AM
> To: Maven Users List; Maven Developers List
> Subject: RC1 release plans
>
>
> After the scathing blame-storming attack by Nick (just kidding), we've
> decided to prepare for a Maven RC1 release.
>
> You can track progress on our attempt to get everything ready for an RC1
> via JIRA. All bugs attached to MAVEN-401 will be processed prior to the
> release OR I will mail to the user / dev lists if I remove dependent
> issues (highly unlikely).
>
> If you have something that positively must be fixed you have one of
> three choices
> 1) Find a compliant committer who will fix the problem for you. No
> guarantees.
> 2) ***BEST PLAN*** Submit a tested patch and then find a committer who
> will apply the patch and test it
> 3) Submit an issue and hope someone takes notice. No guarantees.
>
> Changes to core functionality will probably not be considered at this
> stage as we just want to clean up what we have, run it for a few days
> and then release it.
>
> Please note: If it's not logged in JIRA, the problem does not exist.
> By all means post to the dev list to find out if it is known and listed
> somewhere else, but ultimately, don't expect that mailing to the dev
> list will get it fixed. IT MUST BE PUT INTO JIRA.
>
>
> (Committers: Can you funnel changes to the MAVEN-401 dependant issues
> through me please - Under NO circumstances unlink issues from MAVEN-401)
>
> We'll be looking to lock down for release end of this week with an
> internal release after the weekend and a public release mid week (all
> things permitting).
>
> Cheers,
>
>
> Ben
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org