...
Make sure that the artifacts were synced up to Maven Central. Refer to the recently happened issue (
) Jira server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key INFRA-13073
Usually, this sync should be completed in 4 hours after releasing repository at step 6.3.1. If it is not released, contact infra.
Create a new issue to enforce compatibility checks and prepare the PR. Ask for a review on dev-list if necessary.
Jira server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key IGNITE-13833
Announce the release by sending a single message to announce@apache.org and Ignite's user/dev lists.
Please not note that announce list is ASF-level list and not all subscribers are aware about of Apache Ignite. So it is recommended to include a short description of the project.
Refer to the examples below:
...
If release includes any fixes for the security issue, then announce security vulnerabilities that were fixed in the release.
...
There are several unresoved unresolved issues / open questions:
Warning |
---|
6. Unclear on how to prepare/update 6.3.11.GCE&AWSvirtualmachines 7. Steps to be done for to upload RPM/DEB packages |