[log4net] Next release

[Volkan Yazıcı]

Davyd, can Jan help you with the release? Since he is not a PMC member,
there are certain steps he can't take. Though judging from the RELEASING.md
,
maybe he can bring it to a point within the limits of access rights granted
to him, and then you can intervene (e.g., signing artifacts, uploading to
SVN) whenever needed.

If you say this will make things more difficult, that is also
understandable.

On Thu, Feb 29, 2024 at 11:01 AM Davyd McColl 
wrote:

> Considering my constrained time, and even though @FreeAndNil
>  recently stepped up to be a maintainer, I
> don't see any time really soon. You can, in the meantime, check out the
> repo, build, and distribute a dll with your app if it's that important.
> It's not convenient, I'll admit, but if it's urgent, it's an option.
>
> —
> Reply to this email directly, view it on GitHub
> ,
> or unsubscribe
> 
> .
> You are receiving this because you commented.Message ID:
> 
>

Re: [log4net] Next release

[Davyd McColl]

Hi Volkan


If Jan feels up to the task, it would be worthwhile to give it a go. If 
nothing else, it's a bit of a "trial by fire"


of following the RELEASING.md steps to get to a release. I'm sure there 
are bits I've missed because they


seemed obvious to me or I just missed them - having a second set of eyes 
on it, going through it, has benefits


in itself. As for the actual release, I believe Jan is more than 
capable, but I understand he may be blocked


somewhere, so if I can help, I will (: It would also be a good trial run 
to find out what, if anything, is still


required to be set up for Jan (eg svn access for the docs, etc)


Jan, Volkan brings up one of the sticky points - signing the release - 
which I can do from my personal


machine, with the binary artifacts in place - so I could do steps 3 and 
4 (build and sign) - but I'll only


really have time on Friday afternoon, so I'll check it out then. In the 
mean-time, if you'd like to see


how far you can get with the RELEASING.md instructions, I'd _really_ 
appreciate it. I haven't done


a log4net release in ages because it takes a reasonable amount of time 
and motivation - substances


I'm in short supply of (when I have the motivation, I don't have the 
time, and when I have the time,


it's after a long day, and I don't have the motivation any more ): )


-d


On 2024/02/29 13:02, Volkan Yazıcı wrote:

Davyd, can Jan help you with the release? Since he is not a PMC member,
there are certain steps he can't take. Though judging from the RELEASING.md
,
maybe he can bring it to a point within the limits of access rights granted
to him, and then you can intervene (e.g., signing artifacts, uploading to
SVN) whenever needed.

If you say this will make things more difficult, that is also
understandable.

On Thu, Feb 29, 2024 at 11:01 AM Davyd McColl 
wrote:


Considering my constrained time, and even though @FreeAndNil
 recently stepped up to be a maintainer, I
don't see any time really soon. You can, in the meantime, check out the
repo, build, and distribute a dll with your app if it's that important.
It's not convenient, I'll admit, but if it's urgent, it's an option.

—
Reply to this email directly, view it on GitHub
,
or unsubscribe

.
You are receiving this because you commented.Message ID:

Re: [log4net] Next release

[Piotr P. Karwasz]

Hi Davyd,

On Thu, 29 Feb 2024 at 12:29, Davyd McColl  wrote:
> Jan, Volkan brings up one of the sticky points - signing the release -
> which I can do from my personal
>
> machine, with the binary artifacts in place - so I could do steps 3 and
> 4 (build and sign) - but I'll only

