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
>> <https://github.com/apache/logging-log4net/blob/master/doc/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 <notificati...@github.com>
>> wrote:
>>
>>> Considering my constrained time, and even though @FreeAndNil
>>> <https://github.com/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/AAARTSO5BS7Y4XCZS6WAOXLYV36A3AVCNFSM6AAAAABBYRLE4KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZQG44TKNBWG4>
>>> .
>>> You are receiving this because you commented.Message ID:
>>> <apache/logging-log4net/pull/103/c1970795...@github.com>
>>>

Reply via email to