ID | IEP-69 |
Author | |
Sponsor | |
Created |
|
Status | DRAFT |
It is hard to believe that modern distributed databases can live for years without having releases with breaking backwards compatibility changes as the Apache Ignite does. The lot of @deprecated methods in the API and many obsolete documentation pages leads to a bad user experience. Moreover, the same problem exists for maintaining the obsolete source code for developers and blocks using modern technologies and the latest development language features.
Here are a few Apache project examples with the same approach:
Use three digits for the version of Apache Ignite: grand.major.bug-fix[-rc_number]
...
turn off atomic operation inside transactions by default
deny async operation inside transactions
...
I think the grand release version which contains the new Ignite architecture must be determined when the pre-release source code will be available.
// Links to discussions on the devlist, if applicable.http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-IEP-69-The-evolutionary-release-process-td51655.html
// Links to various reference documents, if applicable.
...