You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@logging.apache.org by Jan Friedrich <fr...@apache.org> on 2025/08/19 21:16:10 UTC
[VOTE] Release Apache Log4net 3.2.0
This is a vote to release the Apache Log4net 3.2.0.
Website: https://logging.staged.apache.org/log4net/release-notes.html
GitHub: https://github.com/apache/logging-log4net
Commit: 0225493d8ac2243a8b0828be4b82e54d199b979a
Distribution: https://dist.apache.org/repos/dist/dev/logging/log4net/3.2.0
Signing key: 0x7D24496A230E29D6349A99EF583E491578F02D5D
Review kit: https://logging.staged.apache.org/log4net/release-review.html
Please download, test, and cast your votes on this mailing list.
[ ] +1, release the artifacts
[ ] -1, don't release, because ...
This vote is open for 72 hours and will pass unless getting a net
negative vote count.
All votes are welcome and we encourage everyone to test the release, but
only the Logging Services PMC votes are officially counted.
[RESULT][VOTE] Release Apache Log4net 3.2.0
Posted by Jan Friedrich <fr...@apache.org>.
and here is my +1.
With that the vote passed with 3 +1 votes from Davyd McColl, Stephen
Webb and myself.
I will continue the release process.
Jan
On 8/19/25 23:16, Jan Friedrich wrote:
> This is a vote to release the Apache Log4net 3.2.0.
>
> Website: https://logging.staged.apache.org/log4net/release-notes.html
> GitHub: https://github.com/apache/logging-log4net
> Commit: 0225493d8ac2243a8b0828be4b82e54d199b979a
> Distribution: https://dist.apache.org/repos/dist/dev/logging/log4net/3.2.0
> Signing key: 0x7D24496A230E29D6349A99EF583E491578F02D5D
> Review kit: https://logging.staged.apache.org/log4net/release-review.html
>
> Please download, test, and cast your votes on this mailing list.
>
> [ ] +1, release the artifacts
> [ ] -1, don't release, because ...
>
> This vote is open for 72 hours and will pass unless getting a net
> negative vote count.
> All votes are welcome and we encourage everyone to test the release, but
> only the Logging Services PMC votes are officially counted.
Re: [VOTE] Release Apache Log4net 3.2.0
Posted by Stephen Webb <sw...@gmail.com>.
+1
On Windows 11, the verify-release passed all tests
Regards,
Stephen Webb
On Wed, Aug 20, 2025 at 7:16 AM Jan Friedrich <fr...@apache.org> wrote:
> This is a vote to release the Apache Log4net 3.2.0.
>
> Website: https://logging.staged.apache.org/log4net/release-notes.html
> GitHub: https://github.com/apache/logging-log4net
> Commit: 0225493d8ac2243a8b0828be4b82e54d199b979a
> Distribution: https://dist.apache.org/repos/dist/dev/logging/log4net/3.2.0
> Signing key: 0x7D24496A230E29D6349A99EF583E491578F02D5D
> Review kit: https://logging.staged.apache.org/log4net/release-review.html
>
> Please download, test, and cast your votes on this mailing list.
>
> [ ] +1, release the artifacts
> [ ] -1, don't release, because ...
>
> This vote is open for 72 hours and will pass unless getting a net
> negative vote count.
> All votes are welcome and we encourage everyone to test the release, but
> only the Logging Services PMC votes are officially counted.
>
Re: [VOTE] Release Apache Log4net 3.2.0
Posted by Davyd McColl <da...@gmail.com>.
Hi
- signatures verified
- tests run
only issue is that the instructions at
https://logging.staged.apache.org/log4net/release-review.html suggest
running tests on the source from a `src` folder within the subversion
checkout. I have the folder, with no contents, and I don't see a src
folder up at
https://dist.apache.org/repos/dist/dev/logging/log4net/3.2.0/ so either
it's not there or I'm doing something very wrong. I ran tests via git
checkout of tag rc/3.2.0-rc1.
-d
On 2025/08/19 23:16, Jan Friedrich wrote:
> This is a vote to release the Apache Log4net 3.2.0.
>
> Website: https://logging.staged.apache.org/log4net/release-notes.html
> GitHub: https://github.com/apache/logging-log4net
> Commit: 0225493d8ac2243a8b0828be4b82e54d199b979a
> Distribution:
> https://dist.apache.org/repos/dist/dev/logging/log4net/3.2.0
> Signing key: 0x7D24496A230E29D6349A99EF583E491578F02D5D
> Review kit: https://logging.staged.apache.org/log4net/release-review.html
>
> Please download, test, and cast your votes on this mailing list.
>
> [ ] +1, release the artifacts
> [ ] -1, don't release, because ...
>
> This vote is open for 72 hours and will pass unless getting a net
> negative vote count.
> All votes are welcome and we encourage everyone to test the release,
> but only the Logging Services PMC votes are officially counted.
Re: [VERIFYING] Release Apache Log4net 3.2.0
Posted by Gary Gregory <ga...@gmail.com>.
On Wed, Aug 20, 2025 at 3:52 PM Jan Friedrich <fr...@apache.org> wrote:
>
> Hi Gary,
>
> Thanks for digging into this! Could you point out where the $ symbols
> are missing in the release kit page? That’ll help us fix it quickly.
I edited the page in GH with the edit button.
It sounds like I am wrong in assuming that the release manager for a
release candidate uses these instructions. I am hoping that whatever
validation the RM performs _is the release kit_. This would
bulletproof the process IMO.
TY!
Gary
>
> Regarding the verify-release.ps1 script, the easiest way to get around
> the execution policy is to run PowerShell as an *administrator* and use:
>
> Set-ExecutionPolicy -ExecutionPolicy RemoteSigned
>
> (I will ad this to the prerequisites)
>
> From here on you no longer need to run as administrator.
>
> After that you maybe need to trust the verify script via (depending on
> how you retrieved the release files):
>
> Unblock-File ./verify-release.ps1
>
> Then you should be able to run ./verify-release.ps1 without the security
> error.
>
> Regards.
>
> Jan
>
> On 8/20/25 20:27, Gary D. Gregory wrote:
> > I gave up after attempting to fix typos in the release kit page, missing $s, did anyone test this?
> >
> > PS C:\tmp\log4net-\3.2.0> & ./verify-release.ps1
> > & : File C:\tmp\log4net-\3.2.0\verify-release.ps1 cannot be loaded because running scripts is disabled on this system. For more information, see
> > about_Execution_Policies at https:/go.microsoft.com/fwlink/?LinkID=135170.
> > At line:1 char:3
> > + & ./verify-release.ps1
> > + ~~~~~~~~~~~~~~~~~~~~
> > + CategoryInfo : SecurityError: (:) [], PSSecurityException
> > + FullyQualifiedErrorId : UnauthorizedAccess
> >
> > Any ideas?
> >
> > Gary
> >
> >
> > On 2025/08/19 21:16:10 Jan Friedrich wrote:
> >> This is a vote to release the Apache Log4net 3.2.0.
> >>
> >> Website: https://logging.staged.apache.org/log4net/release-notes.html
> >> GitHub: https://github.com/apache/logging-log4net
> >> Commit: 0225493d8ac2243a8b0828be4b82e54d199b979a
> >> Distribution: https://dist.apache.org/repos/dist/dev/logging/log4net/3.2.0
> >> Signing key: 0x7D24496A230E29D6349A99EF583E491578F02D5D
> >> Review kit: https://logging.staged.apache.org/log4net/release-review.html
> >>
> >> Please download, test, and cast your votes on this mailing list.
> >>
> >> [ ] +1, release the artifacts
> >> [ ] -1, don't release, because ...
> >>
> >> This vote is open for 72 hours and will pass unless getting a net
> >> negative vote count.
> >> All votes are welcome and we encourage everyone to test the release, but
> >> only the Logging Services PMC votes are officially counted.
> >>
>
Re: [VERIFYING] Release Apache Log4net 3.2.0
Posted by Jan Friedrich <fr...@apache.org>.
Hi Gary,
Thanks for digging into this! Could you point out where the $ symbols
are missing in the release kit page? That’ll help us fix it quickly.
Regarding the verify-release.ps1 script, the easiest way to get around
the execution policy is to run PowerShell as an *administrator* and use:
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned
(I will ad this to the prerequisites)
From here on you no longer need to run as administrator.
After that you maybe need to trust the verify script via (depending on
how you retrieved the release files):
Unblock-File ./verify-release.ps1
Then you should be able to run ./verify-release.ps1 without the security
error.
Regards.
Jan
On 8/20/25 20:27, Gary D. Gregory wrote:
> I gave up after attempting to fix typos in the release kit page, missing $s, did anyone test this?
>
> PS C:\tmp\log4net-\3.2.0> & ./verify-release.ps1
> & : File C:\tmp\log4net-\3.2.0\verify-release.ps1 cannot be loaded because running scripts is disabled on this system. For more information, see
> about_Execution_Policies at https:/go.microsoft.com/fwlink/?LinkID=135170.
> At line:1 char:3
> + & ./verify-release.ps1
> + ~~~~~~~~~~~~~~~~~~~~
> + CategoryInfo : SecurityError: (:) [], PSSecurityException
> + FullyQualifiedErrorId : UnauthorizedAccess
>
> Any ideas?
>
> Gary
>
>
> On 2025/08/19 21:16:10 Jan Friedrich wrote:
>> This is a vote to release the Apache Log4net 3.2.0.
>>
>> Website: https://logging.staged.apache.org/log4net/release-notes.html
>> GitHub: https://github.com/apache/logging-log4net
>> Commit: 0225493d8ac2243a8b0828be4b82e54d199b979a
>> Distribution: https://dist.apache.org/repos/dist/dev/logging/log4net/3.2.0
>> Signing key: 0x7D24496A230E29D6349A99EF583E491578F02D5D
>> Review kit: https://logging.staged.apache.org/log4net/release-review.html
>>
>> Please download, test, and cast your votes on this mailing list.
>>
>> [ ] +1, release the artifacts
>> [ ] -1, don't release, because ...
>>
>> This vote is open for 72 hours and will pass unless getting a net
>> negative vote count.
>> All votes are welcome and we encourage everyone to test the release, but
>> only the Logging Services PMC votes are officially counted.
>>
Re: [VOTE] Release Apache Log4net 3.2.0
Posted by "Gary D. Gregory" <gg...@apache.org>.
I gave up after attempting to fix typos in the release kit page, missing $s, did anyone test this?
PS C:\tmp\log4net-\3.2.0> & ./verify-release.ps1
& : File C:\tmp\log4net-\3.2.0\verify-release.ps1 cannot be loaded because running scripts is disabled on this system. For more information, see
about_Execution_Policies at https:/go.microsoft.com/fwlink/?LinkID=135170.
At line:1 char:3
+ & ./verify-release.ps1
+ ~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : SecurityError: (:) [], PSSecurityException
+ FullyQualifiedErrorId : UnauthorizedAccess
Any ideas?
Gary
On 2025/08/19 21:16:10 Jan Friedrich wrote:
> This is a vote to release the Apache Log4net 3.2.0.
>
> Website: https://logging.staged.apache.org/log4net/release-notes.html
> GitHub: https://github.com/apache/logging-log4net
> Commit: 0225493d8ac2243a8b0828be4b82e54d199b979a
> Distribution: https://dist.apache.org/repos/dist/dev/logging/log4net/3.2.0
> Signing key: 0x7D24496A230E29D6349A99EF583E491578F02D5D
> Review kit: https://logging.staged.apache.org/log4net/release-review.html
>
> Please download, test, and cast your votes on this mailing list.
>
> [ ] +1, release the artifacts
> [ ] -1, don't release, because ...
>
> This vote is open for 72 hours and will pass unless getting a net
> negative vote count.
> All votes are welcome and we encourage everyone to test the release, but
> only the Logging Services PMC votes are officially counted.
>