After community agrees that codebase is ready for the release. Release should be sent for vote.
Subject should be "[VOTE] Apache Ignite <version> <rc>", for example "[VOTE] Apache Ignite 1.5.0.final RC3". Here is the sample email which can help to identify steps that are required.
Dear Sirs! We have uploaded release candidate to https://dist.apache.org/repos/dist/dev/ignite/1.5.0.final-rc3/ This is very important release containing initial versions of Ignite.NET and Ignite C++ and many other important features. Tag name is 1.5.0.final-rc3 1.5.0 changes: * Ignite.NET: Initial Release. * Ignite C++: Initial Release. * Massive performance improvements for cache operations and SQL. * Added new binary cache object marshalling implementation. * Added IgniteSemaphore data structure. * Added MQTT Streamer. * Added Twitter Streamer. * Added Ignite Sink (integration with Apache Flume). * Fixed optimistic serializable transactions: implemented "deadlock-free" locking algorithm. * Fixed failover for continuous queries. * Fixed compilation and runtime errors under OpenJDK and IBM JDK. * Fixed Integer.size limitation for cache. * Fixed and improved cache types configuration. * Fixed cache rebalancing. * Many stability and fault-tolerance fixes. * Added example to demonstrate the usage of EntryProcessor. Complete list of closed issues: https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%201.5%20AND%20status%20%3D%20closed DEVNOTES https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=refs/tags/1.5.0.final-rc3 RELEASENOTES https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/1.5.0.final-rc3 Please start voting. +1 - to accept Apache Ignite 1.5.0.final-rc3 0 - don't care either way -1 - DO NOT accept Apache Ignite 1.5.0.final-rc3 (explain why) This vote will go for 72 hours.
Before sending vote (esp. +1) everyone should do the following:
Check that sha1 & md5 checksum is correct.
sha1sum -c *.sha1 md5sum -c *.md5
Check that signature is correct.
gpg --verify-files *.asc
Check licenses from the source code.
mvn clean validate -DskipTests=true -P check-licenses
Build the binary releases from the source code.
mvn clean package -DskipTests -Dignite.edition=hadoop mvn clean package -DskipTests
After vote passes someone from PMC should do the following:
Upload documentation to https://svn.apache.org/repos/asf/ignite/site/trunk/releases/<version>
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>
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!
Whenever consensus cannot be reached, standard Apache Voting Process will be used to reach a solution.