Page History

...

4.1. Update release branch versions

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

...

Go to Nexus UI https://repository.apache.org/#stagingRepositories, login using Apache credentials and release repository for accepted release candidate. You can release it by pressing the Release button (provided that you have successfully closed the staging repository).

This will move the components into the release repository of OSSRH where it will be synced to the Central Repository (see also https://central.sonatype.org/pages/releasing-the-deployment.html#close-and-drop-or-release-your-staging-repository)

The sync into Maven Central central staging from repository.apache.org occurs every 4 hours. There is a separate hourly schedule that runs which pushes from staging to the other central machines, and then updates the indexes.

...

1. If release step for staging was successful you can access artifacts using service repository:

...

1.   https://repository.apache.org/service/local/repositories/releases/content/org/apache/ignite/ignite-core/2.7.5/
2. Once repository is synced you can see result in 

...

1. 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

6.3.2. Update sources snapshot version in the master branch

...

Execute script from Ignite project root directory, this will update version in the master branch : 

No Format
./scripts/update-versions.sh 2.9.0-SNAPSHOT

 and commit changes. This step is not required if minor release was issued,e.g. 2.7.5

Post-release steps

After successful vote following actions should be done:

1. 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.
2. 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.

1. Update Ignite version in this file - https://ignite.apache.org/latest
2. Mark JIRA version as released.
   
3. 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

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

1. 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
2. Update Web Console docker image: https://hub.docker.com/r/apacheignite/web-console-standalone/tags/
3. Delete previous releases from https://dist.apache.org/repos/dist/release/ignite/..., replace their download URLs by https://archive.apache.org/dist/ignite/...
4. 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).
5. 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
   server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key INFRA-13073

   )
6. 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
      
7. 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. 

...

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

There are several unresoved issues / open questions:

...