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] - https://nvd.nist.gov/vuln/detail/CVE-2022-22965 [2] - https://issues.apache.org/jira/browse/IGNITE-16781 пн, 11 апр. 2022 г. в 19:53, Nikita Amelchev <namelc...@apache.org>: > > 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 <namelc...@apache.org>: > > > > Guys, > > > > Could you help with the TC bot configuration to the `ignite-2.13` > > release branch? > > > > пн, 28 мар. 2022 г. в 09:22, Zhenya Stanilovsky > > <arzamas...@mail.ru.invalid>: > > > > > > > > > > > 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 planning release date was updated > > > >[1]: > > > > > > > >Scope Freeze: March 25, 2022 > > > >Code Freeze: April 8, 2022 > > > >Voting Date: April 15, 2022 > > > >Release Date: April 22, 2022 > > > > > > > >[1] > > > >https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.13 > > > > > > > >чт, 10 мар. 2022 г. в 16:17, Nikita Amelchev < namelc...@apache.org >: > > > >> > > > >> 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/Apache+Ignite+2.13 > > > >> [2] https://lists.apache.org/thread/3fkq3mn2npz326bp6gjtw3sw8xrlqyho > > > >> > > > >> чт, 10 февр. 2022 г. в 15:23, Nikita Amelchev < namelc...@apache.org >: > > > >> > > > > >> > 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 period. The > > > >> > total time between branches cut is 5 months (if there is no delay > > > >> > happens). Seems it is not so frequently. > > > >> > > > > >> > чт, 10 февр. 2022 г. в 15:17, Zhenya Stanilovsky < > > > >> > arzamas...@mail.ru.invalid >: > > > >> > > > > > >> > > > > > >> > > 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 if all > > > >> > > work properly well. > > > >> > > I «vote» for more frequent releases. > > > >> > > > > > >> > > > > > > >> > > >> > > > >> > > >>>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 2.12. Also meetup with > > > >> > > >>>description of 2.12 > > > >> > > >>>will be only next week (16 Feb). > > > >> > > >>>2. In my understanding, users don't switch between versions of > > > >> > > >>>databases > > > >> > > >>>frequently. Actually it's hard work to upgrade such a > > > >> > > >>>dependency. So, no > > > >> > > >>>need for continuous delivery here. I think it's a common > > > >> > > >>>practice, for > > > >> > > >>>example, MongoDB releases 1 time per year, Cassandra 2 times. > > > >> > > >>>CockroachDB > > > >> > > >>>releases minor versions every month, but major versions are > > > >> > > >>>still released > > > >> > > >>>2 times a year. But I'm not aware of all databases. > > > >> > > >>> > > > >> > > >>>I think we should move dates for at least 1 month. Also it > > > >> > > >>>depends on the > > > >> > > >>>Calcite engine readiness. WDYT? > > > >> > > >>> > > > >> > > >>>Anyway, from my side there are some tickets I want to include > > > >> > > >>>to the next > > > >> > > >>>release scope: > > > >> > > >>>1. Partition reservation for cache queries (it will make > > > >> > > >>>IndexQuery work on > > > >> > > >>>unstable topology): IGNITE-16030 and IGNITE-16031 > > > >> > > >>> > > > >> > > >>>2. Also there is a discussion started by Andrey Mashenlov about > > > >> > > >>>known index > > > >> > > >>>corruption scenarios [1]. It looks like there are at least 2 > > > >> > > >>>issues to > > > >> > > >>>resolve: dropping of affinity index, handle of orphaned > > > >> > > >>>indexes. I think we > > > >> > > >>>should fix those known issues before the next release. WDYT? > > > >> > > >>> > > > >> > > >>>[1] > > > >> > > >>>https://lists.apache.org/thread/m6dt0pn1qb01d8w6zm2fvo7lxgt0r068 > > > >> > > >>> > > > >> > > >>> > > > >> > > >>>On Wed, Feb 9, 2022 at 3:13 PM Maxim Muzafarov < > > > >> > > >>>mmu...@apache.org > wrote: > > > >> > > >>> > > > >> > > >>>> 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 < > > > >> > > >>>> namelc...@apache.org > wrote: > > > >> > > >>>> > > > > >> > > >>>> > 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 their release > > > >> > > >>>> > date. For > > > >> > > >>>> > example, > > > >> > > >>>> > > > > >> > > >>>> > BinaryArray introduced, > > > >> > > >>>> > Read Repair strategies implemented, > > > >> > > >>>> > CPP Thin: asynchronous network events handling, > > > >> > > >>>> > NUMA-aware allocator for data regions > > > >> > > >>>> > etc. > > > >> > > >>>> > > > > >> > > >>>> > I want to propose myself to be the release manager of the > > > >> > > >>>> > planning > > > >> > > >>>> release. > > > >> > > >>>> > > > > >> > > >>>> > I propose the following timeline: > > > >> > > >>>> > > > > >> > > >>>> > Scope Freeze: February 21, 2022 > > > >> > > >>>> > Code Freeze: March 7, 2022 > > > >> > > >>>> > Voting Date: March 21, 2022 > > > >> > > >>>> > Release Date: March 28, 2022 > > > >> > > >>>> > > > > >> > > >>>> > WDYT? > > > >> > > >>>> > > > > >> > > >>>> > [1] https://issues.apache.org/jira/browse/IGNITE-15436 > > > >> > > >>>> > [2] > > > >> > > >>>> > > > >> > > >>>> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.13%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority > > > >> > > >>>> > > > > >> > > >>>> > -- > > > >> > > >>>> > Best wishes, > > > >> > > >>>> > Amelchev Nikita > > > >> > > >>>> > > > >> > > >> > > > >> > > >> > > > >> > > >> > > > >> > > >> > > > >> > > > > >> > > > > >> > > > > >> > -- > > > >> > Best wishes, > > > >> > Amelchev Nikita > > > >> > > > >> > > > >> > > > >> -- > > > >> Best wishes, > > > >> Amelchev Nikita > > > > > > > > > > > >-- > > > >Best wishes, > > > >Amelchev Nikita > > > > > > > > > > > > > > > > > > > > -- > > Best wishes, > > Amelchev Nikita > > > > -- > Best wishes, > Amelchev Nikita
