+1 Verified the following: * apache-log4net-source-2.0.16.zip and associated sha/signature * apache-log4net-binaries-2.0.16.zip and associated sha/signature
It looks all good to me. -Robert Middleton On Tue, Mar 5, 2024 at 1:20 AM Ralph Goers <ralph.go...@dslextreme.com> wrote: > > +1 > > Verified signatures > Verified hashes > Verified License and Notice files. > > Note - the copyright year should be the first year the code was created. You > can update it to include “-(currentYear}” but that is not strictly necessary. > > Ralph > > > On Mar 4, 2024, at 10:48 AM, Jan Friedrich <freeand...@apache.org> wrote: > > > > +1 > > > > Unit tests on my machine were successful. > > We integrated the new version into our test environment and all manual > > tests were successful. > > > > Jan > > > >> +1 > > > >> Verified signatures. > >> Verified hashes. > > > >> `NOTICE` contains 2022 as the copyright year, but I don't find it a > >> blocker. (I have fixed it in `master`.) > > > >> On Fri, Mar 1, 2024 at 2:19 PM Davyd McColl <dav...@gmail.com> wrote: > > > >>> Hi all > >>> > >>> > >>> This is the vote to release Apache log4net version 2.0.16 > >>> > >>> > >>> Website: > >>> https://logging.staged.apache.org/log4net/release/release-notes.html > >>> > >>> GitHub: https://github.com/apache/logging-log4net > >>> > >>> GitHub release (pre-release): > >>> https://github.com/apache/logging-log4net/releases/tag/2.0.16-rc1 > >>> > >>> Distribution: I'm not sure - > >>> https://dist.apache.org/repos/dist/dev/logging/log4net should have > >>> 2.0.16 binaries and source (I've added via SVN), but I'm not seeing > >>> them. Any help appreciated. > >>> > >>> > >>> > >>> Please have a look at the staging site & artifacts and test (if you can > >>> - clone, `npm i`, `npm test`) > >>> > >>> [ ] +1, release the artifacts > >>> > >>> [ ] -1, don't release, because.... > >>> > >>> > >>> (thanks Piotr: I copied most of your last VOTE mail!) > >>> > >>> > >>> -d > >>> > >>> > > >
