Kevin,
I don't work on Log4net, but looking through the recent commits it
looks like this may have been fixed:
https://github.com/apache/logging-log4net/pull/92
I don't know if there is currently a timeline as to when this might be
officially released.
-Robert Middleton
On Thu, Dec 29, 2022 at
I am not understanding the format of this table. I expected it to contain a
list of PRs/Jira issues that were not propagated. Instead it seems to be a list
of modules and package names. Are we supposed to mark the packages that have
been validated?
Ralph
> On Dec 30, 2022, at 2:36 AM, Piotr P.
Talking about what might have helped in the past isn’t going to be very useful.
For one, we didn’t cut releases on master because there were too many things
not yet done. That isn’t the case any more.
It is annoying to know commits were made to 2.x that weren’t also committed to
master. I stil
I agree with Volkan; this will be a bit easier to handle once we start cutting
3.x releases. We can better define the baseline there.
—
Matt Sicker
> On Dec 30, 2022, at 06:37, Volkan Yazıcı wrote:
>
> What I am missing most is a baseline. If there would have been a `3.x`
> release right after
On Fri, Dec 30, 2022 at 11:43 AM Tobias Frost wrote:
> When doing the same against the branch "next_stable", currently at [2]
> the result is much much worse:
> https://people.debian.org/~tobi/log4cxx/1_to_next/compat_report.html
>
> /me confused… (I've read your text as it should be the opposite…
On Fri, Dec 30, 2022 at 10:29:46AM -0500, Robert Middleton wrote:
> On Fri, Dec 30, 2022 at 10:17 AM Tobias Frost wrote:
> >
> > On Fri, Dec 30, 2022 at 07:18:46AM +0100, Tobias Frost wrote:
> > > IF an SONAME bump is required, it will become more challenging, as other
> > > Debian teams are invol
On Fri, Dec 30, 2022 at 10:17 AM Tobias Frost wrote:
>
> On Fri, Dec 30, 2022 at 07:18:46AM +0100, Tobias Frost wrote:
> > IF an SONAME bump is required, it will become more challenging, as other
> > Debian teams are involved (and other maintainers if it casues breakages in
> > reverse dependencie
False is the default so I left it alone. It also means it is specified in less
places.
Ralph
> On Dec 30, 2022, at 5:26 AM, Gary Gregory wrote:
>
> Should that setting be flipped such that a Maven module ask to be Javadoc'd?
>
> Gary
>
>> On Fri, Dec 30, 2022, 07:23 Volkan Yazıcı wrote:
>>
On Fri, Dec 30, 2022 at 07:18:46AM +0100, Tobias Frost wrote:
> IF an SONAME bump is required, it will become more challenging, as other
> Debian teams are involved (and other maintainers if it casues breakages in
> reverse dependencies)
> I would basically needs something (it does not need to be t
What I am missing most is a baseline. If there would have been a `3.x`
release right after a `2.y` release, I could have taken `3.x` as a baseline
and whenever `2.(y+1)` comes out, I would make sure `3.(x+1)` contains all
the changes from `2.y` to `2.(y+1)`. In its current state, talking about
the
Should that setting be flipped such that a Maven module ask to be Javadoc'd?
Gary
On Fri, Dec 30, 2022, 07:23 Volkan Yazıcı wrote:
> Agreed.
>
> Ralph, I see that you have only added `true` to
> `log4j-layout-template-json-test` module, why don't we add it to all
> `*-test` and `*-its` modules?
Agreed.
Ralph, I see that you have only added `true` to
`log4j-layout-template-json-test` module, why don't we add it to all
`*-test` and `*-its` modules? That is, `log4j-api-test`, `log4j-core-its`,
`log4j-core-test`, etc.
On Fri, Dec 30, 2022 at 1:45 AM Ralph Goers
wrote:
>
>
> > On Dec 29, 2
Hi,
On Fri, 30 Dec 2022 at 09:47, Piotr P. Karwasz wrote:
> "Next" weekend I'll try to write down the sync status of `master` on
> the Wiki. I'll break it down into modules and for `log4j-core` into
> packages.
That is actually something I can do in a couple of minutes:
https://cwiki.apache.org
Hi all,
As you know `master` is painfully lagging after `release-2.x`. The
main problem is that it is still diverging (in the wrong direction).
In the Tomcat repository you can observe 4 commits within minutes,
addressing the same issue in all 4 supported branches. Can we do
something similar in
14 matches
Mail list logo
