On Wed, May 18, 2022 at 5:37 PM Ralph Goers wrote:
>
> I don’t really care what doc format the manual uses, so long as they are all
> the
> same and it is easy to update the manual outside of a release.
+1
Gary
>
> Ralph
>
> > On May 18, 2022, at 4:15 AM, Volkan Yazıcı wrote:
> >
> > 5. Manua
I don’t really care what doc format the manual uses, so long as they are all
the
same and it is easy to update the manual outside of a release.
Ralph
> On May 18, 2022, at 4:15 AM, Volkan Yazıcı wrote:
>
> 5. Manual is migrated from Markdown and XDOC to AsciiDoc – plus, 2 Markdown
> files, sa
5. Manual is migrated from Markdown and XDOC to AsciiDoc – plus, 2 Markdown
files, sadly.
On Tue, May 3, 2022 at 3:38 PM Piotr P. Karwasz
wrote:
> Hi everyone,
>
> This topic has been discussed several times, but the list of features that
> need to be in version 3.0 is still fuzzy to me. From wh
On the compatibility front, it would be useful to figure out which parts of
core are expected to remain compatible. Different plugin types will likely have
different expectations of compatibility.
—
Matt Sicker
> On May 3, 2022, at 10:11, Gary Gregory wrote:
>
> 5. Define the binary compatibil
5. Define the binary compatibility requirements.
Gary
On Tue, May 3, 2022, 09:38 Piotr P. Karwasz wrote:
> Hi everyone,
>
> This topic has been discussed several times, but the list of features that
> need to be in version 3.0 is still fuzzy to me. From what I gathered
> version 3.0 requires:
>
Hi everyone,
This topic has been discussed several times, but the list of features that
need to be in version 3.0 is still fuzzy to me. From what I gathered
version 3.0 requires:
1. JPMS support with non-automatic modules. This seems to be done for
`log4j-api`, `log4j-plugins` and partially for `
