Re: [log4cxx] Release process releated questions

Hi, Sorry for being late for the party (I was just checking if there is a new release for liblog4cxx, which I would really apprecicate when I came about this thread) Robert Middleton wrote on Tue, 25 Jul 2017 19:11:09 -0700: > It's more of an expected behavior - when people download an autotool

Re: [log4cxx] Release process releated questions

On Tue, Jul 25, 2017 at 3:33 AM, Dominik Psenner wrote: > If xx&&yy&&zz is complicated why not ship a makefile with an install target? > > On 25 Jul 2017 9:16 a.m., "Thorsten Schöning" wrote: > >> Guten Tag Robert Middleton, >> am Dienstag, 25. Juli 2017 um 02:28 schrieben Sie: >> >> > As far as

Re: [log4cxx] Release process releated questions

If xx&&yy&&zz is complicated why not ship a makefile with an install target? On 25 Jul 2017 9:16 a.m., "Thorsten Schöning" wrote: > Guten Tag Robert Middleton, > am Dienstag, 25. Juli 2017 um 02:28 schrieben Sie: > > > As far as I'm aware, the configure.sh is not platform-dependent, > > It is in

Re: [log4cxx] Release process releated questions

Guten Tag Robert Middleton, am Dienstag, 25. Juli 2017 um 02:28 schrieben Sie: > As far as I'm aware, the configure.sh is not platform-dependent, It is in a sense that it's arbitrary old code generated on my platform while obviously each other platform could generate better fitting one on that pl

Re: [log4cxx] Release process releated questions

On Sun, Jul 23, 2017 at 11:37 AM, Thorsten Schöning wrote: > Guten Tag Robert Middleton, > am Samstag, 22. Juli 2017 um 23:44 schrieben Sie: > >> I tried to verify with: gpg --verify apache-log4cxx-0.11.0.tar.gz.asc >> apache-log4cxx-0.11.0.tar.gz >> but gpg couldn't find the public key - do I nee

Re: [log4cxx] Release process releated questions

Guten Tag Robert Middleton, am Samstag, 22. Juli 2017 um 23:44 schrieben Sie: > I tried to verify with: gpg --verify apache-log4cxx-0.11.0.tar.gz.asc > apache-log4cxx-0.11.0.tar.gz > but gpg couldn't find the public key - do I need to import a special key at > all? That depends on GPG I guess, is

Re: [log4cxx] Release process releated questions

I just had a quick look at the files, and I noticed the following potential problems: I tried to verify with: gpg --verify apache-log4cxx-0.11.0.tar.gz.asc apache-log4cxx-0.11.0.tar.gz but gpg couldn't find the public key - do I need to import a special key at all? There's no configure script in

Re: [log4cxx] Release process releated questions

Guten Tag Robert Middleton, am Donnerstag, 13. Juli 2017 um 23:57 schrieben Sie: > I noticed that you uploaded some files to > https://dist.apache.org/repos/dist/dev/logging/log4cxx/, are those for > review yet or not? Not "officially", was just testing some scripts and couldn't decide if it's wo

Re: [log4cxx] Release process releated questions

Thorsten, I noticed that you uploaded some files to https://dist.apache.org/repos/dist/dev/logging/log4cxx/, are those for review yet or not? -Robert Middleton On Sat, Jul 8, 2017 at 2:17 PM, Matt Sicker wrote: > 1. I think a PMC has to commit the key to the file. > > 4. All sounds reasonable

Re: [log4cxx] Release process releated questions

1. I think a PMC has to commit the key to the file. 4. All sounds reasonable to me. 5. Normally we'd stage artifacts on Nexus. However, as we're not putting C++ stuff on Maven Central, I don't think that's right. I found this svn repo that looks p

Re: [log4cxx] Release process releated questions

Guten Tag Matt Sicker, am Freitag, 7. Juli 2017 um 22:41 schrieben Sie: > 1. You should add it to the logging project's KEYS file. I think I was one > of the last keys added to the file. I don't have write access to dist/release. Should I ask someone for write access or is someone else committing

Re: [log4cxx] Release process releated questions

>From what I remember, when I tried this before I had a problem building with ant because of dependencies, which is I think what it's using now for release. PR#2 on Github fixes this to just use shell executions with Maven, although if it's working for you currently then I don't see a need to chan

Re: [log4cxx] Release process releated questions

That is a great suggestion! Ralph > On Jul 7, 2017, at 1:51 PM, Gary Gregory wrote: > > You might want to clone the Log4j 2 build wiki and replace the Git and Java > parts with your build system and language specific parts. > > Gary > > On Fri, Jul 7, 2017 at 1:41 PM, Matt Sicker wrote: > >

Re: [log4cxx] Release process releated questions

You might want to clone the Log4j 2 build wiki and replace the Git and Java parts with your build system and language specific parts. Gary On Fri, Jul 7, 2017 at 1:41 PM, Matt Sicker wrote: > 1. You should add it to the logging project's KEYS file. I think I was one > of the last keys added to

Re: [log4cxx] Release process releated questions

1. You should add it to the logging project's KEYS file. I think I was one of the last keys added to the file. 2. I don't know of any C++ projects distributed through Maven Central. There are projects written mostly in C or C++ that bind to Java which are on MC, though. 3. I'm not exactly sure on

[log4cxx] Release process releated questions

Hi all, I'm working on a release for log4cxx and have some questions about the process itself: 1. KEYS in dist-repo There's a KEYS file at the root of our dist-repo, do I need to get added there with my signing key? I've added it wherever the docs told me, KEYS in project repo, home.apache.org,