Great news Piotr! 🎉
It was pretty much a solo marathon of yours.
I am glad you made it to the finish line. 🙇

Some remarks:

   1. `Build`, `Distribution`, and `Support` sections need to be added to
   `/README.adoc` (you can copy-paste from `log4j-tools`)
   2. I would recommend you to use GitHub Releases for sharing
   user-friendly release notes. (See `log4j-tools` GitHub Releases
   <https://github.com/apache/logging-log4j-tools/releases> for an
   example.) It is not only simple, but also what many software update
   trackers digest.
   3. Please copy `RELEASING.adoc` of `log4j-tools`
   <https://github.com/apache/logging-log4j-tools/blob/master/RELEASING.adoc>,
   mention it in `/README.adoc`, and adopt it for your custom
   `log4j-changelog` usage. *I take this of uttermost importance since it
   enables any PMC member to make releases without breaking a sweat.*
   4. I would limit the `<developers>` in `pom.xml` to those who were
   involved in the development.
   5. In `README.adoc` of `log4j-transform-maven-plugin`, I would explain
   _the transformation_ with a demonstration: "this `logger.info()` call
   gets converted to this `logger.atInfo()` call".
   6. Once the very first `log4j-transform` release is performed,
      1. in Log4j `2.x` sources, create
      `/src/site/asciidoc/log4j-transform.adoc` with some simple content mainly
      linking to the documentation on GitHub,
      2. add it to `<menu name="Components" ...>` block in
      `src/site/site.xml`,
      3. (`cherry-pick` your changes to `main`)
      4. and finally generate the website (`./mvnw -N site`) and copy it to
      `logging-log4j-site` repository

If you need help with any of these steps, you know where to find me.

On Thu, Apr 27, 2023 at 11:43 PM Piotr P. Karwasz <piotr.karw...@gmail.com>
wrote:

> Hi all,
>
> After two months since the release of 2.20.0 I learned AsciiDoc and
> documented `logging-log4j-transform`. As far as I am concerned it is
> ready to go.
>
> Can you check the repository if something is missing?
>
> Since the documentation is on Github, I think I could just:
>
> 1. Prepare a source archive on dist.apache.org (do we still need it),
> 2. Prepare the artifacts on Nexus,
> 3. Send a vote e-mail.
>
> Am I missing something?
>
> Piotr
>

Reply via email to