Versions Compared

Old Version 56

changes.mady.by.user Dmitry Pavlov

Saved on

compared with

New Version 57

changes.mady.by.user Dmitry Pavlov

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: RC preparation steps

...

End of rampdown is code freeze. Code freeze is based on dates, but the actual time of freeze is determined by announcing.

P3. Stabilization

There During stabilization phase only blockers are accepted. Usually it should be approval of release manager to each commit.

Note blockers here is not only a critical bug, but an issue in the product which makes product unstable or non-functioning, performance drop has proven by a benchmark, a security issue, or a regression of existing features.

P4. Vote preparation

...

Sending Release For Vote

After the community agrees that the codebase is ready for a release, release manager should send the release for a vote.

The email subject should be "[VOTE] Apache Ignite <version> <rc>", e.g. "[VOTE] Apache Ignite 1.5.0.final RC3". Here is the sample email.

Code Block
languagexml
Dear Community,

We have uploaded release candidate to
https://dist.apache.org/repos/dist/dev/ignite/2.7.5-rc3/
 
The following staging can be used for a dependent project for testing:
https://repository.apache.org/content/repositories/orgapacheignite-1438/

This is very important release containing initial versions of Ignite.NET
and Ignite C++ and many other important features.

Tag name is
1.5.0.final-rc3

1.5.0 changes:
* Ignite.NET: Initial Release.
* Ignite C++: Initial Release.
* Massive performance improvements for cache operations and SQL.
* Added new binary cache object marshalling implementation.
* Added IgniteSemaphore data structure.
* Added MQTT Streamer.
* Added Twitter Streamer.
* Added Ignite Sink (integration with Apache Flume).
* Fixed optimistic serializable transactions: implemented "deadlock-free"
locking algorithm.
* Fixed failover for continuous queries.
* Fixed compilation and runtime errors under OpenJDK and IBM JDK.
* Fixed Integer.size limitation for cache.
* Fixed and improved cache types configuration.
* Fixed cache rebalancing.
* Many stability and fault-tolerance fixes.
* Added example to demonstrate the usage of EntryProcessor.

Complete list of closed issues:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%201.5%20AND%20status%20%3D%20closed

DEVNOTES
https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=refs/tags/1.5.0.final-rc3

RELEASENOTES
https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/1.5.0.final-rc3

The vote is formal, see voting guidelines https://www.apache.org/foundation/voting.html
+1 - to accept Apache Ignite 1.5.0.final-rc3
0 - don't care either way
-1 - DO NOT accept Apache Ignite 1.5.0.final-rc3 (explain why)

This vote will be open for 72 hours till May 23, 14:00 UTC.
https://www.timeanddate.com/countdown/to?year=2019&month=5&day=23&hour=14&min=0&sec=0&p0=utc-1

Release Verification

Check that all JIRA issues for the specific version are Closed (example JQL: `project = IGNITE AND fixVersion <= 1.7 AND status != closed`).

Code Block
languagebash
curl "https://issues.apache.org/jira/rest/api/2/search?jql=project=ignite%20AND%20status%20!=%20closed%20AND%20fixVersion<=1.7&fields=summary" | grep '"total":0,"issues":\[\]'

Check that sha1 & md5 checksum is correct. 

Code Block
languagexml
sha1sum -c *.sha1
md5sum -c *.md5

Check that signature is correct.

Code Block
languagexml
gpg --verify-files *.asc

...

Check licenses from the source code.

Code Block
languagexml
mvn clean validate -DskipTests=true -P check-licenses

Build the binary releases from the source code.

Code Block
languagexml
mvn clean package -DskipTests -Dignite.edition=hadoop
mvn clean package -DskipTests

Build Ignite.NET binaries and NuGet packages

Code Block
languagebash
cd modules\platforms\dotnet
build -skipJava

...

(building release candidate)

Once all changes are applied it is possible to prepare release candidate.

4.0. Prepare Release Notes

4.0.1. Collect Release Notes (this step is manual now). Check all completed tickets from the release page. Ticket may or may not have release notes, and this depends on if it is reasonable to mention change for users.

