Re: [VOTE] Release Apache Log4net 2.0.16
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 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 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 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
Re: [VOTE] Release Apache Log4net 2.0.16
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 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 > 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 > 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 > 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 >
Re: [VOTE] Release Apache Log4net 2.0.16
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 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 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 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 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
Re: [VOTE] Release Apache Log4net 2.0.16
Hi Davyd, On Fri, 8 Mar 2024 at 14:59, Davyd McColl wrote: > > 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. The vote passed with 4 binding +1 from Ralph, Robert, Volkan and yourself (I presume) and one non-binding +1 from Jan. Piotr
Re: [VOTE] Release Apache Log4net 2.0.16
You don't need memory, if you deleted the messages already from your email app, go to lists.apache.org Gary On Fri, Mar 8, 2024, 8:59 AM Davyd McColl wrote: > 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 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 > >> 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 > >> 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 >
Re: [VOTE] Release Apache Log4net 2.0.16
Hi Gary I receive on the order of a hundred or more emails every day. Searches fail me, at least in Thunderbird. I will rather just keep a record as they come in, but thanks for the suggestion. -d On 08 March 2024 17:09:13 Gary Gregory wrote: You don't need memory, if you deleted the messages already from your email app, go to lists.apache.org Gary On Fri, Mar 8, 2024, 8:59 AM Davyd McColl wrote: 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 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 >> 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 >> 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
Re: Please update Flume DOAP
Thank you Sebb, I just fixed it https://github.com/apache/logging-flume/commit/692039032ce681c3a847847365f0065608eae4e2 On Thu, Mar 7, 2024, at 12:42, sebb wrote: > https://github.com/apache/logging-flume/blob/trunk/doap_Flume.rdf > still shows the PMC as Flume; please update to show PMC Logging. > > Thanks, > Sebb
Re: [RESULT][VOTE] Move Chainsaw to dormant
I have moved Chainsaw to the dormant section on the main website: https://logging.apache.org/ There is a label missing on the CS website itself, but I will have similar work in future, so I am going to do it together with that On Fri, Feb 16, 2024, at 09:56, Christian Grobmeier wrote: > The vote succeeded with 7 +1. > Thanks to everybody who voted. > I will do the necessary steps early next week. > > Kind regards > Christian > > -- > The Apache Software Foundation > V.P., Data Privacy > > - Original message - > From: Christian Grobmeier > To: dev@logging.apache.org > Subject: [VOTE] Move Chainsaw to dormant > Date: Monday, February 12, 2024 22:31 > > Hello, > > This vote is to put Chainsaw to the "Dormant" components. There is much > work to be done on this component, but not enough hours can be > committed to do that work. To reflect this situation to the user, it is > better to move Chainsaw to the dormant section and communicate it as > "no longer maintained." The component can be moved back to the > "active" state whenever people are actively working on it. The main > branch in the repository will be marked with the new state, but the > repository will not be archived for now. > > Please note: > > [ ] +1, move to dormant > [ ] -1, don't because... > > I will leave this vote open for the usual 72 hours. > > Thank you! > > Kind regards, > Christian
