Roman, Hi.
The Spring dependency has been updated in the IGNITE-16781 that's in
the 2.13 scope.
ср, 20 апр. 2022 г. в 19:28, Roman Puchkovskiy :
>
> Hi Nikita.
>
> You already know this, just stating for the record: vulnerable Spring
> versions in ignite-extensions were replaced with the latest
Hi Nikita.
You already know this, just stating for the record: vulnerable Spring
versions in ignite-extensions were replaced with the latest patched
(and safe) versions in [1].
[1] - https://issues.apache.org/jira/browse/IGNITE-16869
пн, 18 апр. 2022 г. в 18:11, Nikita Amelchev :
>
> Hi, Roman.
Hi, Roman.
Vulnerable Spring Boot is used in Ignite extensions. AI 2.13 releases
ignite-parent that will be used for extensions to share versions. I
will cherry-pick the patch.
Thank you.
пн, 18 апр. 2022 г. в 15:00, Roman Puchkovskiy :
>
> Hi Igniters.
>
> A fix for CVE-2022-22965 [1]
Hi Igniters.
A fix for CVE-2022-22965 [1] vulnerability was merged to master branch
recently, Jira issue is [2].
I'm not sure whether this is a blocker, but the vulnerability seems to
be pretty bad.
Should it be cherry-picked to release 2.13?
[1] -
I'm announcing a code freeze for the 2.13 release [1]. Only blockers
are accepted to be included to the scope.
[1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.13
пн, 28 мар. 2022 г. в 12:39, Nikita Amelchev :
>
> Guys,
>
> Could you help with the TC bot configuration to
Guys,
Could you help with the TC bot configuration to the `ignite-2.13`
release branch?
пн, 28 мар. 2022 г. в 09:22, Zhenya Stanilovsky :
>
>
> Thanks Nikita, cherry-picked: IGNITE-16742 Extend calcite module
> documentation.
>
>
>
> >Igniters,
> >
> >I have cut the release branch:
Thanks Nikita, cherry-picked: IGNITE-16742 Extend calcite module documentation.
>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
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
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]
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
> 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
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
Hi, guys!
Ignite 2.12 was released on 17th Jan. And here is a plan to release 2.13 on
28 Mar. It is only 2.5 months between those versions. IMHO, it's better to
have more time between releases:
1. We had some bug reports after releasing 2.11, and it can be worth
waiting for users feedback about
Nikita,
Thank you for starting this thread.
+1 for these dates, but I think it's better to start the code freeze
date when the Calcite engine will be actually merged to the master
branch.
On Tue, 8 Feb 2022 at 13:10, Nikita Amelchev wrote:
>
> Dear Ignite Community!
>
> I suggest starting
Dear Ignite Community!
I suggest starting Apache Ignite 2.13 release activities.
There is a plan to merge the new Calcite SQL engine. [1] I think that
2.13 is a good candidate for it.
Moreover, we've accumulated a hundred resolved [2] issues with new
features and bug fixes which are waiting for
15 matches
Mail list logo
