On Mon, 15 Jan 2024 at 10:40, Volkan Yazıcı <vol...@yazi.ci> 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-parent
> logging-log4j-tools
> logging-log4j-transform
> logging-log4j-kotlin
> logging-log4j-scala
> logging-log4j-jakarta
>
> There is only one left to migrate to this scheme: `logging-log4j2`, which I
> intend to do on February 9 during STF MS12. `logging-site`, `cyclonedx`,
> `activity-monitor` are exceptions, since they are only websites, not source
> code repositories. Hence, your statement of *"the way our website is
> created from multiple repos and branches is somehow incoherent"* is untrue.

I am fine with this scheme if it becomes universal.

Regarding `logging-log4j2`, we will probably need 2 pairs of website
branches, so that we can publish `/log4j/2.x` and `/log4j/3.x`
independently. The `/log4j` folder can be published from
`logging-site`.

Piotr

Reply via email to