4.0.2. Optionally you may ask for review of resulting release notes on the list.

4.0.3. Update RELEASE_NOTES.txt and commit Release Notes changes into master and a release branch.

4.1. Update release branch versions

4.1.1. Update version in the master branch (execute script from Ignite project root directory): 

No Format
./scripts/update-versions.sh 2.7.5

 and commit changes. Source code will be published into SVN, so version update is required before RC building.

4.2. Prepare RC on Teamcity

4.2.1. Run [RELEASES] Apache Ignite / Main [1] Release Build for ignite-x.y or for ignite-x.y.z. branch. You will need to enter version number (value if x.y.0 or x.y.z), and specify release candidate number. For testing purposes it is recommended to use rc0. You may several times re-build same rc- number.

4.2.2.Download and unzip release archive. It can be found at "Artifacts" tab on build page. Example:

Expand

Image Added

Code Block
languagebash
themeRDark
linenumberstrue
~/download:[]$ unzip release-2.7.0-rc0.zip


4.3. Sign and deploy RC using vote preparation scripts

Run vote scripts to prepare RC before voting. You may skip steps 4.3.1 & step 4.3.2 in case you want to run some testing of release. In case release build it made for testing purposes, go to step 3 in this section.

4.3.1. Run script to create VCS tag in git 

Run ./vote_1\[git\]create_rc_tag.sh  Example of script output:

Expand


Code Block
languagebash
themeRDark
~/download/release:[]$ ./vote_1\[git\]create_rc_tag.sh 
Preparing vote 2.7.0-rc0
Removing obsolete tag...
2.7.0
-rc0
Deleted tag '2.7.0-rc0' (was b2119988f0)
Username for 'https://git-wip-us.apache.org': <your apache username here>
Password for 'https://nizhikov@git-wip-us.apache.org': <your apache password here>
To https://git-wip-us.apache.org/repos/asf/ignite
 - [deleted]               2.7.0-rc0
On branch master
Your branch is ahead of 'my/master' by 2 commits.
  (use "git push" to publish your local commits)

nothing to commit, working tree clean
Creating new tag...
Username for 'https://gitbox.apache.org': <your apache username here>
Password for 'https://nizhikov@gitbox.apache.org':   <your apache password here>
Counting objects: 1, done.
Writing objects: 100% (1/1), 166 bytes | 166.00 KiB/s, done.
Total 1 (delta 0), reused 0 (delta 0)
To https://gitbox.apache.org/repos/asf/ignite
 * [new tag]               2.7.0-rc0 -> 2.7.0-rc0
 
======================================================
RC tag should be created.
Please check results at 
https://gitbox.apache.org/repos/asf?p=ignite.git


Please, check corresponding git tag is created and is available in ASF repository: https://gitbox.apache.org/repos/asf?p=ignite.git;a=tags

4.3.2. Create & close (publish) staging repository

Note: If you've already uploaded staging, you should remove it from nexus - https://repository.apache.org/#stagingRepositories

Run script ./vote_2\[mvn\]\[pgp\]deploy_to_staging.sh  Example of script output:

Expand


Code Block
languagebash
themeRDark
~/download/release:[]$ ./vote_2\[mvn\]\[pgp\]deploy_to_staging.sh 
Preparing vote 2.7.0-rc0
Uploading ./org/apache/ignite/ignite-spark (1 of 53).
Uploading ./org/apache/ignite/ignite-clients (2 of 53).

...
Uploading ./org/apache/ignite/ignite-mqtt (53 of 53).
Uploaded
 
======================================================
Maven staging should be created
Please check results at
https://repository.apache.org/#stagingRepositories
Don't forget to close staging with proper comment



Go to Nexus UI https://repository.apache.org/#stagingRepositories, login using Apache credentials and close repository. Close is a heavy background process, which makes repository visible for others. Provide some comment for closing repository, e.g. `Repository for Apache Ignite 2.7.5 - RC2`. After some time check if repository was closed successfully.

4.3.3.1. Build DEB/RPM packages

? Probably this build step was migrated to TC and automated ?


Note: Following script is locale specific. You should execute it on the en locale

