I have 20 mins before a quick dinner and meeting. Cloning the repository
now.
On Mon, 10 Oct 2022 at 19:38, Alex Herbert wrote:
> Can I get another PMC vote for this please?
>
> Thanks,
>
> Alex
>
> On Wed, 5 Oct 2022 at 11:25, Alex Herbert wrote:
>
> > We have fixed quite a few bugs and added
My +1
Alex
On Wed, 5 Oct 2022 at 11:25, Alex Herbert wrote:
> We have fixed quite a few bugs and added some significant enhancements
> since Apache Commons RNG 1.4 was released, so I would like to release
> Apache Commons RNG 1.5.
>
> Apache Commons RNG 1.5 RC1 is available for review here:
>
Can I get another PMC vote for this please?
Thanks,
Alex
On Wed, 5 Oct 2022 at 11:25, Alex Herbert wrote:
> We have fixed quite a few bugs and added some significant enhancements
> since Apache Commons RNG 1.4 was released, so I would like to release
> Apache Commons RNG 1.5.
>
> Apache Common
Le sam. 8 oct. 2022 à 17:06, sebb a écrit :
>
> Some recent changes files include details of updates to GitHub actions
> in workflows.
>
> I don't think these details belong in the changes file.
> They are not relevant to the release.
>
> Indeed the workflows that contain the updates are not inclu
Le 08/10/2022 à 17:56, sebb a écrit :
I don't think we should be cluttering the changes file with irrelevant
and potentially confusing information.
+1, changes.xml should be for user visible changes only (API changes,
bug fixes, updated language level, etc).
Emmanuel Bourg
Thanks Bruno,
Good finds! I will fix those issues post release.
Gary
On Sat, Oct 8, 2022, 23:55 Bruno Kinoshita wrote:
> [x] +1 Release these artifacts (assuming the changes.xml date can be
> fixed later)
>
> Build passed with no issues, running `mvn clean test install site` on
>
> Apache
