Re: 2.9.1 release proposal

2020-11-05 Thread Maxim Muzafarov
Folks, Alexey, Sure, I forgot about the Christmas holidays. I don't think we will be able to complete our release procedures with-in the next few weeks, so let's shift the dates a bit late. Let's prepare everything prior to the holidays and set the TC.Bot for the stabilization period on holidays t

Re: 2.9.1 release proposal

2020-11-05 Thread Alexey Goncharuk
Maxim, Should we shift the dates so they are not too close to state holidays in various countries? I'm concerned we won't be getting much activity around holidays and people who would otherwise spend some time on testing the release will not be able to do so. чт, 5 нояб. 2020 г. в 12:21, Maxim Mu

Re: 2.9.1 release proposal

2020-11-05 Thread Alexey Zinoviev
I'm ok with code freeze dates чт, 5 нояб. 2020 г. в 12:21, Maxim Muzafarov : > Folks, > > What may be the comfortable dates of the 2.10 release to finish all > the related development activities? > I suggest release Apache Ignite 2.10 prior to the end of this year and > focus on the 3.0 activitie

Re: 2.9.1 release proposal

2020-11-05 Thread Maxim Muzafarov
Folks, What may be the comfortable dates of the 2.10 release to finish all the related development activities? I suggest release Apache Ignite 2.10 prior to the end of this year and focus on the 3.0 activities in 2021 with only bug-fix releases for the 2.10.x. I suggest the following release date

Re: 2.9.1 release proposal

2020-11-03 Thread Yaroslav Molochkov
Nikolay, hi! Done. On Tue, Nov 3, 2020 at 10:48 AM Nikolay Izhikov wrote: > Hello, Yaroslav. > > Looks like we have fixVersion 2.9.1 in Jira. > Let’s mark all tickets with label «2.9.1-rc1» with fixVersion=2.9.1 and > use fixVersion instead of label further. > > > https://issues.apache.org/jira

Re: 2.9.1 release proposal

2020-11-02 Thread Nikolay Izhikov
Hello, Yaroslav. Looks like we have fixVersion 2.9.1 in Jira. Let’s mark all tickets with label «2.9.1-rc1» with fixVersion=2.9.1 and use fixVersion instead of label further. https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%202.9.1 > 2 нояб. 2020 г., в

Re: 2.9.1 release proposal

2020-11-02 Thread Yaroslav Molochkov
Guys, should you agree that issues with the 2.9.1-rc tag are good enough for a maintenance release, i'd like to give it a go. On Thu, Oct 29, 2020 at 5:33 PM Alexey Zinoviev wrote: > Let's discuss the possible planning dates for feature freeze for 2.10, for > example? Do you have any plans or i

Re: 2.9.1 release proposal

2020-10-29 Thread Alexey Zinoviev
Let's discuss the possible planning dates for feature freeze for 2.10, for example? Do you have any plans or ideas? чт, 29 окт. 2020 г. в 17:24, Andrey Gura : > Hi, > > I agree with Alexey. We should release 2.9.1 and start preparing for > the 2.10 release. > > 2.x releases usually take a lot of

Re: 2.9.1 release proposal

2020-10-29 Thread Andrey Gura
Hi, I agree with Alexey. We should release 2.9.1 and start preparing for the 2.10 release. 2.x releases usually take a lot of time. So we can release 2.9.1, and even 2.9.2 before 2.10. On Thu, Oct 29, 2020 at 12:02 PM Alexey Goncharuk wrote: > > Hello folks, > > I think we should start both 2.9

Re: 2.9.1 release proposal

2020-10-29 Thread Alexey Goncharuk
Hello folks, I think we should start both 2.9.1 and 2.10. In practice, maintenance release contains only critical and usability bugfixes (for example, I would include this ticket [1] to include in 2.9.1 as it prevents users from using tracing) and is released much faster than a minor release. [1]

Re: 2.9.1 release proposal

2020-10-27 Thread Guru Stron
Hello, Agree with Pavel. On Tue, 27 Oct 2020 at 19:22, Pavel Tupitsyn wrote: > Igniters, > > I think we should plan 2.10 instead of 2.9.1. > ignite-2.9 branch was cut 4 months ago, a bunch of new features are waiting > to be released. > > On Tue, Oct 27, 2020 at 4:23 AM 18624049226 <18624049...

Re: 2.9.1 release proposal

2020-10-27 Thread Pavel Tupitsyn
Igniters, I think we should plan 2.10 instead of 2.9.1. ignite-2.9 branch was cut 4 months ago, a bunch of new features are waiting to be released. On Tue, Oct 27, 2020 at 4:23 AM 18624049226 <18624049...@163.com> wrote: > Hello, > > I suggest that the remaining document issue in version 2.9.0 c

Re: 2.9.1 release proposal

2020-10-26 Thread 18624049226
Hello, I suggest that the remaining document issue in version 2.9.0 can be solved in version 2.9.1, and it is not a good practice to postpone to version 2.10. 在 2020/10/27 上午2:00, Maxim Muzafarov 写道: Hello, +1 Should we start the discussion about the release leader and release dates? On Tu

Re: 2.9.1 release proposal

2020-10-26 Thread Maxim Muzafarov
Hello, +1 Should we start the discussion about the release leader and release dates? On Tue, 20 Oct 2020 at 10:12, Anton Vinogradov wrote: > > +1 to start the 2.9.1 release process once as soon as 2.9 released. > > On Mon, Oct 19, 2020 at 8:49 PM Nikolay Izhikov wrote: > > > Hello, Yaroslav. >

Re: 2.9.1 release proposal

2020-10-20 Thread Anton Vinogradov
+1 to start the 2.9.1 release process once as soon as 2.9 released. On Mon, Oct 19, 2020 at 8:49 PM Nikolay Izhikov wrote: > Hello, Yaroslav. > > I support the idea. > But, we should carefully work with the release scope. > > IGNITE-13477 - fix for a SQL tracing that will be available only in 2.

Re: 2.9.1 release proposal

2020-10-19 Thread Nikolay Izhikov
Hello, Yaroslav. I support the idea. But, we should carefully work with the release scope. IGNITE-13477 - fix for a SQL tracing that will be available only in 2.10 IGNITE-13427 - fix for a new system view that exists in master only, we need to include IGNITE-13409 Other tickets should be checke