paulrutter commented on PR #581: URL: https://github.com/apache/felix-dev/pull/581#issuecomment-6652835439
## Bundles to release These are the artifacts that have to be released after this PR is merged. Each one gets its own version and tag (`<artifactId>-<version>`): | Bundle | Last release (r16) | Release version | Tag | |---|---|---|---| | `org.apache.felix.dependencymanager` | 4.6.1 | 5.0.0 | `org.apache.felix.dependencymanager-5.0.0` | | `org.apache.felix.dependencymanager.annotation` | 5.0.2 | 6.0.0 | `org.apache.felix.dependencymanager.annotation-6.0.0` | | `org.apache.felix.dependencymanager.runtime` | 4.0.8 | 5.0.0 | `org.apache.felix.dependencymanager.runtime-5.0.0` | | `org.apache.felix.dependencymanager.shell` | 4.0.9 | 5.0.0 | `org.apache.felix.dependencymanager.shell-5.0.0` | | `org.apache.felix.dependencymanager.lambda` | 1.2.2 | 2.0.0 | `org.apache.felix.dependencymanager.lambda-2.0.0` | | `dependencymanager-parent` (pom) | new | 1.0.0 | `dependencymanager-parent-1.0.0` | Not released: the integration test, sample and benchmark modules (`maven.deploy.skip` and `maven.install.skip`). All five bundles need a new release: they all move to a new major version because the minimum Java version is now 11, and none of their exported packages changed (baseline against r16 reports no API changes). Prerequisites, all in place now: the integration tests run on Felix Framework 8.0.0, Config Admin 1.10.0 and Gogo runtime 1.2.0 (shell 1.1.4, command 1.1.2), which are released and pinned in `dependencymanager/pom.xml`. Before `release:prepare`, fill in the final entries at the top of the six `changelog.txt` files and make sure the Jira version for FELIX-6872 exists. The release itself is one `mvn release:prepare release:perform` from `dependencymanager/`, with a single staging repository and a single vote for all bundles. -- 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]
