Re: [log4cxx] Current State

[Matt Sicker]

Seems like I forgot to commit this to the KEYS file! I've gone ahead
and done that now.

On Mon, 29 Jan 2018 at 11:31, Matt Sicker  wrote:
>
> On 29 January 2018 at 03:13, Thorsten Schöning  wrote:
>>
>> Guten Tag Matt Sicker,
>> am Dienstag, 23. Januar 2018 um 20:31 schrieben Sie:
>>
>> > Could you include the fingerprint?
>>
>> Isn't that the following line in the file already?
>>
>> > Schl.-Fingerabdruck = A468 E054 E594 9AC5 8FA7  5A0E F649 2CB4 778C 3033
>
>
> Yeah, that's the fingerprint.
>
>>
>> > Also, that site is timing out for me at
>> > the moment. You could encrypt your public key using my public key in the
>> > KEYS file and send it to me to add.
>>
>> Done that in the attachment. Not sure if it's the expected format, so
>> I attached the unencrypted public key as well.
>
>
> The mailing list ate your attachment it appears. I was able to download it 
> this time, though, so no need to resend.
>
>>
>>
>> Mit freundlichen Grüßen,
>>
>> Thorsten Schöning
>>
>> --
>> Thorsten Schöning   E-Mail: thorsten.schoen...@am-soft.de
>> AM-SoFT IT-Systeme  http://www.AM-SoFT.de/
>>
>> Telefon...05151-  9468- 55
>> Fax...05151-  9468- 88
>> Mobil..0178-8 9468- 04
>>
>> AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
>> AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
>
>
>
>
> --
> Matt Sicker 



-- 
Matt Sicker 

Re: [log4cxx] Current State

[Thorsten Schöning]

Guten Tag Matt Sicker,
am Dienstag, 23. Januar 2018 um 20:31 schrieben Sie:

> Could you include the fingerprint?

Isn't that the following line in the file already?

> Schl.-Fingerabdruck = A468 E054 E594 9AC5 8FA7  5A0E F649 2CB4 778C 3033

> Also, that site is timing out for me at
> the moment. You could encrypt your public key using my public key in the
> KEYS file and send it to me to add.

Done that in the attachment. Not sure if it's the expected format, so
I attached the unencrypted public key as well.

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning   E-Mail: thorsten.schoen...@am-soft.de
AM-SoFT IT-Systeme  http://www.AM-SoFT.de/

Telefon...05151-  9468- 55
Fax...05151-  9468- 88
Mobil..0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow

Re: [log4cxx] Current State

[Matt Sicker]

On 23 January 2018 at 13:06, Thorsten Schöning 
wrote:

> Please finde the changed file attached. I think I strictly followed
> the docs, simply added at the bottom and published on the mentioned
> server. But you should have a look yourself I didn't accidently break
> anything.
>
> http://pgpkeys.mit.edu/pks/lookup?search=tschoening%40apache.org=index


Could you include the fingerprint? Also, that site is timing out for me at
the moment. You could encrypt your public key using my public key in the
KEYS file and send it to me to add.


> Sorry, but I don't understand what "commit them there" means. I simply
> send a mail with all artifacts and that mail is the "commit" already
> or is one of you committing afterwards manually to "dist"?
>

I mean the dist svn repo where releases go for mirroring.


> That would be great, thanks. I wouldn't mind publishing artifacts
> using mail of course if necessary, but committing would be slightly
> easier in my VM-environment I guess, like I did with "dist-dev".
>

If possible, you'd be able to make the release by committing the artifacts
to svn dist.


> > If you're publishing them to Maven Central as well[...]
>
> I wouldn't.
>

Good, this simplifies things a little bit.


> > You should be able to commit the website itself, though.
>
> I am, did that already in the past.
>

Also glad to hear that this works already.

-- 
Matt Sicker 

Re: [log4cxx] Current State

[Thorsten Schöning]

Guten Tag Matt Sicker,
am Montag, 22. Januar 2018 um 20:45 schrieben Sie:

> Yes, you can send us your key and any PMC member can commit it to the KEYS
> file.

Please finde the changed file attached. I think I strictly followed
the docs, simply added at the bottom and published on the mentioned
server. But you should have a look yourself I didn't accidently break
anything.

http://pgpkeys.mit.edu/pks/lookup?search=tschoening%40apache.org=index

> If you're not on the PMC, I believe how we'd normally do this is to copy
> the artifacts you offer in the vote thread and commit them there.

Sorry, but I don't understand what "commit them there" means. I simply
send a mail with all artifacts and that mail is the "commit" already
or is one of you committing afterwards manually to "dist"?

> I can find out if it's possible to grant you access to that repo.

That would be great, thanks. I wouldn't mind publishing artifacts
using mail of course if necessary, but committing would be slightly
easier in my VM-environment I guess, like I did with "dist-dev".

> If you're publishing them to Maven Central as well[...]

I wouldn't.

> You should be able to commit the website itself, though.

I am, did that already in the past.

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning   E-Mail: thorsten.schoen...@am-soft.de
AM-SoFT IT-Systeme  http://www.AM-SoFT.de/

Telefon...05151-  9468- 55
Fax...05151-  9468- 88
Mobil..0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow

Re: [log4cxx] Current State

[Thorsten Schöning]

