Hi team, if you don't mind, I would like to release next artifacts: - parent 3.1.0 -> 3.2.0 (javadoc plugin changes to run javadoc as part of the default build) - spi-fly 1.3.7 -> 1.3.8 (all artifacts from reactor, mostly dependencies bumps and fix ARIES-2241)
Current spi-fly supports LST Java 8 - 21 and the follow up step after the release could be merging https://github.com/apache/aries/pull/815 that moves Java versions to 17 - 25 range by using new bnd. Next releases could be then planned for spi-fly. If there is no veto I would like to start releases of parent and spi-fly next week (Aug 31st - Sep 4th). WDYT? When the release above is successful then i would like to release next: - proxy-api 1.1.1 -> 1.1.2 (ARIES-2175 fix osgi dependency declaration, refreshing release) - proxy-impl 1.1.14 -> 1.1.15 (dependencies bump, updates for Java versions up to 25, adding objenesis as the dependency) - quiesce-api 1.0.0 -> 1.0.1 (ARIES-2175 fix osgi dependency declaration, refreshing release) - quiesce-manager 1.0.0 -> 1.0.1 (ARIES-2175 fix osgi dependency declaration, refreshing release) Why quiesce and proxy artifacts? We knows those artifacts are passing the tests on LTS Java 8 - 25 and both are dependencies for blueprint (that supports only java 8 right now) so we should be unblock from this perspective for next blueprint changes and releases. Again, WDYT? -- Regards, Dominik Przybysz
