Re: [VOTE] Release Apache Log4net 2.0.16

[Davyd McColl]

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: [VOTE] Release Apache Log4net 2.0.16

[Gary Gregory]

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

[Piotr P. Karwasz]

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

[Davyd McColl]

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

[Gary Gregory]

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

[Davyd McColl]

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

[Davyd McColl]

Thanks for trying, Gary. I need to update the docs, I think, because I 
dropped client profile framework targets with the last release (iirc) 
because of that exact problem - can't install like that any more. You 
really just need the latest dotnet ask (8) and .net from windows features 
(including the option for 3.5 which says it also brings in 2)


-d


On 07 March 2024 23:29:08 "Gary D. Gregory"  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

[Jan Friedrich]

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

[Gary D. Gregory]

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

[Robert Middleton]

+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

[Ralph Goers]

+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

[Jan Friedrich]

+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

[Volkan Yazıcı]

+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: Uploading release distribution for review (Was: [VOTE] Release Apache Log4net 2.0.16)

[Davyd McColl]

Hi Jan

I think you're right. It's been so long since I've used svn as a daily 
driver - even longer since I wrote a build system in c++ that hooked into 
svn and triggered workloads on commits at the server . Thanks for 
figuring it out.


-d


On 02 March 2024 18:50:14 Jan Friedrich  wrote:


Hi,

I think I got it uploaded (from my machine).

choco install svn
svn co https://dist.apache.org/repos/dist/dev/logging -N 
apache-dist-logging-dev

cd apache-dist-logging-dev
svn up log4net
svn delete .\log4net\binaries\*2.0.14.*
svn add .\log4net\binaries\*
svn add .\log4net\source\*
svn commit -m 'v2.0.16'
 
Take a look at
 
https://dist.apache.org/repos/dist/dev/logging/log4net/binaries/ 
https://dist.apache.org/repos/dist/dev/logging/log4net/source/ 

@Davyd: Maybe we missed the bold lines on Friday?
 
Regards.

Jan

Friday, March 1, 2024, 6:27:38 PM, you wrote:


Hi Volkan




Thanks for taking the time to explain (:



This is pretty-much what I did, as per step 16 
of https://github.com/apache/logging-log4net/blob/master/doc/RELEASING.md - 
unless there's a typo I've made somewhere or something like that. That's 
why I'm confused as to why I can't see the artifacts in the right place ):



