Versions Compared

Old Version 67

changes.mady.by.user Dmitry Pavlov

Saved on

compared with

New Version 68

changes.mady.by.user Dmitry Pavlov

Saved on

Key

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

...

6.3.4. Release documentaion on readme.io

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.

6.3.5. Update reference to docs from site

Update the latest doc reference on ignite.apache.org:

  1. Update the new version number on the .htaccess file: RewriteRule ^releases/latest/(.*)$ /releases/2.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.

6.3.6. Prepare HTML release notes from text release notes

Checkout SVN repository for Apache Ignite site: https://svn.apache.org/repos/asf/ignite/site/trunk

For speed up this operation make sure to limit branches in checkout operation.

Just copy-paste latest release notes from previous release, replace text formatting with headers, lists items.

Place these notes to corresponding release folder, for example releases/2.7.5. If folder is absent, check results of step 6.2.3.

Commit changes. File should be available on the site automatically. 

...

6.3.8. Update version for generating users advices to update

Find latest `latest` text file in SVN repository for Apache Ignite site.

Update Ignite version in this file. Commit changes and check result at https://ignite.apache.org/latest

6.3.9. Mark JIRA version as released

Go to JIRA project administration, select Apache Ignite, select Versions, select appropriate version and select Actions->Release.

6.3.10. Prepare cloud images

Todo: add description of steps ? 

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

6.3.11. Update Web Console docker

Todo add description of the step ?

Update Web Console docker image: https://hub.docker.com/r/apacheignite/web-console-standalone/tags/

6.3.12. Delete previous

releases

release from dist SVN directory

Delete previous releases from https://dist.apache.org/repos/dist/release/ignite/..., replace their download URLs by https://archive.apache.org/dist/ignite/...

6.3.13. Upload NuGet packages to nuget.org

Where and how to get these package?

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

6.3.14. Check artifacts are available in Maven Central

Make sure that the artifacts were synced up

to http://repo2.maven.org/maven2/org/apache/ignite/ and Maven

to  Maven Central. Refer to the recently happened issue (

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

  1. Once repository is synced you can see 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 comleted in 4 hours after releasing repository at step 6.3.1. If it is not released, contat infra.

6.4. Announce 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 that announce list is ASF-level list and not all subscribers are aware about Apache Ignite. So it is recommended to include short description of project.

Refer to the examples below:

Announce the release by sending a single message to announce@apache.org and Ignite's user/dev lists. Refer to the examples below:

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


http://apache-ignite-

developers

users.

2346864

70518.

n4

x6.nabble.com/ANNOUNCE-Apache-Ignite-2-

1

6-0-Released-

td20145

td22760.html

Announce

6.4.2. Announce security vulnerabilities

If release includes any fixes for security issue, then announce security vulnerabilities that were fixed in the release

...

.

Follow 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 , Andrey Gura , Vladimir Ozerov Ozerov , Alexey Kuznetsov , Yakov Zhdanov

...

Warning

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

2. Details on Steps to be done for prepare Nuget packages

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

4. Unclear how to release documenation on readme io - step 6.3.4

5. Unclear how to prepare Step 6.3.10. Prepare cloud images

6. Unclear how to prepare/update Web Console docker. Step 6.3.11

7. Unclear how and where to get nuget package.