I think a more specific problem was that nobody on the PMC knows much about
this component. The active developers are committers and contributors
currently.
On Tue, Aug 4, 2020 at 01:01 Tobias Frost wrote:
> On Mon, Aug 03, 2020 at 07:34:15PM -0500, Matt Sicker wrote:
> > Very well said! It help
On Mon, Aug 03, 2020 at 07:34:15PM -0500, Matt Sicker wrote:
> Very well said! It helps get user feedback quicker, too.
+1!
Also, the current "stable" has some many bugs (I carry 13 non Debian-specific
patches in the current Debian package…) and a new release would also fix some
open
Bugs on the
On Mon, Aug 03, 2020 at 07:49:14PM -0400, Robert Middleton wrote:
> Thorsten,
>
> > > A number of these are rather large changes, so it probably
> > > doesn't make sense to work on them until there's a known-good release, as
> > > they would likely break both API and ABI compatibility.
> >
> > D
Very well said! It helps get user feedback quicker, too.
On Mon, Aug 3, 2020 at 19:03 Ralph Goers wrote:
> Here are my thoughts after working on several ASF projects for over 15
> years.
>
> Theoretically logging projects should follow the “release early, release
> often” philosophy. There are a
Here are my thoughts after working on several ASF projects for over 15 years.
Theoretically logging projects should follow the “release early, release often”
philosophy. There are a few good reasons why it should be that way. However,
when you have a project with very few committers with limited
Thorsten,
> > A number of these are rather large changes, so it probably
> > doesn't make sense to work on them until there's a known-good release, as
> > they would likely break both API and ABI compatibility.
>
> Does it really matter much if things are broken now vs. with 0.12.0 or
> alike? B
Guten Tag Robert Middleton,
am Montag, 3. August 2020 um 02:17 schrieben Sie:
> I'd like to propose some new features/updates for log4cxx, if there's
> interest.
Things mostly read good and interesting to me. Even though I would
suffer myself a lot most likely, as my currently used compiler/IDE i
Hey all,
I'd like to propose some new features/updates for log4cxx, if there's
interest. A number of these are rather large changes, so it probably
doesn't make sense to work on them until there's a known-good release, as
they would likely break both API and ABI compatibility.
Big Changes:
1
