Apache Ignite 2.11
Locked
 
|
Dear Ignite Community!
I suggest starting Apache Ignite 2.11 release activities. Also suggest myself to be a release manager for this release. I plan release at the end of june 2021. ___ Best Regards, Alexey Gidaspov |
|
|
Hi Alexey,
:pmc to sign distribution: Formally, only PMC member can be a release manager, so part of activities should be picked up by committer and PMC member. If noone else want to help you here, I would. :timeline: And, could you estimate all phases of the release. :scope: I guess we can just pick up master current state and release it. But if someone has some ideas if we should wait for particular feature to be completed before branch divergence/release candidate build, please let know. Sincerely, Dmitriy Pavlov On 2021/05/13 09:45:02, Алексей Гидаспов <[hidden email]> wrote: > Dear Ignite Community! > > I suggest starting Apache Ignite 2.11 release activities. Also suggest > myself to be a release manager for this release. I plan release at the end > of june 2021. > > ___ > > Best Regards, > Alexey Gidaspov > |
|
|
Hi, I'd like to include Phase 1 of index queries feature [1] to the next AI
release. Currently there are 2 tickets in progress ([2], [3]), and they will be ready for review next week. What is a time of code freeze if it's going to release AI 2.11 at the end of June? [1] https://cwiki.apache.org/confluence/display/IGNITE/IEP-71%3A+Public+API+for+secondary+index+search [2] https://issues.apache.org/jira/browse/IGNITE-14699 [3] https://issues.apache.org/jira/browse/IGNITE-14703 On Thu, May 13, 2021 at 5:27 PM Dmitry Pavlov <[hidden email]> wrote: > Hi Alexey, > > :pmc to sign distribution: > Formally, only PMC member can be a release manager, so part of activities > should be picked up by committer and PMC member. If noone else want to help > you here, I would. > > :timeline: > And, could you estimate all phases of the release. > > :scope: > I guess we can just pick up master current state and release it. But if > someone has some ideas if we should wait for particular feature to be > completed before branch divergence/release candidate build, please let know. > > Sincerely, > Dmitriy Pavlov > > On 2021/05/13 09:45:02, Алексей Гидаспов <[hidden email]> wrote: > > Dear Ignite Community! > > > > I suggest starting Apache Ignite 2.11 release activities. Also suggest > > myself to be a release manager for this release. I plan release at the > end > > of june 2021. > > > > ___ > > > > Best Regards, > > Alexey Gidaspov > > > |
|
|
Hi, Dmitriy!
I suggest this timeline Scope Freeze: May 31, 2021 Code Freeze: 14 June, 2021 Voting Date: 21 June, 2021 Release Date: 28 June, 2021 пт, 14 мая 2021 г. в 11:32, Maksim Timonin <[hidden email]>: > Hi, I'd like to include Phase 1 of index queries feature [1] to the next AI > release. Currently there are 2 tickets in progress ([2], [3]), and they > will be ready for review next week. What is a time of code freeze if it's > going to release AI 2.11 at the end of June? > > [1] > > https://cwiki.apache.org/confluence/display/IGNITE/IEP-71%3A+Public+API+for+secondary+index+search > [2] https://issues.apache.org/jira/browse/IGNITE-14699 > [3] https://issues.apache.org/jira/browse/IGNITE-14703 > > On Thu, May 13, 2021 at 5:27 PM Dmitry Pavlov <[hidden email]> wrote: > > > Hi Alexey, > > > > :pmc to sign distribution: > > Formally, only PMC member can be a release manager, so part of activities > > should be picked up by committer and PMC member. If noone else want to > help > > you here, I would. > > > > :timeline: > > And, could you estimate all phases of the release. > > > > :scope: > > I guess we can just pick up master current state and release it. But if > > someone has some ideas if we should wait for particular feature to be > > completed before branch divergence/release candidate build, please let > know. > > > > Sincerely, > > Dmitriy Pavlov > > > > On 2021/05/13 09:45:02, Алексей Гидаспов <[hidden email]> wrote: > > > Dear Ignite Community! > > > > > > I suggest starting Apache Ignite 2.11 release activities. Also suggest > > > myself to be a release manager for this release. I plan release at the > > end > > > of june 2021. > > > > > > ___ > > > > > > Best Regards, > > > Alexey Gidaspov > > > > > > |
|
|
Maksim,
why do you want to include just one phase of functionality into release instead of full implementation? History of Ignie development shows (at least from my point of view) that it is bad practice. As result users will have unfinished and badly tested functionality. We have (or had in the past) some examples of such things: MVCC, IEP-35, etc. On Mon, May 17, 2021 at 5:11 PM Алексей Гидаспов <[hidden email]> wrote: > > Hi, Dmitriy! > > I suggest this timeline > > Scope Freeze: May 31, 2021 > Code Freeze: 14 June, 2021 > Voting Date: 21 June, 2021 > Release Date: 28 June, 2021 > > пт, 14 мая 2021 г. в 11:32, Maksim Timonin <[hidden email]>: > > > Hi, I'd like to include Phase 1 of index queries feature [1] to the next AI > > release. Currently there are 2 tickets in progress ([2], [3]), and they > > will be ready for review next week. What is a time of code freeze if it's > > going to release AI 2.11 at the end of June? > > > > [1] > > > > https://cwiki.apache.org/confluence/display/IGNITE/IEP-71%3A+Public+API+for+secondary+index+search > > [2] https://issues.apache.org/jira/browse/IGNITE-14699 > > [3] https://issues.apache.org/jira/browse/IGNITE-14703 > > > > On Thu, May 13, 2021 at 5:27 PM Dmitry Pavlov <[hidden email]> wrote: > > > > > Hi Alexey, > > > > > > :pmc to sign distribution: > > > Formally, only PMC member can be a release manager, so part of activities > > > should be picked up by committer and PMC member. If noone else want to > > help > > > you here, I would. > > > > > > :timeline: > > > And, could you estimate all phases of the release. > > > > > > :scope: > > > I guess we can just pick up master current state and release it. But if > > > someone has some ideas if we should wait for particular feature to be > > > completed before branch divergence/release candidate build, please let > > know. > > > > > > Sincerely, > > > Dmitriy Pavlov > > > > > > On 2021/05/13 09:45:02, Алексей Гидаспов <[hidden email]> wrote: > > > > Dear Ignite Community! > > > > > > > > I suggest starting Apache Ignite 2.11 release activities. Also suggest > > > > myself to be a release manager for this release. I plan release at the > > > end > > > > of june 2021. > > > > > > > > ___ > > > > > > > > Best Regards, > > > > Alexey Gidaspov > > > > > > > > > |
|
|
Hi, Andrey!
Phase 1 delivers complete query functionality. So users will get the API to query indexes and can start to use it. This functionality is not supposed to be changed in the next phases. I think there could be changes in the internal part that can affect performance of queries in next steps, but API will not change. Phases 2 and 3 are improvements and provide additional API. Those features should be discussed on the dev list later. On this dev list topic [1] we discussed phase 1 only and agreed that it is a useful feature. I'll prepare a PR for this feature today, and then up this topic [1]. Actually there are some issues to discuss. So after discussing those issues we can decide to deliver the feature to 2.11 or postpone until 2.12. Currently it's some time until the scope freeze (31 of May), so I'll write to this topic about progress and decisions. [1] http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-IEP-71-Public-API-for-secondary-index-search-td52177.html On Fri, May 21, 2021 at 2:39 PM Andrey Gura <[hidden email]> wrote: > Maksim, > > why do you want to include just one phase of functionality into > release instead of full implementation? History of Ignie development > shows (at least from my point of view) that it is bad practice. As > result users will have unfinished and badly tested functionality. We > have (or had in the past) some examples of such things: MVCC, IEP-35, > etc. > > On Mon, May 17, 2021 at 5:11 PM Алексей Гидаспов <[hidden email]> > wrote: > > > > Hi, Dmitriy! > > > > I suggest this timeline > > > > Scope Freeze: May 31, 2021 > > Code Freeze: 14 June, 2021 > > Voting Date: 21 June, 2021 > > Release Date: 28 June, 2021 > > > > пт, 14 мая 2021 г. в 11:32, Maksim Timonin <[hidden email]>: > > > > > Hi, I'd like to include Phase 1 of index queries feature [1] to the > next AI > > > release. Currently there are 2 tickets in progress ([2], [3]), and they > > > will be ready for review next week. What is a time of code freeze if > it's > > > going to release AI 2.11 at the end of June? > > > > > > [1] > > > > > > > https://cwiki.apache.org/confluence/display/IGNITE/IEP-71%3A+Public+API+for+secondary+index+search > > > [2] https://issues.apache.org/jira/browse/IGNITE-14699 > > > [3] https://issues.apache.org/jira/browse/IGNITE-14703 > > > > > > On Thu, May 13, 2021 at 5:27 PM Dmitry Pavlov <[hidden email]> > wrote: > > > > > > > Hi Alexey, > > > > > > > > :pmc to sign distribution: > > > > Formally, only PMC member can be a release manager, so part of > activities > > > > should be picked up by committer and PMC member. If noone else want > to > > > help > > > > you here, I would. > > > > > > > > :timeline: > > > > And, could you estimate all phases of the release. > > > > > > > > :scope: > > > > I guess we can just pick up master current state and release it. But > if > > > > someone has some ideas if we should wait for particular feature to be > > > > completed before branch divergence/release candidate build, please > let > > > know. > > > > > > > > Sincerely, > > > > Dmitriy Pavlov > > > > > > > > On 2021/05/13 09:45:02, Алексей Гидаспов <[hidden email]> > wrote: > > > > > Dear Ignite Community! > > > > > > > > > > I suggest starting Apache Ignite 2.11 release activities. Also > suggest > > > > > myself to be a release manager for this release. I plan release at > the > > > > end > > > > > of june 2021. > > > > > > > > > > ___ > > > > > > > > > > Best Regards, > > > > > Alexey Gidaspov > > > > > > > > > > > > > |
|
|
Hello!
I have found a blocker: https://issues.apache.org/jira/browse/IGNITE-14781 Regards, -- Ilya Kasnacheev пт, 21 мая 2021 г. в 15:30, Maksim Timonin <[hidden email]>: > Hi, Andrey! > > Phase 1 delivers complete query functionality. So users will get the API to > query indexes and can start to use it. This functionality is not supposed > to be changed in the next phases. I think there could be changes in the > internal part that can affect performance of queries in next steps, but API > will not change. > > Phases 2 and 3 are improvements and provide additional API. Those features > should be discussed on the dev list later. On this dev list topic [1] we > discussed phase 1 only and agreed that it is a useful feature. > > I'll prepare a PR for this feature today, and then up this topic [1]. > Actually there are some issues to discuss. So after discussing those issues > we can decide to deliver the feature to 2.11 or postpone until 2.12. > Currently it's some time until the scope freeze (31 of May), so I'll write > to this topic about progress and decisions. > > [1] > > http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-IEP-71-Public-API-for-secondary-index-search-td52177.html > > > > On Fri, May 21, 2021 at 2:39 PM Andrey Gura <[hidden email]> wrote: > > > Maksim, > > > > why do you want to include just one phase of functionality into > > release instead of full implementation? History of Ignie development > > shows (at least from my point of view) that it is bad practice. As > > result users will have unfinished and badly tested functionality. We > > have (or had in the past) some examples of such things: MVCC, IEP-35, > > etc. > > > > On Mon, May 17, 2021 at 5:11 PM Алексей Гидаспов <[hidden email]> > > wrote: > > > > > > Hi, Dmitriy! > > > > > > I suggest this timeline > > > > > > Scope Freeze: May 31, 2021 > > > Code Freeze: 14 June, 2021 > > > Voting Date: 21 June, 2021 > > > Release Date: 28 June, 2021 > > > > > > пт, 14 мая 2021 г. в 11:32, Maksim Timonin <[hidden email]>: > > > > > > > Hi, I'd like to include Phase 1 of index queries feature [1] to the > > next AI > > > > release. Currently there are 2 tickets in progress ([2], [3]), and > they > > > > will be ready for review next week. What is a time of code freeze if > > it's > > > > going to release AI 2.11 at the end of June? > > > > > > > > [1] > > > > > > > > > > > https://cwiki.apache.org/confluence/display/IGNITE/IEP-71%3A+Public+API+for+secondary+index+search > > > > [2] https://issues.apache.org/jira/browse/IGNITE-14699 > > > > [3] https://issues.apache.org/jira/browse/IGNITE-14703 > > > > > > > > On Thu, May 13, 2021 at 5:27 PM Dmitry Pavlov <[hidden email]> > > wrote: > > > > > > > > > Hi Alexey, > > > > > > > > > > :pmc to sign distribution: > > > > > Formally, only PMC member can be a release manager, so part of > > activities > > > > > should be picked up by committer and PMC member. If noone else want > > to > > > > help > > > > > you here, I would. > > > > > > > > > > :timeline: > > > > > And, could you estimate all phases of the release. > > > > > > > > > > :scope: > > > > > I guess we can just pick up master current state and release it. > But > > if > > > > > someone has some ideas if we should wait for particular feature to > be > > > > > completed before branch divergence/release candidate build, please > > let > > > > know. > > > > > > > > > > Sincerely, > > > > > Dmitriy Pavlov > > > > > > > > > > On 2021/05/13 09:45:02, Алексей Гидаспов <[hidden email]> > > wrote: > > > > > > Dear Ignite Community! > > > > > > > > > > > > I suggest starting Apache Ignite 2.11 release activities. Also > > suggest > > > > > > myself to be a release manager for this release. I plan release > at > > the > > > > > end > > > > > > of june 2021. > > > > > > > > > > > > ___ > > > > > > > > > > > > Best Regards, > > > > > > Alexey Gidaspov > > > > > > > > > > > > > > > > > > |
|
|
Hi, Ilya!
I've picked it. On Tue, May 25, 2021 at 7:04 PM Ilya Kasnacheev <[hidden email]> wrote: > Hello! > > I have found a blocker: https://issues.apache.org/jira/browse/IGNITE-14781 > > Regards, > -- > Ilya Kasnacheev > > > пт, 21 мая 2021 г. в 15:30, Maksim Timonin <[hidden email]>: > > > Hi, Andrey! > > > > Phase 1 delivers complete query functionality. So users will get the API > to > > query indexes and can start to use it. This functionality is not supposed > > to be changed in the next phases. I think there could be changes in the > > internal part that can affect performance of queries in next steps, but > API > > will not change. > > > > Phases 2 and 3 are improvements and provide additional API. Those > features > > should be discussed on the dev list later. On this dev list topic [1] we > > discussed phase 1 only and agreed that it is a useful feature. > > > > I'll prepare a PR for this feature today, and then up this topic [1]. > > Actually there are some issues to discuss. So after discussing those > issues > > we can decide to deliver the feature to 2.11 or postpone until 2.12. > > Currently it's some time until the scope freeze (31 of May), so I'll > write > > to this topic about progress and decisions. > > > > [1] > > > > > http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-IEP-71-Public-API-for-secondary-index-search-td52177.html > > > > > > > > On Fri, May 21, 2021 at 2:39 PM Andrey Gura <[hidden email]> wrote: > > > > > Maksim, > > > > > > why do you want to include just one phase of functionality into > > > release instead of full implementation? History of Ignie development > > > shows (at least from my point of view) that it is bad practice. As > > > result users will have unfinished and badly tested functionality. We > > > have (or had in the past) some examples of such things: MVCC, IEP-35, > > > etc. > > > > > > On Mon, May 17, 2021 at 5:11 PM Алексей Гидаспов <[hidden email] > > > > > wrote: > > > > > > > > Hi, Dmitriy! > > > > > > > > I suggest this timeline > > > > > > > > Scope Freeze: May 31, 2021 > > > > Code Freeze: 14 June, 2021 > > > > Voting Date: 21 June, 2021 > > > > Release Date: 28 June, 2021 > > > > > > > > пт, 14 мая 2021 г. в 11:32, Maksim Timonin <[hidden email] > >: > > > > > > > > > Hi, I'd like to include Phase 1 of index queries feature [1] to the > > > next AI > > > > > release. Currently there are 2 tickets in progress ([2], [3]), and > > they > > > > > will be ready for review next week. What is a time of code freeze > if > > > it's > > > > > going to release AI 2.11 at the end of June? > > > > > > > > > > [1] > > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/IGNITE/IEP-71%3A+Public+API+for+secondary+index+search > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-14699 > > > > > [3] https://issues.apache.org/jira/browse/IGNITE-14703 > > > > > > > > > > On Thu, May 13, 2021 at 5:27 PM Dmitry Pavlov <[hidden email]> > > > wrote: > > > > > > > > > > > Hi Alexey, > > > > > > > > > > > > :pmc to sign distribution: > > > > > > Formally, only PMC member can be a release manager, so part of > > > activities > > > > > > should be picked up by committer and PMC member. If noone else > want > > > to > > > > > help > > > > > > you here, I would. > > > > > > > > > > > > :timeline: > > > > > > And, could you estimate all phases of the release. > > > > > > > > > > > > :scope: > > > > > > I guess we can just pick up master current state and release it. > > But > > > if > > > > > > someone has some ideas if we should wait for particular feature > to > > be > > > > > > completed before branch divergence/release candidate build, > please > > > let > > > > > know. > > > > > > > > > > > > Sincerely, > > > > > > Dmitriy Pavlov > > > > > > > > > > > > On 2021/05/13 09:45:02, Алексей Гидаспов <[hidden email]> > > > wrote: > > > > > > > Dear Ignite Community! > > > > > > > > > > > > > > I suggest starting Apache Ignite 2.11 release activities. Also > > > suggest > > > > > > > myself to be a release manager for this release. I plan release > > at > > > the > > > > > > end > > > > > > > of june 2021. > > > > > > > > > > > > > > ___ > > > > > > > > > > > > > > Best Regards, > > > > > > > Alexey Gidaspov > > > > > > > > > > > > > > > > > > > > > > > > |
|
|
In reply to this post by Dmitry Pavlov
:scope:
Here is a list [1] of 195 tickets, i picked for Apache Ignite 2.11 release Let's start discussion [1] https://issues.apache.org/jira/browse/IGNITE-14781?jql=project%20%3D%20IGNITE%20%20AND%20status%20%20%3D%20Resolved%20and%20fixVersion%20%3D%202.11%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC On 2021/05/13 14:27:33, Dmitry Pavlov <[hidden email]> wrote: > Hi Alexey, > > :pmc to sign distribution: > Formally, only PMC member can be a release manager, so part of activities should be picked up by committer and PMC member. If noone else want to help you here, I would. > > :timeline: > And, could you estimate all phases of the release. > > :scope: > I guess we can just pick up master current state and release it. But if someone has some ideas if we should wait for particular feature to be completed before branch divergence/release candidate build, please let know. > > Sincerely, > Dmitriy Pavlov > > On 2021/05/13 09:45:02, Алексей Гидаспов <[hidden email]> wrote: > > Dear Ignite Community! > > > > I suggest starting Apache Ignite 2.11 release activities. Also suggest > > myself to be a release manager for this release. I plan release at the end > > of june 2021. > > > > ___ > > > > Best Regards, > > Alexey Gidaspov > > > |
|
|
Hi Alexey,
Releasing master as-is makes sence for me. Regarding non-SQL index API it really depends on readiness. I guess if it is not in the master, we can skip and release it next time. We've a bit overdue initial scope freeze date. It's not a big deal, but still makes sense to start discussion, create and share wiki page and create branch. Since committer privileges required to create branch, could you please notify me in advance. Sincerely, Dmitriy Pavlov On 2021/06/03 14:08:34, �������������� ���������������� <[hidden email]> wrote: > :scope: > > Here is a list [1] of 195 tickets, i picked for Apache Ignite 2.11 release > > Let's start discussion > > [1] https://issues.apache.org/jira/browse/IGNITE-14781?jql=project%20%3D%20IGNITE%20%20AND%20status%20%20%3D%20Resolved%20and%20fixVersion%20%3D%202.11%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC > > On 2021/05/13 14:27:33, Dmitry Pavlov <[hidden email]> wrote: > > Hi Alexey, > > > > :pmc to sign distribution: > > Formally, only PMC member can be a release manager, so part of activities should be picked up by committer and PMC member. If noone else want to help you here, I would. > > > > :timeline: > > And, could you estimate all phases of the release. > > > > :scope: > > I guess we can just pick up master current state and release it. But if someone has some ideas if we should wait for particular feature to be completed before branch divergence/release candidate build, please let know. > > > > Sincerely, > > Dmitriy Pavlov > > > > On 2021/05/13 09:45:02, Алексей Гидаспов <[hidden email]> wrote: > > > Dear Ignite Community! > > > > > > I suggest starting Apache Ignite 2.11 release activities. Also suggest > > > myself to be a release manager for this release. I plan release at the end > > > of june 2021. > > > > > > ___ > > > > > > Best Regards, > > > Alexey Gidaspov > > > > > > |
|
|
> Regarding non-SQL index API it really depends on readiness. I guess if it
is not in the master, we can skip and release it next time. Hi, Dmitry! Yes, currently it is on review. I'm OK to release it within the next release. On Thu, Jun 3, 2021 at 5:26 PM Dmitry Pavlov <[hidden email]> wrote: > Hi Alexey, > > Releasing master as-is makes sence for me. > > Regarding non-SQL index API it really depends on readiness. I guess if it > is not in the master, we can skip and release it next time. > > We've a bit overdue initial scope freeze date. It's not a big deal, but > still makes sense to start discussion, create and share wiki page and > create branch. > > Since committer privileges required to create branch, could you please > notify me in advance. > > Sincerely, > Dmitriy Pavlov > > On 2021/06/03 14:08:34, �������������� ���������������� < > [hidden email]> wrote: > > :scope: > > > > Here is a list [1] of 195 tickets, i picked for Apache Ignite 2.11 > release > > > > Let's start discussion > > > > [1] > https://issues.apache.org/jira/browse/IGNITE-14781?jql=project%20%3D%20IGNITE%20%20AND%20status%20%20%3D%20Resolved%20and%20fixVersion%20%3D%202.11%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC > > > > On 2021/05/13 14:27:33, Dmitry Pavlov <[hidden email]> wrote: > > > Hi Alexey, > > > > > > :pmc to sign distribution: > > > Formally, only PMC member can be a release manager, so part of > activities should be picked up by committer and PMC member. If noone else > want to help you here, I would. > > > > > > :timeline: > > > And, could you estimate all phases of the release. > > > > > > :scope: > > > I guess we can just pick up master current state and release it. But > if someone has some ideas if we should wait for particular feature to be > completed before branch divergence/release candidate build, please let know. > > > > > > Sincerely, > > > Dmitriy Pavlov > > > > > > On 2021/05/13 09:45:02, Алексей Гидаспов <[hidden email]> > wrote: > > > > Dear Ignite Community! > > > > > > > > I suggest starting Apache Ignite 2.11 release activities. Also > suggest > > > > myself to be a release manager for this release. I plan release at > the end > > > > of june 2021. > > > > > > > > ___ > > > > > > > > Best Regards, > > > > Alexey Gidaspov > > > > > > > > > > |
|
|
ok, Maksim, keep us posted.
We're in the middle of paperwork rigth now, so there is a chance )) On 2021/06/03 14:30:55, Maksim Timonin <[hidden email]> wrote: > > Regarding non-SQL index API it really depends on readiness. I guess if it > is not in the master, we can skip and release it next time. > > Hi, Dmitry! Yes, currently it is on review. I'm OK to release it within the > next release. > > On Thu, Jun 3, 2021 at 5:26 PM Dmitry Pavlov <[hidden email]> wrote: > > > Hi Alexey, > > > > Releasing master as-is makes sence for me. > > > > Regarding non-SQL index API it really depends on readiness. I guess if it > > is not in the master, we can skip and release it next time. > > > > We've a bit overdue initial scope freeze date. It's not a big deal, but > > still makes sense to start discussion, create and share wiki page and > > create branch. > > > > Since committer privileges required to create branch, could you please > > notify me in advance. > > > > Sincerely, > > Dmitriy Pavlov > > > > On 2021/06/03 14:08:34, �������������� ���������������� < > > [hidden email]> wrote: > > > :scope: > > > > > > Here is a list [1] of 195 tickets, i picked for Apache Ignite 2.11 > > release > > > > > > Let's start discussion > > > > > > [1] > > https://issues.apache.org/jira/browse/IGNITE-14781?jql=project%20%3D%20IGNITE%20%20AND%20status%20%20%3D%20Resolved%20and%20fixVersion%20%3D%202.11%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC > > > > > > On 2021/05/13 14:27:33, Dmitry Pavlov <[hidden email]> wrote: > > > > Hi Alexey, > > > > > > > > :pmc to sign distribution: > > > > Formally, only PMC member can be a release manager, so part of > > activities should be picked up by committer and PMC member. If noone else > > want to help you here, I would. > > > > > > > > :timeline: > > > > And, could you estimate all phases of the release. > > > > > > > > :scope: > > > > I guess we can just pick up master current state and release it. But > > if someone has some ideas if we should wait for particular feature to be > > completed before branch divergence/release candidate build, please let know. > > > > > > > > Sincerely, > > > > Dmitriy Pavlov > > > > > > > > On 2021/05/13 09:45:02, Алексей Гидаспов <[hidden email]> > > wrote: > > > > > Dear Ignite Community! > > > > > > > > > > I suggest starting Apache Ignite 2.11 release activities. Also > > suggest > > > > > myself to be a release manager for this release. I plan release at > > the end > > > > > of june 2021. > > > > > > > > > > ___ > > > > > > > > > > Best Regards, > > > > > Alexey Gidaspov > > > > > > > > > > > > > > > |
|
|
I mean I'm OK to release it with 2.12. So, I am glad to hear there are
chances for 2.11, but I guess we can postpone it. On Thu, Jun 3, 2021 at 5:39 PM Dmitry Pavlov <[hidden email]> wrote: > ok, Maksim, keep us posted. > > We're in the middle of paperwork rigth now, so there is a chance )) > > On 2021/06/03 14:30:55, Maksim Timonin <[hidden email]> wrote: > > > Regarding non-SQL index API it really depends on readiness. I guess if > it > > is not in the master, we can skip and release it next time. > > > > Hi, Dmitry! Yes, currently it is on review. I'm OK to release it within > the > > next release. > > > > On Thu, Jun 3, 2021 at 5:26 PM Dmitry Pavlov <[hidden email]> wrote: > > > > > Hi Alexey, > > > > > > Releasing master as-is makes sence for me. > > > > > > Regarding non-SQL index API it really depends on readiness. I guess if > it > > > is not in the master, we can skip and release it next time. > > > > > > We've a bit overdue initial scope freeze date. It's not a big deal, but > > > still makes sense to start discussion, create and share wiki page and > > > create branch. > > > > > > Since committer privileges required to create branch, could you please > > > notify me in advance. > > > > > > Sincerely, > > > Dmitriy Pavlov > > > > > > On 2021/06/03 14:08:34, �������������� ���������������� < > > > [hidden email]> wrote: > > > > :scope: > > > > > > > > Here is a list [1] of 195 tickets, i picked for Apache Ignite 2.11 > > > release > > > > > > > > Let's start discussion > > > > > > > > [1] > > > > https://issues.apache.org/jira/browse/IGNITE-14781?jql=project%20%3D%20IGNITE%20%20AND%20status%20%20%3D%20Resolved%20and%20fixVersion%20%3D%202.11%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC > > > > > > > > On 2021/05/13 14:27:33, Dmitry Pavlov <[hidden email]> wrote: > > > > > Hi Alexey, > > > > > > > > > > :pmc to sign distribution: > > > > > Formally, only PMC member can be a release manager, so part of > > > activities should be picked up by committer and PMC member. If noone > else > > > want to help you here, I would. > > > > > > > > > > :timeline: > > > > > And, could you estimate all phases of the release. > > > > > > > > > > :scope: > > > > > I guess we can just pick up master current state and release it. > But > > > if someone has some ideas if we should wait for particular feature to > be > > > completed before branch divergence/release candidate build, please let > know. > > > > > > > > > > Sincerely, > > > > > Dmitriy Pavlov > > > > > > > > > > On 2021/05/13 09:45:02, Алексей Гидаспов <[hidden email]> > > > wrote: > > > > > > Dear Ignite Community! > > > > > > > > > > > > I suggest starting Apache Ignite 2.11 release activities. Also > > > suggest > > > > > > myself to be a release manager for this release. I plan release > at > > > the end > > > > > > of june 2021. > > > > > > > > > > > > ___ > > > > > > > > > > > > Best Regards, > > > > > > Alexey Gidaspov > > > > > > > > > > > > > > > > > > > > > |
|
|
Sure, thanks for your reply
Folks, could you please advice how to setup JIRA account integration for non-committers? For the page https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.11 I can see all issues, but Alexey's login seems to be not sufficient. Can wiki admins set up smth? Or Alexey should do some setup on his own? On 2021/06/03 14:55:25, Maksim Timonin <[hidden email]> wrote: > I mean I'm OK to release it with 2.12. So, I am glad to hear there are > chances for 2.11, but I guess we can postpone it. > > > On Thu, Jun 3, 2021 at 5:39 PM Dmitry Pavlov <[hidden email]> wrote: > > > ok, Maksim, keep us posted. > > > > We're in the middle of paperwork rigth now, so there is a chance )) > > > > On 2021/06/03 14:30:55, Maksim Timonin <[hidden email]> wrote: > > > > Regarding non-SQL index API it really depends on readiness. I guess if > > it > > > is not in the master, we can skip and release it next time. > > > > > > Hi, Dmitry! Yes, currently it is on review. I'm OK to release it within > > the > > > next release. > > > > > > On Thu, Jun 3, 2021 at 5:26 PM Dmitry Pavlov <[hidden email]> wrote: > > > > > > > Hi Alexey, > > > > > > > > Releasing master as-is makes sence for me. > > > > > > > > Regarding non-SQL index API it really depends on readiness. I guess if > > it > > > > is not in the master, we can skip and release it next time. > > > > > > > > We've a bit overdue initial scope freeze date. It's not a big deal, but > > > > still makes sense to start discussion, create and share wiki page and > > > > create branch. > > > > > > > > Since committer privileges required to create branch, could you please > > > > notify me in advance. > > > > > > > > Sincerely, > > > > Dmitriy Pavlov > > > > > > > > On 2021/06/03 14:08:34, �������������� ���������������� < > > > > [hidden email]> wrote: > > > > > :scope: > > > > > > > > > > Here is a list [1] of 195 tickets, i picked for Apache Ignite 2.11 > > > > release > > > > > > > > > > Let's start discussion > > > > > > > > > > [1] > > > > > > https://issues.apache.org/jira/browse/IGNITE-14781?jql=project%20%3D%20IGNITE%20%20AND%20status%20%20%3D%20Resolved%20and%20fixVersion%20%3D%202.11%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC > > > > > > > > > > On 2021/05/13 14:27:33, Dmitry Pavlov <[hidden email]> wrote: > > > > > > Hi Alexey, > > > > > > > > > > > > :pmc to sign distribution: > > > > > > Formally, only PMC member can be a release manager, so part of > > > > activities should be picked up by committer and PMC member. If noone > > else > > > > want to help you here, I would. > > > > > > > > > > > > :timeline: > > > > > > And, could you estimate all phases of the release. > > > > > > > > > > > > :scope: > > > > > > I guess we can just pick up master current state and release it. > > But > > > > if someone has some ideas if we should wait for particular feature to > > be > > > > completed before branch divergence/release candidate build, please let > > know. > > > > > > > > > > > > Sincerely, > > > > > > Dmitriy Pavlov > > > > > > > > > > > > On 2021/05/13 09:45:02, Алексей Гидаспов <[hidden email]> > > > > wrote: > > > > > > > Dear Ignite Community! > > > > > > > > > > > > > > I suggest starting Apache Ignite 2.11 release activities. Also > > > > suggest > > > > > > > myself to be a release manager for this release. I plan release > > at > > > > the end > > > > > > > of june 2021. > > > > > > > > > > > > > > ___ > > > > > > > > > > > > > > Best Regards, > > > > > > > Alexey Gidaspov > > > > > > > > > > > > > > > > > > > > > > > > > > > > |
|
|
hello,
can someone can help to merge the following patch into master? https://issues.apache.org/jira/browse/IGNITE-12852 This patch has been completed for a long time, and I think it is a valuable one. 在 2021/6/3 下午11:12, Dmitry Pavlov 写道: > Sure, thanks for your reply > > Folks, could you please advice how to setup JIRA account integration for non-committers? > > For the page > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.11 > I can see all issues, but Alexey's login seems to be not sufficient. Can wiki admins set up smth? Or Alexey should do some setup on his own? > > On 2021/06/03 14:55:25, Maksim Timonin <[hidden email]> wrote: >> I mean I'm OK to release it with 2.12. So, I am glad to hear there are >> chances for 2.11, but I guess we can postpone it. >> >> >> On Thu, Jun 3, 2021 at 5:39 PM Dmitry Pavlov <[hidden email]> wrote: >> >>> ok, Maksim, keep us posted. >>> >>> We're in the middle of paperwork rigth now, so there is a chance )) >>> >>> On 2021/06/03 14:30:55, Maksim Timonin <[hidden email]> wrote: >>>>> Regarding non-SQL index API it really depends on readiness. I guess if >>> it >>>> is not in the master, we can skip and release it next time. >>>> >>>> Hi, Dmitry! Yes, currently it is on review. I'm OK to release it within >>> the >>>> next release. >>>> >>>> On Thu, Jun 3, 2021 at 5:26 PM Dmitry Pavlov <[hidden email]> wrote: >>>> >>>>> Hi Alexey, >>>>> >>>>> Releasing master as-is makes sence for me. >>>>> >>>>> Regarding non-SQL index API it really depends on readiness. I guess if >>> it >>>>> is not in the master, we can skip and release it next time. >>>>> >>>>> We've a bit overdue initial scope freeze date. It's not a big deal, but >>>>> still makes sense to start discussion, create and share wiki page and >>>>> create branch. >>>>> >>>>> Since committer privileges required to create branch, could you please >>>>> notify me in advance. >>>>> >>>>> Sincerely, >>>>> Dmitriy Pavlov >>>>> >>>>> On 2021/06/03 14:08:34, �������������� ���������������� < >>>>> [hidden email]> wrote: >>>>>> :scope: >>>>>> >>>>>> Here is a list [1] of 195 tickets, i picked for Apache Ignite 2.11 >>>>> release >>>>>> Let's start discussion >>>>>> >>>>>> [1] >>> https://issues.apache.org/jira/browse/IGNITE-14781?jql=project%20%3D%20IGNITE%20%20AND%20status%20%20%3D%20Resolved%20and%20fixVersion%20%3D%202.11%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC >>>>>> On 2021/05/13 14:27:33, Dmitry Pavlov <[hidden email]> wrote: >>>>>>> Hi Alexey, >>>>>>> >>>>>>> :pmc to sign distribution: >>>>>>> Formally, only PMC member can be a release manager, so part of >>>>> activities should be picked up by committer and PMC member. If noone >>> else >>>>> want to help you here, I would. >>>>>>> :timeline: >>>>>>> And, could you estimate all phases of the release. >>>>>>> >>>>>>> :scope: >>>>>>> I guess we can just pick up master current state and release it. >>> But >>>>> if someone has some ideas if we should wait for particular feature to >>> be >>>>> completed before branch divergence/release candidate build, please let >>> know. >>>>>>> Sincerely, >>>>>>> Dmitriy Pavlov >>>>>>> >>>>>>> On 2021/05/13 09:45:02, Алексей Гидаспов <[hidden email]> >>>>> wrote: >>>>>>>> Dear Ignite Community! >>>>>>>> >>>>>>>> I suggest starting Apache Ignite 2.11 release activities. Also >>>>> suggest >>>>>>>> myself to be a release manager for this release. I plan release >>> at >>>>> the end >>>>>>>> of june 2021. >>>>>>>> >>>>>>>> ___ >>>>>>>> >>>>>>>> Best Regards, >>>>>>>> Alexey Gidaspov >>>>>>>> |
|
|
Hello Igniters!
I guess that AI 2.11 will include documentation work. I'll be glad to help with this. And I'll be happy to know the scope of features that we need to document. Regards, Nikita пт, 4 июн. 2021 г. в 03:50, 18624049226 <[hidden email]>: > hello, > > can someone can help to merge the following patch into master? > > https://issues.apache.org/jira/browse/IGNITE-12852 > > This patch has been completed for a long time, and I think it is a > valuable one. > > 在 2021/6/3 下午11:12, Dmitry Pavlov 写道: > > Sure, thanks for your reply > > > > Folks, could you please advice how to setup JIRA account integration for > non-committers? > > > > For the page > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.11 > > I can see all issues, but Alexey's login seems to be not sufficient. Can > wiki admins set up smth? Or Alexey should do some setup on his own? > > > > On 2021/06/03 14:55:25, Maksim Timonin <[hidden email]> wrote: > >> I mean I'm OK to release it with 2.12. So, I am glad to hear there are > >> chances for 2.11, but I guess we can postpone it. > >> > >> > >> On Thu, Jun 3, 2021 at 5:39 PM Dmitry Pavlov <[hidden email]> > wrote: > >> > >>> ok, Maksim, keep us posted. > >>> > >>> We're in the middle of paperwork rigth now, so there is a chance )) > >>> > >>> On 2021/06/03 14:30:55, Maksim Timonin <[hidden email]> > wrote: > >>>>> Regarding non-SQL index API it really depends on readiness. I guess > if > >>> it > >>>> is not in the master, we can skip and release it next time. > >>>> > >>>> Hi, Dmitry! Yes, currently it is on review. I'm OK to release it > within > >>> the > >>>> next release. > >>>> > >>>> On Thu, Jun 3, 2021 at 5:26 PM Dmitry Pavlov <[hidden email]> > wrote: > >>>> > >>>>> Hi Alexey, > >>>>> > >>>>> Releasing master as-is makes sence for me. > >>>>> > >>>>> Regarding non-SQL index API it really depends on readiness. I guess > if > >>> it > >>>>> is not in the master, we can skip and release it next time. > >>>>> > >>>>> We've a bit overdue initial scope freeze date. It's not a big deal, > but > >>>>> still makes sense to start discussion, create and share wiki page and > >>>>> create branch. > >>>>> > >>>>> Since committer privileges required to create branch, could you > please > >>>>> notify me in advance. > >>>>> > >>>>> Sincerely, > >>>>> Dmitriy Pavlov > >>>>> > >>>>> On 2021/06/03 14:08:34, �������������� ���������������� < > >>>>> [hidden email]> wrote: > >>>>>> :scope: > >>>>>> > >>>>>> Here is a list [1] of 195 tickets, i picked for Apache Ignite 2.11 > >>>>> release > >>>>>> Let's start discussion > >>>>>> > >>>>>> [1] > >>> > https://issues.apache.org/jira/browse/IGNITE-14781?jql=project%20%3D%20IGNITE%20%20AND%20status%20%20%3D%20Resolved%20and%20fixVersion%20%3D%202.11%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC > >>>>>> On 2021/05/13 14:27:33, Dmitry Pavlov <[hidden email]> wrote: > >>>>>>> Hi Alexey, > >>>>>>> > >>>>>>> :pmc to sign distribution: > >>>>>>> Formally, only PMC member can be a release manager, so part of > >>>>> activities should be picked up by committer and PMC member. If noone > >>> else > >>>>> want to help you here, I would. > >>>>>>> :timeline: > >>>>>>> And, could you estimate all phases of the release. > >>>>>>> > >>>>>>> :scope: > >>>>>>> I guess we can just pick up master current state and release it. > >>> But > >>>>> if someone has some ideas if we should wait for particular feature to > >>> be > >>>>> completed before branch divergence/release candidate build, please > let > >>> know. > >>>>>>> Sincerely, > >>>>>>> Dmitriy Pavlov > >>>>>>> > >>>>>>> On 2021/05/13 09:45:02, Алексей Гидаспов <[hidden email]> > >>>>> wrote: > >>>>>>>> Dear Ignite Community! > >>>>>>>> > >>>>>>>> I suggest starting Apache Ignite 2.11 release activities. Also > >>>>> suggest > >>>>>>>> myself to be a release manager for this release. I plan release > >>> at > >>>>> the end > >>>>>>>> of june 2021. > >>>>>>>> > >>>>>>>> ___ > >>>>>>>> > >>>>>>>> Best Regards, > >>>>>>>> Alexey Gidaspov > >>>>>>>> > |
|
|
Hello all. I’d also join in on Nikita’s question n what docs are required for release. Currently we only have one doc issue for over 200 tickets resolved in the released, and it looks like we might be missing something. >Hello Igniters! > >I guess that AI 2.11 will include documentation work. >I'll be glad to help with this. >And I'll be happy to know the scope of features that we need to document. > >Regards, >Nikita >пт, 4 июн. 2021 г. в 03:50, 18624049226 < [hidden email] >: >>hello, >> >>can someone can help to merge the following patch into master? >> >>https://issues.apache.org/jira/browse/IGNITE-12852 >> >>This patch has been completed for a long time, and I think it is a >>valuable one. >> >>在 2021/6/3 下午11:12, Dmitry Pavlov 写道: >>> Sure, thanks for your reply >>> >>> Folks, could you please advice how to setup JIRA account integration for non-committers? >>> >>> For the page >>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.11 >>> I can see all issues, but Alexey's login seems to be not sufficient. Can wiki admins set up smth? Or Alexey should do some setup on his own? >>> >>> On 2021/06/03 14:55:25, Maksim Timonin < [hidden email] > wrote: >>>> I mean I'm OK to release it with 2.12. So, I am glad to hear there are >>>> chances for 2.11, but I guess we can postpone it. >>>> >>>> >>>> On Thu, Jun 3, 2021 at 5:39 PM Dmitry Pavlov < [hidden email] > wrote: >>>> >>>>> ok, Maksim, keep us posted. >>>>> >>>>> We're in the middle of paperwork rigth now, so there is a chance )) >>>>> >>>>> On 2021/06/03 14:30:55, Maksim Timonin < [hidden email] > wrote: >>>>>>> Regarding non-SQL index API it really depends on readiness. I guess if >>>>> it >>>>>> is not in the master, we can skip and release it next time. >>>>>> >>>>>> Hi, Dmitry! Yes, currently it is on review. I'm OK to release it within >>>>> the >>>>>> next release. >>>>>> >>>>>> On Thu, Jun 3, 2021 at 5:26 PM Dmitry Pavlov < [hidden email] > wrote: >>>>>> >>>>>>> Hi Alexey, >>>>>>> >>>>>>> Releasing master as-is makes sence for me. >>>>>>> >>>>>>> Regarding non-SQL index API it really depends on readiness. I guess if >>>>> it >>>>>>> is not in the master, we can skip and release it next time. >>>>>>> >>>>>>> We've a bit overdue initial scope freeze date. It's not a big deal, but >>>>>>> still makes sense to start discussion, create and share wiki page and >>>>>>> create branch. >>>>>>> >>>>>>> Since committer privileges required to create branch, could you please >>>>>>> notify me in advance. >>>>>>> >>>>>>> Sincerely, >>>>>>> Dmitriy Pavlov >>>>>>> >>>>>>> On 2021/06/03 14:08:34, < >>>>>>> [hidden email] > wrote: >>>>>>>> :scope: >>>>>>>> >>>>>>>> Here is a list [1] of 195 tickets, i picked for Apache Ignite 2.11 >>>>>>> release >>>>>>>> Let's start discussion >>>>>>>> >>>>>>>> [1] >>>>> https://issues.apache.org/jira/browse/IGNITE-14781?jql=project%20%3D%20IGNITE%20%20AND%20status%20%20%3D%20Resolved%20and%20fixVersion%20%3D%202.11%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC >>>>>>>> On 2021/05/13 14:27:33, Dmitry Pavlov < [hidden email] > wrote: >>>>>>>>> Hi Alexey, >>>>>>>>> >>>>>>>>> :pmc to sign distribution: >>>>>>>>> Formally, only PMC member can be a release manager, so part of >>>>>>> activities should be picked up by committer and PMC member. If noone >>>>> else >>>>>>> want to help you here, I would. >>>>>>>>> :timeline: >>>>>>>>> And, could you estimate all phases of the release. >>>>>>>>> >>>>>>>>> :scope: >>>>>>>>> I guess we can just pick up master current state and release it. >>>>> But >>>>>>> if someone has some ideas if we should wait for particular feature to >>>>> be >>>>>>> completed before branch divergence/release candidate build, please let >>>>> know. >>>>>>>>> Sincerely, >>>>>>>>> Dmitriy Pavlov >>>>>>>>> >>>>>>>>> On 2021/05/13 09:45:02, Алексей Гидаспов < [hidden email] > >>>>>>> wrote: >>>>>>>>>> Dear Ignite Community! >>>>>>>>>> >>>>>>>>>> I suggest starting Apache Ignite 2.11 release activities. Also >>>>>>> suggest >>>>>>>>>> myself to be a release manager for this release. I plan release >>>>> at >>>>>>> the end >>>>>>>>>> of june 2021. >>>>>>>>>> >>>>>>>>>> ___ >>>>>>>>>> >>>>>>>>>> Best Regards, >>>>>>>>>> Alexey Gidaspov >>>>>>>>>> -- Igor Gusev |
|
|
I suppose that python thin client documentation should be removed, only
link to actual readthedocs.io documentation should remain пт, 11 июн. 2021 г., 14:01 Игорь Гусев <[hidden email]>: > > Hello all. > > I’d also join in on Nikita’s question n what docs are required for > release. Currently we only have one doc issue for over 200 tickets resolved > in the released, and it looks like we might be missing something. > > > >Hello Igniters! > > > >I guess that AI 2.11 will include documentation work. > >I'll be glad to help with this. > >And I'll be happy to know the scope of features that we need to document. > > > >Regards, > >Nikita > >пт, 4 июн. 2021 г. в 03:50, 18624049226 < [hidden email] >: > >>hello, > >> > >>can someone can help to merge the following patch into master? > >> > >>https://issues.apache.org/jira/browse/IGNITE-12852 > >> > >>This patch has been completed for a long time, and I think it is a > >>valuable one. > >> > >>在 2021/6/3 下午11:12, Dmitry Pavlov 写道: > >>> Sure, thanks for your reply > >>> > >>> Folks, could you please advice how to setup JIRA account integration > for non-committers? > >>> > >>> For the page > >>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.11 > >>> I can see all issues, but Alexey's login seems to be not sufficient. > Can wiki admins set up smth? Or Alexey should do some setup on his own? > >>> > >>> On 2021/06/03 14:55:25, Maksim Timonin < [hidden email] > > wrote: > >>>> I mean I'm OK to release it with 2.12. So, I am glad to hear there are > >>>> chances for 2.11, but I guess we can postpone it. > >>>> > >>>> > >>>> On Thu, Jun 3, 2021 at 5:39 PM Dmitry Pavlov < [hidden email] > > wrote: > >>>> > >>>>> ok, Maksim, keep us posted. > >>>>> > >>>>> We're in the middle of paperwork rigth now, so there is a chance )) > >>>>> > >>>>> On 2021/06/03 14:30:55, Maksim Timonin < [hidden email] > > wrote: > >>>>>>> Regarding non-SQL index API it really depends on readiness. I > guess if > >>>>> it > >>>>>> is not in the master, we can skip and release it next time. > >>>>>> > >>>>>> Hi, Dmitry! Yes, currently it is on review. I'm OK to release it > within > >>>>> the > >>>>>> next release. > >>>>>> > >>>>>> On Thu, Jun 3, 2021 at 5:26 PM Dmitry Pavlov < [hidden email] > > wrote: > >>>>>> > >>>>>>> Hi Alexey, > >>>>>>> > >>>>>>> Releasing master as-is makes sence for me. > >>>>>>> > >>>>>>> Regarding non-SQL index API it really depends on readiness. I > guess if > >>>>> it > >>>>>>> is not in the master, we can skip and release it next time. > >>>>>>> > >>>>>>> We've a bit overdue initial scope freeze date. It's not a big > deal, but > >>>>>>> still makes sense to start discussion, create and share wiki page > and > >>>>>>> create branch. > >>>>>>> > >>>>>>> Since committer privileges required to create branch, could you > please > >>>>>>> notify me in advance. > >>>>>>> > >>>>>>> Sincerely, > >>>>>>> Dmitriy Pavlov > >>>>>>> > >>>>>>> On 2021/06/03 14:08:34, < > >>>>>>> [hidden email] > wrote: > >>>>>>>> :scope: > >>>>>>>> > >>>>>>>> Here is a list [1] of 195 tickets, i picked for Apache Ignite 2.11 > >>>>>>> release > >>>>>>>> Let's start discussion > >>>>>>>> > >>>>>>>> [1] > >>>>> > https://issues.apache.org/jira/browse/IGNITE-14781?jql=project%20%3D%20IGNITE%20%20AND%20status%20%20%3D%20Resolved%20and%20fixVersion%20%3D%202.11%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC > >>>>>>>> On 2021/05/13 14:27:33, Dmitry Pavlov < [hidden email] > > wrote: > >>>>>>>>> Hi Alexey, > >>>>>>>>> > >>>>>>>>> :pmc to sign distribution: > >>>>>>>>> Formally, only PMC member can be a release manager, so part of > >>>>>>> activities should be picked up by committer and PMC member. If > noone > >>>>> else > >>>>>>> want to help you here, I would. > >>>>>>>>> :timeline: > >>>>>>>>> And, could you estimate all phases of the release. > >>>>>>>>> > >>>>>>>>> :scope: > >>>>>>>>> I guess we can just pick up master current state and release it. > >>>>> But > >>>>>>> if someone has some ideas if we should wait for particular feature > to > >>>>> be > >>>>>>> completed before branch divergence/release candidate build, please > let > >>>>> know. > >>>>>>>>> Sincerely, > >>>>>>>>> Dmitriy Pavlov > >>>>>>>>> > >>>>>>>>> On 2021/05/13 09:45:02, Алексей Гидаспов < [hidden email] > > > >>>>>>> wrote: > >>>>>>>>>> Dear Ignite Community! > >>>>>>>>>> > >>>>>>>>>> I suggest starting Apache Ignite 2.11 release activities. Also > >>>>>>> suggest > >>>>>>>>>> myself to be a release manager for this release. I plan release > >>>>> at > >>>>>>> the end > >>>>>>>>>> of june 2021. > >>>>>>>>>> > >>>>>>>>>> ___ > >>>>>>>>>> > >>>>>>>>>> Best Regards, > >>>>>>>>>> Alexey Gidaspov > >>>>>>>>>> > > > -- > Igor Gusev > |
«
Return to Apache Ignite Developers - Legacy Mail Archive
|
1 view|%1 views
| Free forum by Nabble | Edit this page |