Apache Ignite 2.7: scope, time and release manager
Locked
Apache Ignite 2.7: scope, time and release manager
 
|
Re: Apache Ignite 2.7: scope, time and release manager
|
|
Re: Apache Ignite 2.7: scope, time and release manager
|
Re: Apache Ignite 2.7: scope, time and release manager
|
|
Re: Apache Ignite 2.7: scope, time and release manager
|
|
Re: Apache Ignite 2.7: scope, time and release manager
|
|
Hello, Denis.
Actually, I'm on vacation till July, 31. After it I will put all my efforts to manage Ignite release. Can we wait until Tuesday? В Чт, 26/07/2018 в 17:01 -0700, Denis Magda пишет: > Nikolay, > > Could you please prepare Ignite 2.7 page similar to the following? > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.6 > > We need to start tracking the progress and most essential capabilities that will get into the release. > > -- > Denis > On Tue, Jul 24, 2018 at 1:39 AM Vyacheslav Daradur <[hidden email]> wrote: > > Hi, Igniters! > > > > The end of September for Ignite 2.7 release sounds good to me. > > > > I'm working on Service Grid and going to deliver the following tasks: > > - Use discovery messages for service deployment [[1] > > - Collect service deployment results asynchronously on coordinator [2] > > - Propagate service deployment results from assigned nodes to initiator [3] > > - Handle topology changes during service deployment [4] > > - Propagate deployed services to joining nodes [5] > > - Replace service instance parameter with a class name in > > ServiceConfiguration [6] (planned to be implemented by Amelchev > > Nikita) > > > > [1] https://issues.apache.org/jira/browse/IGNITE-8361 > > [2] https://issues.apache.org/jira/browse/IGNITE-8362 > > [3] https://issues.apache.org/jira/browse/IGNITE-3392 > > [4] https://issues.apache.org/jira/browse/IGNITE-8363 > > [5] https://issues.apache.org/jira/browse/IGNITE-8364 > > [6] https://issues.apache.org/jira/browse/IGNITE-8366 > > On Mon, Jul 23, 2018 at 4:02 PM Dmitry Pavlov <[hidden email]> wrote: > > > > > > Hi Denis, Nikolay, > > > > > > I've issued a number of tickets to update dependencies versions. I would > > > like all these updates are available within 2.7. > > > > > > Sincerely, > > > Dmitriy Pavlov > > > > > > сб, 21 июл. 2018 г. в 3:28, Pavel Petroshenko <[hidden email]>: > > > > > > > Hi Denis, Nikolay, > > > > > > > > The proposed 2.7 release timing sounds reasonable to me. > > > > Python [1], PHP [2], and Node.js [3] thin clients should take the train. > > > > > > > > p. > > > > > > > > [1] https://jira.apache.org/jira/browse/IGNITE-7782 > > > > [2] https://jira.apache.org/jira/browse/IGNITE-7783 > > > > [3] https://jira.apache.org/jira/browse/IGNITE-7777 > > > > > > > > > > > > On Fri, Jul 20, 2018 at 2:35 PM, Denis Magda <[hidden email]> wrote: > > > > > > > > > Igniters, > > > > > > > > > > Let's agree on the time and the scope of 2.7. As for the release manager, > > > > > we had a conversation with Nikolay Izhikov and he decided to try the role > > > > > out. Thanks, Nikolay! > > > > > > > > > > Nikolay, we need to prepare a page like that [1] once the release terms > > > > are > > > > > defined. > > > > > > > > > > I propose us to roll Ignite 2.7 at the end of September. Folks who are > > > > > working on SQL, core, C++/NET, thin clients, ML, service grid > > > > > optimizations, data structures please enlist what you're ready to > > > > deliver. > > > > > > > > > > > > > > > [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.6 > > > > > > > > > > > > > > > |
signature.asc (499 bytes)
Re: Apache Ignite 2.7: scope, time and release manager
|
|
Re: Apache Ignite 2.7: scope, time and release manager
|
|
Hello, Igniters.
Release page created [1]. [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.7 В Пт, 27/07/2018 в 00:52 -0700, Denis Magda пишет: > Sure, it can wait. Thanks! Take a rest ) > > On Thu, Jul 26, 2018 at 11:39 PM Nikolay Izhikov <[hidden email]> > wrote: > > > Hello, Denis. > > > > Actually, I'm on vacation till July, 31. > > After it I will put all my efforts to manage Ignite release. > > > > Can we wait until Tuesday? > > > > В Чт, 26/07/2018 в 17:01 -0700, Denis Magda пишет: > > > Nikolay, > > > > > > Could you please prepare Ignite 2.7 page similar to the following? > > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.6 > > > > > > We need to start tracking the progress and most essential capabilities > > > > that will get into the release. > > > > > > -- > > > Denis > > > On Tue, Jul 24, 2018 at 1:39 AM Vyacheslav Daradur <[hidden email]> > > > > wrote: > > > > Hi, Igniters! > > > > > > > > The end of September for Ignite 2.7 release sounds good to me. > > > > > > > > I'm working on Service Grid and going to deliver the following tasks: > > > > - Use discovery messages for service deployment [[1] > > > > - Collect service deployment results asynchronously on coordinator [2] > > > > - Propagate service deployment results from assigned nodes to > > > > initiator [3] > > > > - Handle topology changes during service deployment [4] > > > > - Propagate deployed services to joining nodes [5] > > > > - Replace service instance parameter with a class name in > > > > ServiceConfiguration [6] (planned to be implemented by Amelchev > > > > Nikita) > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-8361 > > > > [2] https://issues.apache.org/jira/browse/IGNITE-8362 > > > > [3] https://issues.apache.org/jira/browse/IGNITE-3392 > > > > [4] https://issues.apache.org/jira/browse/IGNITE-8363 > > > > [5] https://issues.apache.org/jira/browse/IGNITE-8364 > > > > [6] https://issues.apache.org/jira/browse/IGNITE-8366 > > > > On Mon, Jul 23, 2018 at 4:02 PM Dmitry Pavlov <[hidden email]> > > > > wrote: > > > > > > > > > > Hi Denis, Nikolay, > > > > > > > > > > I've issued a number of tickets to update dependencies versions. I > > > > would > > > > > like all these updates are available within 2.7. > > > > > > > > > > Sincerely, > > > > > Dmitriy Pavlov > > > > > > > > > > сб, 21 июл. 2018 г. в 3:28, Pavel Petroshenko <[hidden email] > > > > > > : > > > > > > > > > > > Hi Denis, Nikolay, > > > > > > > > > > > > The proposed 2.7 release timing sounds reasonable to me. > > > > > > Python [1], PHP [2], and Node.js [3] thin clients should take the > > > > train. > > > > > > > > > > > > p. > > > > > > > > > > > > [1] https://jira.apache.org/jira/browse/IGNITE-7782 > > > > > > [2] https://jira.apache.org/jira/browse/IGNITE-7783 > > > > > > [3] https://jira.apache.org/jira/browse/IGNITE-7777 > > > > > > > > > > > > > > > > > > On Fri, Jul 20, 2018 at 2:35 PM, Denis Magda <[hidden email]> > > > > wrote: > > > > > > > > > > > > > Igniters, > > > > > > > > > > > > > > Let's agree on the time and the scope of 2.7. As for the release > > > > manager, > > > > > > > we had a conversation with Nikolay Izhikov and he decided to try > > > > the role > > > > > > > out. Thanks, Nikolay! > > > > > > > > > > > > > > Nikolay, we need to prepare a page like that [1] once the > > > > release terms > > > > > > are > > > > > > > defined. > > > > > > > > > > > > > > I propose us to roll Ignite 2.7 at the end of September. Folks > > > > who are > > > > > > > working on SQL, core, C++/NET, thin clients, ML, service grid > > > > > > > optimizations, data structures please enlist what you're ready to > > > > > > > > > > > > deliver. > > > > > > > > > > > > > > > > > > > > > [1] > > > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.6 > > > > > > > > > > > > > > > > > > > |
Re: Apache Ignite 2.7: scope, time and release manager
|
|
Re: Apache Ignite 2.7: scope, time and release manager
|
Re: Apache Ignite 2.7: scope, time and release manager
|
|
Thanks, Petr!
В Вт, 31/07/2018 в 16:10 +0300, Petr Ivanov пишет: > Fixed that. > It seems that Heading 2 style was applied to some Jira macros. > > > > > On 31 Jul 2018, at 16:06, Dmitriy Pavlov <[hidden email]> wrote: > > > > Hi Nikolay, > > > > Thank you for this page. It seems font size for some filters is bigger than > > for others. It is intentionally done this way? > > > > Sincerely, > > Dmitriy Pavlov > > > > вт, 31 июл. 2018 г. в 15:57, Nikolay Izhikov <[hidden email]>: > > > > > Hello, Igniters. > > > > > > Release page created [1]. > > > > > > [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.7 > > > > > > В Пт, 27/07/2018 в 00:52 -0700, Denis Magda пишет: > > > > Sure, it can wait. Thanks! Take a rest ) > > > > > > > > On Thu, Jul 26, 2018 at 11:39 PM Nikolay Izhikov <[hidden email]> > > > > wrote: > > > > > > > > > Hello, Denis. > > > > > > > > > > Actually, I'm on vacation till July, 31. > > > > > After it I will put all my efforts to manage Ignite release. > > > > > > > > > > Can we wait until Tuesday? > > > > > > > > > > В Чт, 26/07/2018 в 17:01 -0700, Denis Magda пишет: > > > > > > Nikolay, > > > > > > > > > > > > Could you please prepare Ignite 2.7 page similar to the following? > > > > > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.6 > > > > > > > > > > > > We need to start tracking the progress and most essential > > > > > > capabilities > > > > > > > > > > that will get into the release. > > > > > > > > > > > > -- > > > > > > Denis > > > > > > On Tue, Jul 24, 2018 at 1:39 AM Vyacheslav Daradur < > > > > > > [hidden email]> > > > > > > > > > > wrote: > > > > > > > Hi, Igniters! > > > > > > > > > > > > > > The end of September for Ignite 2.7 release sounds good to me. > > > > > > > > > > > > > > I'm working on Service Grid and going to deliver the following > > > > > > tasks: > > > > > > > - Use discovery messages for service deployment [[1] > > > > > > > - Collect service deployment results asynchronously on coordinator > > > > > > [2] > > > > > > > - Propagate service deployment results from assigned nodes to > > > > > > > > > > initiator [3] > > > > > > > - Handle topology changes during service deployment [4] > > > > > > > - Propagate deployed services to joining nodes [5] > > > > > > > - Replace service instance parameter with a class name in > > > > > > > ServiceConfiguration [6] (planned to be implemented by Amelchev > > > > > > > Nikita) > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-8361 > > > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-8362 > > > > > > > [3] https://issues.apache.org/jira/browse/IGNITE-3392 > > > > > > > [4] https://issues.apache.org/jira/browse/IGNITE-8363 > > > > > > > [5] https://issues.apache.org/jira/browse/IGNITE-8364 > > > > > > > [6] https://issues.apache.org/jira/browse/IGNITE-8366 > > > > > > > On Mon, Jul 23, 2018 at 4:02 PM Dmitry Pavlov < > > > > > > [hidden email]> > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > Hi Denis, Nikolay, > > > > > > > > > > > > > > > > I've issued a number of tickets to update dependencies versions. > > > > > > I > > > > > > > > > > would > > > > > > > > like all these updates are available within 2.7. > > > > > > > > > > > > > > > > Sincerely, > > > > > > > > Dmitriy Pavlov > > > > > > > > > > > > > > > > сб, 21 июл. 2018 г. в 3:28, Pavel Petroshenko < > > > > > > [hidden email] > > > > > > > > > > > > : > > > > > > > > > > > > > > > > > Hi Denis, Nikolay, > > > > > > > > > > > > > > > > > > The proposed 2.7 release timing sounds reasonable to me. > > > > > > > > > Python [1], PHP [2], and Node.js [3] thin clients should take > > > > > > the > > > > > > > > > > train. > > > > > > > > > > > > > > > > > > p. > > > > > > > > > > > > > > > > > > [1] https://jira.apache.org/jira/browse/IGNITE-7782 > > > > > > > > > [2] https://jira.apache.org/jira/browse/IGNITE-7783 > > > > > > > > > [3] https://jira.apache.org/jira/browse/IGNITE-7777 > > > > > > > > > > > > > > > > > > > > > > > > > > > On Fri, Jul 20, 2018 at 2:35 PM, Denis Magda < > > > > > > [hidden email]> > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > Igniters, > > > > > > > > > > > > > > > > > > > > Let's agree on the time and the scope of 2.7. As for the > > > > > > release > > > > > > > > > > manager, > > > > > > > > > > we had a conversation with Nikolay Izhikov and he decided to > > > > > > try > > > > > > > > > > the role > > > > > > > > > > out. Thanks, Nikolay! > > > > > > > > > > > > > > > > > > > > Nikolay, we need to prepare a page like that [1] once the > > > > > > > > > > release terms > > > > > > > > > are > > > > > > > > > > defined. > > > > > > > > > > > > > > > > > > > > I propose us to roll Ignite 2.7 at the end of September. > > > > > > Folks > > > > > > > > > > who are > > > > > > > > > > working on SQL, core, C++/NET, thin clients, ML, service grid > > > > > > > > > > optimizations, data structures please enlist what you're > > > > > > ready to > > > > > > > > > > > > > > > > > > deliver. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > [1] > > > > > > > > > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.6 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > |
Re: Apache Ignite 2.7: scope, time and release manager
|
|
In reply to this post by vveider
Hello, Igniters.
We have 3 not assigned tickets for a 2.7 which is labeled "Important". Who can pick up this tickets? https://issues.apache.org/jira/browse/IGNITE-4191 - SQL: support transactions https://issues.apache.org/jira/browse/IGNITE-5473 - Create ignite troubleshooting logger https://issues.apache.org/jira/browse/IGNITE-6903 - Implement new JMX metrics for Indexing В Вт, 31/07/2018 в 16:10 +0300, Petr Ivanov пишет: > Fixed that. > It seems that Heading 2 style was applied to some Jira macros. > > > > > On 31 Jul 2018, at 16:06, Dmitriy Pavlov <[hidden email]> wrote: > > > > Hi Nikolay, > > > > Thank you for this page. It seems font size for some filters is bigger than > > for others. It is intentionally done this way? > > > > Sincerely, > > Dmitriy Pavlov > > > > вт, 31 июл. 2018 г. в 15:57, Nikolay Izhikov <[hidden email]>: > > > > > Hello, Igniters. > > > > > > Release page created [1]. > > > > > > [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.7 > > > > > > В Пт, 27/07/2018 в 00:52 -0700, Denis Magda пишет: > > > > Sure, it can wait. Thanks! Take a rest ) > > > > > > > > On Thu, Jul 26, 2018 at 11:39 PM Nikolay Izhikov <[hidden email]> > > > > wrote: > > > > > > > > > Hello, Denis. > > > > > > > > > > Actually, I'm on vacation till July, 31. > > > > > After it I will put all my efforts to manage Ignite release. > > > > > > > > > > Can we wait until Tuesday? > > > > > > > > > > В Чт, 26/07/2018 в 17:01 -0700, Denis Magda пишет: > > > > > > Nikolay, > > > > > > > > > > > > Could you please prepare Ignite 2.7 page similar to the following? > > > > > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.6 > > > > > > > > > > > > We need to start tracking the progress and most essential > > > > > > capabilities > > > > > > > > > > that will get into the release. > > > > > > > > > > > > -- > > > > > > Denis > > > > > > On Tue, Jul 24, 2018 at 1:39 AM Vyacheslav Daradur < > > > > > > [hidden email]> > > > > > > > > > > wrote: > > > > > > > Hi, Igniters! > > > > > > > > > > > > > > The end of September for Ignite 2.7 release sounds good to me. > > > > > > > > > > > > > > I'm working on Service Grid and going to deliver the following > > > > > > tasks: > > > > > > > - Use discovery messages for service deployment [[1] > > > > > > > - Collect service deployment results asynchronously on coordinator > > > > > > [2] > > > > > > > - Propagate service deployment results from assigned nodes to > > > > > > > > > > initiator [3] > > > > > > > - Handle topology changes during service deployment [4] > > > > > > > - Propagate deployed services to joining nodes [5] > > > > > > > - Replace service instance parameter with a class name in > > > > > > > ServiceConfiguration [6] (planned to be implemented by Amelchev > > > > > > > Nikita) > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-8361 > > > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-8362 > > > > > > > [3] https://issues.apache.org/jira/browse/IGNITE-3392 > > > > > > > [4] https://issues.apache.org/jira/browse/IGNITE-8363 > > > > > > > [5] https://issues.apache.org/jira/browse/IGNITE-8364 > > > > > > > [6] https://issues.apache.org/jira/browse/IGNITE-8366 > > > > > > > On Mon, Jul 23, 2018 at 4:02 PM Dmitry Pavlov < > > > > > > [hidden email]> > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > Hi Denis, Nikolay, > > > > > > > > > > > > > > > > I've issued a number of tickets to update dependencies versions. > > > > > > I > > > > > > > > > > would > > > > > > > > like all these updates are available within 2.7. > > > > > > > > > > > > > > > > Sincerely, > > > > > > > > Dmitriy Pavlov > > > > > > > > > > > > > > > > сб, 21 июл. 2018 г. в 3:28, Pavel Petroshenko < > > > > > > [hidden email] > > > > > > > > > > > > : > > > > > > > > > > > > > > > > > Hi Denis, Nikolay, > > > > > > > > > > > > > > > > > > The proposed 2.7 release timing sounds reasonable to me. > > > > > > > > > Python [1], PHP [2], and Node.js [3] thin clients should take > > > > > > the > > > > > > > > > > train. > > > > > > > > > > > > > > > > > > p. > > > > > > > > > > > > > > > > > > [1] https://jira.apache.org/jira/browse/IGNITE-7782 > > > > > > > > > [2] https://jira.apache.org/jira/browse/IGNITE-7783 > > > > > > > > > [3] https://jira.apache.org/jira/browse/IGNITE-7777 > > > > > > > > > > > > > > > > > > > > > > > > > > > On Fri, Jul 20, 2018 at 2:35 PM, Denis Magda < > > > > > > [hidden email]> > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > Igniters, > > > > > > > > > > > > > > > > > > > > Let's agree on the time and the scope of 2.7. As for the > > > > > > release > > > > > > > > > > manager, > > > > > > > > > > we had a conversation with Nikolay Izhikov and he decided to > > > > > > try > > > > > > > > > > the role > > > > > > > > > > out. Thanks, Nikolay! > > > > > > > > > > > > > > > > > > > > Nikolay, we need to prepare a page like that [1] once the > > > > > > > > > > release terms > > > > > > > > > are > > > > > > > > > > defined. > > > > > > > > > > > > > > > > > > > > I propose us to roll Ignite 2.7 at the end of September. > > > > > > Folks > > > > > > > > > > who are > > > > > > > > > > working on SQL, core, C++/NET, thin clients, ML, service grid > > > > > > > > > > optimizations, data structures please enlist what you're > > > > > > ready to > > > > > > > > > > > > > > > > > > deliver. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > [1] > > > > > > > > > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.6 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > |
Re: Apache Ignite 2.7: scope, time and release manager
|
|
| Free forum by Nabble | Edit this page |