...
Gliffy Diagram |
---|
name | Ignite Release Process |
---|
pagePin | 12 |
---|
|
P0. Initializing
Release phases dates are discussed, as release manager during the first discussion. Release Manager should be PMC Member.
...
Expand |
---|
Code Block |
---|
| Dear Community,
We have uploaded release candidate to
https://dist.apache.org/repos/dist/dev/ignite/2.7.5-rc3/
The following staging can be used for a dependent project for testing:
https://repository.apache.org/content/repositories/orgapacheignite-1438/
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%20closedproject+%3D+IGNITE+AND+fixVersion+%3D+1.5+AND+status+%3D+closed
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
The vote is formal, see voting guidelines https://www.apache.org/foundation/voting.html
+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 be open for 72 hours till May 23, 14:00 UTC.
https://www.timeanddate.com/countdown/to?year=2019&month=5&day=23&hour=14&min=0&sec=0&p0=utc-1 |
|
...
Check that all JIRA issues for the specific version are Closed (example JQL: `project = IGNITE AND fixVersion <= 1.7 AND status != closed`).
Code Block |
---|
|
curl "https://issues.apache.org/jira/rest/api/2/search?jql=project=ignite%20AND%20status%20ignite+AND+status+!=%20closed%20AND%20fixVersion<+closed+AND+fixVersion<=1.7&fields=summary" | grep '"total":0,"issues":\[\]' |
Check that sha1 & md5 checksum is correct.
Code Block |
---|
|
sha1sum -c *.sha1
md5sum -c *.md5 |
Check that signature is correct.
Code Block |
---|
|
gpg --verify-files *.asc |
- Check that version is correct.
Check licenses from the source code.
Code Block |
---|
|
mvn clean validate -DskipTests=true -P check-licenses |
Build the binary releases from the source code.
Code Block |
---|
|
mvn clean package -DskipTests -Dignite.edition=hadoop
mvn clean package -DskipTests |
Build Ignite.NET binaries and NuGet packages
Code Block |
---|
|
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
...