Yes, this vote is cancelled. I’d like to see if we can update the parent pom
first so that we get the correct build timestamp. Otherwise, I’ve updated the
other parts in master which will go into RC2.
—
Matt Sicker
> On Jan 24, 2022, at 06:50, Gary Gregory wrote:
>
> Hi Matt,
>
> I am not c
Hi Matt,
I am not clear if you plan on rolling another release candidate to address
the copyright year issue in Javadoc. Can you make it clear so we can cancel
this VOTE, or not?
TY,
Gary
On Sat, Jan 22, 2022, 17:42 Matt Sicker wrote:
> Alright, digging through the parent parent parent pom, it
I’m in with the partent pom right now….can work on getting that sorted…plus I
need to to get our release plugin working with the latest version of maven.
-Rob
> On Jan 22, 2022, at 5:42 PM, Matt Sicker wrote:
>
> Alright, digging through the parent parent parent pom, it looks like the
> Apach
Alright, digging through the parent parent parent pom, it looks like the Apache
parent pom has a release date from 2020 which is what ended up getting used by
the javadocs. This was fixed in that parent pom version 24, so we could
probably use an updated version of the commons parent pom as well
The copyright year is derived from POM properties or can be hard coded.
Trying to have a reproducible build can further muck things up where you
end up with 1969 as then end year as I recently fixed in Log4j. AFK but
there is a property called output build timestamp or something like that
that I se
Looks like some of the non-blockers are things I didn’t notice before (like the
user’s guide). I suppose I assumed that the site build automatically added
links to the new release, though that only seems to be for the download page. I
can update this in git (though it might require a second rele
Thank you for cutting the RC! :-)
Maybe blocker:
The Javadoc end copyright year is 2020 instead of 2022.
Not blockers:
The git tag name does not match the instructions below so the git clone
command fails (upper case instructions, lower case in actuality).
New Blake3 class has a FindBugs style
We have fixed quite a few bugs and added some significant enhancements since
Apache Commons Codec 1.15 was released, so I would like to release Apache
Commons Codec 1.16.
Apache Commons Codec 1.16 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/codec/1.16-RC1
