With the following votes:
Gary Gregory: +1
Oliver Heger: +1
Rob Tompkins: +1
and no -1’s this [VOTE] passes.
I’ll promote the RC now.
-Rob
> On Jun 28, 2018, at 9:21 AM, Rob Tompkins wrote:
>
> We have fixed quite a few bugs and added some significant enhancements since
> Apache Commons
Here’s my +1.
> On Jun 28, 2018, at 9:21 AM, Rob Tompkins wrote:
>
> We have fixed quite a few bugs and added some significant enhancements since
> Apache Commons Parent 46 was released, so I would like to release Apache
> Commons Parent 47.
>
> Apache Commons Parent 47 RC1 is available for
+1
Commons Configuration could be built successfully with CP 47.
Oliver
Am 28.06.2018 um 15:21 schrieb Rob Tompkins:
> We have fixed quite a few bugs and added some significant enhancements since
> Apache Commons Parent 46 was released, so I would like to release Apache
> Commons Parent 47.
>
+1
>From src zip: ASC, SHA1, SHA256 OK
Apache RAT check OK.
Nothing to Clirr (but Clirr check still OK)
Building 'mvn clean site' and 'mvn clean install' OK with:
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
2018-06-17T12:33:14-06:00)
Maven home:
> On Jul 2, 2018, at 4:47 AM, sebb wrote:
>
> One reason why we can use lazy votes for parent is that we have full
> control over when POMs are updated to use a particular version.
>
> If a version turns out to have problems, the poms can just be reverted
> to the previous good version.
>
>
Hi Benedikt,
*JDK 11 is now in Rampdown Phase one***
The overall feature set is frozen. No further JEPs will be targeted to
this release.We’ve forked the main-line source repository, jdk/jdk, to
the jdk/jdk11 stabilization repository. Any changes pushed to jdk/jdk or
jdk/client are now bound
One reason why we can use lazy votes for parent is that we have full
control over when POMs are updated to use a particular version.
If a version turns out to have problems, the poms can just be reverted
to the previous good version.
So long as there are no obvious issues with the revision, it
