Igniters,
Recently, I have filed an issue [1] that deals with possible hanging of WAL
logging. I will appreciate your thoughts on its severity. To make logging
hang two conditions should be satisfied: WAL mode is {{FSYNC}}, and WAL
archiving is disabled. Should we investigate and fix this immediately or is
it possible to postpone till 2.8?
[1] https://issues.apache.org/jira/browse/IGNITE-9776
вт, 9 окт. 2018 г. в 11:17, Andrey Kuznetsov <stku...@gmail.com>:
> Ignite committers,
>
> I have prepared a PR for 2.7 blocker [1]. Could anybody merge it to 2.7
> and master?
>
> [1] https://issues.apache.org/jira/browse/IGNITE-9737
>
>
> ср, 3 окт. 2018 г. в 14:02, Nikolay Izhikov <nizhi...@apache.org>:
>
>> Alexey.
>>
>> Sorry, I lost link to IGNITE-9760 in this thread :)
>>
>> Thanks, for a clarification.
>>
>>
>> В Ср, 03/10/2018 в 13:58 +0300, Alexey Goncharuk пишет:
>> > Nikolay, both commits fixed a regression compared to ignite-2.6. First
>> one was mentioned by Anton Kalashnikov before (java-level deadlock during
>> WAL flush), another - by Andrey Kuznetsov (NPE during a concurrent WAL
>> flush).
>> >
>> > --AG
>> >
>> > ср, 3 окт. 2018 г. в 13:38, Nikolay Izhikov <nizhi...@apache.org>:
>> > > Hello, Igniters.
>> > >
>> > > Release scope is frozen.
>> > > Please, if you include some new issues in release - discuss it in
>> this thread.
>> > >
>> > > Alexey, can you, please, comment on including fix for IGNITE-9760,
>> IGNITE-9761 in 2.7 branch.
>> > >
>> > >
>> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=commit;h=3355201f3e8cafd23b2250aaccccf3b91b8b8ed1
>> > >
>> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=commit;h=9d6e6ff394c05ddf7ef31a9d9ed1b492d9eeba69
>> > >
>> > > В Ср, 03/10/2018 в 13:24 +0300, Vladimir Ozerov пишет:
>> > > > Nobody vetos anything, let's stop use this term unless some really
>> > > > important problem is discussed.
>> > > >
>> > > > At this point we are in situation when new tickets are still
>> included into
>> > > > the scope. All want to ask is to stop including new tickets without
>> > > > explaining on why they should be in AI 2.7. Regression between is
>> AI 2.6
>> > > > and AI 2.7 is enough. But "I found new NPE" is not.
>> > > >
>> > > > On Wed, Oct 3, 2018 at 11:10 AM Dmitriy Pavlov <
>> dpavlov....@gmail.com>
>> > > > wrote:
>> > > >
>> > > > > Nikolay,
>> > > > >
>> > > > > this has nothing about scaring someone. Let me explain about
>> Apache Way.
>> > > > >
>> > > > > Voting -1 to release does not mean blocking it, release can't be
>> vetoed.
>> > > > > Approving release is done by policy: majority approval. 3+1
>> binding and
>> > > > > more +1 than -1. Consensus approval is better but not mandatory.
>> > > > >
>> > > > > Instead, if PMC says -1 to code modification it means veto and
>> can't be
>> > > > > bypassed to anyone. This is a very strong statement, which should
>> be
>> > > > > applied reasonably and with technical justification. Lack of
>> > > > > understanding is not a justification.
>> > > > >
>> > > > > So my point instead of vetoing bugfix let's veto commits where
>> the bugs
>> > > > > were introduced. I feel a number of bugs reported recently are all
>> > > > > connected to WalManager, and these bugs may come from just a
>> couple of
>> > > > > fixes. PDS tests were quite stable last time, so I think it is
>> possible to
>> > > > > find out why WAL crashes and hangs.
>> > > > >
>> > > > > Sincerely,
>> > > > > Dmitriy Pavlov
>> > > > >
>> > > > > ср, 3 окт. 2018 г. в 10:05, Andrey Kuznetsov <stku...@gmail.com>:
>> > > > >
>> > > > > > Vladimir, Nikolay,
>> > > > > >
>> > > > > > For sure, I'm not an experienced Ignite contributor, so I'm
>> sorry for
>> > > > > > intervening. I've just run the reproducer from [1] against
>> ignite-2.6
>> > > > > > branch and it has passed. So, it's not an legacy bug, we've
>> brought it
>> > > > >
>> > > > > with
>> > > > > > some change of 2.7 scope. Is it still ok to ignore the bug?
>> > > > > >
>> > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-9776
>> > > > > >
>> > > > > > ср, 3 окт. 2018 г. в 2:07, Nikolay Izhikov <nizhi...@apache.org
>> >:
>> > > > > >
>> > > > > > > Hello, Dmitriy.
>> > > > > > >
>> > > > > > > I'm sorry, but I don't understand your concern.
>> > > > > > >
>> > > > > > > Vladimir just asks experienced Ignite contributor to *explain
>> impact*
>> > > > >
>> > > > > of
>> > > > > > a
>> > > > > > > bug.
>> > > > > > >
>> > > > > > > Why are you scaring us with your "-1"?
>> > > > > > > Is it Apache Way to do so?
>> > > > > > > What should be done for you to return to a constructive
>> discussion?
>> > > > > > >
>> > > > > > > В Ср, 03/10/2018 в 00:23 +0300, Dmitriy Pavlov пишет:
>> > > > > > > > Hi Igniters, Vladimir,
>> > > > > > > >
>> > > > > > > > NPEs or hangs in WAL is a completely non-functional grid (if
>> > > > > >
>> > > > > > persistence
>> > > > > > > > enabled).
>> > > > > > > >
>> > > > > > > > I see no reasons to release 2.7 with such symptoms until
>> we're sure
>> > > > >
>> > > > > it
>> > > > > > is
>> > > > > > > > too rare/impossible to reproduce. But it seems it is not
>> the case. I
>> > > > > >
>> > > > > > will
>> > > > > > > > definitely vote -1 for the release if I'm aware of such
>> problems
>> > > > >
>> > > > > exist
>> > > > > > > and
>> > > > > > > > were not researched. Community guarantees the quality and
>> usability
>> > > > >
>> > > > > of
>> > > > > > > the
>> > > > > > > > product.
>> > > > > > > >
>> > > > > > > > We should ask and answer other questions:
>> > > > > > > > 1) why there are a lot of NPEs and hangs reported recently
>> in the
>> > > > >
>> > > > > same
>> > > > > > > area
>> > > > > > > > 2) and why we signed-off commit(s).
>> > > > > > > >
>> > > > > > > > Probably we can identify and revert these commit(s) from
>> 2.7 and
>> > > > > >
>> > > > > > research
>> > > > > > > > these failures in master (with no rush).
>> > > > > > > >
>> > > > > > > > Sincerely,
>> > > > > > > > Dmitriy Pavlov
>> > > > > > > >
>> > > > > > > > вт, 2 окт. 2018 г. в 23:54, Vladimir Ozerov <
>> voze...@gridgain.com>:
>> > > > > > > >
>> > > > > > > > > Andrey, Anton,
>> > > > > > > > >
>> > > > > > > > > How do you conclude that these tickets are blockers? What
>> is the
>> > > > > > >
>> > > > > > > impact to
>> > > > > > > > > users and in what circumstances users can met them?
>> > > > > > > > >
>> > > > > > > > > Note that we have many hundreds opened bugs, and yet we
>> do not
>> > > > >
>> > > > > strive
>> > > > > > > to
>> > > > > > > > > include them all, because bug != blocker.
>> > > > > > > > >
>> > > > > > > > > So -1 from my side to including these tickets to release
>> scope,
>> > > > > >
>> > > > > > unless
>> > > > > > > > > impact is explained.
>> > > > > > > > >
>> > > > > > > > > Vladimir.
>> > > > > > > > >
>> > > > > > > > > вт, 2 окт. 2018 г. в 22:45, Andrey Kuznetsov <
>> stku...@gmail.com>:
>> > > > > > > > >
>> > > > > > > > > > I've caught a bug [1] in
>> FsyncModeFileWriteAheadLogManager. It
>> > > > > >
>> > > > > > looks
>> > > > > > > > >
>> > > > > > > > > like a
>> > > > > > > > > > release blocker to me.
>> > > > > > > > > >
>> > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-9776
>> > > > > > > > > >
>> > > > > > > > > > вт, 2 окт. 2018 г. в 13:14, Dmitriy Pavlov <
>> > > > >
>> > > > > dpavlov....@gmail.com
>> > > > > > > :
>> > > > > > > > > >
>> > > > > > > > > > > Hi Anton,
>> > > > > > > > > > >
>> > > > > > > > > > > I definitely agree it is a blocker.
>> > > > > > > > > > >
>> > > > > > > > > > > Sincerely,
>> > > > > > > > > > > Dmitriy Pavlov
>> > > > > > > > > > >
>> > > > > > > > > > > вт, 2 окт. 2018 г. в 13:09, Anton Kalashnikov <
>> > > > >
>> > > > > kaa....@yandex.ru
>> > > > > > > :
>> > > > > > > > > > >
>> > > > > > > > > > > > Hi Igniters.
>> > > > > > > > > > > >
>> > > > > > > > > > > > I have one more possible blockers - deadlock in
>> archiver -
>> > > > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-9761.
>> I almost
>> > > > > > >
>> > > > > > > fixed
>> > > > > > > > >
>> > > > > > > > > it.
>> > > > > > > > > > > > It seems it should be include to scope.
>> > > > > > > > > > > >
>> > > > > > > > > > > > --
>> > > > > > > > > > > > Best regards,
>> > > > > > > > > > > > Anton Kalashnikov
>> > > > > > > > > > > >
>> > > > > > > > > > > >
>> > > > > > > > > > > > 02.10.2018, 00:08, "Dmitriy Setrakyan" <
>> > > > >
>> > > > > dsetrak...@apache.org
>> > > > > > > :
>> > > > > > > > > > > > > Thanks, got it.
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > On Mon, Oct 1, 2018 at 1:14 PM Dmitriy Pavlov <
>> > > > > > > > >
>> > > > > > > > > dpavlov....@gmail.com
>> > > > > > > > > > >
>> > > > > > > > > > > > wrote:
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > > Here I agree with Vladimir. Furthermore, I do
>> my
>> > > > >
>> > > > > absolute
>> > > > > > > best to
>> > > > > > > > > > > >
>> > > > > > > > > > > > finalize
>> > > > > > > > > > > > > > all reviews in all 2.7 tickets I'm related to.
>> I think
>> > > > > >
>> > > > > > most
>> > > > > > > of
>> > > > > > > > >
>> > > > > > > > > the
>> > > > > > > > > > > > > > contributors doing the same.
>> > > > > > > > > > > > > >
>> > > > > > > > > > > > > > пн, 1 окт. 2018 г. в 23:03, Vladimir Ozerov <
>> > > > > > > > >
>> > > > > > > > > voze...@gridgain.com
>> > > > > > > > > > > :
>> > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > This is precisely the scope we have at the
>> moment. All
>> > > > > > >
>> > > > > > > these
>> > > > > > > > > > >
>> > > > > > > > > > > tickets
>> > > > > > > > > > > > were
>> > > > > > > > > > > > > > > considered carefully on whether to include
>> them into
>> > > > >
>> > > > > AI
>> > > > > > > 2.7
>> > > > > > > > > >
>> > > > > > > > > > scope.
>> > > > > > > > > > > I
>> > > > > > > > > > > > > > would
>> > > > > > > > > > > > > > > say that 10-15% of current tickets may be
>> moved
>> > > > >
>> > > > > furhter.
>> > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > Third of current tickets are features on
>> their final
>> > > > > > >
>> > > > > > > review
>> > > > > > > > > >
>> > > > > > > > > > stages
>> > > > > > > > > > > > (e.g.
>> > > > > > > > > > > > > > > TDE, MVCC invoke, TensorFlow, Thin Clients),
>> another
>> > > > >
>> > > > > big
>> > > > > > > part
>> > > > > > > > >
>> > > > > > > > > is
>> > > > > > > > > > > > > > > stabilization tickets (mainly - various test
>> > > > >
>> > > > > failures),
>> > > > > > > and
>> > > > > > > > > >
>> > > > > > > > > > another
>> > > > > > > > > > > > big
>> > > > > > > > > > > > > > > part is infrastructure (adopting new
>> modules, Java 9+
>> > > > > > >
>> > > > > > > support,
>> > > > > > > > > > > >
>> > > > > > > > > > > > etc.). So
>> > > > > > > > > > > > > > > despite big absolute number, most of these
>> tickets are
>> > > > > > >
>> > > > > > > grouped
>> > > > > > > > > > >
>> > > > > > > > > > > around
>> > > > > > > > > > > > > > > several big areas, and overall progress over
>> this week
>> > > > > > >
>> > > > > > > should
>> > > > > > > > >
>> > > > > > > > > be
>> > > > > > > > > > > very
>> > > > > > > > > > > > > > good.
>> > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > On Mon, Oct 1, 2018 at 9:50 PM Dmitriy
>> Setrakyan <
>> > > > > > > > > > > >
>> > > > > > > > > > > > dsetrak...@apache.org>
>> > > > > > > > > > > > > > > wrote:
>> > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > If this filter is for 2.7 release, then I
>> do not
>> > > > > > >
>> > > > > > > believe all
>> > > > > > > > > > >
>> > > > > > > > > > > these
>> > > > > > > > > > > > > > > tickets
>> > > > > > > > > > > > > > > > will be closed. It would be nice to leave
>> only
>> > > > > > >
>> > > > > > > "must-have"
>> > > > > > > > > > >
>> > > > > > > > > > > tickets
>> > > > > > > > > > > > in
>> > > > > > > > > > > > > > 2.7
>> > > > > > > > > > > > > > > > and move the rest to 2.8.
>> > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > D.
>> > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > On Mon, Oct 1, 2018 at 11:02 AM Vladimir
>> Ozerov <
>> > > > > > > > > > > >
>> > > > > > > > > > > > voze...@gridgain.com>
>> > > > > > > > > > > > > > > > wrote:
>> > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > Igniters,
>> > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > Please use this filter, as it properly
>> handles
>> > > > > >
>> > > > > > tickets
>> > > > > > > > > >
>> > > > > > > > > > without
>> > > > > > > > > > > > > > > > components:
>> > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > >
>> > > > > > > > > > > > > >
>> > > > > > > > >
>> > > > > > > > >
>> > > > >
>> > > > >
>> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.7%27)%20AND%20status%20NOT%20IN%20(Resolved%2C%20Closed)%20and%20(component%20is%20null%20or%20component%20not%20in%20(documentation)))%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20%20%20%20%20%20
>> > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > On Mon, Oct 1, 2018 at 6:18 PM Nikolay
>> Izhikov <
>> > > > > > > > > > > >
>> > > > > > > > > > > > nizhi...@apache.org>
>> > > > > > > > > > > > > > > > > wrote:
>> > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > Hello, Igniters.
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > I announce scope freeze for an Apache
>> Ignite 2.7
>> > > > > > >
>> > > > > > > release.
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > It means:
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > 1. We add to 2.7 only critical bugs.
>> > > > > > > > > > > > > > > > > > 2. We merge to 2.7 branch only
>> previously
>> > > > > >
>> > > > > > announces
>> > > > > > > > > >
>> > > > > > > > > > features.
>> > > > > > > > > > > > > > > > > > 3. I expect we should exclude or
>> *MERGE ALL
>> > > > >
>> > > > > TASKS
>> > > > > > > FOR 2.7
>> > > > > > > > > >
>> > > > > > > > > > DUE
>> > > > > > > > > > > > TO
>> > > > > > > > > > > > > > > > OCTOBER
>> > > > > > > > > > > > > > > > > > 10*.
>> > > > > > > > > > > > > > > > > > So the *October 10 is DEADLINE* for new
>> > > > >
>> > > > > features.
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > Thoughts?
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > For now we have 34 In Progress tickets
>> planned
>> > > > >
>> > > > > to
>> > > > > > > 2.7
>> > > > > > > > > >
>> > > > > > > > > > version
>> > > > > > > > > > > > [1].
>> > > > > > > > > > > > > > > > > > So is you assigned to any of this
>> ticker
>> > > > >
>> > > > > friendly
>> > > > > > > > >
>> > > > > > > > > reminder
>> > > > > > > > > > > #1,
>> > > > > > > > > > > > *the
>> > > > > > > > > > > > > > > > > > deadline is near :)*.
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > [1]
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > >
>> > > > > > > > > > > > > >
>> > > > > > > > >
>> > > > > > > > >
>> > > > >
>> > > > >
>> https://issues.apache.org/jira/browse/IGNITE-8803?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.7%27)%20AND%20status%20NOT%20IN%20(Resolved%2C%20Closed)%20and%20component%20!%3D%20documentation%20)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20%20%20%20%20%20
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > В Пн, 01/10/2018 в 16:13 +0300, Andrey
>> Gura
>> > > > >
>> > > > > пишет:
>> > > > > > > > > > > > > > > > > > > Agree with Andrey.
>> > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > IGNITE-9723 will be merged to
>> ignite-2.7
>> > > > >
>> > > > > branch
>> > > > > > > soon.
>> > > > > > > > > > > > > > > > > > > On Mon, Oct 1, 2018 at 3:56 PM Andrey
>> > > > >
>> > > > > Kuznetsov
>> > > > > > <
>> > > > > > > > > > > > > > stku...@gmail.com
>> > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > wrote:
>> > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > Igniters,
>> > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > There is an inaccuracy in critical
>> worker
>> > > > > > >
>> > > > > > > termination
>> > > > > > > > > > > > > > detection,
>> > > > > > > > > > > > > > > > and
>> > > > > > > > > > > > > > > > > > I'm
>> > > > > > > > > > > > > > > > > > > > working on a fix right now, see
>> [1]. Also,
>> > > > >
>> > > > > we
>> > > > > > > have
>> > > > > > > > > > >
>> > > > > > > > > > > trivial
>> > > > > > > > > > > > yet
>> > > > > > > > > > > > > > > > > > important
>> > > > > > > > > > > > > > > > > > > > fix [2], this one is ready to
>> merge.
>> > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > I deem both should get to 2.7. Any
>> > > > >
>> > > > > objections?
>> > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > [1]
>> > > > > > > > >
>> > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-9744
>> > > > > > > > > > > > > > > > > > > > [2]
>> > > > > > > > >
>> > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-9723
>> > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > пн, 1 окт. 2018 г. в 13:13,
>> Dmitriy Pavlov <
>> > > > > > > > > > > > > > > dpavlov....@gmail.com
>> > > > > > > > > > > > > > > > >:
>> > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > Folks,
>> > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > We can consider this thread as
>> an almost
>> > > > > > >
>> > > > > > > healthy
>> > > > > > > > > > > >
>> > > > > > > > > > > > discussion
>> > > > > > > > > > > > > > > about
>> > > > > > > > > > > > > > > > > SG
>> > > > > > > > > > > > > > > > > > > > > inclusion to 2.7.
>> > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > For the future, I encourage all
>> Igniters
>> > > > >
>> > > > > to
>> > > > > > > discuss
>> > > > > > > > > > > >
>> > > > > > > > > > > > things
>> > > > > > > > > > > > > > > before
>> > > > > > > > > > > > > > > > > > agreement
>> > > > > > > > > > > > > > > > > > > > > on dev.list instead of trying to
>> log 'some
>> > > > > > > > >
>> > > > > > > > > pre-build
>> > > > > > > > > > > > > > > agreements'
>> > > > > > > > > > > > > > > > > > here. BTW
>> > > > > > > > > > > > > > > > > > > > > such logged 'agreements' are not
>> always
>> > > > > >
>> > > > > > valid.
>> > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > Dev list is not a log of
>> community
>> > > > >
>> > > > > actions;
>> > > > > > > it is
>> > > > > > > > >
>> > > > > > > > > the
>> > > > > > > > > > > > > > principal
>> > > > > > > > > > > > > > > > > > place where
>> > > > > > > > > > > > > > > > > > > > > discussion runs. I sincerely
>> hope all
>> > > > > >
>> > > > > > similar
>> > > > > > > > > >
>> > > > > > > > > > decisions
>> > > > > > > > > > > > will
>> > > > > > > > > > > > > > be
>> > > > > > > > > > > > > > > > > > building on
>> > > > > > > > > > > > > > > > > > > > > the dev list.
>> > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > Sincerely,
>> > > > > > > > > > > > > > > > > > > > > Dmitriy Pavlov
>> > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > вс, 30 сент. 2018 г. в 10:49,
>> Nikolay
>> > > > > >
>> > > > > > Izhikov
>> > > > > > > <
>> > > > > > > > > > > > > > > > nizhi...@apache.org
>> > > > > > > > > > > > > > > > > >:
>> > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > Hello, guys.
>> > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > I moved SG tasks to 2.8.
>> > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > В Сб, 29/09/2018 в 17:11
>> +0300, Vladimir
>> > > > > > >
>> > > > > > > Ozerov
>> > > > > > > > > > >
>> > > > > > > > > > > пишет:
>> > > > > > > > > > > > > > > > > > > > > > > I fully support Dmitry's
>> concerns. I
>> > > > >
>> > > > > do
>> > > > > > > not
>> > > > > > > > >
>> > > > > > > > > see a
>> > > > > > > > > > > > single
>> > > > > > > > > > > > > > > > chance
>> > > > > > > > > > > > > > > > > > for
>> > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > Service
>> > > > > > > > > > > > > > > > > > > > > > > Grid to be included into 2.7
>> scope,
>> > > > >
>> > > > > but
>> > > > > > > we are
>> > > > > > > > > > >
>> > > > > > > > > > > still
>> > > > > > > > > > > > > > > keeping
>> > > > > > > > > > > > > > > > > hope
>> > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > alive.
>> > > > > > > > > > > > > > > > > > > > > > > What for? Our experience
>> shows, that
>> > > > >
>> > > > > any
>> > > > > > > > >
>> > > > > > > > > feature
>> > > > > > > > > > > > > > involving
>> > > > > > > > > > > > > > > > > > consensus
>> > > > > > > > > > > > > > > > > > > > > > > algorithms typically take
>> weeks to be
>> > > > > > >
>> > > > > > > finalized
>> > > > > > > > > > >
>> > > > > > > > > > > after
>> > > > > > > > > > > > > > > initial
>> > > > > > > > > > > > > > > > > > public
>> > > > > > > > > > > > > > > > > > > > > > > review. Yes, it is possible
>> that at
>> > > > >
>> > > > > some
>> > > > > > > day in
>> > > > > > > > > > > >
>> > > > > > > > > > > > October
>> > > > > > > > > > > > > > we
>> > > > > > > > > > > > > > > > will
>> > > > > > > > > > > > > > > > > > see it
>> > > > > > > > > > > > > > > > > > > > > > > completed, but what about
>> testing?
>> > > > >
>> > > > > What
>> > > > > > > about
>> > > > > > > > > > > >
>> > > > > > > > > > > > regressions
>> > > > > > > > > > > > > > > > with
>> > > > > > > > > > > > > > > > > > other
>> > > > > > > > > > > > > > > > > > > > > > > components? Let me reming
>> you that
>> > > > >
>> > > > > from
>> > > > > > > Monday
>> > > > > > > > >
>> > > > > > > > > a
>> > > > > > > > > > > lot
>> > > > > > > > > > > > of
>> > > > > > > > > > > > > > > > efforts
>> > > > > > > > > > > > > > > > > > will be
>> > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > put
>> > > > > > > > > > > > > > > > > > > > > > > into project stabilization.
>> This is
>> > > > >
>> > > > > the
>> > > > > > > sole
>> > > > > > > > > > >
>> > > > > > > > > > > purpose
>> > > > > > > > > > > > of
>> > > > > > > > > > > > > > > that
>> > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > pre-release
>> > > > > > > > > > > > > > > > > > > > > > > phase. Accepting a patch
>> with deep
>> > > > > >
>> > > > > > rework
>> > > > > > > of
>> > > > > > > > > >
>> > > > > > > > > > Ignite
>> > > > > > > > > > > > > > > internals
>> > > > > > > > > > > > > > > > > in
>> > > > > > > > > > > > > > > > > > the
>> > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > middle
>> > > > > > > > > > > > > > > > > > > > > > > of that process, means that
>> our
>> > > > >
>> > > > > effrots
>> > > > > > > will be
>> > > > > > > > > > >
>> > > > > > > > > > > lost.
>> > > > > > > > > > > > > > This
>> > > > > > > > > > > > > > > is
>> > > > > > > > > > > > > > > > > > simply a
>> > > > > > > > > > > > > > > > > > > > > > > matter of respect to
>> contributor's
>> > > > >
>> > > > > time.
>> > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > Another problem is that this
>> false
>> > > > >
>> > > > > hope
>> > > > > > > puts us
>> > > > > > > > > >
>> > > > > > > > > > at
>> > > > > > > > > > > > rush.
>> > > > > > > > > > > > > > > Rush
>> > > > > > > > > > > > > > > > > > during
>> > > > > > > > > > > > > > > > > > > > > > > design, development, review,
>> testing.
>> > > > > > >
>> > > > > > > Result is
>> > > > > > > > > > > >
>> > > > > > > > > > > > known -
>> > > > > > > > > > > > > > bad
>> > > > > > > > > > > > > > > > > > features,
>> > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > which
>> > > > > > > > > > > > > > > > > > > > > > > makes damage to the project.
>> > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > So my question is - why
>> don't we just
>> > > > > > >
>> > > > > > > want to
>> > > > > > > > > >
>> > > > > > > > > > move
>> > > > > > > > > > > > it to
>> > > > > > > > > > > > > > AI
>> > > > > > > > > > > > > > > > 2.8
>> > > > > > > > > > > > > > > > > > right
>> > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > now?
>> > > > > > > > > > > > > > > > > > > > > > > Feature is big, feature is
>> very far
>> > > > >
>> > > > > from
>> > > > > > > being
>> > > > > > > > > > >
>> > > > > > > > > > > ready.
>> > > > > > > > > > > > > > This
>> > > > > > > > > > > > > > > > > simple
>> > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > action
>> > > > > > > > > > > > > > > > > > > > > > > immediately shifts the focus
>> from
>> > > > >
>> > > > > dates
>> > > > > > to
>> > > > > > > > > >
>> > > > > > > > > > quality
>> > > > > > > > > > > > of the
>> > > > > > > > > > > > > > > > > > product, and
>> > > > > > > > > > > > > > > > > > > > > > > remove any risks that
>> potential merge
>> > > > > >
>> > > > > > will
>> > > > > > > > >
>> > > > > > > > > defeat
>> > > > > > > > > > > > > > > > stabilization
>> > > > > > > > > > > > > > > > > > effrots
>> > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > of
>> > > > > > > > > > > > > > > > > > > > > > > other contributors.
>> > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > On Sat, Sep 29, 2018 at 8:32
>> AM
>> > > > > >
>> > > > > > Vyacheslav
>> > > > > > > > > >
>> > > > > > > > > > Daradur
>> > > > > > > > > > > <
>> > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > daradu...@gmail.com>
>> > > > > > > > > > > > > > > > > > > > > > > wrote:
>> > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > Dmitriy,
>> > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > Hot redeployment and
>> versioning will
>> > > > > > >
>> > > > > > > not be
>> > > > > > > > > > > >
>> > > > > > > > > > > > implemented
>> > > > > > > > > > > > > > > in
>> > > > > > > > > > > > > > > > > > phase 1,
>> > > > > > > > > > > > > > > > > > > > > > > > but it is scheduled once
>> it is
>> > > > > >
>> > > > > > finished.
>> > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > Here is an umbrella ticket
>> [1] to
>> > > > > >
>> > > > > > track
>> > > > > > > > >
>> > > > > > > > > phase 1
>> > > > > > > > > > > > scope.
>> > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > It includes very few new
>> features,
>> > > > >
>> > > > > but
>> > > > > > > we
>> > > > > > > > > > > >
>> > > > > > > > > > > > completely
>> > > > > > > > > > > > > > > rework
>> > > > > > > > > > > > > > > > > > component
>> > > > > > > > > > > > > > > > > > > > > > > > to improve guarantees to
>> be more
>> > > > > > >
>> > > > > > > reliable and
>> > > > > > > > > >
>> > > > > > > > > > we
>> > > > > > > > > > > > build
>> > > > > > > > > > > > > > > the
>> > > > > > > > > > > > > > > > > > base for
>> > > > > > > > > > > > > > > > > > > > > > > > new features.
>> > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > [1]
>> > > > > > > > > > > >
>> > > > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-9607
>> > > > > > > > > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at
>> 9:38 PM
>> > > > > >
>> > > > > > Dmitriy
>> > > > > > > > > > >
>> > > > > > > > > > > Setrakyan <
>> > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > dsetrak...@apache.org>
>> > > > > > > > > > > > > > > > > > > > > > > > wrote:
>> > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > I am not sure I can
>> agree. SG
>> > > > > >
>> > > > > > redesign
>> > > > > > > > > > >
>> > > > > > > > > > > includes:
>> > > > > > > > > > > > > > > > > > > > > > > > > - hot redeployment
>> > > > > > > > > > > > > > > > > > > > > > > > > - versioning
>> > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > In my experience,
>> features like
>> > > > > >
>> > > > > > these
>> > > > > > > take
>> > > > > > > > > > >
>> > > > > > > > > > > about
>> > > > > > > > > > > > 1
>> > > > > > > > > > > > > > > month
>> > > > > > > > > > > > > > > > to
>> > > > > > > > > > > > > > > > > > test
>> > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > properly
>> > > > > > > > > > > > > > > > > > > > > > > > > and fix all the bugs,
>> including
>> > > > > > > > >
>> > > > > > > > > redeployment
>> > > > > > > > > > > > tests
>> > > > > > > > > > > > > > and
>> > > > > > > > > > > > > > > > > > restart
>> > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > tests
>> > > > > > > > > > > > > > > > > > > > > > on
>> > > > > > > > > > > > > > > > > > > > > > > > > larger topologies,
>> together with
>> > > > > > >
>> > > > > > > overnight
>> > > > > > > > > > >
>> > > > > > > > > > > runs.
>> > > > > > > > > > > > If
>> > > > > > > > > > > > > > > this
>> > > > > > > > > > > > > > > > > > type of
>> > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > testing
>> > > > > > > > > > > > > > > > > > > > > > > > > has not been performed,
>> I think it
>> > > > > > >
>> > > > > > > would be
>> > > > > > > > > > > > > > > unreasonable
>> > > > > > > > > > > > > > > > to
>> > > > > > > > > > > > > > > > > > expect
>> > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > this
>> > > > > > > > > > > > > > > > > > > > > > > > > feature making it into
>> the
>> > > > >
>> > > > > release.
>> > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > Can someone comment on
>> the
>> > > > >
>> > > > > testing?
>> > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > D.
>> > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at
>> 10:38 AM
>> > > > > > >
>> > > > > > > Dmitriy
>> > > > > > > > > > >
>> > > > > > > > > > > Pavlov <
>> > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > dpavlov....@gmail.com>
>> > > > > > > > > > > > > > > > > > > > > > > > > wrote:
>> > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > Nikolay, because I
>> think you're
>> > > > >
>> > > > > a
>> > > > > > > do'er,
>> > > > > > > > > >
>> > > > > > > > > > but
>> > > > > > > > > > > > not a
>> > > > > > > > > > > > > > > > > > commenter,
>> > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > like
>> > > > > > > > > > > > > > > > > > > > > > me,
>> > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > for
>> > > > > > > > > > > > > > > > > > > > > > > > > > example, I can trust
>> your
>> > > > >
>> > > > > opinion.
>> > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > I will join review if
>> I have
>> > > > >
>> > > > > spare
>> > > > > > > > >
>> > > > > > > > > cycles.
>> > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в
>> 20:34,
>> > > > > >
>> > > > > > Denis
>> > > > > > > > >
>> > > > > > > > > Magda <
>> > > > > > > > > > > > > > > > > > dma...@apache.org>:
>> > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > Nikolay,
>> > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > Thanks for stepping
>> in and
>> > > > > >
>> > > > > > giving
>> > > > > > > more
>> > > > > > > > > > > >
>> > > > > > > > > > > > context.
>> > > > > > > > > > > > > > In
>> > > > > > > > > > > > > > > > > > general, I'm
>> > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > fully for
>> > > > > > > > > > > > > > > > > > > > > > > > > > > your proposal below:
>> > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > My vote goes to
>> option *a*.
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > I think we should
>> release
>> > > > >
>> > > > > 2.7
>> > > > > > > with
>> > > > > > > > >
>> > > > > > > > > the
>> > > > > > > > > > > > bunch of
>> > > > > > > > > > > > > > > new
>> > > > > > > > > > > > > > > > > > cool
>> > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > features.
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > *AND* we should
>> plan 2.8
>> > > > > > >
>> > > > > > > release at
>> > > > > > > > >
>> > > > > > > > > the
>> > > > > > > > > > > > end of
>> > > > > > > > > > > > > > > the
>> > > > > > > > > > > > > > > > > > year with
>> > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > SG
>> > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > redesign
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > and MVCC
>> stabilization
>> > > > >
>> > > > > tasks.
>> > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > --
>> > > > > > > > > > > > > > > > > > > > > > > > > > > Denis
>> > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018
>> at 10:30
>> > > > >
>> > > > > AM
>> > > > > > > > >
>> > > > > > > > > Nikolay
>> > > > > > > > > > > > Izhikov
>> > > > > > > > > > > > > > <
>> > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > nizhi...@apache.org>
>> > > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
>> > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > Hello, Igniters.
>> > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > I think we
>> shouldn't put so
>> > > > > >
>> > > > > > many
>> > > > > > > > > >
>> > > > > > > > > > emotions
>> > > > > > > > > > > > in
>> > > > > > > > > > > > > > > > > > discussion of
>> > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > any
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > contribution.
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > Even so big and
>> important as
>> > > > > >
>> > > > > > SG
>> > > > > > > > > >
>> > > > > > > > > > redesign.
>> > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > The crucial point
>> we all
>> > > > > >
>> > > > > > agreed
>> > > > > > > > >
>> > > > > > > > > about:
>> > > > > > > > > > > > Service
>> > > > > > > > > > > > > > > Grid
>> > > > > > > > > > > > > > > > > > redesign
>> > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > a
>> > > > > > > > > > > > > > > > > > > > > > big
>> > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > feature
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > that can
>> significally
>> > > > >
>> > > > > improve
>> > > > > > > Ignite.
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > We all want to
>> have it in
>> > > > >
>> > > > > the
>> > > > > > > > >
>> > > > > > > > > product.
>> > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > Let me write my
>> vision of
>> > > > >
>> > > > > the
>> > > > > > > current
>> > > > > > > > > > >
>> > > > > > > > > > > task
>> > > > > > > > > > > > > > state:
>> > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > 1. Design of SG is
>> discussed
>> > > > > > >
>> > > > > > > *and
>> > > > > > > > > > >
>> > > > > > > > > > > aligned*
>> > > > > > > > > > > > > > both:
>> > > > > > > > > > > > > > > > > > privately
>> > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > with
>> > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > Ignite
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > experts(Vladimir
>> Ozerov,
>> > > > > >
>> > > > > > Alexey
>> > > > > > > > > > >
>> > > > > > > > > > > Goncharyuk,
>> > > > > > > > > > > > > > Anton
>> > > > > > > > > > > > > > > > > > Vinogradov,
>> > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > Denis
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > Mekhanikov)
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > and publicly on
>> dev-list.
>> > > > >
>> > > > > This
>> > > > > > > task
>> > > > > > > > >
>> > > > > > > > > is
>> > > > > > > > > > > > done.
>> > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > 2. Current PR
>> state - *on my
>> > > > > > >
>> > > > > > > review*.
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > I spend some time
>> with this
>> > > > > > > > > >
>> > > > > > > > > > contribution
>> > > > > > > > > > > > and
>> > > > > > > > > > > > > > gave
>> > > > > > > > > > > > > > > > > > Vyacheslav
>> > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > a
>> > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > feedback.
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > I expect he can
>> fix my
>> > > > > >
>> > > > > > comments
>> > > > > > > in a
>> > > > > > > > > >
>> > > > > > > > > > day
>> > > > > > > > > > > or
>> > > > > > > > > > > > > > two.
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > Seem we can ask of
>> Anton
>> > > > > > >
>> > > > > > > Vinogradov
>> > > > > > > > > > >
>> > > > > > > > > > > review
>> > > > > > > > > > > > on
>> > > > > > > > > > > > > > the
>> > > > > > > > > > > > > > > > > > beginning
>> > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > of
>> > > > > > > > > > > > > > > > > > > > > > next
>> > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > week.
>> > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > If Dmitriy or any
>> community
>> > > > > > >
>> > > > > > > member
>> > > > > > > > > >
>> > > > > > > > > > wants
>> > > > > > > > > > > to
>> > > > > > > > > > > > > > help
>> > > > > > > > > > > > > > > > *by
>> > > > > > > > > > > > > > > > > > doing
>> > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > things,
>> > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > not
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > discussing them on
>> > > > >
>> > > > > dev-list*.
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > Please, join to
>> the review -
>> > > > > > >
>> > > > > > > you are
>> > > > > > > > > > > >
>> > > > > > > > > > > > welcome.
>> > > > > > > > > > > > > > PR
>> > > > > > > > > > > > > > > is
>> > > > > > > > > > > > > > > > > > here [1]
>> > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > 3. I think, we
>> have two
>> > > > > >
>> > > > > > mutually
>> > > > > > > > > > >
>> > > > > > > > > > > exclusive
>> > > > > > > > > > > > > > > options
>> > > > > > > > > > > > > > > > > > regarding
>> > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > of
>> > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > release
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > 2.7
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > a. We release 2.7
>> in planned
>> > > > > > >
>> > > > > > > dates.
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > b. We include SG
>> in release
>> > > > > > >
>> > > > > > > scope.
>> > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > My vote goes to
>> option *a*.
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > I think we should
>> release
>> > > > >
>> > > > > 2.7
>> > > > > > > with
>> > > > > > > > >
>> > > > > > > > > the
>> > > > > > > > > > > > bunch of
>> > > > > > > > > > > > > > > new
>> > > > > > > > > > > > > > > > > > cool
>> > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > features.
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > *AND* we should
>> plan 2.8
>> > > > > > >
>> > > > > > > release at
>> > > > > > > > >
>> > > > > > > > > the
>> > > > > > > > > > > > end of
>> > > > > > > > > > > > > > > the
>> > > > > > > > > > > > > > > > > > year with
>> > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > SG
>> > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > redesign
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > and MVCC
>> stabilization
>> > > > >
>> > > > > tasks.
>> > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > Anyway, while we
>> preparing
>> > > > > > >
>> > > > > > > release a
>> > > > > > > > > >
>> > > > > > > > > > lot
>> > > > > > > > > > > of
>> > > > > > > > > > > > > > > things
>> > > > > > > > > > > > > > > > > can
>> > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > happen.
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > Let's come back to
>> > > > >
>> > > > > discussion
>> > > > > > > of SG
>> > > > > > > > > > >
>> > > > > > > > > > > release
>> > > > > > > > > > > > > > > version
>> > > > > > > > > > > > > > > > > > *when it
>> > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > will
>> > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > be
>> > > > > > > > > > > > > > > > > > > > > > > > > > > ready
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > to be merged to
>> master*.
>> > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > Guys, does it
>> makes sense
>> > > > >
>> > > > > for
>> > > > > > > you?
>> > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > [1]
>> > > > > > > > > > > >
>> > > > > > > > > > > > https://github.com/apache/ignite/pull/4434
>> > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > В Пт, 28/09/2018 в
>> 19:47
>> > > > > >
>> > > > > > +0300,
>> > > > > > > > >
>> > > > > > > > > Dmitriy
>> > > > > > > > > > > > Pavlov
>> > > > > > > > > > > > > > > > пишет:
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hi Dmitriy,
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > The design is
>> aligned
>> > > > > > >
>> > > > > > > totally. The
>> > > > > > > > > > > >
>> > > > > > > > > > > > thread you
>> > > > > > > > > > > > > > > > > > mention was
>> > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > not
>> > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > named
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > properly.
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > It seems to me
>> some
>> > > > > >
>> > > > > > community
>> > > > > > > > >
>> > > > > > > > > members
>> > > > > > > > > > > are
>> > > > > > > > > > > > > > > trying
>> > > > > > > > > > > > > > > > to
>> > > > > > > > > > > > > > > > > > take
>> > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > over the
>> > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > community
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > and lead it
>> instead of
>> > > > > >
>> > > > > > doing.
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > As a member of
>> the Apache
>> > > > > > > > >
>> > > > > > > > > community,
>> > > > > > > > > > I
>> > > > > > > > > > > > value
>> > > > > > > > > > > > > > > > > > Do-ocracy and
>> > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > power
>> > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > of
>> > > > > > > > > > > > > > > > > > > > > > > > > > > those
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > who do, but not
>> just
>> > > > > >
>> > > > > > disagree.
>> > > > > > > > >
>> > > > > > > > > There
>> > > > > > > > > > > are
>> > > > > > > > > > > > no
>> > > > > > > > > > > > > > > > leaders
>> > > > > > > > > > > > > > > > > > in open
>> > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > source,
>> > > > > > > > > > > > > > > > > > > > > > > > > > > just
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > do'ers.
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > By do'ers here I
>> mean
>> > > > > >
>> > > > > > Nikolay
>> > > > > > > and
>> > > > > > > > > > > >
>> > > > > > > > > > > > Vyacheslav.
>> > > > > > > > > > > > > > > For
>> > > > > > > > > > > > > > > > > > me, their
>> > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > conclusion
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > has
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > more weight
>> here. If
>> > > > > >
>> > > > > > Vladimir
>> > > > > > > is
>> > > > > > > > > >
>> > > > > > > > > > ready
>> > > > > > > > > > > to
>> > > > > > > > > > > > > > lead
>> > > > > > > > > > > > > > > an
>> > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > additional
>> > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > release
>> > > > > > > > > > > > > > > > > > > > > > > > > > > for
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > SG
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > and SG
>> developers agree,
>> > > > >
>> > > > > it
>> > > > > > > works
>> > > > > > > > >
>> > > > > > > > > for
>> > > > > > > > > > > me.
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > Sincerely,
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > Dmitriy Pavlov
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > пт, 28 сент.
>> 2018 г. в
>> > > > > >
>> > > > > > 19:39,
>> > > > > > > > >
>> > > > > > > > > Dmitriy
>> > > > > > > > > > > > > > > Setrakyan <
>> > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > >
>> <dsetrak...@apache.org>
>
>
>
> --
> Best regards,
> Andrey Kuznetsov.
>
--
Best regards,
Andrey Kuznetsov.