Run script ./vote_3_step_1\[packages\]build.sh . Example of output: 

Expand


Code Block
languagebash
themeRDark
~/download/release:[]$ ./vote_3_step_1\[packages\]build.sh 
...

dpkg-deb: building package 'apache-ignite' in '../apache-ignite_2.7.0-1_all.deb'.
copied '/tmp/tmp.rEePHrMMWU/apache-ignite_2.7.0-1_all.deb' -> '/home/dragon/download/release/packaging/apache-ignite_2.7.0-1_all.deb'
удалён '/tmp/tmp.rEePHrMMWU/apache-ignite_2.7.0-1_all.deb'
Removing temporary work directories: /tmp/tmp.rEePHrMMWU 

=== Run time: 0h:00m:36s ===

packaging/apache-ignite-2.7.0-1.noarch.rpm:
Processing packaging/apache-ignite_2.7.0-1_all.deb...
gpg: все значения, переданные в '--default-key', игнорируются
Signed deb packaging/apache-ignite_2.7.0-1_all.deb
mkdir: создан каталог 'packaging/pkg'
renamed 'packaging/apache-ignite-2.7.0-1.noarch.rpm' -> 'packaging/pkg/apache-ignite-2.7.0-1.noarch.rpm'
renamed 'packaging/apache-ignite_2.7.0-1_all.deb' -> 'packaging/pkg/apache-ignite_2.7.0-1_all.deb'


4.3.3.2. Sign artfacts

Run script vote_3_step_2[pgp]sign_artifacts.sh . Example of script output

Expand


Code Block
languagebash
themeRDark
~/download/release:[]$ ./vote_3_step_2\[pgp\]sign_artifacts.sh 
# Starting GPG Agent #
Signing ./svn/vote/apache-ignite-fabric-2.7.0-bin.zip
Signing ./svn/vote/apache-ignite-2.7.0-src.zip
Signing ./svn/vote/apache-ignite-hadoop-2.7.0-bin.zip
Signed OK.
 
===============================================
Artifacts should be signed
Please check results at ./svn/vote
Each file should have corresponding *.asc file

NOTE: Package files are not signed because they
are meant to be stored in Bintray



Please check results at ./svn/vote. Optionally you may also check hash/sign using https://www.apache.org/info/verification.html

4.3.3.3. Deploy artfacts to SVN

Run scrupt vote_3_step_3[svn]deploy_artifacts.sh Example of output:

Expand


Code Block
languagebash
themeRDark
~/download/release:[]$ ./vote_3_step_3\[svn\]deploy_artifacts.sh 
RC 2.7.0-rc0
Adding (binary)  svn/vote/apache-ignite-2.7.0-src.zip
Adding           svn/vote/apache-ignite-2.7.0-src.zip.asc
Adding           svn/vote/apache-ignite-2.7.0-src.zip.sha512
Adding (binary)   svn/vote/apache-ignite-fabric-2.7.0-bin.zip
Adding           svn/vote/apache-ignite-fabric-2.7.0-bin.zip.asc
Adding           svn/vote/apache-ignite-fabric-2.7.0-bin.zip.sha512
Adding (binary)   svn/vote/apache-ignite-hadoop-2.7.0-bin.zip
Adding           svn/vote/apache-ignite-hadoop-2.7.0-bin.zip.asc
Adding           svn/vote/apache-ignite-hadoop-2.7.0-bin.zip.sha512
Committing transaction...
Committed revision 29664.
Adding (binary)  packaging/pkg/apache-ignite-2.7.0-1.noarch.rpm
...




Check binaries and sources are available in the SVN: https://dist.apache.org/repos/dist/dev/ignite/ 

4.4. Verify Release changes using TeamCity

Compare with previous release.

There are TC task to generate report with difference comparing current release with previous.

https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency


You should run it and do sanity check for a changed files.

To start the build you need to specify current (staging) version and released version of Apache Ignite. See "Artifacts" tab to get task results. Example:

Expand

Image Added


For 2.7 release "apache-ignite-hadoop" removed and some new dependencies introduced for a benchmarks.

Image Added

4.5 Prepare NuGet staging

