Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

6.3.14. Check artifacts are available in Maven Central

Make sure that the artifacts were synced up to  Maven Central. Refer to the recently happened issue (

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyINFRA-13073
)

  1. Once the repository is synced you can see the result in http://repo2.maven.org/maven2/org/apache/ignite/ 
  2. With some delay, artifact will be available on the site https://mvnrepository.com/artifact/org.apache.ignite/ignite-core

Usually, this sync should be completed in 4 hours after releasing repository at step 6.3.1. If it is not released, contact infra.

6.3.15. Update compatibility check versions

Create a new issue to enforce compatibility checks and prepare the PR. Ask for a review on dev-list if necessary.

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyIGNITE-13833

6.4. Announce the release

6.4.1. Send release announce to Apache Lists

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.

...

Open Issues

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