You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Brett Porter <br...@apache.org> on 2009/01/27 20:43:26 UTC
releasing 2.0.10?
Hi,
It looks like John fixed up the last issue for this a few days ago and
Benjamin took care of the shade plugin over Christmas. Brian - did you
want to roll another RC?
I'll try and get back to the enforcer and 2.1.0-M2 over the next
couple of weeks now that I'm finally caught up after holidays :)
Cheers,
Brett
--
Brett Porter
brett@apache.org
http://blogs.exist.com/bporter/
RE: releasing 2.0.10?
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
That's the plan.
-----Original Message-----
From: Henri Gomez [mailto:henri.gomez@gmail.com]
Sent: Monday, February 02, 2009 11:09 AM
To: Maven Developers List
Subject: Re: releasing 2.0.10?
2009/2/2 Brian E. Fox <br...@reply.infinity.nu>:
> Who knows. Maybe, maybe not depending on the timing and uptake of 3.x
>
Well if 2.1.0 is quickly stable and you need to add more stuff, 2.2.0
could be a good idea.
But 2.x.y should stop at some time when 3.0 will be available or users
will be stuck by so many differents versions (and a pain for
developpers to check / fix so many branches).
---------------------------------------------------------------------
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: releasing 2.0.10?
Posted by Henri Gomez <he...@gmail.com>.
2009/2/2 Brian E. Fox <br...@reply.infinity.nu>:
> Who knows. Maybe, maybe not depending on the timing and uptake of 3.x
>
Well if 2.1.0 is quickly stable and you need to add more stuff, 2.2.0
could be a good idea.
But 2.x.y should stop at some time when 3.0 will be available or users
will be stuck by so many differents versions (and a pain for
developpers to check / fix so many branches).
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: releasing 2.0.10?
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Who knows. Maybe, maybe not depending on the timing and uptake of 3.x
-----Original Message-----
From: Henri Gomez [mailto:henri.gomez@gmail.com]
Sent: Monday, February 02, 2009 10:11 AM
To: Maven Developers List
Subject: Re: releasing 2.0.10?
I agree.
But no 2.2.x is planned ?
2009/2/2 Brian E. Fox <br...@reply.infinity.nu>:
> Yes, but hopefully 2.0.x is end of life with either 2.0.10 or 2.0.11
and
> 2.1.x becomes the active line.
>
> -----Original Message-----
> From: Henri Gomez [mailto:henri.gomez@gmail.com]
> Sent: Monday, February 02, 2009 3:36 AM
> To: Maven Developers List
> Subject: Re: releasing 2.0.10?
>
> So there will be
>
> 2.0.x
>
> 2.1.x
>
> and 3.0 ?
>
>
> 2009/1/30 Brian E. Fox <br...@reply.infinity.nu>:
>> There's a new 2.1 cut from the 2.0.x branch that provides a space to
> put
>> features. We did this back in Aug/Sept but there's been little
forward
>> progress, so a release should get it started. When we planned it out,
>> there was a lot of interest in new features but I don't think much
has
>> been done in the last 5 months, so I don't see the point in waiting
> for
>> future features, lets get 2.1 out so people will start to use it.
>>
>> -----Original Message-----
>> From: Henri Gomez [mailto:henri.gomez@gmail.com]
>> Sent: Friday, January 30, 2009 8:39 AM
>> To: Maven Developers List
>> Subject: Re: releasing 2.0.10?
>>
>> I was thinking :
>>
>> 2.0.x is the current Maven 2
>>
>> 2.1 deprecated and will became 3.0
>>
>> But what is 2.2 ? or 2.1 ?
>>
>> I'm puzzled
>>
>>
>> 2009/1/30 Brian E. Fox <br...@reply.infinity.nu>:
>>> My original intent was to shift the focus to 2.1 and bring that
>> quickly
>>> to GA. The development on it has stalled so it's irrelevant if it's
>>> feature complete or not, it's stable and usable as it is. Future
>>> features can go into 2.1.x or 2.2.
>>>
>>> -----Original Message-----
>>> From: paulus.benedictus@gmail.com
> [mailto:paulus.benedictus@gmail.com]
>>> On Behalf Of Paul Benedict
>>> Sent: Thursday, January 29, 2009 10:58 PM
>>> To: Maven Developers List
>>> Subject: Re: releasing 2.0.10?
>>>
>>> I don't think it's wise to EOL a product without a GA replacement.
>>> It's true that because 2.1 is in milestone releases it is not usable
>>> by many people in an "approved" managerial environment, but, to the
>>> same token, it's not feature complete either.
>>>
>>> Personally speaking, I definitely am eagerly awaiting the issues
>>> scheduled in 2.0.11.
>>>
>>> Please continue releasing 2.0.x until 2.1/3.0 has a GA.
>>>
>>> Paul
>>>
>>>> On 28/01/2009, at 9:03 AM, Brian E. Fox wrote:
>>>>
>>>>> Normally I would agree on the late change, but it's entirely
>> optional
>>>>> usage so it wouldn't affect existing builds and I'd like to start
>>>>> thinking about 2.0.10 being the EOL for 2.0.x.
>>>>
>>>> Given there's already been a good number of fixes for 2.0.11 that
>>> haven't
>>>> been rolled up to 2.0.10-RC, maybe pushing 2.0.10 out as is and
>> having
>>> .11
>>>> as the EOL is a better way to go - wdyt?
>>>
>>>
---------------------------------------------------------------------
>>> 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
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> 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
>>
>>
>
> ---------------------------------------------------------------------
> 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
>
>
---------------------------------------------------------------------
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: releasing 2.0.10?
Posted by Henri Gomez <he...@gmail.com>.
I agree.
But no 2.2.x is planned ?
2009/2/2 Brian E. Fox <br...@reply.infinity.nu>:
> Yes, but hopefully 2.0.x is end of life with either 2.0.10 or 2.0.11 and
> 2.1.x becomes the active line.
>
> -----Original Message-----
> From: Henri Gomez [mailto:henri.gomez@gmail.com]
> Sent: Monday, February 02, 2009 3:36 AM
> To: Maven Developers List
> Subject: Re: releasing 2.0.10?
>
> So there will be
>
> 2.0.x
>
> 2.1.x
>
> and 3.0 ?
>
>
> 2009/1/30 Brian E. Fox <br...@reply.infinity.nu>:
>> There's a new 2.1 cut from the 2.0.x branch that provides a space to
> put
>> features. We did this back in Aug/Sept but there's been little forward
>> progress, so a release should get it started. When we planned it out,
>> there was a lot of interest in new features but I don't think much has
>> been done in the last 5 months, so I don't see the point in waiting
> for
>> future features, lets get 2.1 out so people will start to use it.
>>
>> -----Original Message-----
>> From: Henri Gomez [mailto:henri.gomez@gmail.com]
>> Sent: Friday, January 30, 2009 8:39 AM
>> To: Maven Developers List
>> Subject: Re: releasing 2.0.10?
>>
>> I was thinking :
>>
>> 2.0.x is the current Maven 2
>>
>> 2.1 deprecated and will became 3.0
>>
>> But what is 2.2 ? or 2.1 ?
>>
>> I'm puzzled
>>
>>
>> 2009/1/30 Brian E. Fox <br...@reply.infinity.nu>:
>>> My original intent was to shift the focus to 2.1 and bring that
>> quickly
>>> to GA. The development on it has stalled so it's irrelevant if it's
>>> feature complete or not, it's stable and usable as it is. Future
>>> features can go into 2.1.x or 2.2.
>>>
>>> -----Original Message-----
>>> From: paulus.benedictus@gmail.com
> [mailto:paulus.benedictus@gmail.com]
>>> On Behalf Of Paul Benedict
>>> Sent: Thursday, January 29, 2009 10:58 PM
>>> To: Maven Developers List
>>> Subject: Re: releasing 2.0.10?
>>>
>>> I don't think it's wise to EOL a product without a GA replacement.
>>> It's true that because 2.1 is in milestone releases it is not usable
>>> by many people in an "approved" managerial environment, but, to the
>>> same token, it's not feature complete either.
>>>
>>> Personally speaking, I definitely am eagerly awaiting the issues
>>> scheduled in 2.0.11.
>>>
>>> Please continue releasing 2.0.x until 2.1/3.0 has a GA.
>>>
>>> Paul
>>>
>>>> On 28/01/2009, at 9:03 AM, Brian E. Fox wrote:
>>>>
>>>>> Normally I would agree on the late change, but it's entirely
>> optional
>>>>> usage so it wouldn't affect existing builds and I'd like to start
>>>>> thinking about 2.0.10 being the EOL for 2.0.x.
>>>>
>>>> Given there's already been a good number of fixes for 2.0.11 that
>>> haven't
>>>> been rolled up to 2.0.10-RC, maybe pushing 2.0.10 out as is and
>> having
>>> .11
>>>> as the EOL is a better way to go - wdyt?
>>>
>>> ---------------------------------------------------------------------
>>> 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
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> 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
>>
>>
>
> ---------------------------------------------------------------------
> 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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: releasing 2.0.10?
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Yes, but hopefully 2.0.x is end of life with either 2.0.10 or 2.0.11 and
2.1.x becomes the active line.
-----Original Message-----
From: Henri Gomez [mailto:henri.gomez@gmail.com]
Sent: Monday, February 02, 2009 3:36 AM
To: Maven Developers List
Subject: Re: releasing 2.0.10?
So there will be
2.0.x
2.1.x
and 3.0 ?
2009/1/30 Brian E. Fox <br...@reply.infinity.nu>:
> There's a new 2.1 cut from the 2.0.x branch that provides a space to
put
> features. We did this back in Aug/Sept but there's been little forward
> progress, so a release should get it started. When we planned it out,
> there was a lot of interest in new features but I don't think much has
> been done in the last 5 months, so I don't see the point in waiting
for
> future features, lets get 2.1 out so people will start to use it.
>
> -----Original Message-----
> From: Henri Gomez [mailto:henri.gomez@gmail.com]
> Sent: Friday, January 30, 2009 8:39 AM
> To: Maven Developers List
> Subject: Re: releasing 2.0.10?
>
> I was thinking :
>
> 2.0.x is the current Maven 2
>
> 2.1 deprecated and will became 3.0
>
> But what is 2.2 ? or 2.1 ?
>
> I'm puzzled
>
>
> 2009/1/30 Brian E. Fox <br...@reply.infinity.nu>:
>> My original intent was to shift the focus to 2.1 and bring that
> quickly
>> to GA. The development on it has stalled so it's irrelevant if it's
>> feature complete or not, it's stable and usable as it is. Future
>> features can go into 2.1.x or 2.2.
>>
>> -----Original Message-----
>> From: paulus.benedictus@gmail.com
[mailto:paulus.benedictus@gmail.com]
>> On Behalf Of Paul Benedict
>> Sent: Thursday, January 29, 2009 10:58 PM
>> To: Maven Developers List
>> Subject: Re: releasing 2.0.10?
>>
>> I don't think it's wise to EOL a product without a GA replacement.
>> It's true that because 2.1 is in milestone releases it is not usable
>> by many people in an "approved" managerial environment, but, to the
>> same token, it's not feature complete either.
>>
>> Personally speaking, I definitely am eagerly awaiting the issues
>> scheduled in 2.0.11.
>>
>> Please continue releasing 2.0.x until 2.1/3.0 has a GA.
>>
>> Paul
>>
>>> On 28/01/2009, at 9:03 AM, Brian E. Fox wrote:
>>>
>>>> Normally I would agree on the late change, but it's entirely
> optional
>>>> usage so it wouldn't affect existing builds and I'd like to start
>>>> thinking about 2.0.10 being the EOL for 2.0.x.
>>>
>>> Given there's already been a good number of fixes for 2.0.11 that
>> haven't
>>> been rolled up to 2.0.10-RC, maybe pushing 2.0.10 out as is and
> having
>> .11
>>> as the EOL is a better way to go - wdyt?
>>
>> ---------------------------------------------------------------------
>> 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
>>
>>
>
> ---------------------------------------------------------------------
> 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
>
>
---------------------------------------------------------------------
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: releasing 2.0.10?
Posted by Henri Gomez <he...@gmail.com>.
So there will be
2.0.x
2.1.x
and 3.0 ?
2009/1/30 Brian E. Fox <br...@reply.infinity.nu>:
> There's a new 2.1 cut from the 2.0.x branch that provides a space to put
> features. We did this back in Aug/Sept but there's been little forward
> progress, so a release should get it started. When we planned it out,
> there was a lot of interest in new features but I don't think much has
> been done in the last 5 months, so I don't see the point in waiting for
> future features, lets get 2.1 out so people will start to use it.
>
> -----Original Message-----
> From: Henri Gomez [mailto:henri.gomez@gmail.com]
> Sent: Friday, January 30, 2009 8:39 AM
> To: Maven Developers List
> Subject: Re: releasing 2.0.10?
>
> I was thinking :
>
> 2.0.x is the current Maven 2
>
> 2.1 deprecated and will became 3.0
>
> But what is 2.2 ? or 2.1 ?
>
> I'm puzzled
>
>
> 2009/1/30 Brian E. Fox <br...@reply.infinity.nu>:
>> My original intent was to shift the focus to 2.1 and bring that
> quickly
>> to GA. The development on it has stalled so it's irrelevant if it's
>> feature complete or not, it's stable and usable as it is. Future
>> features can go into 2.1.x or 2.2.
>>
>> -----Original Message-----
>> From: paulus.benedictus@gmail.com [mailto:paulus.benedictus@gmail.com]
>> On Behalf Of Paul Benedict
>> Sent: Thursday, January 29, 2009 10:58 PM
>> To: Maven Developers List
>> Subject: Re: releasing 2.0.10?
>>
>> I don't think it's wise to EOL a product without a GA replacement.
>> It's true that because 2.1 is in milestone releases it is not usable
>> by many people in an "approved" managerial environment, but, to the
>> same token, it's not feature complete either.
>>
>> Personally speaking, I definitely am eagerly awaiting the issues
>> scheduled in 2.0.11.
>>
>> Please continue releasing 2.0.x until 2.1/3.0 has a GA.
>>
>> Paul
>>
>>> On 28/01/2009, at 9:03 AM, Brian E. Fox wrote:
>>>
>>>> Normally I would agree on the late change, but it's entirely
> optional
>>>> usage so it wouldn't affect existing builds and I'd like to start
>>>> thinking about 2.0.10 being the EOL for 2.0.x.
>>>
>>> Given there's already been a good number of fixes for 2.0.11 that
>> haven't
>>> been rolled up to 2.0.10-RC, maybe pushing 2.0.10 out as is and
> having
>> .11
>>> as the EOL is a better way to go - wdyt?
>>
>> ---------------------------------------------------------------------
>> 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
>>
>>
>
> ---------------------------------------------------------------------
> 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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: releasing 2.0.10?
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
There's a new 2.1 cut from the 2.0.x branch that provides a space to put
features. We did this back in Aug/Sept but there's been little forward
progress, so a release should get it started. When we planned it out,
there was a lot of interest in new features but I don't think much has
been done in the last 5 months, so I don't see the point in waiting for
future features, lets get 2.1 out so people will start to use it.
-----Original Message-----
From: Henri Gomez [mailto:henri.gomez@gmail.com]
Sent: Friday, January 30, 2009 8:39 AM
To: Maven Developers List
Subject: Re: releasing 2.0.10?
I was thinking :
2.0.x is the current Maven 2
2.1 deprecated and will became 3.0
But what is 2.2 ? or 2.1 ?
I'm puzzled
2009/1/30 Brian E. Fox <br...@reply.infinity.nu>:
> My original intent was to shift the focus to 2.1 and bring that
quickly
> to GA. The development on it has stalled so it's irrelevant if it's
> feature complete or not, it's stable and usable as it is. Future
> features can go into 2.1.x or 2.2.
>
> -----Original Message-----
> From: paulus.benedictus@gmail.com [mailto:paulus.benedictus@gmail.com]
> On Behalf Of Paul Benedict
> Sent: Thursday, January 29, 2009 10:58 PM
> To: Maven Developers List
> Subject: Re: releasing 2.0.10?
>
> I don't think it's wise to EOL a product without a GA replacement.
> It's true that because 2.1 is in milestone releases it is not usable
> by many people in an "approved" managerial environment, but, to the
> same token, it's not feature complete either.
>
> Personally speaking, I definitely am eagerly awaiting the issues
> scheduled in 2.0.11.
>
> Please continue releasing 2.0.x until 2.1/3.0 has a GA.
>
> Paul
>
>> On 28/01/2009, at 9:03 AM, Brian E. Fox wrote:
>>
>>> Normally I would agree on the late change, but it's entirely
optional
>>> usage so it wouldn't affect existing builds and I'd like to start
>>> thinking about 2.0.10 being the EOL for 2.0.x.
>>
>> Given there's already been a good number of fixes for 2.0.11 that
> haven't
>> been rolled up to 2.0.10-RC, maybe pushing 2.0.10 out as is and
having
> .11
>> as the EOL is a better way to go - wdyt?
>
> ---------------------------------------------------------------------
> 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
>
>
---------------------------------------------------------------------
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: releasing 2.0.10?
Posted by Henri Gomez <he...@gmail.com>.
I was thinking :
2.0.x is the current Maven 2
2.1 deprecated and will became 3.0
But what is 2.2 ? or 2.1 ?
I'm puzzled
2009/1/30 Brian E. Fox <br...@reply.infinity.nu>:
> My original intent was to shift the focus to 2.1 and bring that quickly
> to GA. The development on it has stalled so it's irrelevant if it's
> feature complete or not, it's stable and usable as it is. Future
> features can go into 2.1.x or 2.2.
>
> -----Original Message-----
> From: paulus.benedictus@gmail.com [mailto:paulus.benedictus@gmail.com]
> On Behalf Of Paul Benedict
> Sent: Thursday, January 29, 2009 10:58 PM
> To: Maven Developers List
> Subject: Re: releasing 2.0.10?
>
> I don't think it's wise to EOL a product without a GA replacement.
> It's true that because 2.1 is in milestone releases it is not usable
> by many people in an "approved" managerial environment, but, to the
> same token, it's not feature complete either.
>
> Personally speaking, I definitely am eagerly awaiting the issues
> scheduled in 2.0.11.
>
> Please continue releasing 2.0.x until 2.1/3.0 has a GA.
>
> Paul
>
>> On 28/01/2009, at 9:03 AM, Brian E. Fox wrote:
>>
>>> Normally I would agree on the late change, but it's entirely optional
>>> usage so it wouldn't affect existing builds and I'd like to start
>>> thinking about 2.0.10 being the EOL for 2.0.x.
>>
>> Given there's already been a good number of fixes for 2.0.11 that
> haven't
>> been rolled up to 2.0.10-RC, maybe pushing 2.0.10 out as is and having
> .11
>> as the EOL is a better way to go - wdyt?
>
> ---------------------------------------------------------------------
> 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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: releasing 2.0.10?
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
My original intent was to shift the focus to 2.1 and bring that quickly
to GA. The development on it has stalled so it's irrelevant if it's
feature complete or not, it's stable and usable as it is. Future
features can go into 2.1.x or 2.2.
-----Original Message-----
From: paulus.benedictus@gmail.com [mailto:paulus.benedictus@gmail.com]
On Behalf Of Paul Benedict
Sent: Thursday, January 29, 2009 10:58 PM
To: Maven Developers List
Subject: Re: releasing 2.0.10?
I don't think it's wise to EOL a product without a GA replacement.
It's true that because 2.1 is in milestone releases it is not usable
by many people in an "approved" managerial environment, but, to the
same token, it's not feature complete either.
Personally speaking, I definitely am eagerly awaiting the issues
scheduled in 2.0.11.
Please continue releasing 2.0.x until 2.1/3.0 has a GA.
Paul
> On 28/01/2009, at 9:03 AM, Brian E. Fox wrote:
>
>> Normally I would agree on the late change, but it's entirely optional
>> usage so it wouldn't affect existing builds and I'd like to start
>> thinking about 2.0.10 being the EOL for 2.0.x.
>
> Given there's already been a good number of fixes for 2.0.11 that
haven't
> been rolled up to 2.0.10-RC, maybe pushing 2.0.10 out as is and having
.11
> as the EOL is a better way to go - wdyt?
---------------------------------------------------------------------
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: releasing 2.0.10?
Posted by Paul Benedict <pb...@apache.org>.
I don't think it's wise to EOL a product without a GA replacement.
It's true that because 2.1 is in milestone releases it is not usable
by many people in an "approved" managerial environment, but, to the
same token, it's not feature complete either.
Personally speaking, I definitely am eagerly awaiting the issues
scheduled in 2.0.11.
Please continue releasing 2.0.x until 2.1/3.0 has a GA.
Paul
> On 28/01/2009, at 9:03 AM, Brian E. Fox wrote:
>
>> Normally I would agree on the late change, but it's entirely optional
>> usage so it wouldn't affect existing builds and I'd like to start
>> thinking about 2.0.10 being the EOL for 2.0.x.
>
> Given there's already been a good number of fixes for 2.0.11 that haven't
> been rolled up to 2.0.10-RC, maybe pushing 2.0.10 out as is and having .11
> as the EOL is a better way to go - wdyt?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: releasing 2.0.10?
Posted by Brett Porter <br...@apache.org>.
On 28/01/2009, at 9:03 AM, Brian E. Fox wrote:
> Normally I would agree on the late change, but it's entirely optional
> usage so it wouldn't affect existing builds and I'd like to start
> thinking about 2.0.10 being the EOL for 2.0.x.
Given there's already been a good number of fixes for 2.0.11 that
haven't been rolled up to 2.0.10-RC, maybe pushing 2.0.10 out as is
and having .11 as the EOL is a better way to go - wdyt?
Cheers,
Brett
>
>
> -----Original Message-----
> From: Brett Porter [mailto:brett@porterclan.net] On Behalf Of Brett
> Porter
> Sent: Tuesday, January 27, 2009 5:00 PM
> To: Maven Developers List
> Subject: Re: releasing 2.0.10?
>
>
> On 27/01/2009, at 1:45 PM, Brian E. Fox wrote:
>
>> Yes, I was actually waiting to look at the stuff oleg put into 2.1
>> as I
>> think this should be considered for 2.0.10.
>
> It's a bit late in the cycle to make a major change again IMO,
> especially since this has become a bogey release.
>
>>
>>
>> I fixed up the enforcer bugs, I think it was just waiting for the
>> parent
>> to be released for the new skin.
>
> Col.
>
>>
>>
>> On 2.1.0, I think we should just release what's there as 2.1.0, many
>> people I spoke to aren't able to use it because it's only a milestone
>> release. It's just as stable as 2.0.10 at this point so we aren't
>> helping anyone with further milestones when no one is actually
>> implementing the plan. We should just push it out and move forward.
>
> I was going to suggest the same thing, as this is also a bogey
> release :) There are regressions and patches in M2 that probably still
> need to be done, which is what I was coming back to. M3 is easy if
> Doxia is released - but I think it could be bumped if not. M4 is just
> merging and testing. I'm prepared to drop M5 out since even though it
> works, we're not going to be infrastructurally prepared to use this
> for a while.
>
> Cheers,
> Brett
>
> --
> Brett Porter
> brett@apache.org
> http://blogs.exist.com/bporter/
>
>
> ---------------------------------------------------------------------
> 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
>
--
Brett Porter
brett@apache.org
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: releasing 2.0.10?
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Normally I would agree on the late change, but it's entirely optional
usage so it wouldn't affect existing builds and I'd like to start
thinking about 2.0.10 being the EOL for 2.0.x.
-----Original Message-----
From: Brett Porter [mailto:brett@porterclan.net] On Behalf Of Brett
Porter
Sent: Tuesday, January 27, 2009 5:00 PM
To: Maven Developers List
Subject: Re: releasing 2.0.10?
On 27/01/2009, at 1:45 PM, Brian E. Fox wrote:
> Yes, I was actually waiting to look at the stuff oleg put into 2.1
> as I
> think this should be considered for 2.0.10.
It's a bit late in the cycle to make a major change again IMO,
especially since this has become a bogey release.
>
>
> I fixed up the enforcer bugs, I think it was just waiting for the
> parent
> to be released for the new skin.
Col.
>
>
> On 2.1.0, I think we should just release what's there as 2.1.0, many
> people I spoke to aren't able to use it because it's only a milestone
> release. It's just as stable as 2.0.10 at this point so we aren't
> helping anyone with further milestones when no one is actually
> implementing the plan. We should just push it out and move forward.
I was going to suggest the same thing, as this is also a bogey
release :) There are regressions and patches in M2 that probably still
need to be done, which is what I was coming back to. M3 is easy if
Doxia is released - but I think it could be bumped if not. M4 is just
merging and testing. I'm prepared to drop M5 out since even though it
works, we're not going to be infrastructurally prepared to use this
for a while.
Cheers,
Brett
--
Brett Porter
brett@apache.org
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
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: releasing 2.0.10?
Posted by Brett Porter <br...@apache.org>.
On 27/01/2009, at 1:45 PM, Brian E. Fox wrote:
> Yes, I was actually waiting to look at the stuff oleg put into 2.1
> as I
> think this should be considered for 2.0.10.
It's a bit late in the cycle to make a major change again IMO,
especially since this has become a bogey release.
>
>
> I fixed up the enforcer bugs, I think it was just waiting for the
> parent
> to be released for the new skin.
Col.
>
>
> On 2.1.0, I think we should just release what's there as 2.1.0, many
> people I spoke to aren't able to use it because it's only a milestone
> release. It's just as stable as 2.0.10 at this point so we aren't
> helping anyone with further milestones when no one is actually
> implementing the plan. We should just push it out and move forward.
I was going to suggest the same thing, as this is also a bogey
release :) There are regressions and patches in M2 that probably still
need to be done, which is what I was coming back to. M3 is easy if
Doxia is released - but I think it could be bumped if not. M4 is just
merging and testing. I'm prepared to drop M5 out since even though it
works, we're not going to be infrastructurally prepared to use this
for a while.
Cheers,
Brett
--
Brett Porter
brett@apache.org
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: releasing 2.0.10?
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Yes, I was actually waiting to look at the stuff oleg put into 2.1 as I
think this should be considered for 2.0.10.
I fixed up the enforcer bugs, I think it was just waiting for the parent
to be released for the new skin.
On 2.1.0, I think we should just release what's there as 2.1.0, many
people I spoke to aren't able to use it because it's only a milestone
release. It's just as stable as 2.0.10 at this point so we aren't
helping anyone with further milestones when no one is actually
implementing the plan. We should just push it out and move forward.
-----Original Message-----
From: Brett Porter [mailto:brett@porterclan.net] On Behalf Of Brett
Porter
Sent: Tuesday, January 27, 2009 2:43 PM
To: Maven Developers List
Subject: releasing 2.0.10?
Hi,
It looks like John fixed up the last issue for this a few days ago and
Benjamin took care of the shade plugin over Christmas. Brian - did you
want to roll another RC?
I'll try and get back to the enforcer and 2.1.0-M2 over the next
couple of weeks now that I'm finally caught up after holidays :)
Cheers,
Brett
--
Brett Porter
brett@apache.org
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org