This is just a curiosity (don't feel pressured to answer). Are .NET
artifacts reproducible? If it is so, could we build it and sign it in
Github actions and you could just verify that the SHAs are identical
to those locally built?

Piotr

Re: [log4net] Next release

[Davyd McColl]

Hi Piotr

I actually don't know with 100% accuracy, but I did find this: 
https://www.mitchelsellers.com/blog/article/net-5-deterministic-builds-source-linking 
which is a little old but might be worthwhile investigating.


-d


On 29 February 2024 13:54:47 "Piotr P. Karwasz"  
wrote:



Hi Davyd,

On Thu, 29 Feb 2024 at 12:29, Davyd McColl  wrote:

Jan, Volkan brings up one of the sticky points - signing the release -
which I can do from my personal

machine, with the binary artifacts in place - so I could do steps 3 and
4 (build and sign) - but I'll only


This is just a curiosity (don't feel pressured to answer). Are .NET
artifacts reproducible? If it is so, could we build it and sign it in
Github actions and you could just verify that the SHAs are identical
to those locally built?

Piotr

Re: [log4net] Next release

[Jan Friedrich]

Hi,

as far as i know, setting true in csproj should 
be enough for this.
See line 73 in 
https://github.com/apache/logging-log4net/pull/115/files#diff-0f81264aa7e82fb31702de904a86565584da1349835af0d3b08b69d09502a384

Regards.

Jan

Thursday, February 29, 2024, 1:12:24 PM, you wrote:

> Hi Piotr

> I actually don't know with 100% accuracy, but I did find this: 
> https://www.mitchelsellers.com/blog/article/net-5-deterministic-builds-source-linking
>  which is a little old but might be worthwhile investigating.

> -d


> On 29 February 2024 13:54:47 "Piotr P. Karwasz"  
> wrote:

>> Hi Davyd,
>>
>> On Thu, 29 Feb 2024 at 12:29, Davyd McColl  wrote:
>>> Jan, Volkan brings up one of the sticky points - signing the release -
>>> which I can do from my personal
>>>
>>> machine, with the binary artifacts in place - so I could do steps 3 and
>>> 4 (build and sign) - but I'll only
>>
>> This is just a curiosity (don't feel pressured to answer). Are .NET
>> artifacts reproducible? If it is so, could we build it and sign it in
>> Github actions and you could just verify that the SHAs are identical
>> to those locally built?
>>
>> Piotr

Re: [log4net] Next release

[Jan Friedrich]

Hi,

thanks for the opportunity, I will try my best.

https://github.com/apache/logging-log4net/pull/115

Regards.

Jan

Thursday, February 29, 2024, 12:26:55 PM, you wrote:

> Hi Volkan


> If Jan feels up to the task, it would be worthwhile to give it a go. If 
> nothing else, it's a bit of a "trial by fire"

> of following the RELEASING.md steps to get to a release. I'm sure there are 
> bits I've missed because they

> seemed obvious to me or I just missed them - having a second set of eyes on 
> it, going through it, has benefits

> in itself. As for the actual release, I believe Jan is more than capable, but 
> I understand he may be blocked

> somewhere, so if I can help, I will (: It would also be a good trial run to 
> find out what, if anything, is still

> required to be set up for Jan (eg svn access for the docs, etc)


> Jan, Volkan brings up one of the sticky points - signing the release - which 
> I can do from my personal

> machine, with the binary artifacts in place - so I could do steps 3 and 4 
> (build and sign) - but I'll only

> really have time on Friday afternoon, so I'll check it out then. In the 
> mean-time, if you'd like to see

> how far you can get with the RELEASING.md instructions, I'd _really_ 
> appreciate it. I haven't done

> a log4net release in ages because it takes a reasonable amount of time and 
> motivation - substances

> I'm in short supply of (when I have the motivation, I don't have the time, 
> and when I have the time,

> it's after a long day, and I don't have the motivation any more ): )


> -d


> On 2024/02/29 13:02, Volkan Yazıcı wrote:
>> Davyd, can Jan help you with the release? Since he is not a PMC member,
>> there are certain steps he can't take. Though judging from the RELEASING.md
>> ,
>> maybe he can bring it to a point within the limits of access rights granted
>> to him, and then you can intervene (e.g., signing artifacts, uploading to
>> SVN) whenever needed.
>>
>> If you say this will make things more difficult, that is also
>> understandable.
>>
>> On Thu, Feb 29, 2024 at 11:01 AM Davyd McColl 
>> wrote:
>>
>>> Considering my constrained time, and even though @FreeAndNil
>>>  recently stepped up to be a maintainer, I
>>> don't see any time really soon. You can, in the meantime, check out the
>>> repo, build, and distribute a dll with your app if it's that important.
>>> It's not convenient, I'll admit, but if it's urgent, it's an option.
>>>
>>> —
>>> Reply to this email directly, view it on GitHub
>>> ,
>>> or unsubscribe
>>> 
>>> .
>>> You are receiving this because you commented.Message ID:
>>> 
>>>

Re: [log4net] Next release

[Volkan Yazıcı]

I think we have a deal! 🤩

Jan, if you prefer, you can also sync. with Davyd on Friday afternoon over the
ASF Slack . We have a `#logging` public channel
there, but you can also DM each other, whatever suits you best. I think
quickly iterating over release procedure steps over chat could save both of
you from long waiting times.

I am looking forward to the outcome! 🤞

On Thu, Feb 29, 2024 at 8:56 PM Jan Friedrich  wrote:

> Hi,
>
> thanks for the opportunity, I will try my best.
>
> https://github.com/apache/logging-log4net/pull/115
>
> Regards.
>
> Jan
>
> Thursday, February 29, 2024, 12:26:55 PM, you wrote:
>
> > Hi Volkan
>
>
> > If Jan feels up to the task, it would be worthwhile to give it a go. If
> nothing else, it's a bit of a "trial by fire"
>
> > of following the RELEASING.md steps to get to a release. I'm sure there
> are bits I've missed because they
>
> > seemed obvious to me or I just missed them - having a second set of eyes
> on it, going through it, has benefits
>
> > in itself. As for the actual release, I believe Jan is more than
> capable, but I understand he may be blocked
>
> > somewhere, so if I can help, I will (: It would also be a good trial run
> to find out what, if anything, is still
>
> > required to be set up for Jan (eg svn access for the docs, etc)
>
>
> > Jan, Volkan brings up one of the sticky points - signing the release -
> which I can do from my personal
>
> > machine, with the binary artifacts in place - so I could do steps 3 and
> 4 (build and sign) - but I'll only
>
> > really have time on Friday afternoon, so I'll check it out then. In the
> mean-time, if you'd like to see
>
> > how far you can get with the RELEASING.md instructions, I'd _really_
> appreciate it. I haven't done
>
> > a log4net release in ages because it takes a reasonable amount of time
> and motivation - substances
>
> > I'm in short supply of (when I have the motivation, I don't have the
> time, and when I have the time,
>
> > it's after a long day, and I don't have the motivation any more ): )
>
>
> > -d
>
>
> > On 2024/02/29 13:02, Volkan Yazıcı wrote:
> >> Davyd, can Jan help you with the release? Since he is not a PMC member,
> >> there are certain steps he can't take. Though judging from the
> RELEASING.md
> >>  >,
> >> maybe he can bring it to a point within the limits of access rights
> granted
> >> to him, and then you can intervene (e.g., signing artifacts, uploading
> to
> >> SVN) whenever needed.
> >>
> >> If you say this will make things more difficult, that is also
> >> understandable.
> >>
> >> On Thu, Feb 29, 2024 at 11:01 AM Davyd McColl  >
> >> wrote:
> >>
> >>> Considering my constrained time, and even though @FreeAndNil
> >>>  recently stepped up to be a
> maintainer, I
> >>> don't see any time really soon. You can, in the meantime, check out the
> >>> repo, build, and distribute a dll with your app if it's that important.
> >>> It's not convenient, I'll admit, but if it's urgent, it's an option.
> >>>
> >>> —
> >>> Reply to this email directly, view it on GitHub
> >>> <
> https://github.com/apache/logging-log4net/pull/103#issuecomment-1970795467
> >,
> >>> or unsubscribe
> >>> <
> https://github.com/notifications/unsubscribe-auth/AAARTSO5BS7Y4XCZS6WAOXLYV36A3AVCNFSM6ABBYRLE4KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZQG44TKNBWG4
> >
> >>> .
> >>> You are receiving this because you commented.Message ID:
> >>> 
> >>>
>
>