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

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

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

rfscholte
Looking for someone who can second the following issues:

MNG-6148: Can't package and assemble with JDK9/Jigsaw

MNG-6127: Fix plugin execution configuration interference

MNG-6220: Add CLI options to control color output
by introducing system property style.color=[auto*|enabled|disabled]

thanks,
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]

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

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

rfscholte
I'm fine with that:
style.color=[auto*|always|never]

the original PR is still based on a CLI option which I don't like because  
all other style options are already and only controlled by system  
properties.
I have to create a new branch if we can agree on this.

Robert

On Fri, 23 Jun 2017 16:34:55 +0200, Michael Osipov <[hidden email]>  
wrote:

> Am 2017-06-23 um 16:27 schrieb Robert Scholte:
>> MNG-6220: Add CLI options to control color output
>> by introducing system property style.color=[auto*|enabled|disabled]
>
> This definitively needs polish and a value style like tree/grep. I left  
> several comments on the PR.
>
> ---------------------------------------------------------------------
> 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

rfscholte
In reply to this post by rfscholte
On Fri, 23 Jun 2017 16:27:03 +0200, Robert Scholte <[hidden email]>  
wrote:

> Looking for someone who can second the following issues:
Second attempt:

>
> MNG-6148: Can't package and assemble with JDK9/Jigsaw

See  
https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=361b902d0c01d9a2b82d4b126ecd3a228b955124
In fact only maven-javadoc-plugin is really required, all other plugins  
were already updated for other issues in 3.5.0

>
> MNG-6127: Fix plugin execution configuration interference

See  
https://git-wip-us.apache.org/repos/asf?p=maven-integration-testing.git;a=commit;h=82b043f8bd2015fc4ccac35df805ec2356100428
See  
https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=57e4b331ebd41ab5337c60a7c8fc4d3d435475fb


>
> MNG-6220: Add CLI options to control color output
Fixed by introducing system property style.color=[auto*|always|never]
See  
https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=fd57754218e749305be1dd745fda9407960cf985

>
> thanks,
> 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]

Loading...