It’s manual work that makes merging PRs non-trivial.
> On Nov 9, 2022, at 10:58 PM, Ralph Goers <ralph.go...@dslextreme.com> wrote:
>
> It is, but it isn’t one of the items that I personally consider broken.
>
> Ralph
>
>> On Nov 9, 2022, at 3:50 PM, Matt Sicker <m...@musigma.org> wrote:
>>
>> The changelog is an important aspect of the website, too.
>>
>>> On Nov 9, 2022, at 1:43 PM, Ralph Goers <ralph.go...@dslextreme.com> wrote:
>>>
>>> See my comments in the issue. I’d rather focus on web site changes that
>>> provide real value.
>>>
>>> Ralph
>>>
>>>> On Nov 8, 2022, at 3:41 PM, Gary Gregory <garydgreg...@gmail.com> wrote:
>>>>
>>>> I do like all the details in the Jira ticket! :-)
>>>>
>>>> Gary
>>>>
>>>> On Mon, Nov 7, 2022, 16:03 Volkan Yazıcı <vol...@yazi.ci> wrote:
>>>>
>>>>> In the context of migrating away from JIRA to GitHub Issues, I want to
>>>>> replace the current maven-changes-plugin setup with a merge-conflict-free
>>>>> Markdown-based solution. I have elaborated the details in LOG4J2-3628
>>>>> <https://issues.apache.org/jira/browse/LOG4J2-3628>.
>>>>>
>>>>> Since this will change the behaviour of how we introduce changes and make
>>>>> releases, I would appreciate it if committers could skim through it and
>>>>> share their feedback.
>>>>>
>>>
>>
>
