Yes it has. The current issue is that if a component does not use the
latest Apache RAT plugins, then it must do so in its POM. This could be
handled automatically if we released a new commons-parent.
Gary
On Tue, Jun 14, 2022, 15:42 Matt Sicker wrote:
> The issue with the previous RC required
The issue with the previous RC required an updated version of the Commons
release plugin. I don’t remember if that’s been done yet.
—
Matt Sicker
> On Jun 14, 2022, at 05:12, Alex Herbert wrote:
>
> On Mon, 13 Jun 2022 at 17:46, Matt Sicker wrote:
>
>> I haven’t had a chance to try a second
On Mon, 13 Jun 2022 at 17:46, Matt Sicker wrote:
> I haven’t had a chance to try a second RC. I’ve been out sick the past few
> days as well. If you’d like to help make the release, let me know!
>
I asked the question as a contributor asked after their PR bug fix was
merged. IIRC the previous vo
I haven’t had a chance to try a second RC. I’ve been out sick the past few days
as well. If you’d like to help make the release, let me know!
—
Matt Sicker
> On Jun 13, 2022, at 11:15, Alex Herbert wrote:
>
> A RC1 cut was made for codec 1.16 in January 2022:
>
>> git tag -l --format='%(refn
A RC1 cut was made for codec 1.16 in January 2022:
> git tag -l --format='%(refname) %(taggerdate) %(tagger)'
commons-codec-1.16-rc1
refs/tags/commons-codec-1.16-rc1 Fri Jan 21 23:03:07 2022 -0600 Matt
Sicker 1642827787 -0600
However this was eventually cancelled. IIRC it was due to
includ
