+1 for 2.0.2
fabrizio
> On 12/14/05, John Casey <[EMAIL PROTECTED]> wrote:
> >
> > Hi all,
> >
> > If you've been watching this list, the users list, or JIRA, I'm sure
> > you've noticed that we managed to introduce some new bugs in 2.0.1. Some
> > of these are critical, and will block the use of
+1 for 2.0.2
On 12/14/05, John Casey <[EMAIL PROTECTED]> wrote:
>
> Hi all,
>
> If you've been watching this list, the users list, or JIRA, I'm sure
> you've noticed that we managed to introduce some new bugs in 2.0.1. Some
> of these are critical, and will block the use of this version.
>
> What
Brett Porter wrote on Thursday, December 15, 2005 7:09 PM:
> I'd like to suggest we take a little more time to test the
> solutions in
> place for these issues so that the release can stand up for the next
> month or so before the next scheduled release.
http://stefan.samaflost.de/blog/2005/05/0
On Wed, 2005-12-14 at 15:23 -0500, John Casey wrote:
> I'm not too interested in which version number we use; I only suggested
> this notation since it's definitely a lot smaller than what we did for
> 2.0.1, and what we've got slated for 2.0.2...that, and it's meant to
> modify the 2.0.1 releas
I was initially confused by this, but now that I understand its a full
Maven release, I'm +1. I agree with 2.0.2. Note that the branch needs to
have its versions converted - it was copied directly from the previous
tag so the versions are not snapshots. Perhaps the part of the release
plugin that d
On Thu, 15 Dec 2005, Jason van Zyl wrote:
+1!
> John Casey wrote:
> > I'm not too interested in which version number we use; I only suggested
> > this notation since it's definitely a lot smaller than what we did for
> > 2.0.1, and what we've got slated for 2.0.2...that, and it's meant to
> > mod
John Casey wrote:
I'm not too interested in which version number we use; I only suggested
this notation since it's definitely a lot smaller than what we did for
2.0.1, and what we've got slated for 2.0.2...that, and it's meant to
modify the 2.0.1 release so it'll work.
2.0.2 is fine with me.
I'm not too interested in which version number we use; I only suggested
this notation since it's definitely a lot smaller than what we did for
2.0.1, and what we've got slated for 2.0.2...that, and it's meant to
modify the 2.0.1 release so it'll work.
2.0.2 is fine with me. I can push the othe
+1
I'd prefer too 2.0.2
I added MNG-1841 because it's blocker for site generation. All our reports are empty in maven site
(http://maven.apache.org/maven-reports.html)
Emmanuel
John Casey a écrit :
Hi all,
If you've been watching this list, the users list, or JIRA, I'm sure
you've noticed
John Casey wrote:
Hi all,
If you've been watching this list, the users list, or JIRA, I'm sure
you've noticed that we managed to introduce some new bugs in 2.0.1. Some
of these are critical, and will block the use of this version.
What I'd like to do is release a bugfix version, 2.0.1-1, to
I meant 2.0.2
and my +1
On 12/14/05, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
> That's what happen when you make a release while you drink beer ;) No
> more releases during the Hackathon !
>
> Why not call it 2.0.3 ?
>
> On 12/14/05, John Casey <[EMAIL PROTECTED]> wrote:
> > Hi all,
> >
> > If y
That's what happen when you make a release while you drink beer ;) No
more releases during the Hackathon !
Why not call it 2.0.3 ?
On 12/14/05, John Casey <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> If you've been watching this list, the users list, or JIRA, I'm sure
> you've noticed that we managed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Casey wrote, On 12/14/2005 11:41 AM:
> Hi all,
>
> If you've been watching this list, the users list, or JIRA, I'm sure
> you've noticed that we managed to introduce some new bugs in 2.0.1. Some
> of these are critical, and will block the use of
Hi all,
If you've been watching this list, the users list, or JIRA, I'm sure
you've noticed that we managed to introduce some new bugs in 2.0.1. Some
of these are critical, and will block the use of this version.
What I'd like to do is release a bugfix version, 2.0.1-1, to address
these crit
Sorry, forgot to mention that the binding votes were:
Jason Van Zyl
Brett Porter
John Casey
Emmanuel Venisse
Vincent Massol
Trygve Laugstol
Carlos Sanchez
Arnaud Heritier
Thanks,
john
John Casey wrote:
I know this is late, but we have 13 X +1 votes. 8 of these are binding,
so I'll get this re
I know this is late, but we have 13 X +1 votes. 8 of these are binding,
so I'll get this release out without further delay.
Thanks, everyone!
-john
John Casey wrote:
Hi everyone,
I'd like to do the next release of the Maven core. We've fixed many
important bugs since 2.0, along with expande
+1
On 12/4/05, Eric Pugh <[EMAIL PROTECTED]> wrote:
>
> +1 Can't wait for all the new Maven goodness!
> On Dec 4, 2005, at 1:10 PM, John Casey wrote:
>
> > Hi everyone,
> >
> > I'd like to do the next release of the Maven core. We've fixed many
> > important bugs since 2.0, along with expanded pl
+1
Emmanuel
John Casey a écrit :
Hi everyone,
I'd like to do the next release of the Maven core. We've fixed many
important bugs since 2.0, along with expanded plugin support, and a new
bootstrap. In total, we've resolved 125 issues (including those related
in some fashion to the core plug
+1
John Casey wrote:
> Hi everyone,
>
> I'd like to do the next release of the Maven core. We've fixed many
> important bugs since 2.0, along with expanded plugin support, and a new
> bootstrap. In total, we've resolved 125 issues (including those related
> in some fashion to the core plugins).
+1 (but if possible MNG-1379 could worth a check before a release)
fabrizio
On 12/4/05, John Casey <[EMAIL PROTECTED]> wrote:
> Hi everyone,
>
> I'd like to do the next release of the Maven core. We've fixed many
> important bugs since 2.0, along with expanded plugin support, and a new
> boots
+1
Lukas
John Casey wrote:
Hi everyone,
I'd like to do the next release of the Maven core. We've fixed many
important bugs since 2.0, along with expanded plugin support, and a new
bootstrap. In total, we've resolved 125 issues (including those related
in some fashion to the core plugins).
+1
On 12/4/05, John Casey <[EMAIL PROTECTED]> wrote:
> Hi everyone,
>
> I'd like to do the next release of the Maven core. We've fixed many
> important bugs since 2.0, along with expanded plugin support, and a new
> bootstrap. In total, we've resolved 125 issues (including those
> related in som
+1
Vincent
2005/12/4, John Casey <[EMAIL PROTECTED]>:
> Hi everyone,
>
> I'd like to do the next release of the Maven core. We've fixed many
> important bugs since 2.0, along with expanded plugin support, and a new
> bootstrap. In total, we've resolved 125 issues (including those
> related in so
John Casey wrote:
Hi everyone,
I'd like to do the next release of the Maven core. We've fixed many
important bugs since 2.0, along with expanded plugin support, and a new
bootstrap. In total, we've resolved 125 issues (including those related
in some fashion to the core plugins). We've also
John Casey wrote:
Hi everyone,
I'd like to do the next release of the Maven core. We've fixed many
important bugs since 2.0, along with expanded plugin support, and a new
bootstrap. In total, we've resolved 125 issues (including those related
in some fashion to the core plugins). We've also
+1
Arnaud
> -Message d'origine-
> De : John Casey [mailto:[EMAIL PROTECTED]
> Envoyé : dimanche 4 décembre 2005 19:10
> À : Maven Developers List
> Objet : [vote] Release Maven 2.0.1
>
> Hi everyone,
>
> I'd like to do the next release of the Mave
> -Original Message-
> From: John Casey [mailto:[EMAIL PROTECTED]
> Sent: dimanche 4 décembre 2005 19:10
> To: Maven Developers List
> Subject: [vote] Release Maven 2.0.1
>
> Hi everyone,
>
> I'd like to do the next release of the Maven core. We've
+1 Can't wait for all the new Maven goodness!
On Dec 4, 2005, at 1:10 PM, John Casey wrote:
Hi everyone,
I'd like to do the next release of the Maven core. We've fixed many
important bugs since 2.0, along with expanded plugin support, and a
new bootstrap. In total, we've resolved 125 issu
Hi everyone,
I'd like to do the next release of the Maven core. We've fixed many
important bugs since 2.0, along with expanded plugin support, and a new
bootstrap. In total, we've resolved 125 issues (including those
related in some fashion to the core plugins). We've also added support
for
29 matches
Mail list logo
