Quantcast

[ANN] First call to round up issues for 3.5.1

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[ANN] First call to round up issues for 3.5.1

stephenconnolly
I'd like people to take this next week to consider what issues we want to
pull in scope for 3.5.1.

If you are a committer, just add the issues to Fix Version of
3.5.1-candidate, ideally adding a comment at the same time with your
reasoning.

If once we have a seconding committer, they can just comment seconding and
move the Fix Version to 3.5.1.

I'm going to suggest a 1 week period of open scoping. After that point in
time, my intent is to be more strict and apply "release manager risk
management" on any new issues being targeted for 3.5.1. Similarly, if
issues targeted for 3.5.1 are not making sufficient progress they will be
dropped... but for now... it's open season!

Get triaging!

-Stephen
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [ANN] First call to round up issues for 3.5.1

Eric Lilja
Is https://issues.apache.org/jira/browse/MNG-6025 being included in
3.5.1? I sure hope so!

- Eric L

On 2017-05-01 22:15, Hervé BOUTEMY wrote:

> great!
> I'll mark it for 3.5.1
>
> Regards,
>
> Hervé
>
> Le lundi 1 mai 2017, 19:59:50 CEST Robert Scholte a écrit :
>> @Hervé, I want to second MNG-6223
>>
>> Robert
>>
>> On Tue, 25 Apr 2017 22:43:54 +0200, Stephen Connolly
>>
>> <[hidden email]> wrote:
>>> I'd like people to take this next week to consider what issues we want to
>>> pull in scope for 3.5.1.
>>>
>>> If you are a committer, just add the issues to Fix Version of
>>> 3.5.1-candidate, ideally adding a comment at the same time with your
>>> reasoning.
>>>
>>> If once we have a seconding committer, they can just comment seconding
>>> and
>>> move the Fix Version to 3.5.1.
>>>
>>> I'm going to suggest a 1 week period of open scoping. After that point in
>>> time, my intent is to be more strict and apply "release manager risk
>>> management" on any new issues being targeted for 3.5.1. Similarly, if
>>> issues targeted for 3.5.1 are not making sufficient progress they will be
>>> dropped... but for now... it's open season!
>>>
>>> Get triaging!
>>>
>>> -Stephen
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [ANN] First call to round up issues for 3.5.1

stephenconnolly
In reply to this post by stephenconnolly
Progress seems to be being made... I'm willing to let current progress
continue for the next 1-2 weeks before starting a whip-round to drive
towards a release... anyone want me to accelerate?
On Tue 25 Apr 2017 at 21:43, Stephen Connolly <
[hidden email]> wrote:

> I'd like people to take this next week to consider what issues we want to
> pull in scope for 3.5.1.
>
> If you are a committer, just add the issues to Fix Version of
> 3.5.1-candidate, ideally adding a comment at the same time with your
> reasoning.
>
> If once we have a seconding committer, they can just comment seconding and
> move the Fix Version to 3.5.1.
>
> I'm going to suggest a 1 week period of open scoping. After that point in
> time, my intent is to be more strict and apply "release manager risk
> management" on any new issues being targeted for 3.5.1. Similarly, if
> issues targeted for 3.5.1 are not making sufficient progress they will be
> dropped... but for now... it's open season!
>
> Get triaging!
>
> -Stephen
>
--
Sent from my phone
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [ANN] First call to round up issues for 3.5.1

michaelo
Am 2017-05-05 um 19:23 schrieb Stephen Connolly:
> Progress seems to be being made... I'm willing to let current progress
> continue for the next 1-2 weeks before starting a whip-round to drive
> towards a release... anyone want me to accelerate?
> On Tue 25 Apr 2017 at 21:43, Stephen Connolly <

No acceleration please, I'll need so time to get my stuff integrated.
Especially because I found some flaws in our ITs and some regressions in
some plugins.


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [ANN] First call to round up issues for 3.5.1

Robert Scholte-6
In reply to this post by stephenconnolly
I gave my spin for the 3.5.1-candidates. I've mentioned the issues I'd  
like to add, but most are still waiting to be seconded.

Robert

On Fri, 05 May 2017 19:23:41 +0200, Stephen Connolly  
<[hidden email]> wrote:

> Progress seems to be being made... I'm willing to let current progress
> continue for the next 1-2 weeks before starting a whip-round to drive
> towards a release... anyone want me to accelerate?
> On Tue 25 Apr 2017 at 21:43, Stephen Connolly <
> [hidden email]> wrote:
>
>> I'd like people to take this next week to consider what issues we want  
>> to
>> pull in scope for 3.5.1.
>>
>> If you are a committer, just add the issues to Fix Version of
>> 3.5.1-candidate, ideally adding a comment at the same time with your
>> reasoning.
>>
>> If once we have a seconding committer, they can just comment seconding  
>> and
>> move the Fix Version to 3.5.1.
>>
>> I'm going to suggest a 1 week period of open scoping. After that point  
>> in
>> time, my intent is to be more strict and apply "release manager risk
>> management" on any new issues being targeted for 3.5.1. Similarly, if
>> issues targeted for 3.5.1 are not making sufficient progress they will  
>> be
>> dropped... but for now... it's open season!
>>
>> Get triaging!
>>
>> -Stephen

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [ANN] First call to round up issues for 3.5.1

