...

4.3.1. Run script to create VCS tag in git 

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

...

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

For build number requested in this build step configuration, you should take build number (Teamcity identification of builds) from release candidate preparation Run Configuration from step 4.2.1.

4.6  Sending Release For Vote

...

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

5.1 Checks

...

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

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

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

  Code Block
  language bash
  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
  language xml
  sha1sum -c *.sha1 md5sum -c *.md5

  
  

• Check that signature is correct.

  Code Block
  language xml
  gpg --verify-files *.asc

  
  

• Check that version is correct.

• Check licenses from the source code.

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

  
  

• Build the binary releases from the source code.

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

  
  

• Build Ignite.NET binaries and NuGet packages

  Code Block
  language bash
  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

...

P6. Release

6.1. Closing Vote

After vote passes someone from PMC should do the following:

...

Send an email with subject "[RESULT] <vote subject>" ("[RESULT] [VOTE] Release Apache Ignite <version> (<rc>)") and provide vote results: if it passes or not, provide voting details. 

For example, "[RESULT] [VOTE] Release Apache Ignite 2.7.5 (RC1)" and body similar to 2.7.5 vote result, 2.7.0 vote result . See also other example:

...

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> 

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

git tag -a <version> -m "<version>"
git push origin <version>

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!

In case vote is unsuccessful or closed by release manager, prepare new release candidate with fixes starting from step 4.2

6.2. Run Release scripts

In case vote was sucessfull, run release* scripts from RC home

6.2.1. Move binaries

Run release_1[svn]move_binaries.sh Example of output

> ./release_1\[svn\]move_binaries.sh

# Releasing 2.7.5-rc4 :: Binaries #
Committing transaction...
Committed revision 34469.

=========================================================
Artifacts should be moved to Apache Ignite's release site
Please check results at:
 * binaries: https://apache.org/dist/ignite/2.7.5

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

Please check results at:
* binaries:  https://apache.org/dist/ignite/{version} ← sync issue or delay here ?

Result should be available at https://dist.apache.org/repos/dist/release/ignite/

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

  Code Block
  language xml
  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)

• 
  

• Create Release tag from RC tag

  Code Block
  language xml
  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: 

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!

...