I'm planning to push out a candidate for 2.0.8 very soon. I have a
couple things I wanted to check out tonight and then it's out.
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 23, 2007 2:09 PM
To: Maven Developers List
Subject: Relea
Hi,
Just a little update on where we are. I think 2.0.8 can be pushed out
now as Herve and Brian have done most of the things that they wanted
to do and it's overdue so we should just release it.
John, and I are fixing a few things in 2.1 but there is one IT that
needs to be fixed and the
-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 19 September 2007 10:09 AM
To: Maven Developers List
Subject: [***POSSIBLE SPAM***] - Re: Releasing 2.0.8 - Email has
different SMTP TO: and MIME TO: fields in the email addresses
I think it was a one off - basically the patch flag
Maven Developers List
Subject: [***POSSIBLE SPAM***] - Re: Releasing 2.0.8 - Email has
different SMTP TO: and MIME TO: fields in the email addresses
Hi William,
The best for us is to add it in the Maven Patch Day
http://docs.codehaus.org/display/MAVENUSER/Maven+Patch+Day
Cheers,
Vi
PROTECTED]
Sent: Wednesday, 19 September 2007 8:27 AM
To: Maven Developers List
Subject: [***POSSIBLE SPAM***] - Re: Releasing 2.0.8 - Email has
different SMTP TO: and MIME TO: fields in the email addresses
Hi William,
The best for us is to add it in the Maven Patch Day
http://docs.codehaus.org
Has a patch attached so I changed the fix version to 2.0.8 and we'll
see where we get with it.
On 18 Sep 07, at 3:13 PM 18 Sep 07, William Ferguson wrote:
Now that it seems a release of 2.0.8 is imminent.
What is the protocol for agitating for issues that have been
patched to
be included i
Hi William,
The best for us is to add it in the Maven Patch Day
http://docs.codehaus.org/display/MAVENUSER/Maven+Patch+Day
Cheers,
Vincent
2007/9/18, William Ferguson <[EMAIL PROTECTED]>:
> Now that it seems a release of 2.0.8 is imminent.
>
> What is the protocol for agitating for issues that
Now that it seems a release of 2.0.8 is imminent.
What is the protocol for agitating for issues that have been patched to
be included in 2.0.8?
Eg http://jira.codehaus.org/browse/MNG-2123
William
-
To unsubscribe, e-mail: [EMAI