michaelo
We should consider this batch
https://github.com/ChristianSchulte/maven/commit/3494c28426b8dd5711b730d622ba98d603caeda6#commitcomment-22009084 
if we want to address the issue we talked about on IRC.

Michael

Am 2017-05-05 um 21:04 schrieb Robert Scholte:

> I gave my spin for the 3.5.1-candidates. I've mentioned the issues I'd
> like to add, but most are still waiting to be seconded.
>
> Robert
>
> On Fri, 05 May 2017 19:23:41 +0200, Stephen Connolly
> <[hidden email]> wrote:
>
>> Progress seems to be being made... I'm willing to let current progress
>> continue for the next 1-2 weeks before starting a whip-round to drive
>> towards a release... anyone want me to accelerate?
>> On Tue 25 Apr 2017 at 21:43, Stephen Connolly <
>> [hidden email]> wrote:
>>
>>> I'd like people to take this next week to consider what issues we
>>> want to
>>> pull in scope for 3.5.1.
>>>
>>> If you are a committer, just add the issues to Fix Version of
>>> 3.5.1-candidate, ideally adding a comment at the same time with your
>>> reasoning.
>>>
>>> If once we have a seconding committer, they can just comment
>>> seconding and
>>> move the Fix Version to 3.5.1.
>>>
>>> I'm going to suggest a 1 week period of open scoping. After that
>>> point in
>>> time, my intent is to be more strict and apply "release manager risk
>>> management" on any new issues being targeted for 3.5.1. Similarly, if
>>> issues targeted for 3.5.1 are not making sufficient progress they
>>> will be
>>> dropped... but for now... it's open season!
>>>
>>> Get triaging!
>>>
>>> -Stephen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [ANN] First call to round up issues for 3.5.1

Robert Scholte-6
This specific issue seems quite isolated to me and is likely introduced  
when switching from Sonetype Aether to Eclipse Aether, where (IIRC) the  
boolean became a Boolean.

On Fri, 05 May 2017 22:18:11 +0200, Michael Osipov <[hidden email]>  
wrote:

> That wasn't actually my point. Christian wrote that to make the entire  
> chain consistent several issues have to be addressed.
>
> Am 2017-05-05 um 21:54 schrieb Robert Scholte:
>> AFAIK you, me and Stephen already agreed that MNG-5935 should be part
>> of  3.5.1
>>
>> On Fri, 05 May 2017 21:09:02 +0200, Michael Osipov <[hidden email]>
>> wrote:
>>
>>> We should consider this batch
>>> https://github.com/ChristianSchulte/maven/commit/3494c28426b8dd5711b730d622ba98d603caeda6#commitcomment-22009084
>>> if we want to address the issue we talked about on IRC.
>>>
>>> Michael
>>>
>>> Am 2017-05-05 um 21:04 schrieb Robert Scholte:
>>>> I gave my spin for the 3.5.1-candidates. I've mentioned the issues I'd
>>>> like to add, but most are still waiting to be seconded.
>>>>
>>>> Robert
>>>>
>>>> On Fri, 05 May 2017 19:23:41 +0200, Stephen Connolly
>>>> <[hidden email]> wrote:
>>>>
>>>>> Progress seems to be being made... I'm willing to let current  
>>>>> progress
>>>>> continue for the next 1-2 weeks before starting a whip-round to drive
>>>>> towards a release... anyone want me to accelerate?
>>>>> On Tue 25 Apr 2017 at 21:43, Stephen Connolly <
>>>>> [hidden email]> wrote:
>>>>>
>>>>>> I'd like people to take this next week to consider what issues we
>>>>>> want to
>>>>>> pull in scope for 3.5.1.
>>>>>>
>>>>>> If you are a committer, just add the issues to Fix Version of
>>>>>> 3.5.1-candidate, ideally adding a comment at the same time with your
>>>>>> reasoning.
>>>>>>
>>>>>> If once we have a seconding committer, they can just comment
>>>>>> seconding and
>>>>>> move the Fix Version to 3.5.1.
>>>>>>
>>>>>> I'm going to suggest a 1 week period of open scoping. After that
>>>>>> point in
>>>>>> time, my intent is to be more strict and apply "release manager risk
>>>>>> management" on any new issues being targeted for 3.5.1. Similarly,  
>>>>>> if
>>>>>> issues targeted for 3.5.1 are not making sufficient progress they
>>>>>> will be
>>>>>> dropped... but for now... it's open season!
>>>>>>
>>>>>> Get triaging!
>>>>>>
>>>>>> -Stephen
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: [hidden email]
>>>> For additional commands, e-mail: [hidden email]
>>>>
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Loading...