Re: [VOTE] Release Apache Commons Lang 3.9 based on RC1

> On Apr 9, 2019, at 9:16 PM, Gary Gregory <[hidden email]> wrote:
>
> I also see that we are using an old version of jacoco and surefire, that
> probably matters…

Maven surefire is 3.0.0-M3. Are we willing to consume a non-release version of the plugin? I ask this because I regard "<version_number>-Mx”, where x is a positive integer, to indicate a milestone release prior to a fully fledged major release.

Re: [VOTE] Release Apache Commons Lang 3.9 based on RC1

>
>
> > On Apr 9, 2019, at 9:16 PM, Gary Gregory <[hidden email]> wrote:
> >
> > I also see that we are using an old version of jacoco and surefire, that
> > probably matters…
>
> Maven surefire is 3.0.0-M3. Are we willing to consume a non-release
> version of the plugin? I ask this because I regard "<version_number>-Mx”,
> where x is a positive integer, to indicate a milestone release prior to a
> fully fledged major release.
>

I am personally OK using a surefire M release in this [lang] release since:

- it still provides reproducible build
- we are playing nice in the Maven ecosystem if report issues when we find
them
- we are not releasing with a snapshot reference (see point 1)

Re: [VOTE] Release Apache Commons Lang 3.9 based on RC1

> On Apr 10, 2019, at 12:25 PM, Gary Gregory <[hidden email]> wrote:
>
> On Wed, Apr 10, 2019 at 12:13 PM Rob Tompkins <[hidden email] <mailto:[hidden email]>> wrote:
>
>>
>>
>>> On Apr 9, 2019, at 9:16 PM, Gary Gregory <[hidden email] <mailto:[hidden email]>> wrote:
>>>
>>> I also see that we are using an old version of jacoco and surefire, that
>>> probably matters…
>>
>> Maven surefire is 3.0.0-M3. Are we willing to consume a non-release
>> version of the plugin? I ask this because I regard "<version_number>-Mx”,
>> where x is a positive integer, to indicate a milestone release prior to a
>> fully fledged major release.
>>
>
> I am personally OK using a surefire M release in this [lang] release since:
>
> - it still provides reproducible build
> - we are playing nice in the Maven ecosystem if report issues when we find
> them
> - we are not releasing with a snapshot reference (see point 1)