? Probably this should be done using https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages


4.6  Sending Release For Vote

After the community agrees that the codebase is ready for a release, release manager should send the release for a vote.

The email subject should be "[VOTE] Release Apache Ignite <version> <rc>", e.g. "[VOTE] Release Apache Ignite 2.7.5 RC4". 

Vote email should include reference that vote is formal and votes meaning for +1,0,-1.

Here is the sample email:

Expand


Code Block
languagexml
Dear Community,

We have uploaded release candidate to
https://dist.apache.org/repos/dist/dev/ignite/2.7.5-rc3/
 
The following staging can be used for a dependent project for testing:
https://repository.apache.org/content/repositories/orgapacheignite-1438/

This is very important release containing initial versions of Ignite.NET
and Ignite C++ and many other important features.

Tag name is
1.5.0.final-rc3

1.5.0 changes:
* Ignite.NET: Initial Release.
* Ignite C++: Initial Release.
* Massive performance improvements for cache operations and SQL.
* Added new binary cache object marshalling implementation.
* Added IgniteSemaphore data structure.
* Added MQTT Streamer.
* Added Twitter Streamer.
* Added Ignite Sink (integration with Apache Flume).
* Fixed optimistic serializable transactions: implemented "deadlock-free"
locking algorithm.
* Fixed failover for continuous queries.
* Fixed compilation and runtime errors under OpenJDK and IBM JDK.
* Fixed Integer.size limitation for cache.
* Fixed and improved cache types configuration.
* Fixed cache rebalancing.
* Many stability and fault-tolerance fixes.
* Added example to demonstrate the usage of EntryProcessor.

Complete list of closed issues:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%201.5%20AND%20status%20%3D%20closed

DEVNOTES
https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=refs/tags/1.5.0.final-rc3

RELEASENOTES
https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/1.5.0.final-rc3

The vote is formal, see voting guidelines https://www.apache.org/foundation/voting.html
+1 - to accept Apache Ignite 1.5.0.final-rc3
0 - don't care either way
-1 - DO NOT accept Apache Ignite 1.5.0.final-rc3 (explain why)

This vote will be open for 72 hours till May 23, 14:00 UTC.
https://www.timeanddate.com/countdown/to?year=2019&month=5&day=23&hour=14&min=0&sec=0&p0=utc-1


Examples of Voting threads Vote on 2.7.5; Vote on 2.7.0

Optionally you can create a separate discussion for questions related to RC: Discussion on 2.7.5

P5. Voting on Release and Release Verification

All community members are encouraged to verify release. PMC members have a binding vote, but each vote matters.

5.1 Checks

It is not complete list, community members can test any module or feature of the product.

Following list are steps, which can be done by each member, see also https://www.apache.org/info/verification.html

  • Check that all JIRA issues for the specific version are Closed (example JQL: `project = IGNITE AND fixVersion <= 1.7 AND status != closed`).

    Code Block
    languagebash
    curl "https://issues.apache.org/jira/rest/api/2/search?jql=project=ignite%20AND%20status%20!=%20closed%20AND%20fixVersion<=1.7&fields=summary" | grep '"total":0,"issues":\[\]'


  • Check that sha1 & md5 checksum is correct. 

    Code Block
    languagexml
    sha1sum -c *.sha1
md5sum -c *.md5


  • Check that signature is correct.

    Code Block
    languagexml
    gpg --verify-files *.asc


  • Check that version is correct.

  • Check licenses from the source code.

    Code Block
    languagexml
    mvn clean validate -DskipTests=true -P check-licenses


  • Build the binary releases from the source code.

    Code Block
    languagexml
    mvn clean package -DskipTests -Dignite.edition=hadoop
mvn clean package -DskipTests


  • Build Ignite.NET binaries and NuGet packages

    Code Block
    languagebash
    cd modules\platforms\dotnet
build -skipJava


  • Do some trivial checks, e.g. start local topology, run several examples from binaries gained at previous step. Unpacked binaries can be found at sources/target/release-package

5.1 Voting process


In case there is -1 vote present (it is not a veto, even if it was casted by PMC), release manager has ultimate rigth to cancel vote immediately to fix related issues. 