No need to rush on this though - monday is fine: I very likely won't do 
anything about it until then anyway (:




-d



On 2024/03/01 18:21, Volkan Yazıcı wrote:
Davyd, assuming you have `svn` in the command line, following should > get 
the job done:

    # Checkout the `dev` distribution repository
    svn co https://dist.apache.org/repos/dist/dev/logging logging-dist-dev
    cd logging-dist-dev
    # Delete old distribution files
    svn rm log4net
    # Add the new distribution of the new release
    mkdir -p log4net/2.0.16
    cp /path/to/distribution/files log4net/2.0.16/
    svn add log4net
    # Commit changes
    svn commit -m 'Add `log4net` version `2.0.16` distribution files'
I presume you are using Windows. Getting `svn` in the Windows shell is > 
explained in this SO post. > 


Let me know if this does/doesn't help.
Good luck!
On Fri, Mar 1, 2024 at 5:02 PM Davyd McColl  wrote:
    Hi Volkan
    That was my whole point with the question on my release vote: I
    have put things in svn, bit I'm not seeing them at the url you've
    posted. I assume I've done something wrong, but I don't know what
    and need someone to help. I must admit my svn-fu is rubbish so
    perhaps I just messed up there. With the other svn repos, I use
    git svn bridge, but I don't want to do that here because that repo
    us huge and filled with binaries
    TL;DR Halp! 
    -d
    On 01 March 2024 15:46:24 Volkan Yazıcı  wrote:

    Davyd, I am afraid it cannot qualify an official vote if the [source]
    distribution artifacts are missing. This is the whole point of
    the ASF
    release ceremony. Binary artifacts, Website, GitHub, VCS, Nuget,
    etc. can
    be the most important mediums for you and/or the project, though
    they are
    irrelevant from an ASF point of view.



    Could you upload the source distribution to the `
    https://dist.apache.org/repos/dist/dev/logging /log4net`
    Subversion folder
    along with checksum and signature files, please?
    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: Uploading release distribution for review (Was: [VOTE] Release Apache Log4net 2.0.16)

[Jan Friedrich]

Hi,

I think I got it uploaded (from my machine).

choco install svn
svn co https://dist.apache.org/repos/dist/dev/logging -N apache-dist-logging-dev
cd apache-dist-logging-dev
svn up log4net
svn delete .\log4net\binaries\*2.0.14.*
svn add .\log4net\binaries\*
svn add .\log4net\source\*
svn commit -m 'v2.0.16'
 
Take a look at
 
https://dist.apache.org/repos/dist/dev/logging/log4net/binaries/ 
https://dist.apache.org/repos/dist/dev/logging/log4net/source/ 

@Davyd: Maybe we missed the bold lines on Friday?
 
Regards.

Jan

Friday, March 1, 2024, 6:27:38 PM, you wrote:

> Hi Volkan


> Thanks for taking the time to explain (:


> This is pretty-much what I did, as per step 16 of 
> https://github.com/apache/logging-log4net/blob/master/doc/RELEASING.md - 
> unless there's a typo I've made somewhere or something like that. That's why 
> I'm confused as to why I can't see the artifacts in the right place ):


> No need to rush on this though - monday is fine: I very likely won't do 
> anything about it until then anyway (:


> -d

> On 2024/03/01 18:21, Volkan Yazıcı wrote:
>> Davyd, assuming you have `svn` in the command line, following should > get 
>> the job done:
>>     # Checkout the `dev` distribution repository
>>     svn co https://dist.apache.org/repos/dist/dev/logging logging-dist-dev
>>     cd logging-dist-dev
>>     # Delete old distribution files
>>     svn rm log4net
>>     # Add the new distribution of the new release
>>     mkdir -p log4net/2.0.16
>>     cp /path/to/distribution/files log4net/2.0.16/
>>     svn add log4net
>>     # Commit changes
>>     svn commit -m 'Add `log4net` version `2.0.16` distribution files'
>> I presume you are using Windows. Getting `svn` in the Windows shell is > 
>> explained in this SO post. > 
>> 
>> Let me know if this does/doesn't help.
>> Good luck!
>> On Fri, Mar 1, 2024 at 5:02 PM Davyd McColl  wrote:
>>     Hi Volkan
>>     That was my whole point with the question on my release vote: I
>>     have put things in svn, bit I'm not seeing them at the url you've
>>     posted. I assume I've done something wrong, but I don't know what
>>     and need someone to help. I must admit my svn-fu is rubbish so
>>     perhaps I just messed up there. With the other svn repos, I use
>>     git svn bridge, but I don't want to do that here because that repo
>>     us huge and filled with binaries
>>     TL;DR Halp! 
>>     -d
>>     On 01 March 2024 15:46:24 Volkan Yazıcı  wrote:
>>>     Davyd, I am afraid it cannot qualify an official vote if the [source]
>>>     distribution artifacts are missing. This is the whole point of
>>>     the ASF
>>>     release ceremony. Binary artifacts, Website, GitHub, VCS, Nuget,
>>>     etc. can
>>>     be the most important mediums for you and/or the project, though
>>>     they are
>>>     irrelevant from an ASF point of view.

>>>     Could you upload the source distribution to the `
>>>     https://dist.apache.org/repos/dist/dev/logging /log4net`
>>>     Subversion folder
>>>     along with checksum and signature files, please?
>>>     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: Uploading release distribution for review (Was: [VOTE] Release Apache Log4net 2.0.16)

[Davyd McColl]

Hi Volkan


Thanks for taking the time to explain (:


This is pretty-much what I did, as per step 16 of 
https://github.com/apache/logging-log4net/blob/master/doc/RELEASING.md - 
unless there's a typo I've made somewhere or something like that. That's 
why I'm confused as to why I can't see the artifacts in the right place ):



No need to rush on this though - monday is fine: I very likely won't do 
anything about it until then anyway (:



-d

On 2024/03/01 18:21, Volkan Yazıcı wrote:
Davyd, assuming you have `svn` in the command line, following should 
get the job done:


# Checkout the `dev` distribution repository
svn co https://dist.apache.org/repos/dist/dev/logging logging-dist-dev
cd logging-dist-dev

# Delete old distribution files
svn rm log4net

# Add the new distribution of the new release
mkdir -p log4net/2.0.16
cp /path/to/distribution/files log4net/2.0.16/
svn add log4net

# Commit changes
svn commit -m 'Add `log4net` version `2.0.16` distribution files'


I presume you are using Windows. Getting `svn` in the Windows shell is 
explained in this SO post. 



Let me know if this does/doesn't help.

Good luck!

On Fri, Mar 1, 2024 at 5:02 PM Davyd McColl  wrote:

Hi Volkan

That was my whole point with the question on my release vote: I
have put things in svn, bit I'm not seeing them at the url you've
posted. I assume I've done something wrong, but I don't know what
and need someone to help. I must admit my svn-fu is rubbish so
perhaps I just messed up there. With the other svn repos, I use
git svn bridge, but I don't want to do that here because that repo
us huge and filled with binaries

TL;DR Halp! 

-d

On 01 March 2024 15:46:24 Volkan Yazıcı  wrote:


Davyd, I am afraid it cannot qualify an official vote if the [source]
distribution artifacts are missing. This is the whole point of
the ASF
release ceremony. Binary artifacts, Website, GitHub, VCS, Nuget,
etc. can
be the most important mediums for you and/or the project, though
they are
irrelevant from an ASF point of view.

Could you upload the source distribution to the `
https://dist.apache.org/repos/dist/dev/logging /log4net`
Subversion folder
along with checksum and signature files, please?

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

Uploading release distribution for review (Was: [VOTE] Release Apache Log4net 2.0.16)

[Volkan Yazıcı]

Davyd, assuming you have `svn` in the command line, following should get
the job done:

# Checkout the `dev` distribution repository
svn co https://dist.apache.org/repos/dist/dev/logging logging-dist-dev
cd logging-dist-dev

# Delete old distribution files
svn rm log4net

# Add the new distribution of the new release
mkdir -p log4net/2.0.16
cp /path/to/distribution/files log4net/2.0.16/
svn add log4net

# Commit changes
svn commit -m 'Add `log4net` version `2.0.16` distribution files'


I presume you are using Windows. Getting `svn` in the Windows shell is
explained in this SO post.


Let me know if this does/doesn't help.

Good luck!

On Fri, Mar 1, 2024 at 5:02 PM Davyd McColl  wrote:

> Hi Volkan
>
> That was my whole point with the question on my release vote: I have put
> things in svn, bit I'm not seeing them at the url you've posted. I assume
> I've done something wrong, but I don't know what and need someone to help.
> I must admit my svn-fu is rubbish so perhaps I just messed up there. With
> the other svn repos, I use git svn bridge, but I don't want to do that here
> because that repo us huge and filled with binaries
>
> TL;DR Halp!  
>
> -d
>
> On 01 March 2024 15:46:24 Volkan Yazıcı  wrote:
>
>> Davyd, I am afraid it cannot qualify an official vote if the [source]
>> distribution artifacts are missing. This is the whole point of the ASF
>> release ceremony. Binary artifacts, Website, GitHub, VCS, Nuget, etc. can
>> be the most important mediums for you and/or the project, though they are
>> irrelevant from an ASF point of view.
>>
>> Could you upload the source distribution to the `
>> https://dist.apache.org/repos/dist/dev/logging /log4net` Subversion
>> folder
>> along with checksum and signature files, please?
>>
>> 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

[Davyd McColl]

Hi Volkan

That was my whole point with the question on my release vote: I have put 
things in svn, bit I'm not seeing them at the url you've posted. I assume 
I've done something wrong, but I don't know what and need someone to help. 
I must admit my svn-fu is rubbish so perhaps I just messed up there. With 
the other svn repos, I use git svn bridge, but I don't want to do that here 
because that repo us huge and filled with binaries


TL;DR Halp!  

-d


On 01 March 2024 15:46:24 Volkan Yazıcı  wrote:


Davyd, I am afraid it cannot qualify an official vote if the [source]
distribution artifacts are missing. This is the whole point of the ASF
release ceremony. Binary artifacts, Website, GitHub, VCS, Nuget, etc. can
be the most important mediums for you and/or the project, though they are
irrelevant from an ASF point of view.

Could you upload the source distribution to the `
https://dist.apache.org/repos/dist/dev/logging /log4net` Subversion folder
along with checksum and signature files, please?

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

[Volkan Yazıcı]

Davyd, I am afraid it cannot qualify an official vote if the [source]
distribution artifacts are missing. This is the whole point of the ASF
release ceremony. Binary artifacts, Website, GitHub, VCS, Nuget, etc. can
be the most important mediums for you and/or the project, though they are
irrelevant from an ASF point of view.

Could you upload the source distribution to the `
https://dist.apache.org/repos/dist/dev/logging /log4net` Subversion folder
along with checksum and signature files, please?

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
>
>

[VOTE] Release Apache Log4net 2.0.16

[Davyd McColl]

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