Should these files contain comments to this effect?
Gary
On Tue, Jan 16, 2024, 1:18 AM Piotr P. Karwasz
wrote:
> Hi Ralph,
>
> On Tue, 16 Jan 2024 at 01:56, Ralph Goers
> wrote:
> >
> > I don’t understand what it means to keep both staging and publish in
> “asf-site”. By definition, the asf-si
Hi Remko! Just saying "Hi".
Gary
On Tue, Jan 16, 2024, 1:40 AM Remko Popma wrote:
> I’m open to improvements in this area.
>
> Before going into details or specifics though, I’m curious:
>
> What do we (users, developers and PMC members) consider to be the “value
> proposition” of Log4j? Why sh
> On Jan 15, 2024, at 11:18 PM, Piotr P. Karwasz
> wrote:
>
> Hi Ralph,
>
> On Tue, 16 Jan 2024 at 01:56, Ralph Goers wrote:
>>
>> I don’t understand what it means to keep both staging and publish in
>> “asf-site”. By definition, the asf-site branch is the live web-site and
>> asf-stagin
> On Jan 16, 2024, at 9:15 AM, Ralph Goers wrote:
>
>
>
>> On Jan 15, 2024, at 11:18 PM, Piotr P. Karwasz
>> wrote:
>>
>> Hi Ralph,
>>
>> On Tue, 16 Jan 2024 at 01:56, Ralph Goers wrote:
>>>
>>> I don’t understand what it means to keep both staging and publish in
>>> “asf-site”. By def
I love this idea, Volkan!
> On Jan 15, 2024, at 3:40 AM, Volkan Yazıcı wrote:
>
> -1 on merging multiple websites to a single repository.
>
> I think documentation should reside in the same repository where sources
> are. I already implemented this for *almost* every repository:
>
> logging-pa
Agreed that we can add things back later if needed. +1
> On Jan 15, 2024, at 3:02 PM, Volkan Yazıcı wrote:
>
> +1
>
> Allow me to remind everyone that anything that is removed from `3.0.0` can
> be added again in a follow up minor release, if need arises. Hence, no need
> to be overcautious.
>
