...

1.2.1. Create release branch, e.g ignite-2.8, push it to the ASF repository. (optional) consider creating PR for release, having PR is convinient because GitHub will notify you about commits to the branch.

1.2.2. Run TC tests (on the appropriate branch), use https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RunAllNightly

...

P4. Vote preparation (building release candidate)

Once all changes are applied, it is possible to prepare a release candidate. It is possilbe to build several release candidates without starting a vote. First RCs can have part of changes scheduled for release.

4.0. Prepare Release Notes

...

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

4.1. Update

...

versions and year

...

for release

4.1.1. Update release branch version in maven poms and assembly

 Update version in the release branch (execute the script from Ignite project root directory, you can use WSL or GitBash on Windows): 

...

 and commit changes. This step is essential for release because later the source code will be published into SVN. Version update is required to be committed before RC building.

4.1.2. Update year in copyright messages

 Double Double-check that year in copyright messages is correct. If the release is minor and based on an older branch, this branch can contain an outdated value of the year. Fix if needed. Example commit of updating year.

4.1.3. (Not  Following step is not actual since 2.8, there is the feature for an auto-generating year). : Update copyright year manually in IgniteVersionUtils

4.1.3. Update DEB & RPM package version

Version of packages update is not automated since it requires to add verison to history to update it. Update is more or less similar to this commit

4.1.3.1. Update packaging/deb/changelog, add similar lines to the top of the files (version, comment, mainteiner, date):

apache-ignite (2.7.6) unstable; urgency=low

  * Updated Apache Ignite to version 2.7.6

 -- Petr Ivanov <mr.weider@gmail.com>  Fri, 20 Aug 2019 20:58:44 +0300

4.1.3.2. Update packaging/rpm/apache-ignite.spec, change current version; insert new line to changes log:

Name:             apache-ignite
Version:          2.7.6 

and add lines similar to following after change log

* Fri 20 Aug 2019 Peter Ivanov <mr.weider@gmail.com> - 2.7.6
- Updated Apache Ignite to version 2.7.6

4.1.3.3. (optional) ask for review

4.1.3.4. Commit package version changes into master and a release branch.

4.2. Prepare RC on Teamcity

...