Usually +1 means that community member agrees that current release is better with previous.

Vote should be open for at least 72hours. In case insufficient votes are available vote can be kept open as long as it needed without additional announce. But in this case release manager has option to close the vote as unsuccessfull in case time is out. 

Info

Whenever consensus cannot be reached, standard Apache Voting Process will be used to reach a solution.

P6. Release

6.1. Closing Vote

After vote passes someone from PMC should do the following:

  • Upload documentation to https://svn.apache.org/repos/asf/ignite/site/trunk/releases/<version>

    Code Block
    languagexml
    svn import apache-ignite-fabric-<version>-bin/docs https://svn.apache.org/repos/asf/ignite/site/trunk/releases/<version> -m "new Release (<version>)" 


  • Update https://svn.apache.org/repos/asf/ignite/site/trunk/download.html (add new release to tables and mark them as latest, if necessary)

  • Move release to https://dist.apache.org/repos/dist/release/ignite/<version> 

    Code Block
    languagexml
    svn mv https://dist.apache.org/repos/dist/dev/ignite/<version><rc> https://dist.apache.org/repos/dist/release/ignite/<version> -m "Release <version>"


  • Create Release tag from RC tag

    Code Block
    languagexml
    git tag -a <version> -m "<version>"
git push origin <version>


  • Send an email with subject "[RESULT] [VOTE] Apache Ignite <version> Release (<rc>)", for example "[RESULT] [VOTE] Apache Ignite 1.4.0 Release (RC1)" and body similar to: 

    Code Block
    languagexml
    Hello!

Apache Ignite 1.4.0 release (RC1) has been accepted.

9 "+1" votes received.

Here are the votes received:

   - Denis Magda (binding)
   - Anton Vinogradov (binding)
   - Alexey Kuznetsov (binding)
   - Sergi Vladykin (binding)
   - Gianfranco Murador (binding)
   - Vladimir Ozerov (binding)
   - Raul Kripalani (binding)
   - Konstantin Boudnik (binding)
   - Chandresh Pancholi

Here is the link to vote thread -
http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-1-4-0-Release-RC1-tp3474.html
 
Ignite 1.4.0 successfuly released to https://dist.apache.org/repos/dist/release/ignite/1.4.0/

Thanks!

     


Post-release steps

After successful vote following actions should be done:

  1. Update version in the master branch (execute script and commit changes): ./scripts/update-versions.sh 2.9.0
  2. Release all the documentation (Java, .NET, C++, etc.) on apacheignite.readme.io. Make sure to update a documentation's version to a version of the release.
  3. Update the latest doc reference on ignite.apache.org:
    1. Update the new version number on the .htaccess file: RewriteRule ^releases/latest/(.*)$ /releases/1.9.0/$1 [L]
    2. Add the following tag to all .html files: <link rel="canonical" href="https://ignite.apache.org/releases/latest/LANGUAGE-DIR/FILENAME.html" />
    3. Use the script that automates the update or contact Mauricio Stekl (mauricio@gridgain.com) who can assist with this step.
  4. Update Ignite version in this file - https://ignite.apache.org/latest
  5. Mark JIRA version as released.
  6. Update https://ignite.apache.org with new download links, make sure to use [preferred]/[distdir] and [disturl]/[distdir]: https://svn.apache.org/repos/asf/ignite/site/trunk
  7. Prepare the cloud images and update links to them here https://ignite.apache.org/download.cgi#docker. In addition, update the links to the images on the following documentation pages whenever is needed:
    1. http://apacheignite.gridgain.org/docs/docker-deployment
    2. https://apacheignite.readme.io/docs/aws-deployment
    3. https://apacheignite.readme.io/docs/google-compute-deployment
  8. Update Web Console docker image: https://hub.docker.com/r/apacheignite/web-console-standalone/tags/
  9. Delete previous releases from https://dist.apache.org/repos/dist/release/ignite/..., replace their download URLs by https://archive.apache.org/dist/ignite/...
  10. Release maven staging (https://maven.apache.org/developers/release/maven-project-release-procedure.html).
  11. Upload .NET NuGet packages to nuget.org. Credentials can be found in https://svn.apache.org/repos/private/pmc/ignite/credentials/nuget.org (PMC only).
  12. Make sure that the artifacts were synced up to http://repo2.maven.org/maven2/org/apache/ignite/ and Maven Central. Refer to the recently happened issue (
    Jira
    serverASF JIRA
    serverId5aa69414-a9e9-3523-82ec-879b028fb15b
    keyINFRA-13073
    )
  13. Announce the release by sending a single message to announce@apache.org and Ignite's user/dev lists. Refer to the examples below:
    1. http://apache-ignite-developers.2346864.n4.nabble.com/ANNOUNCE-Apache-Ignite-2-1-0-Released-td20145.html
  14. Announce security vulnerabilities that were fixed in the release following the ASF process https://www.apache.org/security/committers.html. Check with security@ignite.apache.org if there are any vulnerabilities. 

