Hi Gary

I'll try to remember that for the future. From memory now, there was only one person who had any holdups and that was due to outdated build docs from me - so it should be resolved. There were no -1's, and at least 4 +1's that I saw. I'll try to keep better tally next time.


-d

On 2024/03/08 14:22, Gary Gregory wrote:
Process:

You need to reply to this thread with a [RESULT] prefix, tally all the
votes, and say whether the vote passes or not. It is helpful to note which
votes are binding or not.

Gary

On Fri, Mar 8, 2024, 6:06 AM Davyd McColl <dav...@gmail.com> wrote:

Hi all


Thanks for all the checking - log4net 2.0.16 is out in the wild now (:


-d

On 2024/03/08 00:02, Jan Friedrich wrote:
Hello Gary,

the errors are in the examples project for .net compact framework (which
is no longer supported by microsoft):

C:\Users\ggregory\rc\apache-log4net-source-2.0.16\examples\netcf\1.0\Tutorials\ConsoleApp\cs\src\ConsoleApp.csdproj(23,1):
error MSB4075:
The project file
"C:\Users\ggregory\rc\apache-log4net-source-2.0.16\examples\netcf\1.0\Tutorials\ConsoleApp\cs\src\ConsoleApp.csdproj"
must be opened in the Visual Studio IDE and converted to the latest version
before it can be built by MSBuild.
-> This project file can only be opened by VS 2003.

In the next release we will drop support for those exotic frameworks and
delete the corresponding examples.
I've already updated all the examples in my feature branch for this.

Regards.

Jan

Thursday, March 7, 2024, 10:28:40 PM, you wrote:

I've failed to build probably because the machine I am doing this on is
DNS locked down for security and can only access certain sites.
I was able to install install-dotnet-core-sdk-1.1.ps1 but not
install-net-framework-sdk-3.5.ps1 (Error 0x800F0954 in a dialog that points
to
https://learn.microsoft.com/en-US/troubleshoot/windows-client/application-management/dotnet-framework-35-installation-error)
but I also don't know if how if this machine has enough already on top of
Microsoft Windows [Version 10.0.19045.4046]
My results: https://paste.apache.org/jj3c8
I rebooted and tried again with the same results.
Gary
On 2024/03/07 03:11:22 Robert Middleton wrote:
+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

Reply via email to