There are no patches. We must do it with explanations on dev eclipse site.
----- Original Message ----- From: <[EMAIL PROTECTED]> To: "Maven Developers List" <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > _____________________________________________________________________ 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
