Page History

...

• 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

See also Incubator Release Checklist for more checks.

5.

...

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

Usually with +1 member shares which checks were done.

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. 

...