Igniters,
I would like Mesos integration update be included in the upcoming release.Can
anyone review prs for the following issues?
IGNITE-9388: mesos IgniteProvider tries to access obsolete ignite.run or
download from slow archiveIGNITE-9408: Update mesos version
Roman Shtykh
On Thursday, August 30, 2018, 9:25:43 p.m. GMT+9, Vyacheslav Daradur
<daradu...@gmail.com> wrote:
Hi Igniters!
I'm working on the following Service Grid tasks:
- IGNITE-8361 Use discovery messages for service deployment
- IGNITE-8362 Collect service deployment results asynchronously on coordinator
- IGNITE-8363 Handle topology changes during service deployment
- IGNITE-8364 Propagate deployed services to joining nodes
- IGNITE-8365 Introduce service failure events
- IGNITE-3392 Propagate service deployment results from assigned nodes
to initiator
Let's call them *phase 1* because the should be implemented together
(atomically).
I do my best to finish phase 1 for including to 2.7 release.
But I'm not sure that the solution will be fully completed till the
beginning of October.
On Wed, Aug 29, 2018 at 7:18 PM Nikolay Izhikov <nizhi...@apache.org> wrote:
>
> Hell, Yakov
>
> I'm ok with your proposal.
>
> * Scope freeze - September 17 - We should have a full list of tickets
>for 2.7 here.
> * Code freeze - October 01 - We should merge all 2.7 tickets to master
>here.
> * Vote on RC1 - October 11.
> * Vote on release - October 15.
>
> В Ср, 29/08/2018 в 12:39 +0300, Yakov Zhdanov пишет:
> > Nikolay,
> >
> > I think we should have 2 weeks after code freeze which by the way may
> > include RC1 voting stage. This way I would like us to agree that release
> > candidate should be sent to vote on Oct, 11th and we can release on Oct,
> > 15th.
> >
> > What do you think?
> >
> > --Yakov
--
Best Regards, Vyacheslav D.
