Re: Apache Ignite 2.7 - Service Grid Redesign
Val can be the final reviewer. He knows this component pretty well. Val, could you help the guys with this? -- Denis On Wed, Sep 19, 2018 at 3:14 AM Anton Vinogradov wrote: > Nikolay, > > I'll perform prereview once PR will be ready. > Then we'll need some time to fix all found issues. > After that final review by another expert will be required. > > Let's define the deadline for final PR and reviewer (Alexey Goncharuk?). > In other words, let's define the exact date until which final PR should be > provided to have chances to become a part of 2.7. > > > ср, 19 сент. 2018 г. в 12:46, Nikolay Izhikov : > > > Hello, Igniters. > > > > Currently, we are working on release scope for Apache Ignite 2.7 > > We had plans to include "Service Grid Redesign. Phase 1" to 2.7 release. > > > > If I understand correctly, the plan is following - We should have PR that > > is ready for review at the end of September. > > > > This deadline is very close to the code freeze date. > > > > Let's discuss, how we should handle this risks? > > Who will be able to review this PR when it's will be ready? > > Vyacheslav, can you comment on this? > > >
Re: Apache Ignite 2.7 - Service Grid Redesign
Hi Igniters! I've filled an umbrella ticket [1] to track all tickets which will be implemented in phase 1. We reworked internals completely that allow us to provide us with several main features: * synchronous deployment * propagation of deployment errors across the cluster * basic deployment failure policies * processing pending requests in case of coordinator change * etc. The solution will be ready for review, at best, 30 of September. If code freeze will be at the end of September, then we have no time to do a review. Are we sure that we don't have other tasks which will be included in 2.7 and may move the code freeze date? [1] https://issues.apache.org/jira/browse/IGNITE-9607 On Wed, Sep 19, 2018 at 1:14 PM Anton Vinogradov wrote: > > Nikolay, > > I'll perform prereview once PR will be ready. > Then we'll need some time to fix all found issues. > After that final review by another expert will be required. > > Let's define the deadline for final PR and reviewer (Alexey Goncharuk?). > In other words, let's define the exact date until which final PR should be > provided to have chances to become a part of 2.7. > > > ср, 19 сент. 2018 г. в 12:46, Nikolay Izhikov : >> >> Hello, Igniters. >> >> Currently, we are working on release scope for Apache Ignite 2.7 >> We had plans to include "Service Grid Redesign. Phase 1" to 2.7 release. >> >> If I understand correctly, the plan is following - We should have PR that >> is ready for review at the end of September. >> >> This deadline is very close to the code freeze date. >> >> Let's discuss, how we should handle this risks? >> Who will be able to review this PR when it's will be ready? >> Vyacheslav, can you comment on this? -- Best Regards, Vyacheslav D.
Re: Apache Ignite 2.7 - Service Grid Redesign
Nikolay, I'll perform prereview once PR will be ready. Then we'll need some time to fix all found issues. After that final review by another expert will be required. Let's define the deadline for final PR and reviewer (Alexey Goncharuk?). In other words, let's define the exact date until which final PR should be provided to have chances to become a part of 2.7. ср, 19 сент. 2018 г. в 12:46, Nikolay Izhikov : > Hello, Igniters. > > Currently, we are working on release scope for Apache Ignite 2.7 > We had plans to include "Service Grid Redesign. Phase 1" to 2.7 release. > > If I understand correctly, the plan is following - We should have PR that > is ready for review at the end of September. > > This deadline is very close to the code freeze date. > > Let's discuss, how we should handle this risks? > Who will be able to review this PR when it's will be ready? > Vyacheslav, can you comment on this? >
Apache Ignite 2.7 - Service Grid Redesign
Hello, Igniters. Currently, we are working on release scope for Apache Ignite 2.7 We had plans to include "Service Grid Redesign. Phase 1" to 2.7 release. If I understand correctly, the plan is following - We should have PR that is ready for review at the end of September. This deadline is very close to the code freeze date. Let's discuss, how we should handle this risks? Who will be able to review this PR when it's will be ready? Vyacheslav, can you comment on this?