Notice

Tip
This page was merged from several sources contributed by Nikolay Izhikov, Anton Vinogradov ,Denis Magda , Dmitry Pavlov , Pavel Tupitsyn, Vladimir Ozerov, Alexey Kuznetsov, Yakov Zhdanov

There are several unresoved issues / open questions:

Warning

1. Can committer be release manager and upload artifacts provided that PMC will upload committer's key

Steps to be done for prepare Nuget packages

Steps to be done for prepare RPM/DEB packages - step 4.3.3.1

Closing Vote

After vote passes someone from PMC should do the following:

Upload documentation to https://svn.apache.org/repos/asf/ignite/site/trunk/releases/<version>

Code Block
languagexml
svn import apache-ignite-fabric-<version>-bin/docs https://svn.apache.org/repos/asf/ignite/site/trunk/releases/<version> -m "new Release (<version>)" 

...

Move release to https://dist.apache.org/repos/dist/release/ignite/<version> 

Code Block
languagexml
svn mv https://dist.apache.org/repos/dist/dev/ignite/<version><rc> https://dist.apache.org/repos/dist/release/ignite/<version> -m "Release <version>"

Create Release tag from RC tag

Code Block
languagexml
git tag -a <version> -m "<version>"
git push origin <version>

...

Send an email with subject "[RESULT] [VOTE] Apache Ignite <version> Release (<rc>)", for example "[RESULT] [VOTE] Apache Ignite 1.4.0 Release (RC1)" and body similar to: 

Code Block
languagexml
Hello!

Apache Ignite 1.4.0 release (RC1) has been accepted.

9 "+1" votes received.

Here are the votes received:

   - Denis Magda (binding)
   - Anton Vinogradov (binding)
   - Alexey Kuznetsov (binding)
   - Sergi Vladykin (binding)
   - Gianfranco Murador (binding)
   - Vladimir Ozerov (binding)
   - Raul Kripalani (binding)
   - Konstantin Boudnik (binding)
   - Chandresh Pancholi

Here is the link to vote thread -
http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-1-4-0-Release-RC1-tp3474.html
 
Ignite 1.4.0 successfuly released to https://dist.apache.org/repos/dist/release/ignite/1.4.0/

Thanks!

 

Info

Whenever consensus cannot be reached, standard Apache Voting Process will be used to reach a solution.

Post-release steps

After successful vote following actions should be done:

...

  1. Update the new version number on the .htaccess file: RewriteRule ^releases/latest/(.*)$ /releases/1.9.0/$1 [L]
  2. Add the following tag to all .html files: <link rel="canonical" href="https://ignite.apache.org/releases/latest/LANGUAGE-DIR/FILENAME.html" />
  3. Use the script that automates the update or contact Mauricio Stekl (mauricio@gridgain.com) who can assist with this step.

...

  1. http://apacheignite.gridgain.org/docs/docker-deployment
  2. https://apacheignite.readme.io/docs/aws-deployment
  3. https://apacheignite.readme.io/docs/google-compute-deployment

...

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

...

  1. http://apache-ignite-developers.2346864.n4.nabble.com/ANNOUNCE-Apache-Ignite-2-1-0-Released-td20145.html

...