Igniters,
I have cut the release branch: 'ignite-2.13'. Please, cherry-pick new
issues if needed.
The 2.13 scope is freezed. Unresolved not-blocking issues will be
moved on the code freeze stage. The planning release date was updated
[1]:
Scope Freeze: March 25, 2022
Code Freeze: April 8, 2022
V
Hello, Igniters.
I have created the 2.13 release page. [1]
The new SQL Calcite engine is expected to merge in the coming week.
[2] I suggest cutting the 2.13 branch after the merge. I've updated
the planned release dates on the release page.
[1] https://cwiki.apache.org/confluence/display/IGNITE
Guys,
+1 to await merge of the Calcite SQL engine before code-freeze phase
and release branch cutting. Other features and fixes can be awaited
too, it's discussable.
But the 2.12 branch was cut on October 15, 2021. There are many fixes
and features that were merged into the master during this per
> I «vote» for more frequent releases.
+1
Hotfixes, eg. 2.12.1, should be released asap (no need to wait for 2.13).
And it's ok to release 2.13 without fixes planned for 2.12.1 since not all
users are affected but some wait for features like "Consistency check &
repair".
On Thu, Feb 10, 2022 at
Maxim, i think that more frequent releases are useful.
Ready to release branch means that it passed all known tests and also have an
appropriate votes.
More code changes creates more difficulties in final tests and sometimes
migration.
No need to switch between neighbor minor versions for user i
