hboutemy commented on issue #212: URL: https://github.com/apache/maven-gh-actions-shared/issues/212#issuecomment-3550201139
there has always been a choice done between 2 approaches: 1. publish plugin/component documentation as soon as possible, then for SNAPSHOTs => found "not useful" as not releases 2. publish plugin/component documentation for releases => found late (= what it described in this issue) for now, approach 2 won at ASF Maven (and Plexus and Mojohaus), while for example approach 1 won at [CycloneDX Maven plugin](https://cyclonedx.github.io/cyclonedx-maven-plugin/) how to have best of both worlds? good question: ideas welcome is it a question for GHA? perhaps one day, yes, but AFAIK it all starts with clarifying what doc updates can be published after the "current" release and what doc updates should wait for the next release => if we clarify by hand what we do at Git level (Git tags and commits in branches) and how we build, we'll see what automation can help -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
