You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Alex Herbert <al...@gmail.com> on 2022/06/13 16:14:36 UTC
[codec] 1.16 release progress
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 <ma...@apache.org> 1642827787 -0600
However this was eventually cancelled. IIRC it was due to
included files/datestamps brought in by a parent POM. Is there any update
on progress with this?
Alex
Re: [codec] 1.16 release progress
Posted by Gary Gregory <ga...@gmail.com>.
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 <bo...@gmail.com> wrote:
> 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 <al...@gmail.com>
> wrote:
> >
> > On Mon, 13 Jun 2022 at 17:46, Matt Sicker <bo...@gmail.com> 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 vote was cancelled due to datestamps inherited
> > from the parent and updates required to the site. Have the issues with
> the
> > previous RC been resolved?
> >
> > Unfortunately I cannot RM in the next few weeks due to other commitments.
> >
> > Alex
>
Re: [codec] 1.16 release progress
Posted by Matt Sicker <bo...@gmail.com>.
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 <al...@gmail.com> wrote:
>
> On Mon, 13 Jun 2022 at 17:46, Matt Sicker <bo...@gmail.com> 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 vote was cancelled due to datestamps inherited
> from the parent and updates required to the site. Have the issues with the
> previous RC been resolved?
>
> Unfortunately I cannot RM in the next few weeks due to other commitments.
>
> Alex
Re: [codec] 1.16 release progress
Posted by Alex Herbert <al...@gmail.com>.
On Mon, 13 Jun 2022 at 17:46, Matt Sicker <bo...@gmail.com> 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 vote was cancelled due to datestamps inherited
from the parent and updates required to the site. Have the issues with the
previous RC been resolved?
Unfortunately I cannot RM in the next few weeks due to other commitments.
Alex
Re: [codec] 1.16 release progress
Posted by Matt Sicker <bo...@gmail.com>.
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 <al...@gmail.com> wrote:
>
> 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 <ma...@apache.org> 1642827787 -0600
>
> However this was eventually cancelled. IIRC it was due to
> included files/datestamps brought in by a parent POM. Is there any update
> on progress with this?
>
> Alex