hboutemy commented on code in PR #1836: URL: https://github.com/apache/maven-site/pull/1836#discussion_r4610035908
########## content/markdown/developers/compatibility-plan.md: ########## @@ -39,6 +39,7 @@ Consolidated view for all LATEST plugins release is visible in a [daily generate - In April 2023, Maven before 3.6.3 has been [marked as EOL](/docs/history.html#Maven_3.8.x_and_before), meaning that plugins should use 3.6.3 as minimum - In February 2024, Maven 4 after 4.0.0-alpha-12 will require Java 17 (as per [vote on the Mailing List](https://lists.apache.org/thread/bfkvvjftrxypp06yj8zj919fcz0dt2zt)). - In October 2025, Maven before 3.8.3 has been [marked as EOL](/docs/history.html#Maven_3.8.x_and_before), [PR#842](https://github.com/apache/maven-site/pull/842) meaning that plugins should use 3.9.0 as minimum (as per [Mailing List](https://lists.apache.org/thread/s2dvm1jg37vhrkkkplfknk494c68zfyv)) +- Maven 3.x plugins must be compatible with Maven 4.0. With the release of Maven 4.0, the Maven 4 plugin API [will only be experimental](https://lists.apache.org/thread.html/7dmfmy8hlvbtl7xlhfzz1mqwz08j61kw). Review Comment: "must" (as in RFC-way MUST) or "are expected to be"? I think Maven 4 deserves a dedicated paragraph to clearly state: - situation on Maven 4.0 (near future, we can consider now) - future 4.2 can we work on a shared Git branch, to avoid the PR review only mode of feedback -- 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]
