AW: Help for the Log4cxx podling

Hello, I just want to tell, that am willing to prepare a log4cxx release. Torsten -Ursprüngliche Nachricht- Von: William A Rowe Jr [mailto:wr...@rowe-clan.net] Gesendet: Mittwoch, 13. Januar 2016 22:48 An: Log4CXX Dev Betreff: Re: Help for the Log4cxx podling On Mon, Jan 11, 2016

Re: Help for the Log4cxx podling

Guten Tag Wiebesiek, Torsten, am Dienstag, 26. Januar 2016 um 14:29 schrieben Sie: > I just want to tell, that am willing to prepare a log4cxx release. Sounds good, I just removed the 3 open issues currently assigned to 0.11.0, because if they are not fixed now, they won't be in the short time

Re: Help for the Log4cxx podling

On Mon, Jan 11, 2016 at 3:18 AM, Wiebesiek, Torsten < torsten.wiebes...@grecon.de> wrote: > > > If not you, then ...? Are there other committers who are interesting > > > in taking the release mantle, and really give yourself breathing room > > > to just improve the code without all the rest of

Re: Help for the Log4cxx podling

Guten Tag William A Rowe Jr, am Samstag, 9. Januar 2016 um 18:26 schrieben Sie: > While we are waiting to find out who is interested in the heavy > lifting of creating a release candidate, who here is willing to > review such candidates and cast a +/-1 vote for release of the > package? Which of

Re: Help for the Log4cxx podling

> > If not you, then ...?  Are there other committers who are interesting > > in taking the release mantle, and really give yourself breathing room > > to just improve the code without all the rest of the details? > > Torsten Wiebesiek seemed interested to read the details about the > release

Re: Help for the Log4cxx podling

On Jan 9, 2016 02:53, "Thorsten Schöning" wrote: > > Guten Tag William A Rowe Jr, > am Freitag, 8. Januar 2016 um 23:54 schrieben Sie: > > > If not you, then ...? Are there other committers who are interesting in taking > > the release mantle, and really give yourself

Re: Help for the Log4cxx podling

Assuming the release can be compiled on fedora, I can review and vote on it (as an IPMC member). John On Sat, Jan 9, 2016 at 12:26 PM William A Rowe Jr wrote: > > On Jan 9, 2016 02:53, "Thorsten Schöning" wrote: > > > > Guten Tag William A Rowe Jr,

RE: Help for the Log4cxx podling

As a user (and small time contributor once) of log4cxx, I would vote for a move to a central hosting on github. I don't mind what happens to the project in terms of the apache organization as I use log4cxx as a stand-alone library - and I guess many others use log4cxx in the same fashion.

Re: Help for the Log4cxx podling

On Fri, Jan 8, 2016 at 1:10 PM, Thorsten Schöning wrote: > Guten Tag William A Rowe Jr, > am Freitag, 8. Januar 2016 um 19:18 schrieben Sie: > > > I'm trying to understand whether we are looking at a cultural refusal to > > ever put a post in the stand and say "this is a

Re: Help for the Log4cxx podling

Have no fear, we can extract all history from the svn repo. I don't know what approach you used, such that your IP was auto-banned, but that can be solved. We've done this before. So: please don't worry about that, within this discussion. On Jan 8, 2016 1:11 PM, "Thorsten Schöning"

Re: Help for the Log4cxx podling

Guten Tag William A Rowe Jr, am Freitag, 8. Januar 2016 um 19:18 schrieben Sie: > I'm trying to understand whether we are looking at a cultural refusal to > ever put a post in the stand and say "this is a release, there will be other > releases, but this is our release as of now"? Or is this

Re: Help for the Log4cxx podling

Guten Tag Wiebesiek, Torsten, am Freitag, 8. Januar 2016 um 11:16 schrieben Sie: > I am not familiar with the Apache requirements for a project. From > what I understand, there have to be reports filed every three month. > What else? How can we proceed with the limited resources, we have? The

Re: Help for the Log4cxx podling

Hi, > I am not familiar with the Apache requirements for a project. From > what I understand, there have to be reports filed every three month. > What else? How can we proceed with the limited resources, we have? > The reports every 3 months shouldn't be a big problem, but you need > to do e.g.

Re: Help for the Log4cxx podling

On Fri, Jan 8, 2016 at 3:31 AM, wrote: > As a user (and small time contributor once) of log4cxx, I would vote for a > move to a central hosting on github. I don't mind what happens to the > project in terms of the apache organization as I use log4cxx as a >

Re: Help for the Log4cxx podling

Guten Tag William A Rowe Jr, am Freitag, 8. Januar 2016 um 15:33 schrieben Sie: > Forty forks means 40 prospective committers. Or just people, like some of those currently involved, which change things once in a while because of bugs or such. I'm always just happy if my fixes are simply merged

Re: Help for the Log4cxx podling

Or clone/fork it into Trafodion, if you need updates or continued maintenance. Look at it as just another component (rather than a separate project). On Thu, Jan 7, 2016 at 10:44 AM, Thorsten Schöning wrote: > Guten Tag Roberta Marton, > am Donnerstag, 7. Januar 2016 um

Re: Help for the Log4cxx podling

On Thu, Jan 7, 2016 at 9:53 AM, Thorsten Schöning wrote: > So even if we are to dead for the incubator, we are to alive for the > attic. If you can't make a release, you're dead enough for the Attic. Marvin Humphrey