Hi Volkan, On Mon, 14 Oct 2024 at 20:25, Volkan Yazıcı <vol...@yazi.ci.invalid> wrote: > - In "Staging a release", -1 for replacing a platform-independent > `pom.xml` snippet with OS-specific shell scripts
Are you proposing to use the same Groovy script for Log4Net and Log4cxx? Java is a rather big dependency to add to the build chain of those projects. We could find some other middle ground: * Node: it is already used by Antora and used in Log4Net and Log4j. You can also start if from the POM file (although this somehow makes the build instructions project-specific). * Python: is present on virtually each Linux distribution and has `tar` and `zip` support in the standard library. > - In "Reviewing a release", you say "Since the de facto source archive > is the Git repository". On the contrary, as much as Legal is concerned, de > facto source archive is the one distributed with SVN. _De jure_ the SVN artifacts are the source archive, but _de facto_ we almost never look at them. We assume that they have almost the same content as the Git repository, which is reviewed (theoretically) commit by commit. > There is the Artifact Distribution Platform project > <https://lists.apache.org/thread/bj68p377b6qvw1ms2x57x9l17pw5348l> of INFRA > – see its Slack channel <https://app.slack.com/client/T4S1WH2J3/C049WADAAQG>. > I think it is a better place to improve the release process, ASF-wide. Nice, I didn't know about that. Piotr