Guten Tag Matt Sicker,
am Samstag, 20. Januar 2018 um 18:56 schrieben Sie:

> I'd be available to help with the release process along with any karma
> mangling needed.

Should I send you/to the list a changed KEYS file with my added
PGP-key and you commit that?

What about publishing a release after a successfully vote in "dist"?
Should I simply send you release packages by mail or do you grant me
commit access to the log4cxx subdir? In the latter case I would
consider adding committing to "dist" to the release scripts as a
seperate last step.

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning   E-Mail: thorsten.schoen...@am-soft.de
AM-SoFT IT-Systeme  http://www.AM-SoFT.de/

Telefon...05151-  9468- 55
Fax...05151-  9468- 88
Mobil..0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow

Re: [log4cxx] Current State

[Matt Sicker]

I'd be available to help with the release process along with any karma
mangling needed.

On 20 January 2018 at 06:36, Thorsten Schöning 
wrote:

> Guten Tag Robert Middleton,
> am Samstag, 20. Januar 2018 um 04:00 schrieben Sie:
>
> > As prompted by the discussion last week about the state of log4cxx, is
> > there a current blocker(apart from Thorsten's time) halting a release
> > of log4cxx/regular maintenance?
>
> The PGP-keys of whoever is releasing need to be added to the following
> file BEFORE actually releasing. Don't know who is allowed to do that
> under which circumstances, regarding web-of-trust and all that.
>
> https://dist.apache.org/repos/dist/release/logging/KEYS
>
> Releases need to be published in the dist-repo in the end and I don't
> know how that is organized as well. Somewhere in the Apache docs I've
> read that only PMCs are allowed to do that?
>
> Actually doing a release seemed pretty complicated to me, therefore I
> created the branch "release_scripts" to document/automate what I know
> needs to be done. Those scripts are capable of creating a release
> branch, handling version numbers, Maven stuff and publishing signed
> artifacts to vote on in "dist-dev". Not sure currently if I already
> addressed site commits and the stuff after a vote has passed, like
> moving artifacts from "dist-dev" to "dist", is not handled/documented
> yet.
>
> Handling of LT_VERSION is still unclear to me, I tend to simply
> increase it by one like was done in the past and add that to the
> release scripts I've created. While that might be logically wrong, it
> would work always without breaking anything.
>
> So in the end, getting to the point to vote on a release is pretty
> close, everything afterwards is still somewhat unknown to me and in
> general, I'm not familiar with such complex release processes. The
> only thing I do in my projects is merging between branches without the
> need to ask anyone for anything, because there's no one else. ;-)
>
> Mit freundlichen Grüßen,
>
> Thorsten Schöning
>
> --
> Thorsten Schöning   E-Mail: thorsten.schoen...@am-soft.de
> AM-SoFT IT-Systeme  http://www.AM-SoFT.de/
>
> Telefon...05151-  9468- 55
> Fax...05151-  9468- 88
> Mobil..0178-8 9468- 04
>
> AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
> AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
>
>


-- 
Matt Sicker 

Re: [log4cxx] Current State

[Thorsten Schöning]

Guten Tag Robert Middleton,
am Samstag, 20. Januar 2018 um 04:00 schrieben Sie:

> As prompted by the discussion last week about the state of log4cxx, is
> there a current blocker(apart from Thorsten's time) halting a release
> of log4cxx/regular maintenance?

The PGP-keys of whoever is releasing need to be added to the following
file BEFORE actually releasing. Don't know who is allowed to do that
under which circumstances, regarding web-of-trust and all that.

https://dist.apache.org/repos/dist/release/logging/KEYS

Releases need to be published in the dist-repo in the end and I don't
know how that is organized as well. Somewhere in the Apache docs I've
read that only PMCs are allowed to do that?

Actually doing a release seemed pretty complicated to me, therefore I
created the branch "release_scripts" to document/automate what I know
needs to be done. Those scripts are capable of creating a release
branch, handling version numbers, Maven stuff and publishing signed
artifacts to vote on in "dist-dev". Not sure currently if I already
addressed site commits and the stuff after a vote has passed, like
moving artifacts from "dist-dev" to "dist", is not handled/documented
yet.

Handling of LT_VERSION is still unclear to me, I tend to simply
increase it by one like was done in the past and add that to the
release scripts I've created. While that might be logically wrong, it
would work always without breaking anything.

So in the end, getting to the point to vote on a release is pretty
close, everything afterwards is still somewhat unknown to me and in
general, I'm not familiar with such complex release processes. The
only thing I do in my projects is merging between branches without the
need to ask anyone for anything, because there's no one else. ;-)

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning   E-Mail: thorsten.schoen...@am-soft.de
AM-SoFT IT-Systeme  http://www.AM-SoFT.de/

Telefon...05151-  9468- 55
Fax...05151-  9468- 88
Mobil..0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow

[log4cxx] Current State

[Robert Middleton]

As prompted by the discussion last week about the state of log4cxx, is
there a current blocker(apart from Thorsten's time) halting a release
of log4cxx/regular maintenance?  I would like to help out on the
project to do a release / add new features, but I'm not sure what the
best way to go about this is, or even if my help is needed.

There are some place where I as a user of log4cxx would like to see it
go, but I don't want to spend the time to implement updates/new
features if they're not going to be used.

-Robert Middleton