You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by Nikolay Izhikov <ni...@apache.org> on 2018/08/20 18:22:11 UTC
Apache Ignite 2.7 release
Hello, Igniters.
I'm release manager of Apache Ignite 2.7.
It's time to start discussion of release. [1]
Current code freeze date is September, 30.
If you have any objections - please, responsd to this thread.
[1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.7
Re: Apache Ignite 2.7 release
Posted by Dmitriy Pavlov <dp...@gmail.com>.
yep, someone can use his or her @gridgain address, even it is not best
practice and Apache recommends to avoid it. It is still an individual in
the Community.
I've checked the history of the ticket and there was a strange reassignment
in it. we'll try to find out if it is under review. Hopefully, contributor
assigned this ticket can come and comment.
чт, 20 сент. 2018 г. в 12:48, Paul Anderson <de...@gmail.com>:
> ok... thought I saw gridgain interaction in an email.... Will start a new
> thread with my questions on test code or comment on Jira
>
> On Thu, Sep 20, 2018 at 11:39 AM Dmitriy Pavlov <dp...@gmail.com>
> wrote:
>
> > Hi Paul,
> >
> > Please be more specific, GridGain can't take part in the community, only
> > individual contributors can. So I don't understand which contributor was
> > pulling 9298.
> >
> > Any feedback is appreciated, especially constructive, cause it helps in
> > developing a product in the right direction. But we can't enforce someone
> > to do something faster or in more right manner. Why don't suggest help
> > instead?
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > чт, 20 сент. 2018 г. в 12:29, Paul Anderson <de...@gmail.com>:
> >
> > > Dimitiry, Re: IGNITE-9298 ... this is my first contribution, don't know
> > who
> > > is reviewing the code, I did see that it was pulled by GridGain.
> > >
> > > Additionally I was not happy about the test code, I followed what was
> > there
> > > before but it doesn't seem right.
> > >
> > > On Thu, Sep 20, 2018 at 9:17 AM Dmitriy Pavlov <dp...@gmail.com>
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > As always, our constraint is a review. We as the community seems to
> > agree
> > > > that review and patch commenting is a major contribution, but very
> few
> > of
> > > > us doing a review, and 92 tickets are in Patch Available state.
> > > >
> > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Issues+waiting+for+review
> > > >
> > > >
> > > > Everyone can help, so tests run can be checked (e.g. in the TC Bot);
> > code
> > > > style; change itself is clear and relates to issue. Don't forget to
> > share
> > > > positive things that you like in PR/Change, does not point to
> problems
> > > > only.
> > > >
> > > > So if a ticket is accepted and merged there is usually no reason to
> > move
> > > it
> > > > to the next version instead of the nearest one.
> > > >
> > > > Sincerely,
> > > > Dmitriy Pavlov
> > > >
> > > > чт, 20 сент. 2018 г. в 3:54, Ray <ra...@cisco.com>:
> > > >
> > > > > Hello, Igniters.
> > > > >
> > > > > Is there any specific reason why this ticket is removed from 2.7
> > scope?
> > > > > I think this ticket is important for both usability and
> performance.
> > > > > Without this ticket, we have to create an index manually identical
> to
> > > > > primary key if we want to use SQL query.
> > > > > https://issues.apache.org/jira/browse/IGNITE-8386
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> > > > >
> > > >
> > >
> >
>
Re: Apache Ignite 2.7 release
Posted by Paul Anderson <de...@gmail.com>.
ok... thought I saw gridgain interaction in an email.... Will start a new
thread with my questions on test code or comment on Jira
On Thu, Sep 20, 2018 at 11:39 AM Dmitriy Pavlov <dp...@gmail.com>
wrote:
> Hi Paul,
>
> Please be more specific, GridGain can't take part in the community, only
> individual contributors can. So I don't understand which contributor was
> pulling 9298.
>
> Any feedback is appreciated, especially constructive, cause it helps in
> developing a product in the right direction. But we can't enforce someone
> to do something faster or in more right manner. Why don't suggest help
> instead?
>
> Sincerely,
> Dmitriy Pavlov
>
> чт, 20 сент. 2018 г. в 12:29, Paul Anderson <de...@gmail.com>:
>
> > Dimitiry, Re: IGNITE-9298 ... this is my first contribution, don't know
> who
> > is reviewing the code, I did see that it was pulled by GridGain.
> >
> > Additionally I was not happy about the test code, I followed what was
> there
> > before but it doesn't seem right.
> >
> > On Thu, Sep 20, 2018 at 9:17 AM Dmitriy Pavlov <dp...@gmail.com>
> > wrote:
> >
> > > Hi,
> > >
> > > As always, our constraint is a review. We as the community seems to
> agree
> > > that review and patch commenting is a major contribution, but very few
> of
> > > us doing a review, and 92 tickets are in Patch Available state.
> > >
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Issues+waiting+for+review
> > >
> > >
> > > Everyone can help, so tests run can be checked (e.g. in the TC Bot);
> code
> > > style; change itself is clear and relates to issue. Don't forget to
> share
> > > positive things that you like in PR/Change, does not point to problems
> > > only.
> > >
> > > So if a ticket is accepted and merged there is usually no reason to
> move
> > it
> > > to the next version instead of the nearest one.
> > >
> > > Sincerely,
> > > Dmitriy Pavlov
> > >
> > > чт, 20 сент. 2018 г. в 3:54, Ray <ra...@cisco.com>:
> > >
> > > > Hello, Igniters.
> > > >
> > > > Is there any specific reason why this ticket is removed from 2.7
> scope?
> > > > I think this ticket is important for both usability and performance.
> > > > Without this ticket, we have to create an index manually identical to
> > > > primary key if we want to use SQL query.
> > > > https://issues.apache.org/jira/browse/IGNITE-8386
> > > >
> > > >
> > > >
> > > > --
> > > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> > > >
> > >
> >
>
Re: Apache Ignite 2.7 release
Posted by Dmitriy Pavlov <dp...@gmail.com>.
Hi Paul,
Please be more specific, GridGain can't take part in the community, only
individual contributors can. So I don't understand which contributor was
pulling 9298.
Any feedback is appreciated, especially constructive, cause it helps in
developing a product in the right direction. But we can't enforce someone
to do something faster or in more right manner. Why don't suggest help
instead?
Sincerely,
Dmitriy Pavlov
чт, 20 сент. 2018 г. в 12:29, Paul Anderson <de...@gmail.com>:
> Dimitiry, Re: IGNITE-9298 ... this is my first contribution, don't know who
> is reviewing the code, I did see that it was pulled by GridGain.
>
> Additionally I was not happy about the test code, I followed what was there
> before but it doesn't seem right.
>
> On Thu, Sep 20, 2018 at 9:17 AM Dmitriy Pavlov <dp...@gmail.com>
> wrote:
>
> > Hi,
> >
> > As always, our constraint is a review. We as the community seems to agree
> > that review and patch commenting is a major contribution, but very few of
> > us doing a review, and 92 tickets are in Patch Available state.
> >
> >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Issues+waiting+for+review
> >
> >
> > Everyone can help, so tests run can be checked (e.g. in the TC Bot); code
> > style; change itself is clear and relates to issue. Don't forget to share
> > positive things that you like in PR/Change, does not point to problems
> > only.
> >
> > So if a ticket is accepted and merged there is usually no reason to move
> it
> > to the next version instead of the nearest one.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > чт, 20 сент. 2018 г. в 3:54, Ray <ra...@cisco.com>:
> >
> > > Hello, Igniters.
> > >
> > > Is there any specific reason why this ticket is removed from 2.7 scope?
> > > I think this ticket is important for both usability and performance.
> > > Without this ticket, we have to create an index manually identical to
> > > primary key if we want to use SQL query.
> > > https://issues.apache.org/jira/browse/IGNITE-8386
> > >
> > >
> > >
> > > --
> > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> > >
> >
>
Re: Apache Ignite 2.7 release
Posted by Paul Anderson <de...@gmail.com>.
Dimitiry, Re: IGNITE-9298 ... this is my first contribution, don't know who
is reviewing the code, I did see that it was pulled by GridGain.
Additionally I was not happy about the test code, I followed what was there
before but it doesn't seem right.
On Thu, Sep 20, 2018 at 9:17 AM Dmitriy Pavlov <dp...@gmail.com>
wrote:
> Hi,
>
> As always, our constraint is a review. We as the community seems to agree
> that review and patch commenting is a major contribution, but very few of
> us doing a review, and 92 tickets are in Patch Available state.
>
>
> https://cwiki.apache.org/confluence/display/IGNITE/Issues+waiting+for+review
>
>
> Everyone can help, so tests run can be checked (e.g. in the TC Bot); code
> style; change itself is clear and relates to issue. Don't forget to share
> positive things that you like in PR/Change, does not point to problems
> only.
>
> So if a ticket is accepted and merged there is usually no reason to move it
> to the next version instead of the nearest one.
>
> Sincerely,
> Dmitriy Pavlov
>
> чт, 20 сент. 2018 г. в 3:54, Ray <ra...@cisco.com>:
>
> > Hello, Igniters.
> >
> > Is there any specific reason why this ticket is removed from 2.7 scope?
> > I think this ticket is important for both usability and performance.
> > Without this ticket, we have to create an index manually identical to
> > primary key if we want to use SQL query.
> > https://issues.apache.org/jira/browse/IGNITE-8386
> >
> >
> >
> > --
> > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> >
>
Re: Apache Ignite 2.7 release
Posted by Dmitriy Pavlov <dp...@gmail.com>.
Hi,
As always, our constraint is a review. We as the community seems to agree
that review and patch commenting is a major contribution, but very few of
us doing a review, and 92 tickets are in Patch Available state.
https://cwiki.apache.org/confluence/display/IGNITE/Issues+waiting+for+review
Everyone can help, so tests run can be checked (e.g. in the TC Bot); code
style; change itself is clear and relates to issue. Don't forget to share
positive things that you like in PR/Change, does not point to problems only.
So if a ticket is accepted and merged there is usually no reason to move it
to the next version instead of the nearest one.
Sincerely,
Dmitriy Pavlov
чт, 20 сент. 2018 г. в 3:54, Ray <ra...@cisco.com>:
> Hello, Igniters.
>
> Is there any specific reason why this ticket is removed from 2.7 scope?
> I think this ticket is important for both usability and performance.
> Without this ticket, we have to create an index manually identical to
> primary key if we want to use SQL query.
> https://issues.apache.org/jira/browse/IGNITE-8386
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>
Re: Apache Ignite 2.7 release
Posted by Ray <ra...@cisco.com>.
Hello, Igniters.
Is there any specific reason why this ticket is removed from 2.7 scope?
I think this ticket is important for both usability and performance.
Without this ticket, we have to create an index manually identical to
primary key if we want to use SQL query.
https://issues.apache.org/jira/browse/IGNITE-8386
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Re: Apache Ignite 2.7 release
Posted by Nikolay Izhikov <ni...@apache.org>.
Helo, Dmitriy.
I looked at patch.
Seems it local for a ML module.
Is it's true I'm +1 to include it to 2.7.
В Чт, 04/10/2018 в 08:33 -0500, dmitrievanthony пишет:
> Hi, Yury, Nikolay.
>
> This issue reproduces in "TensorFlow on Apache Ignite" use cases. When user
> prepares training script (like official MNIST model
> https://github.com/tensorflow/models/tree/master/official/mnist), runs it in
> distributed standalone client mode (see this documentation
> https://github.com/tensorflow/tensorflow/tree/master/tensorflow/contrib/distribute#standalone-client-mode)
> using IgniteDataset he can see that workers throw exceptions says that
> IgniteDataset operation is not loaded.
>
> For more information about distributed training please see
> https://docs.google.com/document/d/1PtYmyaT4dPBNp1mWkCczOdCZHt2xaqB183honfMup3g/edit
> documentation.
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Re: Apache Ignite 2.7 release
Posted by dmitrievanthony <dm...@gmail.com>.
Hi, Yury, Nikolay.
This issue reproduces in "TensorFlow on Apache Ignite" use cases. When user
prepares training script (like official MNIST model
https://github.com/tensorflow/models/tree/master/official/mnist), runs it in
distributed standalone client mode (see this documentation
https://github.com/tensorflow/tensorflow/tree/master/tensorflow/contrib/distribute#standalone-client-mode)
using IgniteDataset he can see that workers throw exceptions says that
IgniteDataset operation is not loaded.
For more information about distributed training please see
https://docs.google.com/document/d/1PtYmyaT4dPBNp1mWkCczOdCZHt2xaqB183honfMup3g/edit
documentation.
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Re: Apache Ignite 2.7 release
Posted by Nikolay Izhikov <ni...@apache.org>.
Hello, Yuriy
What is consequences of this issue?
How user can reproduce it?
В Чт, 04/10/2018 в 15:02 +0300, Yuriy Babak пишет:
> Igniters,
>
> We have new ticket related with TensorFlow integration:
> https://issues.apache.org/jira/browse/IGNITE-9788
>
> From my point of view this fix is important for release and I want to
> include it to 2.7.
>
> Any objections?
>
> пн, 20 авг. 2018 г. в 21:22, Nikolay Izhikov <ni...@apache.org>:
>
> > Hello, Igniters.
> >
> > I'm release manager of Apache Ignite 2.7.
> >
> > It's time to start discussion of release. [1]
> >
> > Current code freeze date is September, 30.
> > If you have any objections - please, responsd to this thread.
> >
> > [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.7
Re: Apache Ignite 2.7 release
Posted by Yuriy Babak <y....@gmail.com>.
Igniters,
We have new ticket related with TensorFlow integration:
https://issues.apache.org/jira/browse/IGNITE-9788
From my point of view this fix is important for release and I want to
include it to 2.7.
Any objections?
пн, 20 авг. 2018 г. в 21:22, Nikolay Izhikov <ni...@apache.org>:
> Hello, Igniters.
>
> I'm release manager of Apache Ignite 2.7.
>
> It's time to start discussion of release. [1]
>
> Current code freeze date is September, 30.
> If you have any objections - please, responsd to this thread.
>
> [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.7
Re: Apache Ignite 2.7 release
Posted by Dmitriy Pavlov <dp...@gmail.com>.
Hi Igniters,
I'm a little bit concerned about these failures:
Platform .NET (Long Running)
exe: ExamplesTest.TestRemoteNodes(BinaryModeExample) (fail rate 100,0%)
exe: ExamplesTest.TestRemoteNodes(LinqExample) (fail rate 100,0%)
exe: ExamplesTest.TestRemoteNodes(SqlExample)(fail rate 100,0%)
I will have limited access to the Internet in the nearest 2 weeks, so
volunteer is very wanted here.
It seems following failures are not often now and can be skipped for 2.7
- IGNITE-8771 Unassigned OutOfMemory in Cache2 suite in
master branch on TC
- IGNITE-8770 Unassigned OutOfMemory in Queries1 suite in
master branch on TC
Please correct me if I'm wrong.
I'll change the priority of
- IGNITE-5618 Dmitriy Pavlov .NET: Ignite fails with OOM on
startup under x86 (32 bit) with default configuration
because it is definitely not a blocker.
Sincerely,
Dmitriy Pavlov
пт, 24 авг. 2018 г. в 15:01, Nikolay Izhikov <ni...@apache.org>:
> Hello, Yakov.
>
> Blocker Tickets.
>
> Open:
>
> IGNITE-9184 Mikhail Cherkasov Cluster hangs during concurrent
> node restart and continues query registration
> IGNITE-8552 Vladimir Ozerov Unable to use date as
> primary key
> IGNITE-6980 Aleksey Plekhanov Automatic cancelling of hanging
> Ignite operations
> IGNITE-8671 Peter Ivanov Provide instructions on running
> Apache Ignite on Windows 10 WSL Environment
> IGNITE-7009 Vladimir Ozerov NPE when Ignite persistence is
> enabled for Hadoop accelerator
> IGNITE-8803 Alexey Goncharuk Need to fix Ignite QUIET log output
> IGNITE-8802 Alexey Goncharuk Need to fix Ignite INFO output
> IGNITE-5618 Dmitriy Pavlov .NET: Ignite fails with OOM on
> startup under x86 (32 bit) with default configuration
> IGNITE-9352 Unassigned Web Console: Investigate how
> correctly use package-lock.json
> IGNITE-9347 Unassigned Attempt to start a dynamic cache
> with invalid configuration leads to exchange worker death
> IGNITE-9202 Unassigned .NET `TestRemoteNodes` fails with
> "Failed to map SQL query to topology"
> IGNITE-7793 Unassigned SQL does not work if value has
> index filed which name equals to affinity key name
> IGNITE-8890 Unassigned Ignite YARN Kerberos - Delegation
> Token renewal
> IGNITE-8771 Unassigned OutOfMemory in Cache2 suite in
> master branch on TC
> IGNITE-8770 Unassigned OutOfMemory in Queries1 suite in
> master branch on TC
> IGNITE-8767 Unassigned JavaClient test suite times out in
> master branch
> IGNITE-5302 Unassigned Empty LOST partition may be used
> as OWNING after resetting lost partitions
> IGNITE-7813 Unassigned Method
> org/apache/ignite/cache/hibernate/HibernateRegionFactory.start(Lorg/hibernate/boot/spi/SessionFactoryOptions;Ljava/util/Properties;)V
> is abstract
> IGNITE-8523 Unassigned Java and Scala spark examples are
> mixed
> IGNITE-8772 Unassigned WebSessionFilter does not work
> with jetty 9.4 anymore
> IGNITE-6064 Unassigned Rework control.sh script
> IGNITE-8454 Unassigned Hadoop module compilation failure
> under JDK9
> IGNITE-7620 Unassigned Not able to run query in Ignite
> YARN
>
> In Progress:
>
>
> IGNITE-9305 Pavel Pereslegin Wrong off-heap size is reported
> for a node
> IGNITE-7728 Artem Budnikov Put together a doc that shows how
> to blend SQL with k/v APIs
> IGNITE-7721 ruchir choudhry Apache Ignite web session
> clustering stack after login success
>
> Patch Available:
>
> IGNITE-9068 Ilya Lantukh Node fails to stop when
> CacheObjectBinaryProcessor.addMeta() is executed inside guard()/unguard()
> IGNITE-7251 Anton Vinogradov Remove term "fabric" from Ignite
> deliverables
> IGNITE-9030 Peter Ivanov Apache Ignite 2.7 Linux packages
> version update
>
> В Пт, 24/08/2018 в 14:47 +0300, Yakov Zhdanov пишет:
> > Igniters,
> >
> > We should definitely expand the list of important tickets adding tickets
> > related to (1) Partition Map Exchange speed up and (2) SQL memory
> > optimization tickets. Alex Goncharuk, Vladimir, can you please add labels
> > to corresponding tickets.
> >
> > Also we have several blocker tickets (mostly related to failing tests)
> not
> > yet assigned to anyone. Nikolay, can you please list those tickets and
> ask
> > community to pick them up?
> >
> > We have 556 open tickets now according to [1]. This seems a bit to much.
> > Can I ask everyone to review tickets assigned to yourselves and move
> those
> > that will not be fixed. Then Nikolay will process the ones that are not
> > assigned yet. Nikolay, can you take a look please?
> >
> > --Yakov
> >
> > 2018-08-24 12:58 GMT+03:00 Nikolay Izhikov <ni...@apache.org>:
> >
> > > Hello, Dmitriy.
> > >
> > > Release page - [1]
> > >
> > > > I think it is important to include the links to all important Jira
> > >
> > > tickets> in this thread
> > >
> > > Open:
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-6980 - Automatic
> cancelling
> > > of hanging Ignite operations
> > > 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
> > > https://issues.apache.org/jira/browse/IGNITE-6507 - Commit can be
> lost in
> > > network split scenario
> > >
> > > In Progress:
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-9349
> > >
> > > Patch Available:
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-7251 - Remove term
> "fabric"
> > > from Ignite deliverables
> > >
> > >
> > > Resolved:
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-8780 - File I/O
> operations
> > > must be retried if buffer hasn't read/written completely
> > > https://issues.apache.org/jira/browse/IGNITE-5059 - Implement logistic
> > > regression
> > > https://issues.apache.org/jira/browse/IGNITE-3478 - Multi-version
> > > concurrency control
> > > https://issues.apache.org/jira/browse/IGNITE-9340 - Update jetty
> version
> > > in Apache Ignite (ignite-rest-http)
> > >
> > >
> > >
> > > [1]
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.7
> > >
> > > В Пт, 24/08/2018 в 10:47 +0300, Nikolay Izhikov пишет:
> > > > Hello, Pavel.
> > > >
> > > > Please, be aware of IGNITE-6055 [1]
> > > >
> > > > I'm edit thin protocol in that ticket.
> > > > I can't support changes in Python and PHP clients, because, they are
> not
> > >
> > > merged in master, yet.
> > > > Write me, If you have any questions about new fields.
> > > >
> > > > [1] https://issues.apache.org/jira/browse/IGNITE-6055
> > > >
> > > > В Чт, 23/08/2018 в 18:02 -0700, Pavel Petroshenko пишет:
> > > > > Hi Nikolay,
> > > > >
> > > > > Python [1], PHP [2], and Node.js [3] thin clients will get into the
> > >
> > > release.
> > > > >
> > > > > Thanks,
> > > > > 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 Tue, Aug 21, 2018 at 12:20 PM, Dmitriy Setrakyan <
> > >
> > > dsetrakyan@apache.org> wrote:
> > > > > > Thanks, Nikolay!
> > > > > >
> > > > > > I think it is important to include the links to all important
> Jira
> > >
> > > tickets
> > > > > > in this thread, so that the community can track them.
> > > > > >
> > > > > > D.
> > > > > >
> > > > > > On Tue, Aug 21, 2018 at 12:06 AM, Nikolay Izhikov <
> > >
> > > nizhikov@apache.org>
> > > > > > wrote:
> > > > > >
> > > > > > > Hello, Dmitriy.
> > > > > > >
> > > > > > > I think Transparent Data Encryption will be available in 2.7
> > > > > > >
> > > > > > > В Пн, 20/08/2018 в 13:20 -0700, Dmitriy Setrakyan пишет:
> > > > > > > > Hi Nikolay,
> > > > > > > >
> > > > > > > > Thanks for being the release manager!
> > > > > > > >
> > > > > > > > I am getting a bit lost in all these tickets. Can we specify
> some
> > > > > > > > high-level tickets, that are not plain bug fixes, which will
> be
> > > > > > >
> > > > > > > interesting
> > > > > > > > for the community to notice?
> > > > > > > >
> > > > > > > > For example, here are some significant tasks that the
> community
> > >
> > > is either
> > > > > > > > working on or has been working on:
> > > > > > > >
> > > > > > > > - Node.JS client
> > > > > > > > - Python client
> > > > > > > > - Transactional SQL (MVCC)
> > > > > > > > - service grid stabilization
> > > > > > > > - SQL memory utilization improvements
> > > > > > > > - more?
> > > > > > > >
> > > > > > > > Can you please solicit status from the community for these
> tasks?
> > > > > > > >
> > > > > > > > D.
> > > > > > > >
> > > > > > > > On Mon, Aug 20, 2018 at 11:22 AM, Nikolay Izhikov <
> > >
> > > nizhikov@apache.org>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Hello, Igniters.
> > > > > > > > >
> > > > > > > > > I'm release manager of Apache Ignite 2.7.
> > > > > > > > >
> > > > > > > > > It's time to start discussion of release. [1]
> > > > > > > > >
> > > > > > > > > Current code freeze date is September, 30.
> > > > > > > > > If you have any objections - please, responsd to this
> thread.
> > > > > > > > >
> > > > > > > > > [1] https://cwiki.apache.org/confluence/display/IGNITE/
> > > > > > >
> > > > > > > Apache+Ignite+2.7
> > > > > > >
Re: Apache Ignite 2.7 release
Posted by Alexey Goncharuk <al...@gmail.com>.
I think if a commit does not lead to any test failure in the current
master, there are no reasons to revert the commit. If there are valid
scenarios which are failing, corresponding tests should be added and the
root cause should be fixed under a separate issue.
пт, 28 сент. 2018 г. в 11:19, Dmitriy Pavlov <dp...@gmail.com>:
> Hi Maxim,
>
> Once 1) you are sure that commit is related to the failure, and 2) in case
> contributors are not responding,
> please let me know, probably we need to open one more separate topic about
> revert.
>
> Sincerely,
> Dmitriy Pavlov
>
> пт, 28 сент. 2018 г. в 11:15, Maxim Muzafarov <ma...@gmail.com>:
>
> > Andrey, Dmitry,
> >
> > > I've bumped into a new bug in WAL manager recently, see [1]. It looks
> > critical enough and can be a good candidate for fixing before 2.7
> release.
> >
> > I've found that commit [2] is also lead the exchange worker to hang in my
> > branch related to IGNITE-7196.
> > Not sure, I'm able to fix the whole [1] issue, but I will take a look at
> > it.
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-9731
> > [2]
> >
> >
> https://github.com/apache/ignite/commit/2f72fe758d4256c4eb4610e5922ad3d174b43dc5
> >
> >
> >
> > On Fri, 28 Sep 2018 at 11:11 Dmitriy Pavlov <dp...@gmail.com>
> wrote:
> >
> > > No, it is up to the community to discuss after their review results.
> > >
> > > пт, 28 сент. 2018 г. в 11:09, Vladimir Ozerov <vo...@gridgain.com>:
> > >
> > > > Dmitriy,
> > > >
> > > > Did I read your words correctly that it is up to implementor of a
> > single
> > > > feature to decide whether release of all other features and fixes to
> be
> > > > delayed?
> > > >
> > > > пт, 28 сент. 2018 г. в 11:00, Dmitriy Pavlov <dpavlov.spb@gmail.com
> >:
> > > >
> > > > > My point we can wait a bit for services because
> > > > > 1 we are open-minded and we don't have outside pressure to do
> > release
> > > in
> > > > > October
> > > > > 2 and services it is not some new feature, which suddenly appeared
> > in
> > > > > autumn, it is a well known and important feature.
> > > > >
> > > > > So it is up to Vyacheslav, Anton and Nikolay to decide.
> > > > >
> > > > > Decisions can be services are not ready/ready to merge only to
> > > > master/ready
> > > > > to merge to master and to 2.7.
> > > > >
> > > > >
> > > > > пт, 28 сент. 2018 г. в 10:46, Vladimir Ozerov <
> vozerov@gridgain.com
> > >:
> > > > >
> > > > > > Dmitry,
> > > > > >
> > > > > > Community agreement was to perform the release in October. Of
> > course
> > > we
> > > > > can
> > > > > > wait a bit for services. Then we wait a bit for other cool
> features
> > > > ready
> > > > > > by that time, then again and again, and release will never
> happen.
> > > And
> > > > > > while we are waiting for new features to come, already completerd
> > > > > features
> > > > > > cannot be used by anyone.
> > > > > >
> > > > > > This is why we have an agreement that if feature is not ready, it
> > > > should
> > > > > be
> > > > > > moved to future release, instead of shifting release. The sole
> > reason
> > > > to
> > > > > > have strict dates when decisions are made is to let release
> happen.
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Fri, Sep 28, 2018 at 2:22 AM Dmitriy Pavlov <
> > > dpavlov.spb@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Vladimir, I'm not searching for enemy, and not fighting with
> > you.
> > > > I'm
> > > > > > not
> > > > > > > happy about cases when we are hurrying.
> > > > > > >
> > > > > > > We can't fix test, fill ticket details, can't wait for
> > > contributions
> > > > to
> > > > > > > finish their tasks. It is not best idea to use experience from
> > > > > > commercial
> > > > > > > companies in open source. Are there any pressure outside
> > community?
> > > > Did
> > > > > > > someone promised rest of features to be released at 30
> September?
> > > > > > >
> > > > > > > Let's remember principle do-orcracy, power of those who do. If
> > > > > contribor
> > > > > > > does change and reviewer does review, let's give right of
> making
> > > > > decision
> > > > > > > to them, but not to some closed club of people who privately
> > > discuss
> > > > > > > something.
> > > > > > >
> > > > > > > Sincerely
> > > > > > > Dmitriy Pavlov
> > > > > > >
> > > > > > > чт, 27 сент. 2018 г., 23:42 Vyacheslav Daradur <
> > > daradurvs@gmail.com
> > > > >:
> > > > > > >
> > > > > > > > Hi Igniters!
> > > > > > > >
> > > > > > > > As I have written about Service Grid before [1] I'm
> finalizing
> > > the
> > > > > > > > solution to be sure that implementation is reliable.
> > > > > > > >
> > > > > > > > About including it in 2.7, if we talk that code freeze
> tomorrow
> > > > then
> > > > > > > > the solution is not ready to merge yet.
> > > > > > > > I hope that prereviewers Anton Vinogradov and Nikolay Izhikov
> > > will
> > > > be
> > > > > > > > able to answer if solution out of scope or not in a couple of
> > > days.
> > > > > > > >
> > > > > > > > [1]
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-release-td34076.html#a34485
> > > > > > > > On Thu, Sep 27, 2018 at 11:14 PM Dmitriy Pavlov <
> > > > > dpavlov.spb@gmail.com
> > > > > > >
> > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > Yes, I agree, NPE during WAL flush is definitely a blocker.
> > > > > > > > >
> > > > > > > > > It is strange why the current test set did not fail after
> > > commit.
> > > > > > > > >
> > > > > > > > > чт, 27 сент. 2018 г. в 21:45, Andrey Kuznetsov <
> > > > stkuzma@gmail.com
> > > > > >:
> > > > > > > > >
> > > > > > > > > > Igniters,
> > > > > > > > > >
> > > > > > > > > > I've bumped into a new bug in WAL manager recently, see
> > [1].
> > > It
> > > > > > looks
> > > > > > > > > > critical enough, and can be a good candidate for fixing
> > > before
> > > > > 2.7
> > > > > > > > release.
> > > > > > > > > >
> > > > > > > > > > Do you agree?
> > > > > > > > > >
> > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-9731
> > > > > > > > > >
> > > > > > > > > > чт, 27 сент. 2018 г. в 19:45, Dmitriy Pavlov <
> > > > > > dpavlov.spb@gmail.com
> > > > > > > >:
> > > > > > > > > >
> > > > > > > > > > > I need Vhyacheslav's opinion to be absolutely sure what
> > > > status
> > > > > is
> > > > > > > > now.
> > > > > > > > > > >
> > > > > > > > > > > We never committed to dates of release, as well. I
> don't
> > > > quite
> > > > > > > > understand
> > > > > > > > > > > what can mean 'the community committed to
> doing/releasing
> > > > > > > something'.
> > > > > > > > > > >
> > > > > > > > > > > About SG, I also concerned why such a big feature has
> > > quite a
> > > > > few
> > > > > > > > > > > discussions on the list. But it is another story.
> > > > > > > > > > >
> > > > > > > > > > > чт, 27 сент. 2018 г. в 19:33, Vladimir Ozerov <
> > > > > > > vozerov@gridgain.com
> > > > > > > > >:
> > > > > > > > > > >
> > > > > > > > > > > > Folks,
> > > > > > > > > > > >
> > > > > > > > > > > > Please stop looking for enemies everywhere. Just went
> > > > through
> > > > > > > this
> > > > > > > > > > thread
> > > > > > > > > > > > and search for "service" word.
> > > > > > > > > > > >
> > > > > > > > > > > > On Thu, Sep 27, 2018 at 7:30 PM Denis Magda <
> > > > > dmagda@apache.org
> > > > > > >
> > > > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > >> >
> > > > > > > > > > > >> > Denis, as PMC Chair, could you please control,
> that
> > > > > Service
> > > > > > > Grid
> > > > > > > > > > > >> > inclusion/exclusion is discussed properly
> according
> > to
> > > > the
> > > > > > > > Apache
> > > > > > > > > > Way.
> > > > > > > > > > > >>
> > > > > > > > > > > >>
> > > > > > > > > > > >> It's fine when committers/contributors have private
> > > > > > discussions
> > > > > > > > > > related
> > > > > > > > > > > to
> > > > > > > > > > > >> a feature they've been working on. Not everything
> > should
> > > > go
> > > > > > > > through
> > > > > > > > > > the
> > > > > > > > > > > >> dev
> > > > > > > > > > > >> list. Otherwise, it will be inundated. However,
> > agree,
> > > > that
> > > > > > > > > > > architectural
> > > > > > > > > > > >> and release decisions need to be done publicly.
> > > > > > > > > > > >>
> > > > > > > > > > > >> Speaking about Service Grid, there was a discussion
> > > where
> > > > I
> > > > > > saw
> > > > > > > > that
> > > > > > > > > > it
> > > > > > > > > > > >> was
> > > > > > > > > > > >> questionable whether it gets added to the release or
> > > not.
> > > > > > > > > > > >>
> > > > > > > > > > > >> *Vladislav*, could you please shed some light on the
> > > > current
> > > > > > > > status of
> > > > > > > > > > > the
> > > > > > > > > > > >> service grid?
> > > > > > > > > > > >>
> > > > > > > > > > > >> On Thu, Sep 27, 2018 at 9:12 AM Dmitriy Pavlov <
> > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > >
> > > > > > > > > > > >> wrote:
> > > > > > > > > > > >>
> > > > > > > > > > > >> > Ok, let's wait for feedback from SG
> > > > Author(s)/Reviewer(s)
> > > > > > > > first. If
> > > > > > > > > > it
> > > > > > > > > > > >> is
> > > > > > > > > > > >> > not ready, ok. But I thought it is almost done.
> > > > > > > > > > > >> >
> > > > > > > > > > > >> > I apologize if I missed some discussion (it can
> > > happen),
> > > > > but
> > > > > > > > > > > >> > According to the statement "our current agreement"
> > > > > > > > > > > >> > I can suspect some members are making some sort of
> > > > private
> > > > > > > > > > agreements,
> > > > > > > > > > > >> and
> > > > > > > > > > > >> > do not to discuss it on the list.
> > > > > > > > > > > >> >
> > > > > > > > > > > >> > Let's build consensus here first, and then name an
> > > > > > agreement.
> > > > > > > > > > > >> >
> > > > > > > > > > > >> > Denis, as PMC Chair, could you please control,
> that
> > > > > Service
> > > > > > > Grid
> > > > > > > > > > > >> > inclusion/exclusion is discussed properly
> according
> > to
> > > > the
> > > > > > > > Apache
> > > > > > > > > > Way.
> > > > > > > > > > > >> >
> > > > > > > > > > > >> > чт, 27 сент. 2018 г. в 18:55, Vladimir Ozerov <
> > > > > > > > vozerov@gridgain.com
> > > > > > > > > > >:
> > > > > > > > > > > >> >
> > > > > > > > > > > >> >> Dmitriy,
> > > > > > > > > > > >> >>
> > > > > > > > > > > >> >> This is an outcome of current state of Service
> > Grid -
> > > > it
> > > > > is
> > > > > > > not
> > > > > > > > > > > ready.
> > > > > > > > > > > >> We
> > > > > > > > > > > >> >> never committed to have it to 2.7. Our goal was
> to
> > > try
> > > > to
> > > > > > > > include
> > > > > > > > > > it
> > > > > > > > > > > >> into
> > > > > > > > > > > >> >> 2.7.
> > > > > > > > > > > >> >>
> > > > > > > > > > > >> >> On Thu, Sep 27, 2018 at 6:48 PM Dmitriy Pavlov <
> > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > >> >> wrote:
> > > > > > > > > > > >> >>
> > > > > > > > > > > >> >> > Could you please provide a reference to some
> > > thread?
> > > > > > > > Probably I
> > > > > > > > > > > >> missed
> > > > > > > > > > > >> >> it.
> > > > > > > > > > > >> >> >
> > > > > > > > > > > >> >> > чт, 27 сент. 2018 г. в 18:46, Vladimir Ozerov <
> > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > >> >:
> > > > > > > > > > > >> >> >
> > > > > > > > > > > >> >> > > Our current agreement is that Service Grid is
> > out
> > > > of
> > > > > > > scope.
> > > > > > > > > > This
> > > > > > > > > > > >> is a
> > > > > > > > > > > >> >> > huge
> > > > > > > > > > > >> >> > > feature, which hasn't entered review stage so
> > > far,
> > > > We
> > > > > > > will
> > > > > > > > not
> > > > > > > > > > be
> > > > > > > > > > > >> >> able to
> > > > > > > > > > > >> >> > > review/fix/test it properly.
> > > > > > > > > > > >> >> > >
> > > > > > > > > > > >> >> > > On Thu, Sep 27, 2018 at 6:32 PM Dmitriy
> Pavlov
> > <
> > > > > > > > > > > >> dpavlov.spb@gmail.com
> > > > > > > > > > > >> >> >
> > > > > > > > > > > >> >> > > wrote:
> > > > > > > > > > > >> >> > >
> > > > > > > > > > > >> >> > > > I agree, and I prefer four weeks for
> > > > stabilization*
> > > > > > (1
> > > > > > > > Oct -
> > > > > > > > > > 29
> > > > > > > > > > > >> Oct)
> > > > > > > > > > > >> >> > > >
> > > > > > > > > > > >> >> > > > Do I understand it correctly: Service Grid
> is
> > > > still
> > > > > > in
> > > > > > > > scope,
> > > > > > > > > > > >> isn't
> > > > > > > > > > > >> >> > it? I
> > > > > > > > > > > >> >> > > > find it very important.
> > > > > > > > > > > >> >> > > >
> > > > > > > > > > > >> >> > > > чт, 27 сент. 2018 г. в 18:28, Nikolay
> > Izhikov <
> > > > > > > > > > > >> nizhikov@apache.org
> > > > > > > > > > > >> >> >:
> > > > > > > > > > > >> >> > > >
> > > > > > > > > > > >> >> > > > > Hello, Vova.
> > > > > > > > > > > >> >> > > > >
> > > > > > > > > > > >> >> > > > > Thank you for clear release status.
> > > > > > > > > > > >> >> > > > > I'm +1 for your proposal.
> > > > > > > > > > > >> >> > > > >
> > > > > > > > > > > >> >> > > > > чт, 27 сент. 2018 г., 18:25 Alexey
> > Kuznetsov
> > > <
> > > > > > > > > > > >> >> akuznetsov@apache.org
> > > > > > > > > > > >> >> > >:
> > > > > > > > > > > >> >> > > > >
> > > > > > > > > > > >> >> > > > > > Vova,
> > > > > > > > > > > >> >> > > > > >
> > > > > > > > > > > >> >> > > > > > Huge +1 to do a stabilization.
> > > > > > > > > > > >> >> > > > > >
> > > > > > > > > > > >> >> > > > > >
> > > > > > > > > > > >> >> > > > > > --
> > > > > > > > > > > >> >> > > > > > Alexey Kuznetsov
> > > > > > > > > > > >> >> > > > > >
> > > > > > > > > > > >> >> > > > >
> > > > > > > > > > > >> >> > > >
> > > > > > > > > > > >> >> > >
> > > > > > > > > > > >> >> >
> > > > > > > > > > > >> >>
> > > > > > > > > > > >> >
> > > > > > > > > > > >>
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > --
> > > > > > > > > > Best regards,
> > > > > > > > > > Andrey Kuznetsov.
> > > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > Best Regards, Vyacheslav D.
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > --
> > --
> > Maxim Muzafarov
> >
>
Re: Apache Ignite 2.7 release
Posted by Dmitriy Pavlov <dp...@gmail.com>.
Hi Maxim,
Once 1) you are sure that commit is related to the failure, and 2) in case
contributors are not responding,
please let me know, probably we need to open one more separate topic about
revert.
Sincerely,
Dmitriy Pavlov
пт, 28 сент. 2018 г. в 11:15, Maxim Muzafarov <ma...@gmail.com>:
> Andrey, Dmitry,
>
> > I've bumped into a new bug in WAL manager recently, see [1]. It looks
> critical enough and can be a good candidate for fixing before 2.7 release.
>
> I've found that commit [2] is also lead the exchange worker to hang in my
> branch related to IGNITE-7196.
> Not sure, I'm able to fix the whole [1] issue, but I will take a look at
> it.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-9731
> [2]
>
> https://github.com/apache/ignite/commit/2f72fe758d4256c4eb4610e5922ad3d174b43dc5
>
>
>
> On Fri, 28 Sep 2018 at 11:11 Dmitriy Pavlov <dp...@gmail.com> wrote:
>
> > No, it is up to the community to discuss after their review results.
> >
> > пт, 28 сент. 2018 г. в 11:09, Vladimir Ozerov <vo...@gridgain.com>:
> >
> > > Dmitriy,
> > >
> > > Did I read your words correctly that it is up to implementor of a
> single
> > > feature to decide whether release of all other features and fixes to be
> > > delayed?
> > >
> > > пт, 28 сент. 2018 г. в 11:00, Dmitriy Pavlov <dp...@gmail.com>:
> > >
> > > > My point we can wait a bit for services because
> > > > 1 we are open-minded and we don't have outside pressure to do
> release
> > in
> > > > October
> > > > 2 and services it is not some new feature, which suddenly appeared
> in
> > > > autumn, it is a well known and important feature.
> > > >
> > > > So it is up to Vyacheslav, Anton and Nikolay to decide.
> > > >
> > > > Decisions can be services are not ready/ready to merge only to
> > > master/ready
> > > > to merge to master and to 2.7.
> > > >
> > > >
> > > > пт, 28 сент. 2018 г. в 10:46, Vladimir Ozerov <vozerov@gridgain.com
> >:
> > > >
> > > > > Dmitry,
> > > > >
> > > > > Community agreement was to perform the release in October. Of
> course
> > we
> > > > can
> > > > > wait a bit for services. Then we wait a bit for other cool features
> > > ready
> > > > > by that time, then again and again, and release will never happen.
> > And
> > > > > while we are waiting for new features to come, already completerd
> > > > features
> > > > > cannot be used by anyone.
> > > > >
> > > > > This is why we have an agreement that if feature is not ready, it
> > > should
> > > > be
> > > > > moved to future release, instead of shifting release. The sole
> reason
> > > to
> > > > > have strict dates when decisions are made is to let release happen.
> > > > >
> > > > >
> > > > >
> > > > > On Fri, Sep 28, 2018 at 2:22 AM Dmitriy Pavlov <
> > dpavlov.spb@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Vladimir, I'm not searching for enemy, and not fighting with
> you.
> > > I'm
> > > > > not
> > > > > > happy about cases when we are hurrying.
> > > > > >
> > > > > > We can't fix test, fill ticket details, can't wait for
> > contributions
> > > to
> > > > > > finish their tasks. It is not best idea to use experience from
> > > > > commercial
> > > > > > companies in open source. Are there any pressure outside
> community?
> > > Did
> > > > > > someone promised rest of features to be released at 30 September?
> > > > > >
> > > > > > Let's remember principle do-orcracy, power of those who do. If
> > > > contribor
> > > > > > does change and reviewer does review, let's give right of making
> > > > decision
> > > > > > to them, but not to some closed club of people who privately
> > discuss
> > > > > > something.
> > > > > >
> > > > > > Sincerely
> > > > > > Dmitriy Pavlov
> > > > > >
> > > > > > чт, 27 сент. 2018 г., 23:42 Vyacheslav Daradur <
> > daradurvs@gmail.com
> > > >:
> > > > > >
> > > > > > > Hi Igniters!
> > > > > > >
> > > > > > > As I have written about Service Grid before [1] I'm finalizing
> > the
> > > > > > > solution to be sure that implementation is reliable.
> > > > > > >
> > > > > > > About including it in 2.7, if we talk that code freeze tomorrow
> > > then
> > > > > > > the solution is not ready to merge yet.
> > > > > > > I hope that prereviewers Anton Vinogradov and Nikolay Izhikov
> > will
> > > be
> > > > > > > able to answer if solution out of scope or not in a couple of
> > days.
> > > > > > >
> > > > > > > [1]
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-release-td34076.html#a34485
> > > > > > > On Thu, Sep 27, 2018 at 11:14 PM Dmitriy Pavlov <
> > > > dpavlov.spb@gmail.com
> > > > > >
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > Yes, I agree, NPE during WAL flush is definitely a blocker.
> > > > > > > >
> > > > > > > > It is strange why the current test set did not fail after
> > commit.
> > > > > > > >
> > > > > > > > чт, 27 сент. 2018 г. в 21:45, Andrey Kuznetsov <
> > > stkuzma@gmail.com
> > > > >:
> > > > > > > >
> > > > > > > > > Igniters,
> > > > > > > > >
> > > > > > > > > I've bumped into a new bug in WAL manager recently, see
> [1].
> > It
> > > > > looks
> > > > > > > > > critical enough, and can be a good candidate for fixing
> > before
> > > > 2.7
> > > > > > > release.
> > > > > > > > >
> > > > > > > > > Do you agree?
> > > > > > > > >
> > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-9731
> > > > > > > > >
> > > > > > > > > чт, 27 сент. 2018 г. в 19:45, Dmitriy Pavlov <
> > > > > dpavlov.spb@gmail.com
> > > > > > >:
> > > > > > > > >
> > > > > > > > > > I need Vhyacheslav's opinion to be absolutely sure what
> > > status
> > > > is
> > > > > > > now.
> > > > > > > > > >
> > > > > > > > > > We never committed to dates of release, as well. I don't
> > > quite
> > > > > > > understand
> > > > > > > > > > what can mean 'the community committed to doing/releasing
> > > > > > something'.
> > > > > > > > > >
> > > > > > > > > > About SG, I also concerned why such a big feature has
> > quite a
> > > > few
> > > > > > > > > > discussions on the list. But it is another story.
> > > > > > > > > >
> > > > > > > > > > чт, 27 сент. 2018 г. в 19:33, Vladimir Ozerov <
> > > > > > vozerov@gridgain.com
> > > > > > > >:
> > > > > > > > > >
> > > > > > > > > > > Folks,
> > > > > > > > > > >
> > > > > > > > > > > Please stop looking for enemies everywhere. Just went
> > > through
> > > > > > this
> > > > > > > > > thread
> > > > > > > > > > > and search for "service" word.
> > > > > > > > > > >
> > > > > > > > > > > On Thu, Sep 27, 2018 at 7:30 PM Denis Magda <
> > > > dmagda@apache.org
> > > > > >
> > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > >> >
> > > > > > > > > > >> > Denis, as PMC Chair, could you please control, that
> > > > Service
> > > > > > Grid
> > > > > > > > > > >> > inclusion/exclusion is discussed properly according
> to
> > > the
> > > > > > > Apache
> > > > > > > > > Way.
> > > > > > > > > > >>
> > > > > > > > > > >>
> > > > > > > > > > >> It's fine when committers/contributors have private
> > > > > discussions
> > > > > > > > > related
> > > > > > > > > > to
> > > > > > > > > > >> a feature they've been working on. Not everything
> should
> > > go
> > > > > > > through
> > > > > > > > > the
> > > > > > > > > > >> dev
> > > > > > > > > > >> list. Otherwise, it will be inundated. However,
> agree,
> > > that
> > > > > > > > > > architectural
> > > > > > > > > > >> and release decisions need to be done publicly.
> > > > > > > > > > >>
> > > > > > > > > > >> Speaking about Service Grid, there was a discussion
> > where
> > > I
> > > > > saw
> > > > > > > that
> > > > > > > > > it
> > > > > > > > > > >> was
> > > > > > > > > > >> questionable whether it gets added to the release or
> > not.
> > > > > > > > > > >>
> > > > > > > > > > >> *Vladislav*, could you please shed some light on the
> > > current
> > > > > > > status of
> > > > > > > > > > the
> > > > > > > > > > >> service grid?
> > > > > > > > > > >>
> > > > > > > > > > >> On Thu, Sep 27, 2018 at 9:12 AM Dmitriy Pavlov <
> > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > >
> > > > > > > > > > >> wrote:
> > > > > > > > > > >>
> > > > > > > > > > >> > Ok, let's wait for feedback from SG
> > > Author(s)/Reviewer(s)
> > > > > > > first. If
> > > > > > > > > it
> > > > > > > > > > >> is
> > > > > > > > > > >> > not ready, ok. But I thought it is almost done.
> > > > > > > > > > >> >
> > > > > > > > > > >> > I apologize if I missed some discussion (it can
> > happen),
> > > > but
> > > > > > > > > > >> > According to the statement "our current agreement"
> > > > > > > > > > >> > I can suspect some members are making some sort of
> > > private
> > > > > > > > > agreements,
> > > > > > > > > > >> and
> > > > > > > > > > >> > do not to discuss it on the list.
> > > > > > > > > > >> >
> > > > > > > > > > >> > Let's build consensus here first, and then name an
> > > > > agreement.
> > > > > > > > > > >> >
> > > > > > > > > > >> > Denis, as PMC Chair, could you please control, that
> > > > Service
> > > > > > Grid
> > > > > > > > > > >> > inclusion/exclusion is discussed properly according
> to
> > > the
> > > > > > > Apache
> > > > > > > > > Way.
> > > > > > > > > > >> >
> > > > > > > > > > >> > чт, 27 сент. 2018 г. в 18:55, Vladimir Ozerov <
> > > > > > > vozerov@gridgain.com
> > > > > > > > > >:
> > > > > > > > > > >> >
> > > > > > > > > > >> >> Dmitriy,
> > > > > > > > > > >> >>
> > > > > > > > > > >> >> This is an outcome of current state of Service
> Grid -
> > > it
> > > > is
> > > > > > not
> > > > > > > > > > ready.
> > > > > > > > > > >> We
> > > > > > > > > > >> >> never committed to have it to 2.7. Our goal was to
> > try
> > > to
> > > > > > > include
> > > > > > > > > it
> > > > > > > > > > >> into
> > > > > > > > > > >> >> 2.7.
> > > > > > > > > > >> >>
> > > > > > > > > > >> >> On Thu, Sep 27, 2018 at 6:48 PM Dmitriy Pavlov <
> > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > >> >> wrote:
> > > > > > > > > > >> >>
> > > > > > > > > > >> >> > Could you please provide a reference to some
> > thread?
> > > > > > > Probably I
> > > > > > > > > > >> missed
> > > > > > > > > > >> >> it.
> > > > > > > > > > >> >> >
> > > > > > > > > > >> >> > чт, 27 сент. 2018 г. в 18:46, Vladimir Ozerov <
> > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > >> >:
> > > > > > > > > > >> >> >
> > > > > > > > > > >> >> > > Our current agreement is that Service Grid is
> out
> > > of
> > > > > > scope.
> > > > > > > > > This
> > > > > > > > > > >> is a
> > > > > > > > > > >> >> > huge
> > > > > > > > > > >> >> > > feature, which hasn't entered review stage so
> > far,
> > > We
> > > > > > will
> > > > > > > not
> > > > > > > > > be
> > > > > > > > > > >> >> able to
> > > > > > > > > > >> >> > > review/fix/test it properly.
> > > > > > > > > > >> >> > >
> > > > > > > > > > >> >> > > On Thu, Sep 27, 2018 at 6:32 PM Dmitriy Pavlov
> <
> > > > > > > > > > >> dpavlov.spb@gmail.com
> > > > > > > > > > >> >> >
> > > > > > > > > > >> >> > > wrote:
> > > > > > > > > > >> >> > >
> > > > > > > > > > >> >> > > > I agree, and I prefer four weeks for
> > > stabilization*
> > > > > (1
> > > > > > > Oct -
> > > > > > > > > 29
> > > > > > > > > > >> Oct)
> > > > > > > > > > >> >> > > >
> > > > > > > > > > >> >> > > > Do I understand it correctly: Service Grid is
> > > still
> > > > > in
> > > > > > > scope,
> > > > > > > > > > >> isn't
> > > > > > > > > > >> >> > it? I
> > > > > > > > > > >> >> > > > find it very important.
> > > > > > > > > > >> >> > > >
> > > > > > > > > > >> >> > > > чт, 27 сент. 2018 г. в 18:28, Nikolay
> Izhikov <
> > > > > > > > > > >> nizhikov@apache.org
> > > > > > > > > > >> >> >:
> > > > > > > > > > >> >> > > >
> > > > > > > > > > >> >> > > > > Hello, Vova.
> > > > > > > > > > >> >> > > > >
> > > > > > > > > > >> >> > > > > Thank you for clear release status.
> > > > > > > > > > >> >> > > > > I'm +1 for your proposal.
> > > > > > > > > > >> >> > > > >
> > > > > > > > > > >> >> > > > > чт, 27 сент. 2018 г., 18:25 Alexey
> Kuznetsov
> > <
> > > > > > > > > > >> >> akuznetsov@apache.org
> > > > > > > > > > >> >> > >:
> > > > > > > > > > >> >> > > > >
> > > > > > > > > > >> >> > > > > > Vova,
> > > > > > > > > > >> >> > > > > >
> > > > > > > > > > >> >> > > > > > Huge +1 to do a stabilization.
> > > > > > > > > > >> >> > > > > >
> > > > > > > > > > >> >> > > > > >
> > > > > > > > > > >> >> > > > > > --
> > > > > > > > > > >> >> > > > > > Alexey Kuznetsov
> > > > > > > > > > >> >> > > > > >
> > > > > > > > > > >> >> > > > >
> > > > > > > > > > >> >> > > >
> > > > > > > > > > >> >> > >
> > > > > > > > > > >> >> >
> > > > > > > > > > >> >>
> > > > > > > > > > >> >
> > > > > > > > > > >>
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > Best regards,
> > > > > > > > > Andrey Kuznetsov.
> > > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Best Regards, Vyacheslav D.
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> --
> --
> Maxim Muzafarov
>
Re: Apache Ignite 2.7 release
Posted by Maxim Muzafarov <ma...@gmail.com>.
Andrey, Dmitry,
> I've bumped into a new bug in WAL manager recently, see [1]. It looks
critical enough and can be a good candidate for fixing before 2.7 release.
I've found that commit [2] is also lead the exchange worker to hang in my
branch related to IGNITE-7196.
Not sure, I'm able to fix the whole [1] issue, but I will take a look at it.
[1] https://issues.apache.org/jira/browse/IGNITE-9731
[2]
https://github.com/apache/ignite/commit/2f72fe758d4256c4eb4610e5922ad3d174b43dc5
On Fri, 28 Sep 2018 at 11:11 Dmitriy Pavlov <dp...@gmail.com> wrote:
> No, it is up to the community to discuss after their review results.
>
> пт, 28 сент. 2018 г. в 11:09, Vladimir Ozerov <vo...@gridgain.com>:
>
> > Dmitriy,
> >
> > Did I read your words correctly that it is up to implementor of a single
> > feature to decide whether release of all other features and fixes to be
> > delayed?
> >
> > пт, 28 сент. 2018 г. в 11:00, Dmitriy Pavlov <dp...@gmail.com>:
> >
> > > My point we can wait a bit for services because
> > > 1 we are open-minded and we don't have outside pressure to do release
> in
> > > October
> > > 2 and services it is not some new feature, which suddenly appeared in
> > > autumn, it is a well known and important feature.
> > >
> > > So it is up to Vyacheslav, Anton and Nikolay to decide.
> > >
> > > Decisions can be services are not ready/ready to merge only to
> > master/ready
> > > to merge to master and to 2.7.
> > >
> > >
> > > пт, 28 сент. 2018 г. в 10:46, Vladimir Ozerov <vo...@gridgain.com>:
> > >
> > > > Dmitry,
> > > >
> > > > Community agreement was to perform the release in October. Of course
> we
> > > can
> > > > wait a bit for services. Then we wait a bit for other cool features
> > ready
> > > > by that time, then again and again, and release will never happen.
> And
> > > > while we are waiting for new features to come, already completerd
> > > features
> > > > cannot be used by anyone.
> > > >
> > > > This is why we have an agreement that if feature is not ready, it
> > should
> > > be
> > > > moved to future release, instead of shifting release. The sole reason
> > to
> > > > have strict dates when decisions are made is to let release happen.
> > > >
> > > >
> > > >
> > > > On Fri, Sep 28, 2018 at 2:22 AM Dmitriy Pavlov <
> dpavlov.spb@gmail.com>
> > > > wrote:
> > > >
> > > > > Vladimir, I'm not searching for enemy, and not fighting with you.
> > I'm
> > > > not
> > > > > happy about cases when we are hurrying.
> > > > >
> > > > > We can't fix test, fill ticket details, can't wait for
> contributions
> > to
> > > > > finish their tasks. It is not best idea to use experience from
> > > > commercial
> > > > > companies in open source. Are there any pressure outside community?
> > Did
> > > > > someone promised rest of features to be released at 30 September?
> > > > >
> > > > > Let's remember principle do-orcracy, power of those who do. If
> > > contribor
> > > > > does change and reviewer does review, let's give right of making
> > > decision
> > > > > to them, but not to some closed club of people who privately
> discuss
> > > > > something.
> > > > >
> > > > > Sincerely
> > > > > Dmitriy Pavlov
> > > > >
> > > > > чт, 27 сент. 2018 г., 23:42 Vyacheslav Daradur <
> daradurvs@gmail.com
> > >:
> > > > >
> > > > > > Hi Igniters!
> > > > > >
> > > > > > As I have written about Service Grid before [1] I'm finalizing
> the
> > > > > > solution to be sure that implementation is reliable.
> > > > > >
> > > > > > About including it in 2.7, if we talk that code freeze tomorrow
> > then
> > > > > > the solution is not ready to merge yet.
> > > > > > I hope that prereviewers Anton Vinogradov and Nikolay Izhikov
> will
> > be
> > > > > > able to answer if solution out of scope or not in a couple of
> days.
> > > > > >
> > > > > > [1]
> > > > > >
> > > > >
> > > >
> > >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-release-td34076.html#a34485
> > > > > > On Thu, Sep 27, 2018 at 11:14 PM Dmitriy Pavlov <
> > > dpavlov.spb@gmail.com
> > > > >
> > > > > > wrote:
> > > > > > >
> > > > > > > Yes, I agree, NPE during WAL flush is definitely a blocker.
> > > > > > >
> > > > > > > It is strange why the current test set did not fail after
> commit.
> > > > > > >
> > > > > > > чт, 27 сент. 2018 г. в 21:45, Andrey Kuznetsov <
> > stkuzma@gmail.com
> > > >:
> > > > > > >
> > > > > > > > Igniters,
> > > > > > > >
> > > > > > > > I've bumped into a new bug in WAL manager recently, see [1].
> It
> > > > looks
> > > > > > > > critical enough, and can be a good candidate for fixing
> before
> > > 2.7
> > > > > > release.
> > > > > > > >
> > > > > > > > Do you agree?
> > > > > > > >
> > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-9731
> > > > > > > >
> > > > > > > > чт, 27 сент. 2018 г. в 19:45, Dmitriy Pavlov <
> > > > dpavlov.spb@gmail.com
> > > > > >:
> > > > > > > >
> > > > > > > > > I need Vhyacheslav's opinion to be absolutely sure what
> > status
> > > is
> > > > > > now.
> > > > > > > > >
> > > > > > > > > We never committed to dates of release, as well. I don't
> > quite
> > > > > > understand
> > > > > > > > > what can mean 'the community committed to doing/releasing
> > > > > something'.
> > > > > > > > >
> > > > > > > > > About SG, I also concerned why such a big feature has
> quite a
> > > few
> > > > > > > > > discussions on the list. But it is another story.
> > > > > > > > >
> > > > > > > > > чт, 27 сент. 2018 г. в 19:33, Vladimir Ozerov <
> > > > > vozerov@gridgain.com
> > > > > > >:
> > > > > > > > >
> > > > > > > > > > Folks,
> > > > > > > > > >
> > > > > > > > > > Please stop looking for enemies everywhere. Just went
> > through
> > > > > this
> > > > > > > > thread
> > > > > > > > > > and search for "service" word.
> > > > > > > > > >
> > > > > > > > > > On Thu, Sep 27, 2018 at 7:30 PM Denis Magda <
> > > dmagda@apache.org
> > > > >
> > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > >> >
> > > > > > > > > >> > Denis, as PMC Chair, could you please control, that
> > > Service
> > > > > Grid
> > > > > > > > > >> > inclusion/exclusion is discussed properly according to
> > the
> > > > > > Apache
> > > > > > > > Way.
> > > > > > > > > >>
> > > > > > > > > >>
> > > > > > > > > >> It's fine when committers/contributors have private
> > > > discussions
> > > > > > > > related
> > > > > > > > > to
> > > > > > > > > >> a feature they've been working on. Not everything should
> > go
> > > > > > through
> > > > > > > > the
> > > > > > > > > >> dev
> > > > > > > > > >> list. Otherwise, it will be inundated. However, agree,
> > that
> > > > > > > > > architectural
> > > > > > > > > >> and release decisions need to be done publicly.
> > > > > > > > > >>
> > > > > > > > > >> Speaking about Service Grid, there was a discussion
> where
> > I
> > > > saw
> > > > > > that
> > > > > > > > it
> > > > > > > > > >> was
> > > > > > > > > >> questionable whether it gets added to the release or
> not.
> > > > > > > > > >>
> > > > > > > > > >> *Vladislav*, could you please shed some light on the
> > current
> > > > > > status of
> > > > > > > > > the
> > > > > > > > > >> service grid?
> > > > > > > > > >>
> > > > > > > > > >> On Thu, Sep 27, 2018 at 9:12 AM Dmitriy Pavlov <
> > > > > > dpavlov.spb@gmail.com
> > > > > > > > >
> > > > > > > > > >> wrote:
> > > > > > > > > >>
> > > > > > > > > >> > Ok, let's wait for feedback from SG
> > Author(s)/Reviewer(s)
> > > > > > first. If
> > > > > > > > it
> > > > > > > > > >> is
> > > > > > > > > >> > not ready, ok. But I thought it is almost done.
> > > > > > > > > >> >
> > > > > > > > > >> > I apologize if I missed some discussion (it can
> happen),
> > > but
> > > > > > > > > >> > According to the statement "our current agreement"
> > > > > > > > > >> > I can suspect some members are making some sort of
> > private
> > > > > > > > agreements,
> > > > > > > > > >> and
> > > > > > > > > >> > do not to discuss it on the list.
> > > > > > > > > >> >
> > > > > > > > > >> > Let's build consensus here first, and then name an
> > > > agreement.
> > > > > > > > > >> >
> > > > > > > > > >> > Denis, as PMC Chair, could you please control, that
> > > Service
> > > > > Grid
> > > > > > > > > >> > inclusion/exclusion is discussed properly according to
> > the
> > > > > > Apache
> > > > > > > > Way.
> > > > > > > > > >> >
> > > > > > > > > >> > чт, 27 сент. 2018 г. в 18:55, Vladimir Ozerov <
> > > > > > vozerov@gridgain.com
> > > > > > > > >:
> > > > > > > > > >> >
> > > > > > > > > >> >> Dmitriy,
> > > > > > > > > >> >>
> > > > > > > > > >> >> This is an outcome of current state of Service Grid -
> > it
> > > is
> > > > > not
> > > > > > > > > ready.
> > > > > > > > > >> We
> > > > > > > > > >> >> never committed to have it to 2.7. Our goal was to
> try
> > to
> > > > > > include
> > > > > > > > it
> > > > > > > > > >> into
> > > > > > > > > >> >> 2.7.
> > > > > > > > > >> >>
> > > > > > > > > >> >> On Thu, Sep 27, 2018 at 6:48 PM Dmitriy Pavlov <
> > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > >> >> wrote:
> > > > > > > > > >> >>
> > > > > > > > > >> >> > Could you please provide a reference to some
> thread?
> > > > > > Probably I
> > > > > > > > > >> missed
> > > > > > > > > >> >> it.
> > > > > > > > > >> >> >
> > > > > > > > > >> >> > чт, 27 сент. 2018 г. в 18:46, Vladimir Ozerov <
> > > > > > > > > vozerov@gridgain.com
> > > > > > > > > >> >:
> > > > > > > > > >> >> >
> > > > > > > > > >> >> > > Our current agreement is that Service Grid is out
> > of
> > > > > scope.
> > > > > > > > This
> > > > > > > > > >> is a
> > > > > > > > > >> >> > huge
> > > > > > > > > >> >> > > feature, which hasn't entered review stage so
> far,
> > We
> > > > > will
> > > > > > not
> > > > > > > > be
> > > > > > > > > >> >> able to
> > > > > > > > > >> >> > > review/fix/test it properly.
> > > > > > > > > >> >> > >
> > > > > > > > > >> >> > > On Thu, Sep 27, 2018 at 6:32 PM Dmitriy Pavlov <
> > > > > > > > > >> dpavlov.spb@gmail.com
> > > > > > > > > >> >> >
> > > > > > > > > >> >> > > wrote:
> > > > > > > > > >> >> > >
> > > > > > > > > >> >> > > > I agree, and I prefer four weeks for
> > stabilization*
> > > > (1
> > > > > > Oct -
> > > > > > > > 29
> > > > > > > > > >> Oct)
> > > > > > > > > >> >> > > >
> > > > > > > > > >> >> > > > Do I understand it correctly: Service Grid is
> > still
> > > > in
> > > > > > scope,
> > > > > > > > > >> isn't
> > > > > > > > > >> >> > it? I
> > > > > > > > > >> >> > > > find it very important.
> > > > > > > > > >> >> > > >
> > > > > > > > > >> >> > > > чт, 27 сент. 2018 г. в 18:28, Nikolay Izhikov <
> > > > > > > > > >> nizhikov@apache.org
> > > > > > > > > >> >> >:
> > > > > > > > > >> >> > > >
> > > > > > > > > >> >> > > > > Hello, Vova.
> > > > > > > > > >> >> > > > >
> > > > > > > > > >> >> > > > > Thank you for clear release status.
> > > > > > > > > >> >> > > > > I'm +1 for your proposal.
> > > > > > > > > >> >> > > > >
> > > > > > > > > >> >> > > > > чт, 27 сент. 2018 г., 18:25 Alexey Kuznetsov
> <
> > > > > > > > > >> >> akuznetsov@apache.org
> > > > > > > > > >> >> > >:
> > > > > > > > > >> >> > > > >
> > > > > > > > > >> >> > > > > > Vova,
> > > > > > > > > >> >> > > > > >
> > > > > > > > > >> >> > > > > > Huge +1 to do a stabilization.
> > > > > > > > > >> >> > > > > >
> > > > > > > > > >> >> > > > > >
> > > > > > > > > >> >> > > > > > --
> > > > > > > > > >> >> > > > > > Alexey Kuznetsov
> > > > > > > > > >> >> > > > > >
> > > > > > > > > >> >> > > > >
> > > > > > > > > >> >> > > >
> > > > > > > > > >> >> > >
> > > > > > > > > >> >> >
> > > > > > > > > >> >>
> > > > > > > > > >> >
> > > > > > > > > >>
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > Best regards,
> > > > > > > > Andrey Kuznetsov.
> > > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Best Regards, Vyacheslav D.
> > > > > >
> > > > >
> > > >
> > >
> >
>
--
--
Maxim Muzafarov
Re: Apache Ignite 2.7 release
Posted by Dmitriy Pavlov <dp...@gmail.com>.
Hi Nikolay,
Thank you for announcing that we entered this new stage of release. I
believe it is a paramount thing to keep community members posted.
BTW, this link worked for me
https://issues.apache.org/jira/issues/?jql=(project%20%3D%20'Ignite'%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20('2.7')%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
I noticed that we have 5 MVCC tickets to 2.7 still not assigned. I hope
contributors will assign these tickets.
Sincerely,
Dmitriy Pavlov
пн, 1 окт. 2018 г. в 18:17, Nikolay Izhikov <ni...@apache.org>:
> 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 <st...@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 <dp...@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 <ni...@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 <
> > > >
> > > > daradurvs@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 <
> > > > >
> > > > > dsetrakyan@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.spb@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 <
> dmagda@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 <
> > > > > > >
> > > > > > > nizhikov@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 <
> > > > > > > > >
> > > > > > > > > dsetrakyan@apache.org
> > > > > > > > > > > :
> > > > > > > > > > > >
> > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > >
> > > > > > > > > > > > > We agreed in the beginning of this thread that
> Service
> > > >
> > > > Grid
> > > > > > >
> > > > > > > changes
> > > > > > > > > > > are not
> > > > > > > > > > > > > going to make the release because the community
> still did
> > > > >
> > > > > not
> > > > > > > > >
> > > > > > > > > approve
> > > > > > > > > > > the
> > > > > > > > > > > > > design. Nothing has changed since. I have not seen
> any
> > > > >
> > > > > design
> > > > > > > > > > >
> > > > > > > > > > > discussions.
> > > > > > > > > > > > > At this point, I have no confidence that the
> Service Grid
> > > > > > >
> > > > > > > changes
> > > > > > > > > > will
> > > > > > > > > > > make
> > > > > > > > > > > > > it into the 2.8 release. The 2.7 release seems out
> of
> > > > >
> > > > > question
> > > > > > > > > > >
> > > > > > > > > > > altogether.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Also, Nikolay is a release manager. We should let
> him
> > > > >
> > > > > drive the
> > > > > > > > > > >
> > > > > > > > > > > release. To
> > > > > > > > > > > > > my knowledge, he is doing a great job and the
> release is
> > > > >
> > > > > going
> > > > > > > > > > >
> > > > > > > > > > > according to
> > > > > > > > > > > > > the schedule he proposed.
> > > > > > > > > > > > >
> > > > > > > > > > > > > D.
> > > > > > > > > > > > >
> > > > > > > > > > > > > On Fri, Sep 28, 2018 at 4:31 AM Dmitriy Pavlov <
> > > > > > > > > >
> > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > > > Hi Dmitriy, Vladimir,
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > I suggest we stop this nonsense with release
> > > > >
> > > > > dates-pushing
> > > > > > > > >
> > > > > > > > > because
> > > > > > > > > > of
> > > > > > > > > > > > >
> > > > > > > > > > > > > some
> > > > > > > > > > > > > > open question.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Just because you disagreed with any
> include/exclude
> > > > >
> > > > > something
> > > > > > > > >
> > > > > > > > > into
> > > > > > > > > > > scope,
> > > > > > > > > > > > > > does not mean that whole community disagreed.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > If folks will start a separate discussion with
> results
> > > > >
> > > > > of the
> > > > > > > > > > >
> > > > > > > > > > > review, I
> > > > > > > > > > > > >
> > > > > > > > > > > > > see
> > > > > > > > > > > > > > no reasons to reject their contribution, even if
> we
> > > >
> > > > need
> > > > > to
> > > > > > > > >
> > > > > > > > > revisit
> > > > > > > > > > > our
> > > > > > > > > > > > > > agreements and wait for a couple of days more.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Am I missing some reason why dates are so
> fundamentally
> > > > > > >
> > > > > > > important
> > > > > > > > > > to
> > > > > > > > > > > you?
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Sincerely,
> > > > > > > > > > > > > > Dmitriy Pavlov
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 12:20, Dmitriy Setrakyan <
> > > > > > > > > > >
> > > > > > > > > > > dsetrakyan@apache.org>:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > > If services is not ready, which it is not,
> then we
> > > > >
> > > > > should
> > > > > > > > >
> > > > > > > > > include
> > > > > > > > > > > them
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > into
> > > > > > > > > > > > > > > the next release. There is no need to force
> them into
> > > > >
> > > > > 2.7.
> > > > > > >
> > > > > > > I
> > > > > > > > > > > suggest we
> > > > > > > > > > > > > > > move according to the schedule we all agreed
> on.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > D.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at 1:22 AM Dmitriy Pavlov
> <
> > > > > > > > > > >
> > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Yes, so correct statement is "community did
> not
> > > >
> > > > make
> > > > > any
> > > > > > > > > > >
> > > > > > > > > > > decisions
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > about
> > > > > > > > > > > > > > > > services not go to 2.7/ services are out of
> scope".
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > If so, please forgive me my confusion.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:19, Vladimir
> Ozerov <
> > > > > > > > > > >
> > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Exactly. So correct statement is “it is up
> to
> > > > > > >
> > > > > > > *community*
> > > > > > > > > to
> > > > > > > > > > > decide
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > whether
> > > > > > > > > > > > > > > > > something goes to 2.7”.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:11, Dmitriy
> Pavlov <
> > > > > > > > > > > > >
> > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > No, it is up to the community to discuss
> after
> > > > >
> > > > > their
> > > > > > > > >
> > > > > > > > > review
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > results.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:09, Vladimir
> Ozerov <
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > Did I read your words correctly that
> it is up
> > > > >
> > > > > to
> > > > > > > > > > >
> > > > > > > > > > > implementor
> > > > > > > > > > > > >
> > > > > > > > > > > > > of a
> > > > > > > > > > > > > > > > > single
> > > > > > > > > > > > > > > > > > > feature to decide whether release of
> all
> > > >
> > > > other
> > > > > > >
> > > > > > > features
> > > > > > > > > > and
> > > > > > > > > > > > >
> > > > > > > > > > > > > fixes
> > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > > delayed?
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:00, Dmitriy
> Pavlov
> > > >
> > > > <
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > My point we can wait a bit for
> services
> > > > >
> > > > > because
> > > > > > > > > > > > > > > > > > > > 1 we are open-minded and we don't
> have
> > > > >
> > > > > outside
> > > > > > > > > >
> > > > > > > > > > pressure
> > > > > > > > > > > to
> > > > > > > > > > > > >
> > > > > > > > > > > > > do
> > > > > > > > > > > > > > > > > release
> > > > > > > > > > > > > > > > > > in
> > > > > > > > > > > > > > > > > > > > October
> > > > > > > > > > > > > > > > > > > > 2 and services it is not some new
> feature,
> > > > >
> > > > > which
> > > > > > > > > > >
> > > > > > > > > > > suddenly
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > appeared
> > > > > > > > > > > > > > > > > in
> > > > > > > > > > > > > > > > > > > > autumn, it is a well known and
> important
> > > > >
> > > > > feature.
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > So it is up to Vyacheslav, Anton and
> > > >
> > > > Nikolay
> > > > > to
> > > > > > > > >
> > > > > > > > > decide.
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > Decisions can be services are not
> > > > >
> > > > > ready/ready to
> > > > > > > > >
> > > > > > > > > merge
> > > > > > > > > > > only
> > > > > > > > > > > > >
> > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > master/ready
> > > > > > > > > > > > > > > > > > > > to merge to master and to 2.7.
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 10:46,
> Vladimir
> > > > >
> > > > > Ozerov <
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > Dmitry,
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > Community agreement was to perform
> the
> > > > >
> > > > > release
> > > > > > >
> > > > > > > in
> > > > > > > > > > > October.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Of
> > > > > > > > > > > > > > > > > course
> > > > > > > > > > > > > > > > > > we
> > > > > > > > > > > > > > > > > > > > can
> > > > > > > > > > > > > > > > > > > > > wait a bit for services. Then we
> wait a
> > > > >
> > > > > bit for
> > > > > > > > >
> > > > > > > > > other
> > > > > > > > > > > cool
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > features
> > > > > > > > > > > > > > > > > > > ready
> > > > > > > > > > > > > > > > > > > > > by that time, then again and
> again, and
> > > > >
> > > > > release
> > > > > > > > >
> > > > > > > > > will
> > > > > > > > > > > never
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > happen.
> > > > > > > > > > > > > > > > > > And
> > > > > > > > > > > > > > > > > > > > > while we are waiting for new
> features to
> > > > >
> > > > > come,
> > > > > > > > > >
> > > > > > > > > > already
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > completerd
> > > > > > > > > > > > > > > > > > > > features
> > > > > > > > > > > > > > > > > > > > > cannot be used by anyone.
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > This is why we have an agreement
> that if
> > > > > > >
> > > > > > > feature is
> > > > > > > > > > not
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > ready,
> > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > should
> > > > > > > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > > > > moved to future release, instead of
> > > > >
> > > > > shifting
> > > > > > > > >
> > > > > > > > > release.
> > > > > > > > > > > The
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > sole
> > > > > > > > > > > > > > > > > reason
> > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > have strict dates when decisions
> are made
> > > > >
> > > > > is
> > > > > > >
> > > > > > > to let
> > > > > > > > > > > release
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > happen.
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at 2:22 AM
> Dmitriy
> > > > >
> > > > > Pavlov
> > > > > > >
> > > > > > > <
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > Vladimir, I'm not searching for
> enemy,
> > > > >
> > > > > and
> > > > > > >
> > > > > > > not
> > > > > > > > > > > fighting
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > with
> > > > > > > > > > > > > > > > > you.
> > > > > > > > > > > > > > > > > > > I'm
> > > > > > > > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > > > > > > happy about cases when we are
> hurrying.
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > We can't fix test, fill ticket
> details,
> > > > >
> > > > > can't
> > > > > > > > >
> > > > > > > > > wait
> > > > > > > > > > > for
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > contributions
> > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > finish their tasks. It is not
> best
> > > >
> > > > idea
> > > > > to
> > > > > > >
> > > > > > > use
> > > > > > > > > > > > >
> > > > > > > > > > > > > experience
> > > > > > > > > > > > > > > from
> > > > > > > > > > > > > > > > > > > > > commercial
> > > > > > > > > > > > > > > > > > > > > > companies in open source. Are
> there any
> > > > > > >
> > > > > > > pressure
> > > > > > > > > > > outside
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > community?
> > > > > > > > > > > > > > > > > > > Did
> > > > > > > > > > > > > > > > > > > > > > someone promised rest of
> features to be
> > > > > > >
> > > > > > > released
> > > > > > > > > at
> > > > > > > > > > > 30
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > September?
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > Let's remember principle
> do-orcracy,
> > > > >
> > > > > power of
> > > > > > > > >
> > > > > > > > > those
> > > > > > > > > > > who
> > > > > > > > > > > > >
> > > > > > > > > > > > > do.
> > > > > > > > > > > > > > > If
> > > > > > > > > > > > > > > > > > > > contribor
> > > > > > > > > > > > > > > > > > > > > > does change and reviewer does
> review,
> > > > >
> > > > > let's
> > > > > > >
> > > > > > > give
> > > > > > > > > > > right of
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > making
> > > > > > > > > > > > > > > > > > > > decision
> > > > > > > > > > > > > > > > > > > > > > to them, but not to some closed
> club of
> > > > > > >
> > > > > > > people
> > > > > > > > > who
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > privately
> > > > > > > > > > > > > > > > > > discuss
> > > > > > > > > > > > > > > > > > > > > > something.
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > Sincerely
> > > > > > > > > > > > > > > > > > > > > > Dmitriy Pavlov
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г., 23:42
> Vyacheslav
> > > > > > >
> > > > > > > Daradur <
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > daradurvs@gmail.com
> > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > Hi Igniters!
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > As I have written about
> Service Grid
> > > > > > >
> > > > > > > before [1]
> > > > > > > > > > I'm
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > finalizing
> > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > solution to be sure that
> > > > >
> > > > > implementation is
> > > > > > > > > > >
> > > > > > > > > > > reliable.
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > About including it in 2.7, if
> we talk
> > > > >
> > > > > that
> > > > > > >
> > > > > > > code
> > > > > > > > > > > freeze
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > tomorrow
> > > > > > > > > > > > > > > > > > > then
> > > > > > > > > > > > > > > > > > > > > > > the solution is not ready to
> merge
> > > >
> > > > yet.
> > > > > > > > > > > > > > > > > > > > > > > I hope that prereviewers Anton
> > > > >
> > > > > Vinogradov
> > > > > > >
> > > > > > > and
> > > > > > > > > > > Nikolay
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Izhikov
> > > > > > > > > > > > > > > > > > will
> > > > > > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > > > > > > able to answer if solution out
> of
> > > > >
> > > > > scope or
> > > > > > >
> > > > > > > not
> > > > > > > > > > in a
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > couple
> > > > > > > > > > > > > > > of
> > > > > > > > > > > > > > > > > > days.
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > [1]
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > >
> > > > > > >
> > > >
> > > >
> http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-release-td34076.html#a34485
> > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 11:14
> PM
> > > > >
> > > > > Dmitriy
> > > > > > > > >
> > > > > > > > > Pavlov <
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > Yes, I agree, NPE during WAL
> flush
> > > >
> > > > is
> > > > > > > > > >
> > > > > > > > > > definitely
> > > > > > > > > > > a
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > blocker.
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > It is strange why the
> current test
> > > > >
> > > > > set
> > > > > > >
> > > > > > > did
> > > > > > > > > not
> > > > > > > > > > > fail
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > after
> > > > > > > > > > > > > > > > > > commit.
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 21:45,
> > > >
> > > > Andrey
> > > > > > > > >
> > > > > > > > > Kuznetsov
> > > > > > > > > > <
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > stkuzma@gmail.com
> > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > Igniters,
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > I've bumped into a new bug
> in WAL
> > > > > > >
> > > > > > > manager
> > > > > > > > > > > recently,
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > see
> > > > > > > > > > > > > > > > > [1].
> > > > > > > > > > > > > > > > > > It
> > > > > > > > > > > > > > > > > > > > > looks
> > > > > > > > > > > > > > > > > > > > > > > > > critical enough, and can
> be a
> > > >
> > > > good
> > > > > > > > >
> > > > > > > > > candidate
> > > > > > > > > > > for
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > fixing
> > > > > > > > > > > > > > > > > > before
> > > > > > > > > > > > > > > > > > > > 2.7
> > > > > > > > > > > > > > > > > > > > > > > release.
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > Do you agree?
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > [1]
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> https://issues.apache.org/jira/browse/IGNITE-9731
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в
> 19:45,
> > > > >
> > > > > Dmitriy
> > > > > > > > >
> > > > > > > > > Pavlov
> > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > I need Vhyacheslav's
> opinion to
> > > > >
> > > > > be
> > > > > > > > > >
> > > > > > > > > > absolutely
> > > > > > > > > > > > >
> > > > > > > > > > > > > sure
> > > > > > > > > > > > > > > what
> > > > > > > > > > > > > > > > > > > status
> > > > > > > > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > > > > > > > > now.
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > We never committed to
> dates of
> > > > > > >
> > > > > > > release,
> > > > > > > > > as
> > > > > > > > > > > well.
> > > > > > > > > > > > >
> > > > > > > > > > > > > I
> > > > > > > > > > > > > > > > don't
> > > > > > > > > > > > > > > > > > > quite
> > > > > > > > > > > > > > > > > > > > > > > understand
> > > > > > > > > > > > > > > > > > > > > > > > > > what can mean 'the
> community
> > > > > > >
> > > > > > > committed to
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > doing/releasing
> > > > > > > > > > > > > > > > > > > > > > something'.
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > About SG, I also
> concerned why
> > > > >
> > > > > such
> > > > > > >
> > > > > > > a big
> > > > > > > > > > > feature
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > has
> > > > > > > > > > > > > > > > > > quite a
> > > > > > > > > > > > > > > > > > > > few
> > > > > > > > > > > > > > > > > > > > > > > > > > discussions on the list.
> But it
> > > > >
> > > > > is
> > > > > > > > >
> > > > > > > > > another
> > > > > > > > > > > story.
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в
> 19:33,
> > > > > > >
> > > > > > > Vladimir
> > > > > > > > > > > Ozerov <
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > Folks,
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > Please stop looking for
> > > >
> > > > enemies
> > > > > > > > > >
> > > > > > > > > > everywhere.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Just
> > > > > > > > > > > > > > > went
> > > > > > > > > > > > > > > > > > > through
> > > > > > > > > > > > > > > > > > > > > > this
> > > > > > > > > > > > > > > > > > > > > > > > > thread
> > > > > > > > > > > > > > > > > > > > > > > > > > > and search for
> "service"
> > > >
> > > > word.
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018
> at 7:30
> > > >
> > > > PM
> > > > > > >
> > > > > > > Denis
> > > > > > > > > > > Magda <
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > dmagda@apache.org
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > Denis, as PMC
> Chair,
> > > >
> > > > could
> > > > > you
> > > > > > > > >
> > > > > > > > > please
> > > > > > > > > > > > >
> > > > > > > > > > > > > control,
> > > > > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > > > > Service
> > > > > > > > > > > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> inclusion/exclusion is
> > > > > > >
> > > > > > > discussed
> > > > > > > > > > > properly
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > according
> > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > Apache
> > > > > > > > > > > > > > > > > > > > > > > > > Way.
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > It's fine when
> > > > > > > > >
> > > > > > > > > committers/contributors
> > > > > > > > > > > have
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > private
> > > > > > > > > > > > > > > > > > > > > discussions
> > > > > > > > > > > > > > > > > > > > > > > > > related
> > > > > > > > > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > > > > > > > a feature they've
> been
> > > > >
> > > > > working
> > > > > > >
> > > > > > > on.
> > > > > > > > > Not
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > everything
> > > > > > > > > > > > > > > > > should
> > > > > > > > > > > > > > > > > > > go
> > > > > > > > > > > > > > > > > > > > > > > through
> > > > > > > > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > > > > > > dev
> > > > > > > > > > > > > > > > > > > > > > > > > > > > list. Otherwise, it
> will be
> > > > > > > > >
> > > > > > > > > inundated.
> > > > > > > > > > > > >
> > > > > > > > > > > > > However,
> > > > > > > > > > > > > > > > > agree,
> > > > > > > > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > > > > > > > > > > architectural
> > > > > > > > > > > > > > > > > > > > > > > > > > > > and release
> decisions need
> > > > >
> > > > > to be
> > > > > > >
> > > > > > > done
> > > > > > > > > > > > >
> > > > > > > > > > > > > publicly.
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > Speaking about
> Service
> > > >
> > > > Grid,
> > > > > > >
> > > > > > > there
> > > > > > > > > was
> > > > > > > > > > a
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > discussion
> > > > > > > > > > > > > > > > > > where
> > > > > > > > > > > > > > > > > > > I
> > > > > > > > > > > > > > > > > > > > > saw
> > > > > > > > > > > > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > > > > > > > > > was
> > > > > > > > > > > > > > > > > > > > > > > > > > > > questionable whether
> it
> > > >
> > > > gets
> > > > > > >
> > > > > > > added to
> > > > > > > > > > the
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > release
> > > > > > > > > > > > > > > or
> > > > > > > > > > > > > > > > > > not.
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > *Vladislav*, could
> you
> > > >
> > > > please
> > > > > > >
> > > > > > > shed
> > > > > > > > > some
> > > > > > > > > > > light
> > > > > > > > > > > > >
> > > > > > > > > > > > > on
> > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > current
> > > > > > > > > > > > > > > > > > > > > > > status of
> > > > > > > > > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > > > > > > service grid?
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018
> at
> > > >
> > > > 9:12
> > > > > AM
> > > > > > > > >
> > > > > > > > > Dmitriy
> > > > > > > > > > > > >
> > > > > > > > > > > > > Pavlov <
> > > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > Ok, let's wait for
> > > >
> > > > feedback
> > > > > > >
> > > > > > > from SG
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > Author(s)/Reviewer(s)
> > > > > > > > > > > > > > > > > > > > > > > first. If
> > > > > > > > > > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > not ready, ok. But
> I
> > > > >
> > > > > thought
> > > > > > >
> > > > > > > it is
> > > > > > > > > > > almost
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > done.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > I apologize if I
> missed
> > > > >
> > > > > some
> > > > > > > > > > >
> > > > > > > > > > > discussion (it
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > can
> > > > > > > > > > > > > > > > > > happen),
> > > > > > > > > > > > > > > > > > > > but
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > According to the
> > > >
> > > > statement
> > > > > "our
> > > > > > > > > >
> > > > > > > > > > current
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > agreement"
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > I can suspect some
> > > >
> > > > members
> > > > > are
> > > > > > > > >
> > > > > > > > > making
> > > > > > > > > > > some
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > sort
> > > > > > > > > > > > > > > of
> > > > > > > > > > > > > > > > > > > private
> > > > > > > > > > > > > > > > > > > > > > > > > agreements,
> > > > > > > > > > > > > > > > > > > > > > > > > > > > and
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > do not to discuss
> it on
> > > >
> > > > the
> > > > > > >
> > > > > > > list.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > Let's build
> consensus
> > > >
> > > > here
> > > > > > >
> > > > > > > first,
> > > > > > > > > and
> > > > > > > > > > > then
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > name
> > > > > > > > > > > > > > > an
> > > > > > > > > > > > > > > > > > > > > agreement.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > Denis, as PMC
> Chair,
> > > >
> > > > could
> > > > > you
> > > > > > > > >
> > > > > > > > > please
> > > > > > > > > > > > >
> > > > > > > > > > > > > control,
> > > > > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > > > > Service
> > > > > > > > > > > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> inclusion/exclusion is
> > > > > > >
> > > > > > > discussed
> > > > > > > > > > > properly
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > according
> > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > Apache
> > > > > > > > > > > > > > > > > > > > > > > > > Way.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018
> г. в
> > > > >
> > > > > 18:55,
> > > > > > > > > >
> > > > > > > > > > Vladimir
> > > > > > > > > > > > >
> > > > > > > > > > > > > Ozerov
> > > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > This is an
> outcome of
> > > > >
> > > > > current
> > > > > > > > >
> > > > > > > > > state
> > > > > > > > > > > of
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Service
> > > > > > > > > > > > > > > > > Grid -
> > > > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > > > > > > > > > > ready.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > We
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > never committed
> to have
> > > > >
> > > > > it to
> > > > > > > > >
> > > > > > > > > 2.7.
> > > > > > > > > > > Our goal
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > was
> > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > try
> > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > > include
> > > > > > > > > > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > > > > > > > > > into
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 2.7.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27,
> 2018 at
> > > > >
> > > > > 6:48
> > > > > > >
> > > > > > > PM
> > > > > > > > > > > Dmitriy
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Pavlov
> > > > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Could you
> please
> > > > >
> > > > > provide a
> > > > > > > > > > >
> > > > > > > > > > > reference to
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > some
> > > > > > > > > > > > > > > > > > thread?
> > > > > > > > > > > > > > > > > > > > > > > Probably I
> > > > > > > > > > > > > > > > > > > > > > > > > > > > missed
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > it.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент.
> 2018 г.
> > > >
> > > > в
> > > > > > >
> > > > > > > 18:46,
> > > > > > > > > > > Vladimir
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Ozerov <
> > > > > > > > > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Our current
> > > > >
> > > > > agreement is
> > > > > > >
> > > > > > > that
> > > > > > > > > > > Service
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > > out
> > > > > > > > > > > > > > > > > > > of
> > > > > > > > > > > > > > > > > > > > > > scope.
> > > > > > > > > > > > > > > > > > > > > > > > > This
> > > > > > > > > > > > > > > > > > > > > > > > > > > > is a
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > huge
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > feature,
> which
> > > >
> > > > hasn't
> > > > > > >
> > > > > > > entered
> > > > > > > > > > > review
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > stage
> > > > > > > > > > > > > > > so
> > > > > > > > > > > > > > > > > > far,
> > > > > > > > > > > > > > > > > > > We
> > > > > > > > > > > > > > > > > > > > > > will
> > > > > > > > > > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > able to
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> review/fix/test it
> > > > > > >
> > > > > > > properly.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep
> 27,
> > > >
> > > > 2018
> > > > > at
> > > > > > >
> > > > > > > 6:32
> > > > > > > > > PM
> > > > > > > > > > > Dmitriy
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Pavlov
> > > > > > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I agree,
> and I
> > > > >
> > > > > prefer
> > > > > > >
> > > > > > > four
> > > > > > > > > > > weeks for
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > stabilization*
> > > > > > > > > > > > > > > > > > > > > (1
> > > > > > > > > > > > > > > > > > > > > > > Oct -
> > > > > > > > > > > > > > > > > > > > > > > > > 29
> > > > > > > > > > > > > > > > > > > > > > > > > > > > Oct)
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Do I
> understand
> > > >
> > > > it
> > > > > > > > >
> > > > > > > > > correctly:
> > > > > > > > > > > Service
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > > > > still
> > > > > > > > > > > > > > > > > > > > > in
> > > > > > > > > > > > > > > > > > > > > > > scope,
> > > > > > > > > > > > > > > > > > > > > > > > > > > > isn't
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > it? I
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > find it
> very
> > > > >
> > > > > important.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27
> сент. 2018
> > > > >
> > > > > г. в
> > > > > > > > >
> > > > > > > > > 18:28,
> > > > > > > > > > > Nikolay
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Izhikov <
> > > > > > > > > > > > > > > > > > > > > > > > > > > > nizhikov@apache.org
> >
Re: Apache Ignite 2.7 release
Posted by Nikolay Izhikov <ni...@apache.org>.
Hello, Igniters.
Today is a code freeze date but we still have 29 not merged tickets mapped to 2.7 release [1]
It means:
1. We should continue work on 2.7 release and merge remaining tickets
2. Anyone who can help with #1, please, do it.
3. RC1 and further release builds will be created after all tickets will be merged.
I will inform you about the progress on a daily basis.
[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%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
В Ср, 03/10/2018 в 14:02 +0300, Nikolay Izhikov пишет:
> 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 <ni...@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 <dp...@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 <st...@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 <ni...@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 <vo...@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 <st...@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.spb@gmail.com
> > > > > > > :
> > > > > > > > > >
> > > > > > > > > > > Hi Anton,
> > > > > > > > > > >
> > > > > > > > > > > I definitely agree it is a blocker.
> > > > > > > > > > >
> > > > > > > > > > > Sincerely,
> > > > > > > > > > > Dmitriy Pavlov
> > > > > > > > > > >
> > > > > > > > > > > вт, 2 окт. 2018 г. в 13:09, Anton Kalashnikov <
> > > > >
> > > > > kaa.dev@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" <
> > > > >
> > > > > dsetrakyan@apache.org
> > > > > > > :
> > > > > > > > > > > > > Thanks, got it.
> > > > > > > > > > > > >
> > > > > > > > > > > > > On Mon, Oct 1, 2018 at 1:14 PM Dmitriy Pavlov <
> > > > > > > > >
> > > > > > > > > dpavlov.spb@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 <
> > > > > > > > >
> > > > > > > > > vozerov@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 <
> > > > > > > > > > > >
> > > > > > > > > > > > dsetrakyan@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 <
> > > > > > > > > > > >
> > > > > > > > > > > > vozerov@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 <
> > > > > > > > > > > >
> > > > > > > > > > > > nizhikov@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
> > > > > > <
> > > > > > > > > > > > > > stkuzma@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.spb@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
> > > > > > > <
> > > > > > > > > > > > > > > > nizhikov@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
> > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > daradurvs@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 <
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > dsetrakyan@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.spb@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 <
> > > > > > > > > > > > > > > > > > dmagda@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
> > > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > nizhikov@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 <
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > dsetrakyan@apache.org
> > > > > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > We agreed in the
> > > > >
> > > > > beginning
> > > > > > > of
> > > > > > > > >
> > > > > > > > > this
> > > > > > > > > > > > thread
> > > > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > > Service
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > changes
> > > > > > > > > > > > > > > > > > > > > > > > > > > > are not
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > going to make the
> > > > >
> > > > > release
> > > > > > > because
> > > > > > > > > >
> > > > > > > > > > the
> > > > > > > > > > > > > > > community
> > > > > > > > > > > > > > > > > > still did
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > approve
> > > > > > > > > > > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > design. Nothing has
> > > > > >
> > > > > > changed
> > > > > > > > >
> > > > > > > > > since.
> > > > > > > > > > I
> > > > > > > > > > > > have
> > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > seen
> > > > > > > > > > > > > > > > > > any
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > design
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > discussions.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > At this point, I have no
> > > > > > > > >
> > > > > > > > > confidence
> > > > > > > > > > > > that
> > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > Service Grid
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > changes
> > > > > > > > > > > > > > > > > > > > > > > > > > > will
> > > > > > > > > > > > > > > > > > > > > > > > > > > > make
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > it into the 2.8 release.
> > > > > > >
> > > > > > > The 2.7
> > > > > > > > > > > >
> > > > > > > > > > > > release
> > > > > > > > > > > > > > > seems
> > > > > > > > > > > > > > > > > out
> > > > > > > > > > > > > > > > > > of
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > question
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > altogether.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Also, Nikolay is a
> > > > >
> > > > > release
> > > > > > > > >
> > > > > > > > > manager.
> > > > > > > > > > > We
> > > > > > > > > > > > > > should
> > > > > > > > > > > > > > > > let
> > > > > > > > > > > > > > > > > > him
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > drive the
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > release. To
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > my knowledge, he is
> > > > >
> > > > > doing
> > > > > > a
> > > > > > > great
> > > > > > > > > >
> > > > > > > > > > job
> > > > > > > > > > > > and
> > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > release is
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > going
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > according to
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > the schedule he
> > > > >
> > > > > proposed.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > D.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at
> > > > > > >
> > > > > > > 4:31 AM
> > > > > > > > > > >
> > > > > > > > > > > Dmitriy
> > > > > > > > > > > > > > > Pavlov
> > > > > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hi Dmitriy, Vladimir,
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I suggest we stop this
> > > > > > >
> > > > > > > nonsense
> > > > > > > > > > >
> > > > > > > > > > > with
> > > > > > > > > > > > > > > release
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > dates-pushing
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > because
> > > > > > > > > > > > > > > > > > > > > > > > > > > of
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > some
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > open question.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Just because you
> > > > > > >
> > > > > > > disagreed with
> > > > > > > > > >
Re: Apache Ignite 2.7 release
Posted by Vladimir Ozerov <vo...@gridgain.com>.
Igniters,
I reviewed Spring Session integration [1] and propose to move it to the
next release. The reason is that current implementation has a number of
performance issues, had potential bugs which are yet to be covered with
tests, and possible lacks some features which other vendors like Hazelcast
or GemFire have. I left respective comments in the ticket.
As our goal is to have competitive implementation, it is better to exclude
it out of AI 2.7 scope to have enough time.
Vladimir.
[1] https://issues.apache.org/jira/browse/IGNITE-9676
On Tue, Oct 9, 2018 at 11:17 AM Andrey Kuznetsov <st...@gmail.com> wrote:
> 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 <ni...@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 <ni...@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.spb@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 <stkuzma@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 <
> nizhikov@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 <
> > vozerov@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 <
> > stkuzma@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.spb@gmail.com
> > > > > > > > :
> > > > > > > > > > >
> > > > > > > > > > > > Hi Anton,
> > > > > > > > > > > >
> > > > > > > > > > > > I definitely agree it is a blocker.
> > > > > > > > > > > >
> > > > > > > > > > > > Sincerely,
> > > > > > > > > > > > Dmitriy Pavlov
> > > > > > > > > > > >
> > > > > > > > > > > > вт, 2 окт. 2018 г. в 13:09, Anton Kalashnikov <
> > > > > >
> > > > > > kaa.dev@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" <
> > > > > >
> > > > > > dsetrakyan@apache.org
> > > > > > > > :
> > > > > > > > > > > > > > Thanks, got it.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > On Mon, Oct 1, 2018 at 1:14 PM Dmitriy Pavlov <
> > > > > > > > > >
> > > > > > > > > > dpavlov.spb@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 <
> > > > > > > > > >
> > > > > > > > > > vozerov@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 <
> > > > > > > > > > > > >
> > > > > > > > > > > > > dsetrakyan@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 <
> > > > > > > > > > > > >
> > > > > > > > > > > > > vozerov@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 <
> > > > > > > > > > > > >
> > > > > > > > > > > > > nizhikov@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
> > > > > > > <
> > > > > > > > > > > > > > > stkuzma@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.spb@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
> > > > > > > > <
> > > > > > > > > > > > > > > > > nizhikov@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
> > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > daradurvs@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 <
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > dsetrakyan@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.spb@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 <
> > > > > > > > > > > > > > > > > > > dmagda@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
> > > > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > nizhikov@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
> > > > > > > >
Re: Apache Ignite 2.7 release
Posted by Nikolay Izhikov <ni...@apache.org>.
+1 from me.
В Вт, 09/10/2018 в 19:16 +0300, Alexey Goncharuk пишет:
> Igniters, Nikolay,
>
> I've recently discovered an issue [1] which was causing test suite to quit
> on TC. The root cause of the issue was an incorrect handling of WAL
> archiver stop, which causes a failure propagated to the failure processor
> and lead to a JVM halt on each node stop. This is a regression compared
> from 2.6.
> I think it is worth including this fix to 2.7 given that the fix is ready
> and verified on TC.
>
> Please let me know if you have any objections.
>
> вт, 9 окт. 2018 г. в 19:00, Andrey Kuznetsov <st...@gmail.com>:
>
> > 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 <st...@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 <ni...@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 <ni...@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.spb@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 <stkuzma@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 <
> >
> > nizhikov@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 <
> > > >
> > > > vozerov@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 <
> > > >
> > > > stkuzma@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.spb@gmail.com
> > > > > > > > > > :
> > > > > > > > > > > > >
> > > > > > > > > > > > > > Hi Anton,
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > I definitely agree it is a blocker.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Sincerely,
> > > > > > > > > > > > > > Dmitriy Pavlov
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > вт, 2 окт. 2018 г. в 13:09, Anton Kalashnikov <
> > > > > > > >
> > > > > > > > kaa.dev@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" <
> > > > > > > >
> > > > > > > > dsetrakyan@apache.org
> > > > > > > > > > :
> > > > > > > > > > > > > > > > Thanks, got it.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > On Mon, Oct 1, 2018 at 1:14 PM Dmitriy Pavlov <
> > > > > > > > > > > >
> > > > > > > > > > > > dpavlov.spb@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 <
> > > > > > > > > > > >
> > > > > > > > > > > > vozerov@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 <
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > dsetrakyan@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 <
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > vozerov@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 <
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > nizhikov@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
> > > > > > > > > <
> > > > > > > > > > > > > > > > > stkuzma@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.spb@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
> > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > nizhikov@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
> > > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > daradurvs@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 <
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > dsetrakyan@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.spb@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 <
> > > > > > > > > > > > > > > > > > > > > dmagda@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
> > > > > > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > nizhikov@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
> > > > > > > > > > > > > > > > >
Re: Apache Ignite 2.7 release
Posted by Alexey Goncharuk <al...@gmail.com>.
Igniters, Nikolay,
I've recently discovered an issue [1] which was causing test suite to quit
on TC. The root cause of the issue was an incorrect handling of WAL
archiver stop, which causes a failure propagated to the failure processor
and lead to a JVM halt on each node stop. This is a regression compared
from 2.6.
I think it is worth including this fix to 2.7 given that the fix is ready
and verified on TC.
Please let me know if you have any objections.
вт, 9 окт. 2018 г. в 19:00, Andrey Kuznetsov <st...@gmail.com>:
> 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 <st...@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 <ni...@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 <ni...@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.spb@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 <stkuzma@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 <
> nizhikov@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 <
> >> vozerov@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 <
> >> stkuzma@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.spb@gmail.com
> >> > > > > > > :
> >> > > > > > > > > >
> >> > > > > > > > > > > Hi Anton,
> >> > > > > > > > > > >
> >> > > > > > > > > > > I definitely agree it is a blocker.
> >> > > > > > > > > > >
> >> > > > > > > > > > > Sincerely,
> >> > > > > > > > > > > Dmitriy Pavlov
> >> > > > > > > > > > >
> >> > > > > > > > > > > вт, 2 окт. 2018 г. в 13:09, Anton Kalashnikov <
> >> > > > >
> >> > > > > kaa.dev@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" <
> >> > > > >
> >> > > > > dsetrakyan@apache.org
> >> > > > > > > :
> >> > > > > > > > > > > > > Thanks, got it.
> >> > > > > > > > > > > > >
> >> > > > > > > > > > > > > On Mon, Oct 1, 2018 at 1:14 PM Dmitriy Pavlov <
> >> > > > > > > > >
> >> > > > > > > > > dpavlov.spb@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 <
> >> > > > > > > > >
> >> > > > > > > > > vozerov@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 <
> >> > > > > > > > > > > >
> >> > > > > > > > > > > > dsetrakyan@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 <
> >> > > > > > > > > > > >
> >> > > > > > > > > > > > vozerov@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 <
> >> > > > > > > > > > > >
> >> > > > > > > > > > > > nizhikov@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
> >> > > > > > <
> >> > > > > > > > > > > > > > stkuzma@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.spb@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
> >> > > > > > > <
> >> > > > > > > > > > > > > > > > nizhikov@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
> >> > > > > > > > > > > <
> >> > > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > > daradurvs@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 <
> >> > > > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > > > dsetrakyan@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.spb@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 <
> >> > > > > > > > > > > > > > > > > > dmagda@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
> >> > > > > > > > > > > > > > <
> >> > > > > > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > > > > > nizhikov@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
> >> > > > > > > > > > > > > >
Re: Apache Ignite 2.7 release
Posted by Andrey Kuznetsov <st...@gmail.com>.
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 <st...@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 <ni...@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 <ni...@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.spb@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 <st...@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 <nizhikov@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 <
>> vozerov@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 <
>> stkuzma@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.spb@gmail.com
>> > > > > > > :
>> > > > > > > > > >
>> > > > > > > > > > > Hi Anton,
>> > > > > > > > > > >
>> > > > > > > > > > > I definitely agree it is a blocker.
>> > > > > > > > > > >
>> > > > > > > > > > > Sincerely,
>> > > > > > > > > > > Dmitriy Pavlov
>> > > > > > > > > > >
>> > > > > > > > > > > вт, 2 окт. 2018 г. в 13:09, Anton Kalashnikov <
>> > > > >
>> > > > > kaa.dev@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" <
>> > > > >
>> > > > > dsetrakyan@apache.org
>> > > > > > > :
>> > > > > > > > > > > > > Thanks, got it.
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > On Mon, Oct 1, 2018 at 1:14 PM Dmitriy Pavlov <
>> > > > > > > > >
>> > > > > > > > > dpavlov.spb@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 <
>> > > > > > > > >
>> > > > > > > > > vozerov@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 <
>> > > > > > > > > > > >
>> > > > > > > > > > > > dsetrakyan@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 <
>> > > > > > > > > > > >
>> > > > > > > > > > > > vozerov@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 <
>> > > > > > > > > > > >
>> > > > > > > > > > > > nizhikov@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
>> > > > > > <
>> > > > > > > > > > > > > > stkuzma@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.spb@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
>> > > > > > > <
>> > > > > > > > > > > > > > > > nizhikov@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
>> > > > > > > > > > > <
>> > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > daradurvs@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 <
>> > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > dsetrakyan@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.spb@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 <
>> > > > > > > > > > > > > > > > > > dmagda@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
>> > > > > > > > > > > > > > <
>> > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > nizhikov@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 <
>> > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > >
>> <ds...@apache.org>
>
>
>
> --
> Best regards,
> Andrey Kuznetsov.
>
--
Best regards,
Andrey Kuznetsov.
Re: Apache Ignite 2.7 release
Posted by Andrey Kuznetsov <st...@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 <ni...@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 <ni...@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.spb@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 <st...@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 <nizhikov@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 <
> vozerov@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 <
> stkuzma@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.spb@gmail.com
> > > > > > > :
> > > > > > > > > >
> > > > > > > > > > > Hi Anton,
> > > > > > > > > > >
> > > > > > > > > > > I definitely agree it is a blocker.
> > > > > > > > > > >
> > > > > > > > > > > Sincerely,
> > > > > > > > > > > Dmitriy Pavlov
> > > > > > > > > > >
> > > > > > > > > > > вт, 2 окт. 2018 г. в 13:09, Anton Kalashnikov <
> > > > >
> > > > > kaa.dev@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" <
> > > > >
> > > > > dsetrakyan@apache.org
> > > > > > > :
> > > > > > > > > > > > > Thanks, got it.
> > > > > > > > > > > > >
> > > > > > > > > > > > > On Mon, Oct 1, 2018 at 1:14 PM Dmitriy Pavlov <
> > > > > > > > >
> > > > > > > > > dpavlov.spb@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 <
> > > > > > > > >
> > > > > > > > > vozerov@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 <
> > > > > > > > > > > >
> > > > > > > > > > > > dsetrakyan@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 <
> > > > > > > > > > > >
> > > > > > > > > > > > vozerov@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 <
> > > > > > > > > > > >
> > > > > > > > > > > > nizhikov@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
> > > > > > <
> > > > > > > > > > > > > > stkuzma@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.spb@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
> > > > > > > <
> > > > > > > > > > > > > > > > nizhikov@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
> > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > daradurvs@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 <
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > dsetrakyan@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.spb@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 <
> > > > > > > > > > > > > > > > > > dmagda@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
> > > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > nizhikov@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 <
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > <ds...@apache.org>
--
Best regards,
Andrey Kuznetsov.
Re: Apache Ignite 2.7 release
Posted by Dmitriy Pavlov <dp...@gmail.com>.
Hi Alexey,
Security is always mandatory for all Apache projects. So I agree we should
include.
Sincerely,
Dmitriy Pavlov
чт, 4 окт. 2018 г. в 12:37, Alexey Kuznetsov <ak...@apache.org>:
> Hi, All!
>
> I found a bug with *IGNITE_MBEANS_DISABLED* system property.
> I created issue: IGNITE-9792 Setting system property
> *IGNITE_MBEANS_DISABLED* to true lead to NPE.
>
> I think this one can be included into 2.7, because java docs
> for IGNITE_MBEANS_DISABLED
> claims that "*This may be helpful if MBeans are not allowed e.g. for
> security reasons.*"
>
> The fix is trivial (one liner + simple text).
>
> I can contribute the fix for this bug.
>
> 1. https://issues.apache.org/jira/browse/IGNITE-9792
>
> --
> Alexey Kuznetsov
>
Re: Apache Ignite 2.7 release
Posted by Alexey Kuznetsov <ak...@apache.org>.
Hi, All!
I found a bug with *IGNITE_MBEANS_DISABLED* system property.
I created issue: IGNITE-9792 Setting system property
*IGNITE_MBEANS_DISABLED* to true lead to NPE.
I think this one can be included into 2.7, because java docs
for IGNITE_MBEANS_DISABLED
claims that "*This may be helpful if MBeans are not allowed e.g. for
security reasons.*"
The fix is trivial (one liner + simple text).
I can contribute the fix for this bug.
1. https://issues.apache.org/jira/browse/IGNITE-9792
--
Alexey Kuznetsov
Re: Apache Ignite 2.7 release
Posted by Vladimir Ozerov <vo...@gridgain.com>.
Igniters,
We observe serious drop in SQL performance. Corresponding ticket with
"blocker" priority has been added to AI 2.7 scope [1].
[1] https://issues.apache.org/jira/browse/IGNITE-9784
On Wed, Oct 3, 2018 at 2:02 PM Nikolay Izhikov <ni...@apache.org> wrote:
> 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 <ni...@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.spb@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 <st...@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 <nizhikov@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 <
> vozerov@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 <
> stkuzma@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.spb@gmail.com
> > > > > > > :
> > > > > > > > > >
> > > > > > > > > > > Hi Anton,
> > > > > > > > > > >
> > > > > > > > > > > I definitely agree it is a blocker.
> > > > > > > > > > >
> > > > > > > > > > > Sincerely,
> > > > > > > > > > > Dmitriy Pavlov
> > > > > > > > > > >
> > > > > > > > > > > вт, 2 окт. 2018 г. в 13:09, Anton Kalashnikov <
> > > > >
> > > > > kaa.dev@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" <
> > > > >
> > > > > dsetrakyan@apache.org
> > > > > > > :
> > > > > > > > > > > > > Thanks, got it.
> > > > > > > > > > > > >
> > > > > > > > > > > > > On Mon, Oct 1, 2018 at 1:14 PM Dmitriy Pavlov <
> > > > > > > > >
> > > > > > > > > dpavlov.spb@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 <
> > > > > > > > >
> > > > > > > > > vozerov@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 <
> > > > > > > > > > > >
> > > > > > > > > > > > dsetrakyan@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 <
> > > > > > > > > > > >
> > > > > > > > > > > > vozerov@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 <
> > > > > > > > > > > >
> > > > > > > > > > > > nizhikov@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
> > > > > > <
> > > > > > > > > > > > > > stkuzma@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.spb@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
> > > > > > > <
> > > > > > > > > > > > > > > > nizhikov@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
> > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > daradurvs@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 <
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > dsetrakyan@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.spb@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 <
> > > > > > > > > > > > > > > > > > dmagda@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
> > > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > nizhikov@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 <
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > <ds...@apache.org>
Re: Apache Ignite 2.7 release
Posted by Nikolay Izhikov <ni...@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 <ni...@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 <dp...@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 <st...@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 <ni...@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 <vo...@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 <st...@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.spb@gmail.com
> > > > > > :
> > > > > > > > >
> > > > > > > > > > Hi Anton,
> > > > > > > > > >
> > > > > > > > > > I definitely agree it is a blocker.
> > > > > > > > > >
> > > > > > > > > > Sincerely,
> > > > > > > > > > Dmitriy Pavlov
> > > > > > > > > >
> > > > > > > > > > вт, 2 окт. 2018 г. в 13:09, Anton Kalashnikov <
> > > >
> > > > kaa.dev@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" <
> > > >
> > > > dsetrakyan@apache.org
> > > > > > :
> > > > > > > > > > > > Thanks, got it.
> > > > > > > > > > > >
> > > > > > > > > > > > On Mon, Oct 1, 2018 at 1:14 PM Dmitriy Pavlov <
> > > > > > > >
> > > > > > > > dpavlov.spb@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 <
> > > > > > > >
> > > > > > > > vozerov@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 <
> > > > > > > > > > >
> > > > > > > > > > > dsetrakyan@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 <
> > > > > > > > > > >
> > > > > > > > > > > vozerov@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 <
> > > > > > > > > > >
> > > > > > > > > > > nizhikov@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
> > > > > <
> > > > > > > > > > > > > stkuzma@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.spb@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
> > > > > > <
> > > > > > > > > > > > > > > nizhikov@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
> > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > daradurvs@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 <
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > dsetrakyan@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.spb@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 <
> > > > > > > > > > > > > > > > > dmagda@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
> > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > nizhikov@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 <
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > dsetrakyan@apache.org
> > > > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > We agreed in the
> > > >
> > > > beginning
> > > > > > of
> > > > > > > >
> > > > > > > > this
> > > > > > > > > > > thread
> > > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > Service
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > changes
> > > > > > > > > > > > > > > > > > > > > > > > > > > are not
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > going to make the
> > > >
> > > > release
> > > > > > because
> > > > > > > > >
> > > > > > > > > the
> > > > > > > > > > > > > > community
> > > > > > > > > > > > > > > > > still did
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > approve
> > > > > > > > > > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > design. Nothing has
> > > > >
> > > > > changed
> > > > > > > >
> > > > > > > > since.
> > > > > > > > > I
> > > > > > > > > > > have
> > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > seen
> > > > > > > > > > > > > > > > > any
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > design
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > discussions.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > At this point, I have no
> > > > > > > >
> > > > > > > > confidence
> > > > > > > > > > > that
> > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > Service Grid
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > changes
> > > > > > > > > > > > > > > > > > > > > > > > > > will
> > > > > > > > > > > > > > > > > > > > > > > > > > > make
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > it into the 2.8 release.
> > > > > >
> > > > > > The 2.7
> > > > > > > > > > >
> > > > > > > > > > > release
> > > > > > > > > > > > > > seems
> > > > > > > > > > > > > > > > out
> > > > > > > > > > > > > > > > > of
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > question
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > altogether.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > Also, Nikolay is a
> > > >
> > > > release
> > > > > > > >
> > > > > > > > manager.
> > > > > > > > > > We
> > > > > > > > > > > > > should
> > > > > > > > > > > > > > > let
> > > > > > > > > > > > > > > > > him
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > drive the
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > release. To
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > my knowledge, he is
> > > >
> > > > doing
> > > > > a
> > > > > > great
> > > > > > > > >
> > > > > > > > > job
> > > > > > > > > > > and
> > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > release is
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > going
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > according to
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > the schedule he
> > > >
> > > > proposed.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > D.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at
> > > > > >
> > > > > > 4:31 AM
> > > > > > > > > >
> > > > > > > > > > Dmitriy
> > > > > > > > > > > > > > Pavlov
> > > > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hi Dmitriy, Vladimir,
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I suggest we stop this
> > > > > >
> > > > > > nonsense
> > > > > > > > > >
> > > > > > > > > > with
> > > > > > > > > > > > > > release
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > dates-pushing
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > because
> > > > > > > > > > > > > > > > > > > > > > > > > > of
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > some
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > open question.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Just because you
> > > > > >
> > > > > > disagreed with
> > > > > > > > >
Re: Apache Ignite 2.7 release
Posted by Alexey Goncharuk <al...@gmail.com>.
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 <ni...@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 <dp...@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 <st...@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 <ni...@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 <
> vozerov@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 <
> stkuzma@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.spb@gmail.com
> > > > > :
> > > > > > > >
> > > > > > > > > Hi Anton,
> > > > > > > > >
> > > > > > > > > I definitely agree it is a blocker.
> > > > > > > > >
> > > > > > > > > Sincerely,
> > > > > > > > > Dmitriy Pavlov
> > > > > > > > >
> > > > > > > > > вт, 2 окт. 2018 г. в 13:09, Anton Kalashnikov <
> > >
> > > kaa.dev@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" <
> > >
> > > dsetrakyan@apache.org
> > > > > :
> > > > > > > > > > > Thanks, got it.
> > > > > > > > > > >
> > > > > > > > > > > On Mon, Oct 1, 2018 at 1:14 PM Dmitriy Pavlov <
> > > > > > >
> > > > > > > dpavlov.spb@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 <
> > > > > > >
> > > > > > > vozerov@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 <
> > > > > > > > > >
> > > > > > > > > > dsetrakyan@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
> <
> > > > > > > > > >
> > > > > > > > > > vozerov@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 <
> > > > > > > > > >
> > > > > > > > > > nizhikov@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
> > > > <
> > > > > > > > > > > > stkuzma@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.spb@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
> > > > > <
> > > > > > > > > > > > > > nizhikov@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
> > > > > > > > > <
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > daradurvs@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 <
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > dsetrakyan@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.spb@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 <
> > > > > > > > > > > > > > > > dmagda@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
> > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > nizhikov@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 <
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > dsetrakyan@apache.org
> > > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > We agreed in the
> > >
> > > beginning
> > > > > of
> > > > > > >
> > > > > > > this
> > > > > > > > > > thread
> > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > Service
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > changes
> > > > > > > > > > > > > > > > > > > > > > > > > > are not
> > > > > > > > > > > > > > > > > > > > > > > > > > > > going to make the
> > >
> > > release
> > > > > because
> > > > > > > >
> > > > > > > > the
> > > > > > > > > > > > > community
> > > > > > > > > > > > > > > > still did
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > approve
> > > > > > > > > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > > > > > > design. Nothing has
> > > >
> > > > changed
> > > > > > >
> > > > > > > since.
> > > > > > > > I
> > > > > > > > > > have
> > > > > > > > > > > > not
> > > > > > > > > > > > > > > seen
> > > > > > > > > > > > > > > > any
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > design
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > discussions.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > At this point, I
> have no
> > > > > > >
> > > > > > > confidence
> > > > > > > > > > that
> > > > > > > > > > > > the
> > > > > > > > > > > > > > > > Service Grid
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > changes
> > > > > > > > > > > > > > > > > > > > > > > > > will
> > > > > > > > > > > > > > > > > > > > > > > > > > make
> > > > > > > > > > > > > > > > > > > > > > > > > > > > it into the 2.8
> release.
> > > > >
> > > > > The 2.7
> > > > > > > > > >
> > > > > > > > > > release
> > > > > > > > > > > > > seems
> > > > > > > > > > > > > > > out
> > > > > > > > > > > > > > > > of
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > question
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > altogether.
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > Also, Nikolay is a
> > >
> > > release
> > > > > > >
> > > > > > > manager.
> > > > > > > > > We
> > > > > > > > > > > > should
> > > > > > > > > > > > > > let
> > > > > > > > > > > > > > > > him
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > drive the
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > release. To
> > > > > > > > > > > > > > > > > > > > > > > > > > > > my knowledge, he is
> > >
> > > doing
> > > > a
> > > > > great
> > > > > > > >
> > > > > > > > job
> > > > > > > > > > and
> > > > > > > > > > > > the
> > > > > > > > > > > > > > > > release is
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > going
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > according to
> > > > > > > > > > > > > > > > > > > > > > > > > > > > the schedule he
> > >
> > > proposed.
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > D.
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > On Fri, Sep 28,
> 2018 at
> > > > >
> > > > > 4:31 AM
> > > > > > > > >
> > > > > > > > > Dmitriy
> > > > > > > > > > > > > Pavlov
> > > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hi Dmitriy,
> Vladimir,
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > I suggest we stop
> this
> > > > >
> > > > > nonsense
> > > > > > > > >
> > > > > > > > > with
> > > > > > > > > > > > > release
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > dates-pushing
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > because
> > > > > > > > > > > > > > > > > > > > > > > > > of
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > some
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > open question.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > Just because you
> > > > >
> > > > > disagreed with
> > > > > > > >
>
Re: Apache Ignite 2.7 release
Posted by Dmitriy Pavlov <dp...@gmail.com>.
Hi Igniters,
After a short chat with Vladimir I understood the concern, it should be a
regression, but not just a bug, which existed for years. It is the case of
all fixes related to WAL nowadays.
I can research a bit which ticket caused regression, but I see no reason to
do if we already have fixes instead.
Nikolay,
we've passed only scope freeze, but not code freeze. I've mentioned we
should discuss ticket including in our process, and features are
prohibited, but please note it is a draft for now.
Sincerely,
Dmitriy Pavlov
ср, 3 окт. 2018 г. в 13:38, Nikolay Izhikov <ni...@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 <dp...@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 <st...@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 <ni...@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 <
> vozerov@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 <
> stkuzma@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.spb@gmail.com
> > > > > :
> > > > > > > >
> > > > > > > > > Hi Anton,
> > > > > > > > >
> > > > > > > > > I definitely agree it is a blocker.
> > > > > > > > >
> > > > > > > > > Sincerely,
> > > > > > > > > Dmitriy Pavlov
> > > > > > > > >
> > > > > > > > > вт, 2 окт. 2018 г. в 13:09, Anton Kalashnikov <
> > >
> > > kaa.dev@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" <
> > >
> > > dsetrakyan@apache.org
> > > > > :
> > > > > > > > > > > Thanks, got it.
> > > > > > > > > > >
> > > > > > > > > > > On Mon, Oct 1, 2018 at 1:14 PM Dmitriy Pavlov <
> > > > > > >
> > > > > > > dpavlov.spb@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 <
> > > > > > >
> > > > > > > vozerov@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 <
> > > > > > > > > >
> > > > > > > > > > dsetrakyan@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
> <
> > > > > > > > > >
> > > > > > > > > > vozerov@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 <
> > > > > > > > > >
> > > > > > > > > > nizhikov@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
> > > > <
> > > > > > > > > > > > stkuzma@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.spb@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
> > > > > <
> > > > > > > > > > > > > > nizhikov@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
> > > > > > > > > <
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > daradurvs@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 <
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > dsetrakyan@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.spb@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 <
> > > > > > > > > > > > > > > > dmagda@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
> > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > nizhikov@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 <
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > dsetrakyan@apache.org
> > > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > We agreed in the
> > >
> > > beginning
> > > > > of
> > > > > > >
> > > > > > > this
> > > > > > > > > > thread
> > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > Service
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > changes
> > > > > > > > > > > > > > > > > > > > > > > > > > are not
> > > > > > > > > > > > > > > > > > > > > > > > > > > > going to make the
> > >
> > > release
> > > > > because
> > > > > > > >
> > > > > > > > the
> > > > > > > > > > > > > community
> > > > > > > > > > > > > > > > still did
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > approve
> > > > > > > > > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > > > > > > design. Nothing has
> > > >
> > > > changed
> > > > > > >
> > > > > > > since.
> > > > > > > > I
> > > > > > > > > > have
> > > > > > > > > > > > not
> > > > > > > > > > > > > > > seen
> > > > > > > > > > > > > > > > any
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > design
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > discussions.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > At this point, I
> have no
> > > > > > >
> > > > > > > confidence
> > > > > > > > > > that
> > > > > > > > > > > > the
> > > > > > > > > > > > > > > > Service Grid
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > changes
> > > > > > > > > > > > > > > > > > > > > > > > > will
> > > > > > > > > > > > > > > > > > > > > > > > > > make
> > > > > > > > > > > > > > > > > > > > > > > > > > > > it into the 2.8
> release.
> > > > >
> > > > > The 2.7
> > > > > > > > > >
> > > > > > > > > > release
> > > > > > > > > > > > > seems
> > > > > > > > > > > > > > > out
> > > > > > > > > > > > > > > > of
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > question
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > altogether.
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > Also, Nikolay is a
> > >
> > > release
> > > > > > >
> > > > > > > manager.
> > > > > > > > > We
> > > > > > > > > > > > should
> > > > > > > > > > > > > > let
> > > > > > > > > > > > > > > > him
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > drive the
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > release. To
> > > > > > > > > > > > > > > > > > > > > > > > > > > > my knowledge, he is
> > >
> > > doing
> > > > a
> > > > > great
> > > > > > > >
> > > > > > > > job
> > > > > > > > > > and
> > > > > > > > > > > > the
> > > > > > > > > > > > > > > > release is
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > going
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > according to
> > > > > > > > > > > > > > > > > > > > > > > > > > > > the schedule he
> > >
> > > proposed.
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > D.
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > On Fri, Sep 28,
> 2018 at
> > > > >
> > > > > 4:31 AM
> > > > > > > > >
> > > > > > > > > Dmitriy
> > > > > > > > > > > > > Pavlov
> > > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hi Dmitriy,
> Vladimir,
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > I suggest we stop
> this
> > > > >
> > > > > nonsense
> > > > > > > > >
> > > > > > > > > with
> > > > > > > > > > > > > release
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > dates-pushing
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > because
> > > > > > > > > > > > > > > > > > > > > > > > > of
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > some
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > open question.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > Just because you
> > > > >
> > > > > disagreed with
> > > > > > > >
>
Re: Apache Ignite 2.7 release
Posted by Nikolay Izhikov <ni...@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 <dp...@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 <st...@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 <ni...@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 <vo...@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 <st...@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.spb@gmail.com
> > > > :
> > > > > > >
> > > > > > > > Hi Anton,
> > > > > > > >
> > > > > > > > I definitely agree it is a blocker.
> > > > > > > >
> > > > > > > > Sincerely,
> > > > > > > > Dmitriy Pavlov
> > > > > > > >
> > > > > > > > вт, 2 окт. 2018 г. в 13:09, Anton Kalashnikov <
> >
> > kaa.dev@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" <
> >
> > dsetrakyan@apache.org
> > > > :
> > > > > > > > > > Thanks, got it.
> > > > > > > > > >
> > > > > > > > > > On Mon, Oct 1, 2018 at 1:14 PM Dmitriy Pavlov <
> > > > > >
> > > > > > dpavlov.spb@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 <
> > > > > >
> > > > > > vozerov@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 <
> > > > > > > > >
> > > > > > > > > dsetrakyan@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 <
> > > > > > > > >
> > > > > > > > > vozerov@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 <
> > > > > > > > >
> > > > > > > > > nizhikov@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
> > > <
> > > > > > > > > > > stkuzma@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.spb@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
> > > > <
> > > > > > > > > > > > > nizhikov@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
> > > > > > > > <
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > daradurvs@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 <
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > dsetrakyan@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.spb@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 <
> > > > > > > > > > > > > > > dmagda@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
> > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > nizhikov@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 <
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > dsetrakyan@apache.org
> > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > We agreed in the
> >
> > beginning
> > > > of
> > > > > >
> > > > > > this
> > > > > > > > > thread
> > > > > > > > > > > > that
> > > > > > > > > > > > > > > Service
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > changes
> > > > > > > > > > > > > > > > > > > > > > > > > are not
> > > > > > > > > > > > > > > > > > > > > > > > > > > going to make the
> >
> > release
> > > > because
> > > > > > >
> > > > > > > the
> > > > > > > > > > > > community
> > > > > > > > > > > > > > > still did
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > approve
> > > > > > > > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > > > > > design. Nothing has
> > >
> > > changed
> > > > > >
> > > > > > since.
> > > > > > > I
> > > > > > > > > have
> > > > > > > > > > > not
> > > > > > > > > > > > > > seen
> > > > > > > > > > > > > > > any
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > design
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > discussions.
> > > > > > > > > > > > > > > > > > > > > > > > > > > At this point, I have no
> > > > > >
> > > > > > confidence
> > > > > > > > > that
> > > > > > > > > > > the
> > > > > > > > > > > > > > > Service Grid
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > changes
> > > > > > > > > > > > > > > > > > > > > > > > will
> > > > > > > > > > > > > > > > > > > > > > > > > make
> > > > > > > > > > > > > > > > > > > > > > > > > > > it into the 2.8 release.
> > > >
> > > > The 2.7
> > > > > > > > >
> > > > > > > > > release
> > > > > > > > > > > > seems
> > > > > > > > > > > > > > out
> > > > > > > > > > > > > > > of
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > question
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > altogether.
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > Also, Nikolay is a
> >
> > release
> > > > > >
> > > > > > manager.
> > > > > > > > We
> > > > > > > > > > > should
> > > > > > > > > > > > > let
> > > > > > > > > > > > > > > him
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > drive the
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > release. To
> > > > > > > > > > > > > > > > > > > > > > > > > > > my knowledge, he is
> >
> > doing
> > > a
> > > > great
> > > > > > >
> > > > > > > job
> > > > > > > > > and
> > > > > > > > > > > the
> > > > > > > > > > > > > > > release is
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > going
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > according to
> > > > > > > > > > > > > > > > > > > > > > > > > > > the schedule he
> >
> > proposed.
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > D.
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at
> > > >
> > > > 4:31 AM
> > > > > > > >
> > > > > > > > Dmitriy
> > > > > > > > > > > > Pavlov
> > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > Hi Dmitriy, Vladimir,
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > I suggest we stop this
> > > >
> > > > nonsense
> > > > > > > >
> > > > > > > > with
> > > > > > > > > > > > release
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > dates-pushing
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > because
> > > > > > > > > > > > > > > > > > > > > > > > of
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > some
> > > > > > > > > > > > > > > > > > > > > > > > > > > > open question.
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > Just because you
> > > >
> > > > disagreed with
> > > > > > >
> > > > > > > any
> > > > > > > > > > > > > > > include/exclude
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > something
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > into
> > > > > > > > > > > > > > > > > > > > > > > > > scope,
> > > > > > > > > > > > > > > > > > > > > > > > > > > > does not mean that
> >
> > whole
> > > > > > >
> > > > > > > community
> > > > > > > > > > > > disagreed.
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > If folks will start a
> > > >
> > > > separate
> > > > > > > > >
> > > > > > > > > discussion
> > > > > > > > > > > > > with
> > > > > > > > > > > > > > > results
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > of the
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > review, I
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > see
> > > > > > > > > > > > > > > > > > > > > > > > > > > > no reasons to reject
> > >
> > > their
> > > > > > > > >
> > > > > > > > > contribution,
> > > > > > > > > > > > even
> > > > > > > > > > > > > > if
> > > > > > > > > > > > > > > we
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > need
> > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > revisit
> > > > > > > > > > > > > > > > > > > > > > > > > our
> > > > > > > > > > > > > > > > > > > > > > > > > > > > agreements and wait
> >
> > for
> > > a
> > > > > >
> > > > > > couple
> > > > > > > of
> > > > > > > > > days
> > > > > > > > > > > > > more.
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > Am I missing some
> >
> > reason
> > > > why
> > > > > > >
> > > > > > > dates
> > > > > > > > > are so
> > > > > > > > > > > > > > > fundamentally
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > important
> > > > > > > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > > > > you?
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > Sincerely,
> > > > > > > > > > > > > > > > > > > > > > > > > > > > Dmitriy Pavlov
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в
> > > >
> > > > 12:20,
> > > > > > > >
> > > > > > > > Dmitriy
> > > > > > > > > > > > > > Setrakyan <
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > dsetrakyan@apache.org>:
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > If services is not
> > > >
> > > > ready,
> > > > > >
> > > > > > which
> > > > > > > > it
> > > > > > > > > is
> > > > > > > > > > > > not,
> > > > > > > > > > > > > > > then we
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > should
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > include
> > > > > > > > > > > > > > > > > > > > > > > > > them
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > into
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > the next release.
> > >
> > > There
> > > > is no
> > > > > > > >
> > > > > > > > need
> > > > > > > > > to
> > > > > > > > > > > > force
> > > > > > > > > > > > > > > them into
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > 2.7.
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > I
> > > > > > > > > > > > > > > > > > > > > > > > > suggest we
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > move according to
> >
> > the
> > > > > >
> > > > > > schedule
> > > > > > > we
> > > > > > > > > all
> > > > > > > > > > > > > agreed
> > > > > > > > > > > > > > > on.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > D.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018
> > >
> > > at
> > > > 1:22
> > > > > >
> > > > > > AM
> > > > > > > > > Dmitriy
> > > > > > > > > > > > > > Pavlov
> > > > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Yes, so correct
> > > >
> > > > statement
> > > > > >
> > > > > > is
> > > > > > > > > > > "community
> > > > > > > > > > > > > did
> > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > make
> > > > > > > > > > > > > > > > > > > any
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > decisions
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > about
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > services not go to
> > > >
> > > > 2.7/
> > > > > > > >
> > > > > > > > services
> > > > > > > > > are
> > > > > > > > > > > > out
> > > > > > > > > > > > > of
> > > > > > > > > > > > > > > scope".
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > If so, please
> > >
> > > forgive
> > > > me my
> > > > > > > > > > > confusion.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018
> > >
> > > г. в
> > > > > >
> > > > > > 11:19,
> > > > > > > > > > > Vladimir
> > > > > > > > > > > > > > > Ozerov <
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Exactly. So
> > >
> > > correct
> > > > > > >
> > > > > > > statement
> > > > > > > > > is
> > > > > > > > > > > “it
> > > > > > > > > > > > is
> > > > > > > > > > > > > > up
> > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > *community*
> > > > > > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > > > > decide
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > whether
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > something goes
> >
> > to
> > > > 2.7”.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > пт, 28 сент.
> >
> > 2018
> > > > г. в
> > > > > > >
> > > > > > > 11:11,
> > > > > > > > > > > Dmitriy
> > > > > > > > > > > > > > > Pavlov <
> > > > > > > > > > > > > > >
Re: Apache Ignite 2.7 release
Posted by Vladimir Ozerov <vo...@gridgain.com>.
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 I want to ask is to stop including new tickets without
explaining why they should be in AI 2.7. Regression between AI 2.6 and AI
2.7 is enough. But "I found new NPE" is not.
On Wed, Oct 3, 2018 at 1:24 PM Vladimir Ozerov <vo...@gridgain.com> wrote:
> 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 <dp...@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 <st...@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 <ni...@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 <vo...@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 <st...@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.spb@gmail.com
>> > >:
>> > > > > >
>> > > > > > > Hi Anton,
>> > > > > > >
>> > > > > > > I definitely agree it is a blocker.
>> > > > > > >
>> > > > > > > Sincerely,
>> > > > > > > Dmitriy Pavlov
>> > > > > > >
>> > > > > > > вт, 2 окт. 2018 г. в 13:09, Anton Kalashnikov <
>> kaa.dev@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" <
>> dsetrakyan@apache.org
>> > >:
>> > > > > > > > > Thanks, got it.
>> > > > > > > > >
>> > > > > > > > > On Mon, Oct 1, 2018 at 1:14 PM Dmitriy Pavlov <
>> > > > >
>> > > > > dpavlov.spb@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 <
>> > > > >
>> > > > > vozerov@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 <
>> > > > > > > >
>> > > > > > > > dsetrakyan@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 <
>> > > > > > > >
>> > > > > > > > vozerov@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 <
>> > > > > > > >
>> > > > > > > > nizhikov@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
>> > <
>> > > > > > > > > > stkuzma@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.spb@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
>> > > <
>> > > > > > > > > > > > nizhikov@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
>> > > > > > > <
>> > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > daradurvs@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 <
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > dsetrakyan@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.spb@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 <
>> > > > > > > > > > > > > > dmagda@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
>> > > > > > > > > > <
>> > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > nizhikov@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 <
>> > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > dsetrakyan@apache.org
>> > > > > > > > > > > > > > > > > > > > > > > > :
>> > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > Dmitriy,
>> > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > We agreed in the
>> beginning
>> > > of
>> > > > >
>> > > > > this
>> > > > > > > > thread
>> > > > > > > > > > > that
>> > > > > > > > > > > > > > Service
>> > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > Grid
>> > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > changes
>> > > > > > > > > > > > > > > > > > > > > > > > are not
>> > > > > > > > > > > > > > > > > > > > > > > > > > going to make the
>> release
>> > > because
>> > > > > >
>> > > > > > the
>> > > > > > > > > > > community
>> > > > > > > > > > > > > > still did
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > not
>> > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > approve
>> > > > > > > > > > > > > > > > > > > > > > > > the
>> > > > > > > > > > > > > > > > > > > > > > > > > > design. Nothing has
>> > changed
>> > > > >
>> > > > > since.
>> > > > > > I
>> > > > > > > > have
>> > > > > > > > > > not
>> > > > > > > > > > > > > seen
>> > > > > > > > > > > > > > any
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > design
>> > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > discussions.
>> > > > > > > > > > > > > > > > > > > > > > > > > > At this point, I have
>> no
>> > > > >
>> > > > > confidence
>> > > > > > > > that
>> > > > > > > > > > the
>> > > > > > > > > > > > > > Service Grid
>> > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > changes
>> > > > > > > > > > > > > > > > > > > > > > > will
>> > > > > > > > > > > > > > > > > > > > > > > > make
>> > > > > > > > > > > > > > > > > > > > > > > > > > it into the 2.8
>> release.
>> > > The 2.7
>> > > > > > > >
>> > > > > > > > release
>> > > > > > > > > > > seems
>> > > > > > > > > > > > > out
>> > > > > > > > > > > > > > of
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > question
>> > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > altogether.
>> > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > Also, Nikolay is a
>> release
>> > > > >
>> > > > > manager.
>> > > > > > > We
>> > > > > > > > > > should
>> > > > > > > > > > > > let
>> > > > > > > > > > > > > > him
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > drive the
>> > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > release. To
>> > > > > > > > > > > > > > > > > > > > > > > > > > my knowledge, he is
>> doing
>> > a
>> > > great
>> > > > > >
>> > > > > > job
>> > > > > > > > and
>> > > > > > > > > > the
>> > > > > > > > > > > > > > release is
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > going
>> > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > according to
>> > > > > > > > > > > > > > > > > > > > > > > > > > the schedule he
>> proposed.
>> > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > D.
>> > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at
>> > > 4:31 AM
>> > > > > > >
>> > > > > > > Dmitriy
>> > > > > > > > > > > Pavlov
>> > > > > > > > > > > > <
>> > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
>> > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
>> > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > Hi Dmitriy, Vladimir,
>> > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > I suggest we stop
>> this
>> > > nonsense
>> > > > > > >
>> > > > > > > with
>> > > > > > > > > > > release
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > dates-pushing
>> > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > because
>> > > > > > > > > > > > > > > > > > > > > > > of
>> > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > some
>> > > > > > > > > > > > > > > > > > > > > > > > > > > open question.
>> > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > Just because you
>> > > disagreed with
>> > > > > >
>> > > > > > any
>> > > > > > > > > > > > > > include/exclude
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > something
>> > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > into
>> > > > > > > > > > > > > > > > > > > > > > > > scope,
>> > > > > > > > > > > > > > > > > > > > > > > > > > > does not mean that
>> whole
>> > > > > >
>> > > > > > community
>> > > > > > > > > > > disagreed.
>> > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > If folks will start a
>> > > separate
>> > > > > > > >
>> > > > > > > > discussion
>> > > > > > > > > > > > with
>> > > > > > > > > > > > > > results
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > of the
>> > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > review, I
>> > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > see
>> > > > > > > > > > > > > > > > > > > > > > > > > > > no reasons to reject
>> > their
>> > > > > > > >
>> > > > > > > > contribution,
>> > > > > > > > > > > even
>> > > > > > > > > > > > > if
>> > > > > > > > > > > > > > we
>> > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > need
>> > > > > > > > > > > > > > > > > > to
>> > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > revisit
>> > > > > > > > > > > > > > > > > > > > > > > > our
>> > > > > > > > > > > > > > > > > > > > > > > > > > > agreements and wait
>> for
>> > a
>> > > > >
>> > > > > couple
>> > > > > > of
>> > > > > > > > days
>> > > > > > > > > > > > more.
>> > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > Am I missing some
>> reason
>> > > why
>> > > > > >
>> > > > > > dates
>> > > > > > > > are so
>> > > > > > > > > > > > > > fundamentally
>> > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > important
>> > > > > > > > > > > > > > > > > > > > > > > to
>> > > > > > > > > > > > > > > > > > > > > > > > you?
>> > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > Sincerely,
>> > > > > > > > > > > > > > > > > > > > > > > > > > > Dmitriy Pavlov
>> > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г.
>> в
>> > > 12:20,
>> > > > > > >
>> > > > > > > Dmitriy
>> > > > > > > > > > > > > Setrakyan <
>> > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > dsetrakyan@apache.org>:
>> > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > If services is not
>> > > ready,
>> > > > >
>> > > > > which
>> > > > > > > it
>> > > > > > > > is
>> > > > > > > > > > > not,
>> > > > > > > > > > > > > > then we
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > should
>> > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > include
>> > > > > > > > > > > > > > > > > > > > > > > > them
>> > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > into
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > the next release.
>> > There
>> > > is no
>> > > > > > >
>> > > > > > > need
>> > > > > > > > to
>> > > > > > > > > > > force
>> > > > > > > > > > > > > > them into
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > 2.7.
>> > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > I
>> > > > > > > > > > > > > > > > > > > > > > > > suggest we
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > move according to
>> the
>> > > > >
>> > > > > schedule
>> > > > > > we
>> > > > > > > > all
>> > > > > > > > > > > > agreed
>> > > > > > > > > > > > > > on.
>> > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > D.
>> > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > On Fri, Sep 28,
>> 2018
>> > at
>> > > 1:22
>> > > > >
>> > > > > AM
>> > > > > > > > Dmitriy
>> > > > > > > > > > > > > Pavlov
>> > > > > > > > > > > > > > <
>> > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
>> > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > Yes, so correct
>> > > statement
>> > > > >
>> > > > > is
>> > > > > > > > > > "community
>> > > > > > > > > > > > did
>> > > > > > > > > > > > > > not
>> > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > make
>> > > > > > > > > > > > > > > > > > any
>> > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > decisions
>> > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > about
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > services not go
>> to
>> > > 2.7/
>> > > > > > >
>> > > > > > > services
>> > > > > > > > are
>> > > > > > > > > > > out
>> > > > > > > > > > > > of
>> > > > > > > > > > > > > > scope".
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > If so, please
>> > forgive
>> > > me my
>> > > > > > > > > > confusion.
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018
>> > г. в
>> > > > >
>> > > > > 11:19,
>> > > > > > > > > > Vladimir
>> > > > > > > > > > > > > > Ozerov <
>> > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
>> > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > :
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Exactly. So
>> > correct
>> > > > > >
>> > > > > > statement
>> > > > > > > > is
>> > > > > > > > > > “it
>> > > > > > > > > > > is
>> > > > > > > > > > > > > up
>> > > > > > > > > > > > > > to
>> > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > *community*
>> > > > > > > > > > > > > > > > > > > > > > to
>> > > > > > > > > > > > > > > > > > > > > > > > decide
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > whether
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > something goes
>> to
>> > > 2.7”.
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > пт, 28 сент.
>> 2018
>> > > г. в
>> > > > > >
>> > > > > > 11:11,
>> > > > > > > > > > Dmitriy
>> > > > > > > > > > > > > > Pavlov <
>> > > > > > > > > > > > > >
>
>
Re: Apache Ignite 2.7 release
Posted by Vladimir Ozerov <vo...@gridgain.com>.
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 <dp...@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 <st...@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 <ni...@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 <vo...@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 <st...@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.spb@gmail.com
> > >:
> > > > > >
> > > > > > > Hi Anton,
> > > > > > >
> > > > > > > I definitely agree it is a blocker.
> > > > > > >
> > > > > > > Sincerely,
> > > > > > > Dmitriy Pavlov
> > > > > > >
> > > > > > > вт, 2 окт. 2018 г. в 13:09, Anton Kalashnikov <
> kaa.dev@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" <
> dsetrakyan@apache.org
> > >:
> > > > > > > > > Thanks, got it.
> > > > > > > > >
> > > > > > > > > On Mon, Oct 1, 2018 at 1:14 PM Dmitriy Pavlov <
> > > > >
> > > > > dpavlov.spb@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 <
> > > > >
> > > > > vozerov@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 <
> > > > > > > >
> > > > > > > > dsetrakyan@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 <
> > > > > > > >
> > > > > > > > vozerov@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 <
> > > > > > > >
> > > > > > > > nizhikov@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
> > <
> > > > > > > > > > stkuzma@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.spb@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
> > > <
> > > > > > > > > > > > nizhikov@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
> > > > > > > <
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > daradurvs@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 <
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > dsetrakyan@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.spb@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 <
> > > > > > > > > > > > > > dmagda@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
> > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > nizhikov@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 <
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > dsetrakyan@apache.org
> > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > We agreed in the
> beginning
> > > of
> > > > >
> > > > > this
> > > > > > > > thread
> > > > > > > > > > > that
> > > > > > > > > > > > > > Service
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > changes
> > > > > > > > > > > > > > > > > > > > > > > > are not
> > > > > > > > > > > > > > > > > > > > > > > > > > going to make the
> release
> > > because
> > > > > >
> > > > > > the
> > > > > > > > > > > community
> > > > > > > > > > > > > > still did
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > approve
> > > > > > > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > > > > design. Nothing has
> > changed
> > > > >
> > > > > since.
> > > > > > I
> > > > > > > > have
> > > > > > > > > > not
> > > > > > > > > > > > > seen
> > > > > > > > > > > > > > any
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > design
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > discussions.
> > > > > > > > > > > > > > > > > > > > > > > > > > At this point, I have no
> > > > >
> > > > > confidence
> > > > > > > > that
> > > > > > > > > > the
> > > > > > > > > > > > > > Service Grid
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > changes
> > > > > > > > > > > > > > > > > > > > > > > will
> > > > > > > > > > > > > > > > > > > > > > > > make
> > > > > > > > > > > > > > > > > > > > > > > > > > it into the 2.8 release.
> > > The 2.7
> > > > > > > >
> > > > > > > > release
> > > > > > > > > > > seems
> > > > > > > > > > > > > out
> > > > > > > > > > > > > > of
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > question
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > altogether.
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > Also, Nikolay is a
> release
> > > > >
> > > > > manager.
> > > > > > > We
> > > > > > > > > > should
> > > > > > > > > > > > let
> > > > > > > > > > > > > > him
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > drive the
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > release. To
> > > > > > > > > > > > > > > > > > > > > > > > > > my knowledge, he is
> doing
> > a
> > > great
> > > > > >
> > > > > > job
> > > > > > > > and
> > > > > > > > > > the
> > > > > > > > > > > > > > release is
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > going
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > according to
> > > > > > > > > > > > > > > > > > > > > > > > > > the schedule he
> proposed.
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > D.
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at
> > > 4:31 AM
> > > > > > >
> > > > > > > Dmitriy
> > > > > > > > > > > Pavlov
> > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > Hi Dmitriy, Vladimir,
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > I suggest we stop this
> > > nonsense
> > > > > > >
> > > > > > > with
> > > > > > > > > > > release
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > dates-pushing
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > because
> > > > > > > > > > > > > > > > > > > > > > > of
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > some
> > > > > > > > > > > > > > > > > > > > > > > > > > > open question.
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > Just because you
> > > disagreed with
> > > > > >
> > > > > > any
> > > > > > > > > > > > > > include/exclude
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > something
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > into
> > > > > > > > > > > > > > > > > > > > > > > > scope,
> > > > > > > > > > > > > > > > > > > > > > > > > > > does not mean that
> whole
> > > > > >
> > > > > > community
> > > > > > > > > > > disagreed.
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > If folks will start a
> > > separate
> > > > > > > >
> > > > > > > > discussion
> > > > > > > > > > > > with
> > > > > > > > > > > > > > results
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > of the
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > review, I
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > see
> > > > > > > > > > > > > > > > > > > > > > > > > > > no reasons to reject
> > their
> > > > > > > >
> > > > > > > > contribution,
> > > > > > > > > > > even
> > > > > > > > > > > > > if
> > > > > > > > > > > > > > we
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > need
> > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > revisit
> > > > > > > > > > > > > > > > > > > > > > > > our
> > > > > > > > > > > > > > > > > > > > > > > > > > > agreements and wait
> for
> > a
> > > > >
> > > > > couple
> > > > > > of
> > > > > > > > days
> > > > > > > > > > > > more.
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > Am I missing some
> reason
> > > why
> > > > > >
> > > > > > dates
> > > > > > > > are so
> > > > > > > > > > > > > > fundamentally
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > important
> > > > > > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > > > you?
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > Sincerely,
> > > > > > > > > > > > > > > > > > > > > > > > > > > Dmitriy Pavlov
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в
> > > 12:20,
> > > > > > >
> > > > > > > Dmitriy
> > > > > > > > > > > > > Setrakyan <
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > dsetrakyan@apache.org>:
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > If services is not
> > > ready,
> > > > >
> > > > > which
> > > > > > > it
> > > > > > > > is
> > > > > > > > > > > not,
> > > > > > > > > > > > > > then we
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > should
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > include
> > > > > > > > > > > > > > > > > > > > > > > > them
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > into
> > > > > > > > > > > > > > > > > > > > > > > > > > > > the next release.
> > There
> > > is no
> > > > > > >
> > > > > > > need
> > > > > > > > to
> > > > > > > > > > > force
> > > > > > > > > > > > > > them into
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > 2.7.
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > I
> > > > > > > > > > > > > > > > > > > > > > > > suggest we
> > > > > > > > > > > > > > > > > > > > > > > > > > > > move according to
> the
> > > > >
> > > > > schedule
> > > > > > we
> > > > > > > > all
> > > > > > > > > > > > agreed
> > > > > > > > > > > > > > on.
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > D.
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018
> > at
> > > 1:22
> > > > >
> > > > > AM
> > > > > > > > Dmitriy
> > > > > > > > > > > > > Pavlov
> > > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > Yes, so correct
> > > statement
> > > > >
> > > > > is
> > > > > > > > > > "community
> > > > > > > > > > > > did
> > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > make
> > > > > > > > > > > > > > > > > > any
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > decisions
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > about
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > services not go to
> > > 2.7/
> > > > > > >
> > > > > > > services
> > > > > > > > are
> > > > > > > > > > > out
> > > > > > > > > > > > of
> > > > > > > > > > > > > > scope".
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > If so, please
> > forgive
> > > me my
> > > > > > > > > > confusion.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018
> > г. в
> > > > >
> > > > > 11:19,
> > > > > > > > > > Vladimir
> > > > > > > > > > > > > > Ozerov <
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Exactly. So
> > correct
> > > > > >
> > > > > > statement
> > > > > > > > is
> > > > > > > > > > “it
> > > > > > > > > > > is
> > > > > > > > > > > > > up
> > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > *community*
> > > > > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > > > decide
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > whether
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > something goes
> to
> > > 2.7”.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > пт, 28 сент.
> 2018
> > > г. в
> > > > > >
> > > > > > 11:11,
> > > > > > > > > > Dmitriy
> > > > > > > > > > > > > > Pavlov <
> > > > > > > > > > > > > >
Re: Apache Ignite 2.7 release
Posted by Dmitriy Pavlov <dp...@gmail.com>.
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 <st...@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 <ni...@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 <vo...@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 <st...@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.spb@gmail.com
> >:
> > > > >
> > > > > > Hi Anton,
> > > > > >
> > > > > > I definitely agree it is a blocker.
> > > > > >
> > > > > > Sincerely,
> > > > > > Dmitriy Pavlov
> > > > > >
> > > > > > вт, 2 окт. 2018 г. в 13:09, Anton Kalashnikov <kaa.dev@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" <dsetrakyan@apache.org
> >:
> > > > > > > > Thanks, got it.
> > > > > > > >
> > > > > > > > On Mon, Oct 1, 2018 at 1:14 PM Dmitriy Pavlov <
> > > >
> > > > dpavlov.spb@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 <
> > > >
> > > > vozerov@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 <
> > > > > > >
> > > > > > > dsetrakyan@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 <
> > > > > > >
> > > > > > > vozerov@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 <
> > > > > > >
> > > > > > > nizhikov@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
> <
> > > > > > > > > stkuzma@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.spb@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
> > <
> > > > > > > > > > > nizhikov@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
> > > > > > <
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > daradurvs@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 <
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > dsetrakyan@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.spb@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 <
> > > > > > > > > > > > > dmagda@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
> > > > > > > > > <
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > nizhikov@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 <
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > dsetrakyan@apache.org
> > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > We agreed in the beginning
> > of
> > > >
> > > > this
> > > > > > > thread
> > > > > > > > > > that
> > > > > > > > > > > > > Service
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > changes
> > > > > > > > > > > > > > > > > > > > > > > are not
> > > > > > > > > > > > > > > > > > > > > > > > > going to make the release
> > because
> > > > >
> > > > > the
> > > > > > > > > > community
> > > > > > > > > > > > > still did
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > approve
> > > > > > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > > > design. Nothing has
> changed
> > > >
> > > > since.
> > > > > I
> > > > > > > have
> > > > > > > > > not
> > > > > > > > > > > > seen
> > > > > > > > > > > > > any
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > design
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > discussions.
> > > > > > > > > > > > > > > > > > > > > > > > > At this point, I have no
> > > >
> > > > confidence
> > > > > > > that
> > > > > > > > > the
> > > > > > > > > > > > > Service Grid
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > changes
> > > > > > > > > > > > > > > > > > > > > > will
> > > > > > > > > > > > > > > > > > > > > > > make
> > > > > > > > > > > > > > > > > > > > > > > > > it into the 2.8 release.
> > The 2.7
> > > > > > >
> > > > > > > release
> > > > > > > > > > seems
> > > > > > > > > > > > out
> > > > > > > > > > > > > of
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > question
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > altogether.
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > Also, Nikolay is a release
> > > >
> > > > manager.
> > > > > > We
> > > > > > > > > should
> > > > > > > > > > > let
> > > > > > > > > > > > > him
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > drive the
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > release. To
> > > > > > > > > > > > > > > > > > > > > > > > > my knowledge, he is doing
> a
> > great
> > > > >
> > > > > job
> > > > > > > and
> > > > > > > > > the
> > > > > > > > > > > > > release is
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > going
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > according to
> > > > > > > > > > > > > > > > > > > > > > > > > the schedule he proposed.
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > D.
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at
> > 4:31 AM
> > > > > >
> > > > > > Dmitriy
> > > > > > > > > > Pavlov
> > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > Hi Dmitriy, Vladimir,
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > I suggest we stop this
> > nonsense
> > > > > >
> > > > > > with
> > > > > > > > > > release
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > dates-pushing
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > because
> > > > > > > > > > > > > > > > > > > > > > of
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > some
> > > > > > > > > > > > > > > > > > > > > > > > > > open question.
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > Just because you
> > disagreed with
> > > > >
> > > > > any
> > > > > > > > > > > > > include/exclude
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > something
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > into
> > > > > > > > > > > > > > > > > > > > > > > scope,
> > > > > > > > > > > > > > > > > > > > > > > > > > does not mean that whole
> > > > >
> > > > > community
> > > > > > > > > > disagreed.
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > If folks will start a
> > separate
> > > > > > >
> > > > > > > discussion
> > > > > > > > > > > with
> > > > > > > > > > > > > results
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > of the
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > review, I
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > see
> > > > > > > > > > > > > > > > > > > > > > > > > > no reasons to reject
> their
> > > > > > >
> > > > > > > contribution,
> > > > > > > > > > even
> > > > > > > > > > > > if
> > > > > > > > > > > > > we
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > need
> > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > revisit
> > > > > > > > > > > > > > > > > > > > > > > our
> > > > > > > > > > > > > > > > > > > > > > > > > > agreements and wait for
> a
> > > >
> > > > couple
> > > > > of
> > > > > > > days
> > > > > > > > > > > more.
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > Am I missing some reason
> > why
> > > > >
> > > > > dates
> > > > > > > are so
> > > > > > > > > > > > > fundamentally
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > important
> > > > > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > > you?
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > Sincerely,
> > > > > > > > > > > > > > > > > > > > > > > > > > Dmitriy Pavlov
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в
> > 12:20,
> > > > > >
> > > > > > Dmitriy
> > > > > > > > > > > > Setrakyan <
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > dsetrakyan@apache.org>:
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > If services is not
> > ready,
> > > >
> > > > which
> > > > > > it
> > > > > > > is
> > > > > > > > > > not,
> > > > > > > > > > > > > then we
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > should
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > include
> > > > > > > > > > > > > > > > > > > > > > > them
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > into
> > > > > > > > > > > > > > > > > > > > > > > > > > > the next release.
> There
> > is no
> > > > > >
> > > > > > need
> > > > > > > to
> > > > > > > > > > force
> > > > > > > > > > > > > them into
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > 2.7.
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > I
> > > > > > > > > > > > > > > > > > > > > > > suggest we
> > > > > > > > > > > > > > > > > > > > > > > > > > > move according to the
> > > >
> > > > schedule
> > > > > we
> > > > > > > all
> > > > > > > > > > > agreed
> > > > > > > > > > > > > on.
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > D.
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018
> at
> > 1:22
> > > >
> > > > AM
> > > > > > > Dmitriy
> > > > > > > > > > > > Pavlov
> > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > Yes, so correct
> > statement
> > > >
> > > > is
> > > > > > > > > "community
> > > > > > > > > > > did
> > > > > > > > > > > > > not
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > make
> > > > > > > > > > > > > > > > > any
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > decisions
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > about
> > > > > > > > > > > > > > > > > > > > > > > > > > > > services not go to
> > 2.7/
> > > > > >
> > > > > > services
> > > > > > > are
> > > > > > > > > > out
> > > > > > > > > > > of
> > > > > > > > > > > > > scope".
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > If so, please
> forgive
> > me my
> > > > > > > > > confusion.
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018
> г. в
> > > >
> > > > 11:19,
> > > > > > > > > Vladimir
> > > > > > > > > > > > > Ozerov <
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > Exactly. So
> correct
> > > > >
> > > > > statement
> > > > > > > is
> > > > > > > > > “it
> > > > > > > > > > is
> > > > > > > > > > > > up
> > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > *community*
> > > > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > > decide
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > whether
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > something goes to
> > 2.7”.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018
> > г. в
> > > > >
> > > > > 11:11,
> > > > > > > > > Dmitriy
> > > > > > > > > > > > > Pavlov <
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > No, it is up to
> > the
> > > > > > >
> > > > > > > community to
> > > > > > > > > > > > discuss
> > > > > > > > > > > > > after
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > their
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > review
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > results.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > пт, 28 сент.
> 2018
> > г. в
> > > > > >
> > > > > > 11:09,
> > > > > > > > > > > Vladimir
> > > > > > > > > > > > > Ozerov <
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Did I read
> your
> > words
> > > > > > >
> > > > > > > correctly
> > > > > > > > > > > that
> > > > > > > > > > > > > it is up
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > implementor
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > of a
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > single
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > feature to
> > decide
> > > > >
> > > > > whether
> > > > > > > > > release
> > > > > > > > > > > of
> > > > > > > > > > > > > all
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > other
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > features
> > > > > > > > > > > > > > > > > > > > > > and
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > fixes
> > > > > > > > > > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > delayed?
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > пт, 28 сент.
> > 2018 г.
> > > >
> > > > в
> > > > > > > 11:00,
> > > > > > > > > > > Dmitriy
> > > > > > > > > > > > > Pavlov
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > >
Re: Apache Ignite 2.7 release
Posted by Andrey Kuznetsov <st...@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 <ni...@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 <vo...@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 <st...@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 <dp...@gmail.com>:
> > > >
> > > > > Hi Anton,
> > > > >
> > > > > I definitely agree it is a blocker.
> > > > >
> > > > > Sincerely,
> > > > > Dmitriy Pavlov
> > > > >
> > > > > вт, 2 окт. 2018 г. в 13:09, Anton Kalashnikov <ka...@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" <ds...@apache.org>:
> > > > > > > Thanks, got it.
> > > > > > >
> > > > > > > On Mon, Oct 1, 2018 at 1:14 PM Dmitriy Pavlov <
> > >
> > > dpavlov.spb@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 <
> > >
> > > vozerov@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 <
> > > > > >
> > > > > > dsetrakyan@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 <
> > > > > >
> > > > > > vozerov@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 <
> > > > > >
> > > > > > nizhikov@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 <
> > > > > > > > stkuzma@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.spb@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
> <
> > > > > > > > > > nizhikov@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
> > > > > <
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > daradurvs@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 <
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > dsetrakyan@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.spb@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 <
> > > > > > > > > > > > dmagda@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
> > > > > > > > <
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > nizhikov@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 <
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > dsetrakyan@apache.org
> > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > We agreed in the beginning
> of
> > >
> > > this
> > > > > > thread
> > > > > > > > > that
> > > > > > > > > > > > Service
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > changes
> > > > > > > > > > > > > > > > > > > > > > are not
> > > > > > > > > > > > > > > > > > > > > > > > going to make the release
> because
> > > >
> > > > the
> > > > > > > > > community
> > > > > > > > > > > > still did
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > approve
> > > > > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > > design. Nothing has changed
> > >
> > > since.
> > > > I
> > > > > > have
> > > > > > > > not
> > > > > > > > > > > seen
> > > > > > > > > > > > any
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > design
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > discussions.
> > > > > > > > > > > > > > > > > > > > > > > > At this point, I have no
> > >
> > > confidence
> > > > > > that
> > > > > > > > the
> > > > > > > > > > > > Service Grid
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > changes
> > > > > > > > > > > > > > > > > > > > > will
> > > > > > > > > > > > > > > > > > > > > > make
> > > > > > > > > > > > > > > > > > > > > > > > it into the 2.8 release.
> The 2.7
> > > > > >
> > > > > > release
> > > > > > > > > seems
> > > > > > > > > > > out
> > > > > > > > > > > > of
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > question
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > altogether.
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > Also, Nikolay is a release
> > >
> > > manager.
> > > > > We
> > > > > > > > should
> > > > > > > > > > let
> > > > > > > > > > > > him
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > drive the
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > release. To
> > > > > > > > > > > > > > > > > > > > > > > > my knowledge, he is doing a
> great
> > > >
> > > > job
> > > > > > and
> > > > > > > > the
> > > > > > > > > > > > release is
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > going
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > according to
> > > > > > > > > > > > > > > > > > > > > > > > the schedule he proposed.
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > D.
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at
> 4:31 AM
> > > > >
> > > > > Dmitriy
> > > > > > > > > Pavlov
> > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > Hi Dmitriy, Vladimir,
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > I suggest we stop this
> nonsense
> > > > >
> > > > > with
> > > > > > > > > release
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > dates-pushing
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > because
> > > > > > > > > > > > > > > > > > > > > of
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > some
> > > > > > > > > > > > > > > > > > > > > > > > > open question.
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > Just because you
> disagreed with
> > > >
> > > > any
> > > > > > > > > > > > include/exclude
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > something
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > into
> > > > > > > > > > > > > > > > > > > > > > scope,
> > > > > > > > > > > > > > > > > > > > > > > > > does not mean that whole
> > > >
> > > > community
> > > > > > > > > disagreed.
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > If folks will start a
> separate
> > > > > >
> > > > > > discussion
> > > > > > > > > > with
> > > > > > > > > > > > results
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > of the
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > review, I
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > see
> > > > > > > > > > > > > > > > > > > > > > > > > no reasons to reject their
> > > > > >
> > > > > > contribution,
> > > > > > > > > even
> > > > > > > > > > > if
> > > > > > > > > > > > we
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > need
> > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > revisit
> > > > > > > > > > > > > > > > > > > > > > our
> > > > > > > > > > > > > > > > > > > > > > > > > agreements and wait for a
> > >
> > > couple
> > > > of
> > > > > > days
> > > > > > > > > > more.
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > Am I missing some reason
> why
> > > >
> > > > dates
> > > > > > are so
> > > > > > > > > > > > fundamentally
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > important
> > > > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > you?
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > Sincerely,
> > > > > > > > > > > > > > > > > > > > > > > > > Dmitriy Pavlov
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в
> 12:20,
> > > > >
> > > > > Dmitriy
> > > > > > > > > > > Setrakyan <
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > dsetrakyan@apache.org>:
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > If services is not
> ready,
> > >
> > > which
> > > > > it
> > > > > > is
> > > > > > > > > not,
> > > > > > > > > > > > then we
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > should
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > include
> > > > > > > > > > > > > > > > > > > > > > them
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > into
> > > > > > > > > > > > > > > > > > > > > > > > > > the next release. There
> is no
> > > > >
> > > > > need
> > > > > > to
> > > > > > > > > force
> > > > > > > > > > > > them into
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > 2.7.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > I
> > > > > > > > > > > > > > > > > > > > > > suggest we
> > > > > > > > > > > > > > > > > > > > > > > > > > move according to the
> > >
> > > schedule
> > > > we
> > > > > > all
> > > > > > > > > > agreed
> > > > > > > > > > > > on.
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > D.
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at
> 1:22
> > >
> > > AM
> > > > > > Dmitriy
> > > > > > > > > > > Pavlov
> > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > Yes, so correct
> statement
> > >
> > > is
> > > > > > > > "community
> > > > > > > > > > did
> > > > > > > > > > > > not
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > make
> > > > > > > > > > > > > > > > any
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > decisions
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > about
> > > > > > > > > > > > > > > > > > > > > > > > > > > services not go to
> 2.7/
> > > > >
> > > > > services
> > > > > > are
> > > > > > > > > out
> > > > > > > > > > of
> > > > > > > > > > > > scope".
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > If so, please forgive
> me my
> > > > > > > > confusion.
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в
> > >
> > > 11:19,
> > > > > > > > Vladimir
> > > > > > > > > > > > Ozerov <
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > Exactly. So correct
> > > >
> > > > statement
> > > > > > is
> > > > > > > > “it
> > > > > > > > > is
> > > > > > > > > > > up
> > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > *community*
> > > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > decide
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > whether
> > > > > > > > > > > > > > > > > > > > > > > > > > > > something goes to
> 2.7”.
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018
> г. в
> > > >
> > > > 11:11,
> > > > > > > > Dmitriy
> > > > > > > > > > > > Pavlov <
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > No, it is up to
> the
> > > > > >
> > > > > > community to
> > > > > > > > > > > discuss
> > > > > > > > > > > > after
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > their
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > review
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > results.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018
> г. в
> > > > >
> > > > > 11:09,
> > > > > > > > > > Vladimir
> > > > > > > > > > > > Ozerov <
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Did I read your
> words
> > > > > >
> > > > > > correctly
> > > > > > > > > > that
> > > > > > > > > > > > it is up
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > implementor
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > of a
> > > > > > > > > > > > > > > > > > > > > > > > > > > > single
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > feature to
> decide
> > > >
> > > > whether
> > > > > > > > release
> > > > > > > > > > of
> > > > > > > > > > > > all
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > other
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > features
> > > > > > > > > > > > > > > > > > > > > and
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > fixes
> > > > > > > > > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > delayed?
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > пт, 28 сент.
> 2018 г.
> > >
> > > в
> > > > > > 11:00,
> > > > > > > > > > Dmitriy
> > > > > > > > > > > > Pavlov
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > My point we
> can
> > >
> > > wait
> > > > a
> > > > > > bit
> > > > > > > > for
> > > > > > > > > > > > services
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > because
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 1 we are
> > >
> > > open-minded
> > > > > and
> > > > > > we
> > > > > > > > > > don't
> > > > > > > > > > > > have
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > outside
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > pressure
> > > > > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > do
> > > > > > > > > > > > > > > > > > > > > > > > > > > > release
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > in
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > October
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 2 and
> services it
> > >
> > > is
> > > > > not
> > > > > > > > some
> > > > > > > > > > new
> > > > > > > > > > > > feature,
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > which
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > suddenly
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > appeared
> > > > > > > > > > > > > > > > > > > > > > > > > > > > in
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > autumn, it is
> a
> > >
> > > well
> > > > > > known
> > > > > > > > and
> > > > > > > > > > > > important
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > feature.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > So it is up to
> > > > > >
> > > > > > Vyacheslav,
> > > > > > > > > Anton
> > > > > > > > > > > and
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Nikolay
> > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > decide.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Decisions can
> be
> > > > > >
> > > > > > services are
> > > > > > > > > not
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > ready/ready to
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > merge
> > > > > > > > > > > > > > > > > > > > > > only
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > master/ready
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > to merge to
> master
> > > >
> > > > and
> > > > > to
> > > > > > > > 2.7.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > пт, 28 сент.
> 2018
> > >
> > > г.
> > > > в
> > > > > > 10:46,
> > > > > > > > > > > > Vladimir
>
--
Best regards,
Andrey Kuznetsov.
Re: Apache Ignite 2.7 release
Posted by Nikolay Izhikov <ni...@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 <vo...@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 <st...@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 <dp...@gmail.com>:
> > >
> > > > Hi Anton,
> > > >
> > > > I definitely agree it is a blocker.
> > > >
> > > > Sincerely,
> > > > Dmitriy Pavlov
> > > >
> > > > вт, 2 окт. 2018 г. в 13:09, Anton Kalashnikov <ka...@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" <ds...@apache.org>:
> > > > > > Thanks, got it.
> > > > > >
> > > > > > On Mon, Oct 1, 2018 at 1:14 PM Dmitriy Pavlov <
> >
> > dpavlov.spb@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 <
> >
> > vozerov@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 <
> > > > >
> > > > > dsetrakyan@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 <
> > > > >
> > > > > vozerov@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 <
> > > > >
> > > > > nizhikov@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 <
> > > > > > > stkuzma@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.spb@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 <
> > > > > > > > > nizhikov@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
> > > > <
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > daradurvs@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 <
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > dsetrakyan@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.spb@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 <
> > > > > > > > > > > dmagda@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
> > > > > > > <
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > nizhikov@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 <
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > dsetrakyan@apache.org
> > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > We agreed in the beginning of
> >
> > this
> > > > > thread
> > > > > > > > that
> > > > > > > > > > > Service
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > changes
> > > > > > > > > > > > > > > > > > > > > are not
> > > > > > > > > > > > > > > > > > > > > > > going to make the release because
> > >
> > > the
> > > > > > > > community
> > > > > > > > > > > still did
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > approve
> > > > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > design. Nothing has changed
> >
> > since.
> > > I
> > > > > have
> > > > > > > not
> > > > > > > > > > seen
> > > > > > > > > > > any
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > design
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > discussions.
> > > > > > > > > > > > > > > > > > > > > > > At this point, I have no
> >
> > confidence
> > > > > that
> > > > > > > the
> > > > > > > > > > > Service Grid
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > changes
> > > > > > > > > > > > > > > > > > > > will
> > > > > > > > > > > > > > > > > > > > > make
> > > > > > > > > > > > > > > > > > > > > > > it into the 2.8 release. The 2.7
> > > > >
> > > > > release
> > > > > > > > seems
> > > > > > > > > > out
> > > > > > > > > > > of
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > question
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > altogether.
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > Also, Nikolay is a release
> >
> > manager.
> > > > We
> > > > > > > should
> > > > > > > > > let
> > > > > > > > > > > him
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > drive the
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > release. To
> > > > > > > > > > > > > > > > > > > > > > > my knowledge, he is doing a great
> > >
> > > job
> > > > > and
> > > > > > > the
> > > > > > > > > > > release is
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > going
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > according to
> > > > > > > > > > > > > > > > > > > > > > > the schedule he proposed.
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > D.
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at 4:31 AM
> > > >
> > > > Dmitriy
> > > > > > > > Pavlov
> > > > > > > > > <
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > Hi Dmitriy, Vladimir,
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > I suggest we stop this nonsense
> > > >
> > > > with
> > > > > > > > release
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > dates-pushing
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > because
> > > > > > > > > > > > > > > > > > > > of
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > some
> > > > > > > > > > > > > > > > > > > > > > > > open question.
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > Just because you disagreed with
> > >
> > > any
> > > > > > > > > > > include/exclude
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > something
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > into
> > > > > > > > > > > > > > > > > > > > > scope,
> > > > > > > > > > > > > > > > > > > > > > > > does not mean that whole
> > >
> > > community
> > > > > > > > disagreed.
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > If folks will start a separate
> > > > >
> > > > > discussion
> > > > > > > > > with
> > > > > > > > > > > results
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > of the
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > review, I
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > see
> > > > > > > > > > > > > > > > > > > > > > > > no reasons to reject their
> > > > >
> > > > > contribution,
> > > > > > > > even
> > > > > > > > > > if
> > > > > > > > > > > we
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > need
> > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > revisit
> > > > > > > > > > > > > > > > > > > > > our
> > > > > > > > > > > > > > > > > > > > > > > > agreements and wait for a
> >
> > couple
> > > of
> > > > > days
> > > > > > > > > more.
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > Am I missing some reason why
> > >
> > > dates
> > > > > are so
> > > > > > > > > > > fundamentally
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > important
> > > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > you?
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > Sincerely,
> > > > > > > > > > > > > > > > > > > > > > > > Dmitriy Pavlov
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 12:20,
> > > >
> > > > Dmitriy
> > > > > > > > > > Setrakyan <
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > dsetrakyan@apache.org>:
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > If services is not ready,
> >
> > which
> > > > it
> > > > > is
> > > > > > > > not,
> > > > > > > > > > > then we
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > should
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > include
> > > > > > > > > > > > > > > > > > > > > them
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > into
> > > > > > > > > > > > > > > > > > > > > > > > > the next release. There is no
> > > >
> > > > need
> > > > > to
> > > > > > > > force
> > > > > > > > > > > them into
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > 2.7.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > I
> > > > > > > > > > > > > > > > > > > > > suggest we
> > > > > > > > > > > > > > > > > > > > > > > > > move according to the
> >
> > schedule
> > > we
> > > > > all
> > > > > > > > > agreed
> > > > > > > > > > > on.
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > D.
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at 1:22
> >
> > AM
> > > > > Dmitriy
> > > > > > > > > > Pavlov
> > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > Yes, so correct statement
> >
> > is
> > > > > > > "community
> > > > > > > > > did
> > > > > > > > > > > not
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > make
> > > > > > > > > > > > > > > any
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > decisions
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > about
> > > > > > > > > > > > > > > > > > > > > > > > > > services not go to 2.7/
> > > >
> > > > services
> > > > > are
> > > > > > > > out
> > > > > > > > > of
> > > > > > > > > > > scope".
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > If so, please forgive me my
> > > > > > > confusion.
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в
> >
> > 11:19,
> > > > > > > Vladimir
> > > > > > > > > > > Ozerov <
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > Exactly. So correct
> > >
> > > statement
> > > > > is
> > > > > > > “it
> > > > > > > > is
> > > > > > > > > > up
> > > > > > > > > > > to
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > *community*
> > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > decide
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > whether
> > > > > > > > > > > > > > > > > > > > > > > > > > > something goes to 2.7”.
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в
> > >
> > > 11:11,
> > > > > > > Dmitriy
> > > > > > > > > > > Pavlov <
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > No, it is up to the
> > > > >
> > > > > community to
> > > > > > > > > > discuss
> > > > > > > > > > > after
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > their
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > review
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > results.
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в
> > > >
> > > > 11:09,
> > > > > > > > > Vladimir
> > > > > > > > > > > Ozerov <
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > Did I read your words
> > > > >
> > > > > correctly
> > > > > > > > > that
> > > > > > > > > > > it is up
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > implementor
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > of a
> > > > > > > > > > > > > > > > > > > > > > > > > > > single
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > feature to decide
> > >
> > > whether
> > > > > > > release
> > > > > > > > > of
> > > > > > > > > > > all
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > other
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > features
> > > > > > > > > > > > > > > > > > > > and
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > fixes
> > > > > > > > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > delayed?
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г.
> >
> > в
> > > > > 11:00,
> > > > > > > > > Dmitriy
> > > > > > > > > > > Pavlov
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > My point we can
> >
> > wait
> > > a
> > > > > bit
> > > > > > > for
> > > > > > > > > > > services
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > because
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 1 we are
> >
> > open-minded
> > > > and
> > > > > we
> > > > > > > > > don't
> > > > > > > > > > > have
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > outside
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > pressure
> > > > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > do
> > > > > > > > > > > > > > > > > > > > > > > > > > > release
> > > > > > > > > > > > > > > > > > > > > > > > > > > > in
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > October
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 2 and services it
> >
> > is
> > > > not
> > > > > > > some
> > > > > > > > > new
> > > > > > > > > > > feature,
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > which
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > suddenly
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > appeared
> > > > > > > > > > > > > > > > > > > > > > > > > > > in
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > autumn, it is a
> >
> > well
> > > > > known
> > > > > > > and
> > > > > > > > > > > important
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > feature.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > So it is up to
> > > > >
> > > > > Vyacheslav,
> > > > > > > > Anton
> > > > > > > > > > and
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Nikolay
> > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > decide.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Decisions can be
> > > > >
> > > > > services are
> > > > > > > > not
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > ready/ready to
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > merge
> > > > > > > > > > > > > > > > > > > > > only
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > master/ready
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > to merge to master
> > >
> > > and
> > > > to
> > > > > > > 2.7.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018
> >
> > г.
> > > в
> > > > > 10:46,
> > > > > > > > > > > Vladimir
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Ozerov <
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Dmitry,
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Community
> >
> > agreement
> > > > > was to
> > > > > > > > > > perform
> > > > > > > > > > > the
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > release
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > in
> > > > > > > > > > > > > > > > > > > > > October.
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > Of
> > > > > > > > > > > > > > > > > > > > > > > > > > > course
> > > > > > > > > > > > > > > > > > > > > > > > > > > > we
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > can
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > wait a bit for
> > > > >
> > > > > services.
> > > > > > > Then
> > > > > > > > > we
> > > > > > > > > > > wait a
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > bit for
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > other
> > > > > > > > > > > > > > > > > > > > > cool
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > features
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > ready
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > by that time,
> >
> > then
> > > > > again
> > > > > > > and
> > > > > > > > > > > again, and
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > release
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > will
> > > > > > > > > > > > > > > > > > > > > never
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > happen.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > And
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > while we are
> > >
> > > waiting
> > > > > for
> > > > > > > new
> > > > > > > > > > > features to
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > come,
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > already
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > completerd
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > features
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > cannot be used by
> > > > >
> > > > > anyone.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > This is why we
> >
> > have
> > > > an
> > > > > > > > > agreement
> > > > > > > > > > > that if
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > feature is
> > > > > > > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > ready,
> > > > > > > > > > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > should
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > moved to future
> > > > >
> > > > > release,
> > > > > > > > > instead
> > > > > > > > > > of
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > shifting
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > release.
> > > > > > > > > > > > > > > > > > > > > The
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > sole
> > > > > > > > > > > > > > > > > > > > > > > > > > > reason
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > have strict dates
> > > >
> > > > when
> > > > > > > > > decisions
> > > > > > > > > > > are made
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > to let
> > > > > > > > > > > > > > > > > > > > > release
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > happen.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Fri, Sep 28,
> > >
> > > 2018
> > > > at
> > > > > > > 2:22
> > > > > > > > AM
> > > > > > > > > > > Dmitriy
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Pavlov
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Vladimir, I'm
> >
> > not
> > > > > > > > searching
> > > > > > > > > > for
> > > > > > > > > > > enemy,
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > and
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > > > > > fighting
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > with
> > > > > > > > > > > > > > > > > > > > > > > > > > > you.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > I'm
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > happy about
> >
> > cases
> > > > > when we
> > > > > > > > are
> > > > > > > > > > > hurrying.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > We can't fix
> > >
> > > test,
> > > > > fill
> > > > > > > > > ticket
> > > > > > > > > > > details,
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > can't
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > wait
> > > > > > > > > > > > > > > > > > > > > for
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > contributions
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > finish their
> > >
> > > tasks.
> > > > > It
> > > > > > > is
> > > > > > > > > not
> > > > > > > > > > > best
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > idea
> > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > use
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > experience
> > > > > > > > > > > > > > > > > > > > > > > > > from
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > commercial
> > > > > > > > > > > > > > > > > > > > > > >
Re: Apache Ignite 2.7 release
Posted by Dmitriy Pavlov <dp...@gmail.com>.
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 <vo...@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 <st...@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 <dp...@gmail.com>:
> >
> > > Hi Anton,
> > >
> > > I definitely agree it is a blocker.
> > >
> > > Sincerely,
> > > Dmitriy Pavlov
> > >
> > > вт, 2 окт. 2018 г. в 13:09, Anton Kalashnikov <ka...@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" <ds...@apache.org>:
> > > > > Thanks, got it.
> > > > >
> > > > > On Mon, Oct 1, 2018 at 1:14 PM Dmitriy Pavlov <
> dpavlov.spb@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 <
> vozerov@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 <
> > > > dsetrakyan@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 <
> > > > vozerov@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 <
> > > > nizhikov@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 <
> > > > >> stkuzma@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.spb@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 <
> > > > >> > > nizhikov@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
> > > <
> > > > >> > > > > > > >
> > > > >> > > > > > > > daradurvs@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 <
> > > > >> > > > > > > > >
> > > > >> > > > > > > > > dsetrakyan@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.spb@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 <
> > > > >> > > > > dmagda@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
> > > > >> <
> > > > >> > > > > > > > > > >
> > > > >> > > > > > > > > > > nizhikov@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 <
> > > > >> > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > dsetrakyan@apache.org
> > > > >> > > > > > > > > > > > > > > :
> > > > >> > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > Dmitriy,
> > > > >> > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > We agreed in the beginning of
> this
> > > > thread
> > > > >> > that
> > > > >> > > > > Service
> > > > >> > > > > > > >
> > > > >> > > > > > > > Grid
> > > > >> > > > > > > > > > >
> > > > >> > > > > > > > > > > changes
> > > > >> > > > > > > > > > > > > > > are not
> > > > >> > > > > > > > > > > > > > > > > going to make the release because
> > the
> > > > >> > community
> > > > >> > > > > still did
> > > > >> > > > > > > > >
> > > > >> > > > > > > > > not
> > > > >> > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > approve
> > > > >> > > > > > > > > > > > > > > the
> > > > >> > > > > > > > > > > > > > > > > design. Nothing has changed
> since.
> > I
> > > > have
> > > > >> not
> > > > >> > > > seen
> > > > >> > > > > any
> > > > >> > > > > > > > >
> > > > >> > > > > > > > > design
> > > > >> > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > discussions.
> > > > >> > > > > > > > > > > > > > > > > At this point, I have no
> confidence
> > > > that
> > > > >> the
> > > > >> > > > > Service Grid
> > > > >> > > > > > > > > > >
> > > > >> > > > > > > > > > > changes
> > > > >> > > > > > > > > > > > > > will
> > > > >> > > > > > > > > > > > > > > make
> > > > >> > > > > > > > > > > > > > > > > it into the 2.8 release. The 2.7
> > > > release
> > > > >> > seems
> > > > >> > > > out
> > > > >> > > > > of
> > > > >> > > > > > > > >
> > > > >> > > > > > > > > question
> > > > >> > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > altogether.
> > > > >> > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > Also, Nikolay is a release
> manager.
> > > We
> > > > >> should
> > > > >> > > let
> > > > >> > > > > him
> > > > >> > > > > > > > >
> > > > >> > > > > > > > > drive the
> > > > >> > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > release. To
> > > > >> > > > > > > > > > > > > > > > > my knowledge, he is doing a great
> > job
> > > > and
> > > > >> the
> > > > >> > > > > release is
> > > > >> > > > > > > > >
> > > > >> > > > > > > > > going
> > > > >> > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > according to
> > > > >> > > > > > > > > > > > > > > > > the schedule he proposed.
> > > > >> > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > D.
> > > > >> > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at 4:31 AM
> > > Dmitriy
> > > > >> > Pavlov
> > > > >> > > <
> > > > >> > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > >> > > > > > > > > > > > > > > > > wrote:
> > > > >> > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > Hi Dmitriy, Vladimir,
> > > > >> > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > I suggest we stop this nonsense
> > > with
> > > > >> > release
> > > > >> > > > > > > > >
> > > > >> > > > > > > > > dates-pushing
> > > > >> > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > because
> > > > >> > > > > > > > > > > > > > of
> > > > >> > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > some
> > > > >> > > > > > > > > > > > > > > > > > open question.
> > > > >> > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > Just because you disagreed with
> > any
> > > > >> > > > > include/exclude
> > > > >> > > > > > > > >
> > > > >> > > > > > > > > something
> > > > >> > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > into
> > > > >> > > > > > > > > > > > > > > scope,
> > > > >> > > > > > > > > > > > > > > > > > does not mean that whole
> > community
> > > > >> > disagreed.
> > > > >> > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > If folks will start a separate
> > > > discussion
> > > > >> > > with
> > > > >> > > > > results
> > > > >> > > > > > > > >
> > > > >> > > > > > > > > of the
> > > > >> > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > review, I
> > > > >> > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > see
> > > > >> > > > > > > > > > > > > > > > > > no reasons to reject their
> > > > contribution,
> > > > >> > even
> > > > >> > > > if
> > > > >> > > > > we
> > > > >> > > > > > > >
> > > > >> > > > > > > > need
> > > > >> > > > > > > > > to
> > > > >> > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > revisit
> > > > >> > > > > > > > > > > > > > > our
> > > > >> > > > > > > > > > > > > > > > > > agreements and wait for a
> couple
> > of
> > > > days
> > > > >> > > more.
> > > > >> > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > Am I missing some reason why
> > dates
> > > > are so
> > > > >> > > > > fundamentally
> > > > >> > > > > > > > > > >
> > > > >> > > > > > > > > > > important
> > > > >> > > > > > > > > > > > > > to
> > > > >> > > > > > > > > > > > > > > you?
> > > > >> > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > Sincerely,
> > > > >> > > > > > > > > > > > > > > > > > Dmitriy Pavlov
> > > > >> > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 12:20,
> > > Dmitriy
> > > > >> > > > Setrakyan <
> > > > >> > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > dsetrakyan@apache.org>:
> > > > >> > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > > If services is not ready,
> which
> > > it
> > > > is
> > > > >> > not,
> > > > >> > > > > then we
> > > > >> > > > > > > > >
> > > > >> > > > > > > > > should
> > > > >> > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > include
> > > > >> > > > > > > > > > > > > > > them
> > > > >> > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > into
> > > > >> > > > > > > > > > > > > > > > > > > the next release. There is no
> > > need
> > > > to
> > > > >> > force
> > > > >> > > > > them into
> > > > >> > > > > > > > >
> > > > >> > > > > > > > > 2.7.
> > > > >> > > > > > > > > > >
> > > > >> > > > > > > > > > > I
> > > > >> > > > > > > > > > > > > > > suggest we
> > > > >> > > > > > > > > > > > > > > > > > > move according to the
> schedule
> > we
> > > > all
> > > > >> > > agreed
> > > > >> > > > > on.
> > > > >> > > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > > D.
> > > > >> > > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at 1:22
> AM
> > > > Dmitriy
> > > > >> > > > Pavlov
> > > > >> > > > > <
> > > > >> > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > >> > > > > > > > > > > > > > > > > > > wrote:
> > > > >> > > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > > > Yes, so correct statement
> is
> > > > >> "community
> > > > >> > > did
> > > > >> > > > > not
> > > > >> > > > > > > >
> > > > >> > > > > > > > make
> > > > >> > > > > > > > > any
> > > > >> > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > decisions
> > > > >> > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > about
> > > > >> > > > > > > > > > > > > > > > > > > > services not go to 2.7/
> > > services
> > > > are
> > > > >> > out
> > > > >> > > of
> > > > >> > > > > scope".
> > > > >> > > > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > > > If so, please forgive me my
> > > > >> confusion.
> > > > >> > > > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в
> 11:19,
> > > > >> Vladimir
> > > > >> > > > > Ozerov <
> > > > >> > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > >> > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > :
> > > > >> > > > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > > > > Exactly. So correct
> > statement
> > > > is
> > > > >> “it
> > > > >> > is
> > > > >> > > > up
> > > > >> > > > > to
> > > > >> > > > > > > > > > >
> > > > >> > > > > > > > > > > *community*
> > > > >> > > > > > > > > > > > > to
> > > > >> > > > > > > > > > > > > > > decide
> > > > >> > > > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > > > whether
> > > > >> > > > > > > > > > > > > > > > > > > > > something goes to 2.7”.
> > > > >> > > > > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в
> > 11:11,
> > > > >> Dmitriy
> > > > >> > > > > Pavlov <
> > > > >> > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > >> > > > > > > > > > > > > > > > > > > :
> > > > >> > > > > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > > > > > No, it is up to the
> > > > community to
> > > > >> > > > discuss
> > > > >> > > > > after
> > > > >> > > > > > > > >
> > > > >> > > > > > > > > their
> > > > >> > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > review
> > > > >> > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > results.
> > > > >> > > > > > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в
> > > 11:09,
> > > > >> > > Vladimir
> > > > >> > > > > Ozerov <
> > > > >> > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > >> > > > > > > > > > > > > > > > > > > > :
> > > > >> > > > > > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > > > > > > Dmitriy,
> > > > >> > > > > > > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > > > > > > Did I read your words
> > > > correctly
> > > > >> > > that
> > > > >> > > > > it is up
> > > > >> > > > > > > > >
> > > > >> > > > > > > > > to
> > > > >> > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > implementor
> > > > >> > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > of a
> > > > >> > > > > > > > > > > > > > > > > > > > > single
> > > > >> > > > > > > > > > > > > > > > > > > > > > > feature to decide
> > whether
> > > > >> release
> > > > >> > > of
> > > > >> > > > > all
> > > > >> > > > > > > >
> > > > >> > > > > > > > other
> > > > >> > > > > > > > > > >
> > > > >> > > > > > > > > > > features
> > > > >> > > > > > > > > > > > > > and
> > > > >> > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > fixes
> > > > >> > > > > > > > > > > > > > > > > > > to
> > > > >> > > > > > > > > > > > > > > > > > > > be
> > > > >> > > > > > > > > > > > > > > > > > > > > > > delayed?
> > > > >> > > > > > > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г.
> в
> > > > 11:00,
> > > > >> > > Dmitriy
> > > > >> > > > > Pavlov
> > > > >> > > > > > > >
> > > > >> > > > > > > > <
> > > > >> > > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > >> > > > > > > > > > > > > > > > > > > > > :
> > > > >> > > > > > > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > > > > > > > My point we can
> wait
> > a
> > > > bit
> > > > >> for
> > > > >> > > > > services
> > > > >> > > > > > > > >
> > > > >> > > > > > > > > because
> > > > >> > > > > > > > > > > > > > > > > > > > > > > > 1 we are
> open-minded
> > > and
> > > > we
> > > > >> > > don't
> > > > >> > > > > have
> > > > >> > > > > > > > >
> > > > >> > > > > > > > > outside
> > > > >> > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > pressure
> > > > >> > > > > > > > > > > > > > > to
> > > > >> > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > do
> > > > >> > > > > > > > > > > > > > > > > > > > > release
> > > > >> > > > > > > > > > > > > > > > > > > > > > in
> > > > >> > > > > > > > > > > > > > > > > > > > > > > > October
> > > > >> > > > > > > > > > > > > > > > > > > > > > > > 2 and services it
> is
> > > not
> > > > >> some
> > > > >> > > new
> > > > >> > > > > feature,
> > > > >> > > > > > > > >
> > > > >> > > > > > > > > which
> > > > >> > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > suddenly
> > > > >> > > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > > appeared
> > > > >> > > > > > > > > > > > > > > > > > > > > in
> > > > >> > > > > > > > > > > > > > > > > > > > > > > > autumn, it is a
> well
> > > > known
> > > > >> and
> > > > >> > > > > important
> > > > >> > > > > > > > >
> > > > >> > > > > > > > > feature.
> > > > >> > > > > > > > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > > > > > > > So it is up to
> > > > Vyacheslav,
> > > > >> > Anton
> > > > >> > > > and
> > > > >> > > > > > > >
> > > > >> > > > > > > > Nikolay
> > > > >> > > > > > > > > to
> > > > >> > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > decide.
> > > > >> > > > > > > > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > > > > > > > Decisions can be
> > > > services are
> > > > >> > not
> > > > >> > > > > > > > >
> > > > >> > > > > > > > > ready/ready to
> > > > >> > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > merge
> > > > >> > > > > > > > > > > > > > > only
> > > > >> > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > to
> > > > >> > > > > > > > > > > > > > > > > > > > > > > master/ready
> > > > >> > > > > > > > > > > > > > > > > > > > > > > > to merge to master
> > and
> > > to
> > > > >> 2.7.
> > > > >> > > > > > > > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018
> г.
> > в
> > > > 10:46,
> > > > >> > > > > Vladimir
> > > > >> > > > > > > > >
> > > > >> > > > > > > > > Ozerov <
> > > > >> > > > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > >> > > > > > > > > > > > > > > > > > > > > > :
> > > > >> > > > > > > > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > > > > > > > > Dmitry,
> > > > >> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > > > > > > > > Community
> agreement
> > > > was to
> > > > >> > > > perform
> > > > >> > > > > the
> > > > >> > > > > > > > >
> > > > >> > > > > > > > > release
> > > > >> > > > > > > > > > >
> > > > >> > > > > > > > > > > in
> > > > >> > > > > > > > > > > > > > > October.
> > > > >> > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > Of
> > > > >> > > > > > > > > > > > > > > > > > > > > course
> > > > >> > > > > > > > > > > > > > > > > > > > > > we
> > > > >> > > > > > > > > > > > > > > > > > > > > > > > can
> > > > >> > > > > > > > > > > > > > > > > > > > > > > > > wait a bit for
> > > > services.
> > > > >> Then
> > > > >> > > we
> > > > >> > > > > wait a
> > > > >> > > > > > > > >
> > > > >> > > > > > > > > bit for
> > > > >> > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > other
> > > > >> > > > > > > > > > > > > > > cool
> > > > >> > > > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > > > features
> > > > >> > > > > > > > > > > > > > > > > > > > > > > ready
> > > > >> > > > > > > > > > > > > > > > > > > > > > > > > by that time,
> then
> > > > again
> > > > >> and
> > > > >> > > > > again, and
> > > > >> > > > > > > > >
> > > > >> > > > > > > > > release
> > > > >> > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > will
> > > > >> > > > > > > > > > > > > > > never
> > > > >> > > > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > > > happen.
> > > > >> > > > > > > > > > > > > > > > > > > > > > And
> > > > >> > > > > > > > > > > > > > > > > > > > > > > > > while we are
> > waiting
> > > > for
> > > > >> new
> > > > >> > > > > features to
> > > > >> > > > > > > > >
> > > > >> > > > > > > > > come,
> > > > >> > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > already
> > > > >> > > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > > completerd
> > > > >> > > > > > > > > > > > > > > > > > > > > > > > features
> > > > >> > > > > > > > > > > > > > > > > > > > > > > > > cannot be used by
> > > > anyone.
> > > > >> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > > > > > > > > This is why we
> have
> > > an
> > > > >> > > agreement
> > > > >> > > > > that if
> > > > >> > > > > > > > > > >
> > > > >> > > > > > > > > > > feature is
> > > > >> > > > > > > > > > > > > > not
> > > > >> > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > ready,
> > > > >> > > > > > > > > > > > > > > > > > > it
> > > > >> > > > > > > > > > > > > > > > > > > > > > > should
> > > > >> > > > > > > > > > > > > > > > > > > > > > > > be
> > > > >> > > > > > > > > > > > > > > > > > > > > > > > > moved to future
> > > > release,
> > > > >> > > instead
> > > > >> > > > of
> > > > >> > > > > > > > >
> > > > >> > > > > > > > > shifting
> > > > >> > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > release.
> > > > >> > > > > > > > > > > > > > > The
> > > > >> > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > sole
> > > > >> > > > > > > > > > > > > > > > > > > > > reason
> > > > >> > > > > > > > > > > > > > > > > > > > > > > to
> > > > >> > > > > > > > > > > > > > > > > > > > > > > > > have strict dates
> > > when
> > > > >> > > decisions
> > > > >> > > > > are made
> > > > >> > > > > > > > >
> > > > >> > > > > > > > > is
> > > > >> > > > > > > > > > >
> > > > >> > > > > > > > > > > to let
> > > > >> > > > > > > > > > > > > > > release
> > > > >> > > > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > > > happen.
> > > > >> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > > > > > > > > On Fri, Sep 28,
> > 2018
> > > at
> > > > >> 2:22
> > > > >> > AM
> > > > >> > > > > Dmitriy
> > > > >> > > > > > > > >
> > > > >> > > > > > > > > Pavlov
> > > > >> > > > > > > > > > >
> > > > >> > > > > > > > > > > <
> > > > >> > > > > > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > >> > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > >> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > Vladimir, I'm
> not
> > > > >> > searching
> > > > >> > > > for
> > > > >> > > > > enemy,
> > > > >> > > > > > > > >
> > > > >> > > > > > > > > and
> > > > >> > > > > > > > > > >
> > > > >> > > > > > > > > > > not
> > > > >> > > > > > > > > > > > > > > fighting
> > > > >> > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > with
> > > > >> > > > > > > > > > > > > > > > > > > > > you.
> > > > >> > > > > > > > > > > > > > > > > > > > > > > I'm
> > > > >> > > > > > > > > > > > > > > > > > > > > > > > > not
> > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > happy about
> cases
> > > > when we
> > > > >> > are
> > > > >> > > > > hurrying.
> > > > >> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > We can't fix
> > test,
> > > > fill
> > > > >> > > ticket
> > > > >> > > > > details,
> > > > >> > > > > > > > >
> > > > >> > > > > > > > > can't
> > > > >> > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > wait
> > > > >> > > > > > > > > > > > > > > for
> > > > >> > > > > > > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > > > > > > contributions
> > > > >> > > > > > > > > > > > > > > > > > > > > > > to
> > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > finish their
> > tasks.
> > > > It
> > > > >> is
> > > > >> > > not
> > > > >> > > > > best
> > > > >> > > > > > > >
> > > > >> > > > > > > > idea
> > > > >> > > > > > > > > to
> > > > >> > > > > > > > > > >
> > > > >> > > > > > > > > > > use
> > > > >> > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > experience
> > > > >> > > > > > > > > > > > > > > > > > > from
> > > > >> > > > > > > > > > > > > > > > > > > > > > > > > commercial
> > > > >> > > > > > > > > > > > > > > > >
Re: Apache Ignite 2.7 release
Posted by Vladimir Ozerov <vo...@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 <st...@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 <dp...@gmail.com>:
>
> > Hi Anton,
> >
> > I definitely agree it is a blocker.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > вт, 2 окт. 2018 г. в 13:09, Anton Kalashnikov <ka...@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" <ds...@apache.org>:
> > > > Thanks, got it.
> > > >
> > > > On Mon, Oct 1, 2018 at 1:14 PM Dmitriy Pavlov <dpavlov.spb@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 <vozerov@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 <
> > > dsetrakyan@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 <
> > > vozerov@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 <
> > > nizhikov@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 <
> > > >> stkuzma@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.spb@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 <
> > > >> > > nizhikov@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
> > <
> > > >> > > > > > > >
> > > >> > > > > > > > daradurvs@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 <
> > > >> > > > > > > > >
> > > >> > > > > > > > > dsetrakyan@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.spb@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 <
> > > >> > > > > dmagda@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
> > > >> <
> > > >> > > > > > > > > > >
> > > >> > > > > > > > > > > nizhikov@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 <
> > > >> > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > dsetrakyan@apache.org
> > > >> > > > > > > > > > > > > > > :
> > > >> > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > Dmitriy,
> > > >> > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > We agreed in the beginning of this
> > > thread
> > > >> > that
> > > >> > > > > Service
> > > >> > > > > > > >
> > > >> > > > > > > > Grid
> > > >> > > > > > > > > > >
> > > >> > > > > > > > > > > changes
> > > >> > > > > > > > > > > > > > > are not
> > > >> > > > > > > > > > > > > > > > > going to make the release because
> the
> > > >> > community
> > > >> > > > > still did
> > > >> > > > > > > > >
> > > >> > > > > > > > > not
> > > >> > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > approve
> > > >> > > > > > > > > > > > > > > the
> > > >> > > > > > > > > > > > > > > > > design. Nothing has changed since.
> I
> > > have
> > > >> not
> > > >> > > > seen
> > > >> > > > > any
> > > >> > > > > > > > >
> > > >> > > > > > > > > design
> > > >> > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > discussions.
> > > >> > > > > > > > > > > > > > > > > At this point, I have no confidence
> > > that
> > > >> the
> > > >> > > > > Service Grid
> > > >> > > > > > > > > > >
> > > >> > > > > > > > > > > changes
> > > >> > > > > > > > > > > > > > will
> > > >> > > > > > > > > > > > > > > make
> > > >> > > > > > > > > > > > > > > > > it into the 2.8 release. The 2.7
> > > release
> > > >> > seems
> > > >> > > > out
> > > >> > > > > of
> > > >> > > > > > > > >
> > > >> > > > > > > > > question
> > > >> > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > altogether.
> > > >> > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > Also, Nikolay is a release manager.
> > We
> > > >> should
> > > >> > > let
> > > >> > > > > him
> > > >> > > > > > > > >
> > > >> > > > > > > > > drive the
> > > >> > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > release. To
> > > >> > > > > > > > > > > > > > > > > my knowledge, he is doing a great
> job
> > > and
> > > >> the
> > > >> > > > > release is
> > > >> > > > > > > > >
> > > >> > > > > > > > > going
> > > >> > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > according to
> > > >> > > > > > > > > > > > > > > > > the schedule he proposed.
> > > >> > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > D.
> > > >> > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at 4:31 AM
> > Dmitriy
> > > >> > Pavlov
> > > >> > > <
> > > >> > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > >> > > > > > > > > > > > > > > > > wrote:
> > > >> > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > Hi Dmitriy, Vladimir,
> > > >> > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > I suggest we stop this nonsense
> > with
> > > >> > release
> > > >> > > > > > > > >
> > > >> > > > > > > > > dates-pushing
> > > >> > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > because
> > > >> > > > > > > > > > > > > > of
> > > >> > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > some
> > > >> > > > > > > > > > > > > > > > > > open question.
> > > >> > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > Just because you disagreed with
> any
> > > >> > > > > include/exclude
> > > >> > > > > > > > >
> > > >> > > > > > > > > something
> > > >> > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > into
> > > >> > > > > > > > > > > > > > > scope,
> > > >> > > > > > > > > > > > > > > > > > does not mean that whole
> community
> > > >> > disagreed.
> > > >> > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > If folks will start a separate
> > > discussion
> > > >> > > with
> > > >> > > > > results
> > > >> > > > > > > > >
> > > >> > > > > > > > > of the
> > > >> > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > review, I
> > > >> > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > see
> > > >> > > > > > > > > > > > > > > > > > no reasons to reject their
> > > contribution,
> > > >> > even
> > > >> > > > if
> > > >> > > > > we
> > > >> > > > > > > >
> > > >> > > > > > > > need
> > > >> > > > > > > > > to
> > > >> > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > revisit
> > > >> > > > > > > > > > > > > > > our
> > > >> > > > > > > > > > > > > > > > > > agreements and wait for a couple
> of
> > > days
> > > >> > > more.
> > > >> > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > Am I missing some reason why
> dates
> > > are so
> > > >> > > > > fundamentally
> > > >> > > > > > > > > > >
> > > >> > > > > > > > > > > important
> > > >> > > > > > > > > > > > > > to
> > > >> > > > > > > > > > > > > > > you?
> > > >> > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > Sincerely,
> > > >> > > > > > > > > > > > > > > > > > Dmitriy Pavlov
> > > >> > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 12:20,
> > Dmitriy
> > > >> > > > Setrakyan <
> > > >> > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > dsetrakyan@apache.org>:
> > > >> > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > If services is not ready, which
> > it
> > > is
> > > >> > not,
> > > >> > > > > then we
> > > >> > > > > > > > >
> > > >> > > > > > > > > should
> > > >> > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > include
> > > >> > > > > > > > > > > > > > > them
> > > >> > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > into
> > > >> > > > > > > > > > > > > > > > > > > the next release. There is no
> > need
> > > to
> > > >> > force
> > > >> > > > > them into
> > > >> > > > > > > > >
> > > >> > > > > > > > > 2.7.
> > > >> > > > > > > > > > >
> > > >> > > > > > > > > > > I
> > > >> > > > > > > > > > > > > > > suggest we
> > > >> > > > > > > > > > > > > > > > > > > move according to the schedule
> we
> > > all
> > > >> > > agreed
> > > >> > > > > on.
> > > >> > > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > D.
> > > >> > > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at 1:22 AM
> > > Dmitriy
> > > >> > > > Pavlov
> > > >> > > > > <
> > > >> > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > >> > > > > > > > > > > > > > > > > > > wrote:
> > > >> > > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > > Yes, so correct statement is
> > > >> "community
> > > >> > > did
> > > >> > > > > not
> > > >> > > > > > > >
> > > >> > > > > > > > make
> > > >> > > > > > > > > any
> > > >> > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > decisions
> > > >> > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > about
> > > >> > > > > > > > > > > > > > > > > > > > services not go to 2.7/
> > services
> > > are
> > > >> > out
> > > >> > > of
> > > >> > > > > scope".
> > > >> > > > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > > If so, please forgive me my
> > > >> confusion.
> > > >> > > > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:19,
> > > >> Vladimir
> > > >> > > > > Ozerov <
> > > >> > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > vozerov@gridgain.com
> > > >> > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > :
> > > >> > > > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > > > Exactly. So correct
> statement
> > > is
> > > >> “it
> > > >> > is
> > > >> > > > up
> > > >> > > > > to
> > > >> > > > > > > > > > >
> > > >> > > > > > > > > > > *community*
> > > >> > > > > > > > > > > > > to
> > > >> > > > > > > > > > > > > > > decide
> > > >> > > > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > > whether
> > > >> > > > > > > > > > > > > > > > > > > > > something goes to 2.7”.
> > > >> > > > > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в
> 11:11,
> > > >> Dmitriy
> > > >> > > > > Pavlov <
> > > >> > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > >> > > > > > > > > > > > > > > > > > > :
> > > >> > > > > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > > > > No, it is up to the
> > > community to
> > > >> > > > discuss
> > > >> > > > > after
> > > >> > > > > > > > >
> > > >> > > > > > > > > their
> > > >> > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > review
> > > >> > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > results.
> > > >> > > > > > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в
> > 11:09,
> > > >> > > Vladimir
> > > >> > > > > Ozerov <
> > > >> > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > >> > > > > > > > > > > > > > > > > > > > :
> > > >> > > > > > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > > > > > Dmitriy,
> > > >> > > > > > > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > > > > > Did I read your words
> > > correctly
> > > >> > > that
> > > >> > > > > it is up
> > > >> > > > > > > > >
> > > >> > > > > > > > > to
> > > >> > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > implementor
> > > >> > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > of a
> > > >> > > > > > > > > > > > > > > > > > > > > single
> > > >> > > > > > > > > > > > > > > > > > > > > > > feature to decide
> whether
> > > >> release
> > > >> > > of
> > > >> > > > > all
> > > >> > > > > > > >
> > > >> > > > > > > > other
> > > >> > > > > > > > > > >
> > > >> > > > > > > > > > > features
> > > >> > > > > > > > > > > > > > and
> > > >> > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > fixes
> > > >> > > > > > > > > > > > > > > > > > > to
> > > >> > > > > > > > > > > > > > > > > > > > be
> > > >> > > > > > > > > > > > > > > > > > > > > > > delayed?
> > > >> > > > > > > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в
> > > 11:00,
> > > >> > > Dmitriy
> > > >> > > > > Pavlov
> > > >> > > > > > > >
> > > >> > > > > > > > <
> > > >> > > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > >> > > > > > > > > > > > > > > > > > > > > :
> > > >> > > > > > > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > > > > > > My point we can wait
> a
> > > bit
> > > >> for
> > > >> > > > > services
> > > >> > > > > > > > >
> > > >> > > > > > > > > because
> > > >> > > > > > > > > > > > > > > > > > > > > > > > 1 we are open-minded
> > and
> > > we
> > > >> > > don't
> > > >> > > > > have
> > > >> > > > > > > > >
> > > >> > > > > > > > > outside
> > > >> > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > pressure
> > > >> > > > > > > > > > > > > > > to
> > > >> > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > do
> > > >> > > > > > > > > > > > > > > > > > > > > release
> > > >> > > > > > > > > > > > > > > > > > > > > > in
> > > >> > > > > > > > > > > > > > > > > > > > > > > > October
> > > >> > > > > > > > > > > > > > > > > > > > > > > > 2 and services it is
> > not
> > > >> some
> > > >> > > new
> > > >> > > > > feature,
> > > >> > > > > > > > >
> > > >> > > > > > > > > which
> > > >> > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > suddenly
> > > >> > > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > appeared
> > > >> > > > > > > > > > > > > > > > > > > > > in
> > > >> > > > > > > > > > > > > > > > > > > > > > > > autumn, it is a well
> > > known
> > > >> and
> > > >> > > > > important
> > > >> > > > > > > > >
> > > >> > > > > > > > > feature.
> > > >> > > > > > > > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > > > > > > So it is up to
> > > Vyacheslav,
> > > >> > Anton
> > > >> > > > and
> > > >> > > > > > > >
> > > >> > > > > > > > Nikolay
> > > >> > > > > > > > > to
> > > >> > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > decide.
> > > >> > > > > > > > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > > > > > > Decisions can be
> > > services are
> > > >> > not
> > > >> > > > > > > > >
> > > >> > > > > > > > > ready/ready to
> > > >> > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > merge
> > > >> > > > > > > > > > > > > > > only
> > > >> > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > to
> > > >> > > > > > > > > > > > > > > > > > > > > > > master/ready
> > > >> > > > > > > > > > > > > > > > > > > > > > > > to merge to master
> and
> > to
> > > >> 2.7.
> > > >> > > > > > > > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г.
> в
> > > 10:46,
> > > >> > > > > Vladimir
> > > >> > > > > > > > >
> > > >> > > > > > > > > Ozerov <
> > > >> > > > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > >> > > > > > > > > > > > > > > > > > > > > > :
> > > >> > > > > > > > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > > > > > > > Dmitry,
> > > >> > > > > > > > > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > > > > > > > Community agreement
> > > was to
> > > >> > > > perform
> > > >> > > > > the
> > > >> > > > > > > > >
> > > >> > > > > > > > > release
> > > >> > > > > > > > > > >
> > > >> > > > > > > > > > > in
> > > >> > > > > > > > > > > > > > > October.
> > > >> > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > Of
> > > >> > > > > > > > > > > > > > > > > > > > > course
> > > >> > > > > > > > > > > > > > > > > > > > > > we
> > > >> > > > > > > > > > > > > > > > > > > > > > > > can
> > > >> > > > > > > > > > > > > > > > > > > > > > > > > wait a bit for
> > > services.
> > > >> Then
> > > >> > > we
> > > >> > > > > wait a
> > > >> > > > > > > > >
> > > >> > > > > > > > > bit for
> > > >> > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > other
> > > >> > > > > > > > > > > > > > > cool
> > > >> > > > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > > features
> > > >> > > > > > > > > > > > > > > > > > > > > > > ready
> > > >> > > > > > > > > > > > > > > > > > > > > > > > > by that time, then
> > > again
> > > >> and
> > > >> > > > > again, and
> > > >> > > > > > > > >
> > > >> > > > > > > > > release
> > > >> > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > will
> > > >> > > > > > > > > > > > > > > never
> > > >> > > > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > > happen.
> > > >> > > > > > > > > > > > > > > > > > > > > > And
> > > >> > > > > > > > > > > > > > > > > > > > > > > > > while we are
> waiting
> > > for
> > > >> new
> > > >> > > > > features to
> > > >> > > > > > > > >
> > > >> > > > > > > > > come,
> > > >> > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > already
> > > >> > > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > completerd
> > > >> > > > > > > > > > > > > > > > > > > > > > > > features
> > > >> > > > > > > > > > > > > > > > > > > > > > > > > cannot be used by
> > > anyone.
> > > >> > > > > > > > > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > > > > > > > This is why we have
> > an
> > > >> > > agreement
> > > >> > > > > that if
> > > >> > > > > > > > > > >
> > > >> > > > > > > > > > > feature is
> > > >> > > > > > > > > > > > > > not
> > > >> > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > ready,
> > > >> > > > > > > > > > > > > > > > > > > it
> > > >> > > > > > > > > > > > > > > > > > > > > > > should
> > > >> > > > > > > > > > > > > > > > > > > > > > > > be
> > > >> > > > > > > > > > > > > > > > > > > > > > > > > moved to future
> > > release,
> > > >> > > instead
> > > >> > > > of
> > > >> > > > > > > > >
> > > >> > > > > > > > > shifting
> > > >> > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > release.
> > > >> > > > > > > > > > > > > > > The
> > > >> > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > sole
> > > >> > > > > > > > > > > > > > > > > > > > > reason
> > > >> > > > > > > > > > > > > > > > > > > > > > > to
> > > >> > > > > > > > > > > > > > > > > > > > > > > > > have strict dates
> > when
> > > >> > > decisions
> > > >> > > > > are made
> > > >> > > > > > > > >
> > > >> > > > > > > > > is
> > > >> > > > > > > > > > >
> > > >> > > > > > > > > > > to let
> > > >> > > > > > > > > > > > > > > release
> > > >> > > > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > > happen.
> > > >> > > > > > > > > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > > > > > > > On Fri, Sep 28,
> 2018
> > at
> > > >> 2:22
> > > >> > AM
> > > >> > > > > Dmitriy
> > > >> > > > > > > > >
> > > >> > > > > > > > > Pavlov
> > > >> > > > > > > > > > >
> > > >> > > > > > > > > > > <
> > > >> > > > > > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > >> > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > >> > > > > > > > > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > > > > > > > > Vladimir, I'm not
> > > >> > searching
> > > >> > > > for
> > > >> > > > > enemy,
> > > >> > > > > > > > >
> > > >> > > > > > > > > and
> > > >> > > > > > > > > > >
> > > >> > > > > > > > > > > not
> > > >> > > > > > > > > > > > > > > fighting
> > > >> > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > with
> > > >> > > > > > > > > > > > > > > > > > > > > you.
> > > >> > > > > > > > > > > > > > > > > > > > > > > I'm
> > > >> > > > > > > > > > > > > > > > > > > > > > > > > not
> > > >> > > > > > > > > > > > > > > > > > > > > > > > > > happy about cases
> > > when we
> > > >> > are
> > > >> > > > > hurrying.
> > > >> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > > > > > > > > We can't fix
> test,
> > > fill
> > > >> > > ticket
> > > >> > > > > details,
> > > >> > > > > > > > >
> > > >> > > > > > > > > can't
> > > >> > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > wait
> > > >> > > > > > > > > > > > > > > for
> > > >> > > > > > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > > > > contributions
> > > >> > > > > > > > > > > > > > > > > > > > > > > to
> > > >> > > > > > > > > > > > > > > > > > > > > > > > > > finish their
> tasks.
> > > It
> > > >> is
> > > >> > > not
> > > >> > > > > best
> > > >> > > > > > > >
> > > >> > > > > > > > idea
> > > >> > > > > > > > > to
> > > >> > > > > > > > > > >
> > > >> > > > > > > > > > > use
> > > >> > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > experience
> > > >> > > > > > > > > > > > > > > > > > > from
> > > >> > > > > > > > > > > > > > > > > > > > > > > > > commercial
> > > >> > > > > > > > > > > > > > > > > > > > > > > > > > companies in open
> > > source.
> > > >> > Are
> > > >> > > > > there any
> > > >> > > > > > > > > > >
> > > >> > > > > > > > > > > pressure
> > > >> > > > > > > > > > > > > > > outside
> > > >> > > > > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > > > community?
> > > >> > > > > > > > > > > > > > > > > > > > > > > Did
> > > >> > > > > > > > > > > > > > > > > > > > > > > > > > someone promised
> > > rest of
> > > >> > > > > features to be
> > > >> > > > > > > > > > >
> > > >> > > > > > > > > > > released
> > > >> > > > > > > > > > > > > at
> > > >> > > > > > > > > > > > > > > 30
> > > >> > > > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > > September?
> > > >> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > > > > > > > > Let's remember
> > > principle
> > > >> > > > > do-orcracy,
> > > >> > > > > > > > >
> > > >> > > > > > > > > power of
> > > >> > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > those
> > > >> > > > > > > > > > > > > > > who
> > > >> > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > do.
> > > >> > > > > > > > > > > > > > > > > > > If
> > > >> > > > > > > > > > > > > > > > > > > > > > > > contribor
> > > >> > > > > > > > > > > > > > > > > > > > > > > > > > does change and
> > > reviewer
> > > >> > does
> > > >> > > > > review,
> > > >> > > > > > > > >
> > > >> > > > > > > > > let's
> > > >> > > > > > > > > > >
> > > >> > > > > > > > > > > give
> > > >> > > > > > > > > > > > > > > right of
> > > >> > > > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > > making
> > > >> > > > > > > > > > > > > > > > > > > > > > > > decision
> > > >> > > > > > > > > > > > > > > > > > > > > > > > > > to them, but not
> to
> > > some
> > > >> > > closed
> > > >> > > > > club of
> > > >> > > > > > > > > > >
> > > >> > > > > > > > > > > people
> > > >> > > > > > > > > > > > > who
> > > >> > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > privately
> > > >> > > > > > > > > > > > > > > > > > > > > > discuss
> > > >> > > > > > > > > > > > > > > > > > > > > > > > > > something.
> > > >> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > > > > > > > > Sincerely
> > > >> > > > > > > > > > > > > > > > > > > > > > > > > > Dmitriy Pavlov
> > > >> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018
> > г.,
> > > >> 23:42
> > > >> > > > > Vyacheslav
> > > >> > > > > > > > > > >
> > > >> > > > > > > > > > > Daradur <
> > > >> > > > > > > > > > > > > > > > > > > > > >
> > > >> > > > > > > > > > > > > > > > > > > > >
Re: Apache Ignite 2.7 release
Posted by Andrey Kuznetsov <st...@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 <dp...@gmail.com>:
> Hi Anton,
>
> I definitely agree it is a blocker.
>
> Sincerely,
> Dmitriy Pavlov
>
> вт, 2 окт. 2018 г. в 13:09, Anton Kalashnikov <ka...@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" <ds...@apache.org>:
> > > Thanks, got it.
> > >
> > > On Mon, Oct 1, 2018 at 1:14 PM Dmitriy Pavlov <dp...@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 <vo...@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 <
> > dsetrakyan@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 <
> > vozerov@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 <
> > nizhikov@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 <
> > >> stkuzma@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.spb@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 <
> > >> > > nizhikov@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
> <
> > >> > > > > > > >
> > >> > > > > > > > daradurvs@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 <
> > >> > > > > > > > >
> > >> > > > > > > > > dsetrakyan@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.spb@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 <
> > >> > > > > dmagda@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
> > >> <
> > >> > > > > > > > > > >
> > >> > > > > > > > > > > nizhikov@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 <
> > >> > > > > > > > > > > > >
> > >> > > > > > > > > > > > > dsetrakyan@apache.org
> > >> > > > > > > > > > > > > > > :
> > >> > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > Dmitriy,
> > >> > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > We agreed in the beginning of this
> > thread
> > >> > that
> > >> > > > > Service
> > >> > > > > > > >
> > >> > > > > > > > Grid
> > >> > > > > > > > > > >
> > >> > > > > > > > > > > changes
> > >> > > > > > > > > > > > > > > are not
> > >> > > > > > > > > > > > > > > > > going to make the release because the
> > >> > community
> > >> > > > > still did
> > >> > > > > > > > >
> > >> > > > > > > > > not
> > >> > > > > > > > > > > > >
> > >> > > > > > > > > > > > > approve
> > >> > > > > > > > > > > > > > > the
> > >> > > > > > > > > > > > > > > > > design. Nothing has changed since. I
> > have
> > >> not
> > >> > > > seen
> > >> > > > > any
> > >> > > > > > > > >
> > >> > > > > > > > > design
> > >> > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > discussions.
> > >> > > > > > > > > > > > > > > > > At this point, I have no confidence
> > that
> > >> the
> > >> > > > > Service Grid
> > >> > > > > > > > > > >
> > >> > > > > > > > > > > changes
> > >> > > > > > > > > > > > > > will
> > >> > > > > > > > > > > > > > > make
> > >> > > > > > > > > > > > > > > > > it into the 2.8 release. The 2.7
> > release
> > >> > seems
> > >> > > > out
> > >> > > > > of
> > >> > > > > > > > >
> > >> > > > > > > > > question
> > >> > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > altogether.
> > >> > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > Also, Nikolay is a release manager.
> We
> > >> should
> > >> > > let
> > >> > > > > him
> > >> > > > > > > > >
> > >> > > > > > > > > drive the
> > >> > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > release. To
> > >> > > > > > > > > > > > > > > > > my knowledge, he is doing a great job
> > and
> > >> the
> > >> > > > > release is
> > >> > > > > > > > >
> > >> > > > > > > > > going
> > >> > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > according to
> > >> > > > > > > > > > > > > > > > > the schedule he proposed.
> > >> > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > D.
> > >> > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at 4:31 AM
> Dmitriy
> > >> > Pavlov
> > >> > > <
> > >> > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > >> > > > > > > > > > > > > > > > > wrote:
> > >> > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > Hi Dmitriy, Vladimir,
> > >> > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > I suggest we stop this nonsense
> with
> > >> > release
> > >> > > > > > > > >
> > >> > > > > > > > > dates-pushing
> > >> > > > > > > > > > > > >
> > >> > > > > > > > > > > > > because
> > >> > > > > > > > > > > > > > of
> > >> > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > some
> > >> > > > > > > > > > > > > > > > > > open question.
> > >> > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > Just because you disagreed with any
> > >> > > > > include/exclude
> > >> > > > > > > > >
> > >> > > > > > > > > something
> > >> > > > > > > > > > > > >
> > >> > > > > > > > > > > > > into
> > >> > > > > > > > > > > > > > > scope,
> > >> > > > > > > > > > > > > > > > > > does not mean that whole community
> > >> > disagreed.
> > >> > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > If folks will start a separate
> > discussion
> > >> > > with
> > >> > > > > results
> > >> > > > > > > > >
> > >> > > > > > > > > of the
> > >> > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > review, I
> > >> > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > see
> > >> > > > > > > > > > > > > > > > > > no reasons to reject their
> > contribution,
> > >> > even
> > >> > > > if
> > >> > > > > we
> > >> > > > > > > >
> > >> > > > > > > > need
> > >> > > > > > > > > to
> > >> > > > > > > > > > > > >
> > >> > > > > > > > > > > > > revisit
> > >> > > > > > > > > > > > > > > our
> > >> > > > > > > > > > > > > > > > > > agreements and wait for a couple of
> > days
> > >> > > more.
> > >> > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > Am I missing some reason why dates
> > are so
> > >> > > > > fundamentally
> > >> > > > > > > > > > >
> > >> > > > > > > > > > > important
> > >> > > > > > > > > > > > > > to
> > >> > > > > > > > > > > > > > > you?
> > >> > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > Sincerely,
> > >> > > > > > > > > > > > > > > > > > Dmitriy Pavlov
> > >> > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 12:20,
> Dmitriy
> > >> > > > Setrakyan <
> > >> > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > dsetrakyan@apache.org>:
> > >> > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > If services is not ready, which
> it
> > is
> > >> > not,
> > >> > > > > then we
> > >> > > > > > > > >
> > >> > > > > > > > > should
> > >> > > > > > > > > > > > >
> > >> > > > > > > > > > > > > include
> > >> > > > > > > > > > > > > > > them
> > >> > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > into
> > >> > > > > > > > > > > > > > > > > > > the next release. There is no
> need
> > to
> > >> > force
> > >> > > > > them into
> > >> > > > > > > > >
> > >> > > > > > > > > 2.7.
> > >> > > > > > > > > > >
> > >> > > > > > > > > > > I
> > >> > > > > > > > > > > > > > > suggest we
> > >> > > > > > > > > > > > > > > > > > > move according to the schedule we
> > all
> > >> > > agreed
> > >> > > > > on.
> > >> > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > D.
> > >> > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at 1:22 AM
> > Dmitriy
> > >> > > > Pavlov
> > >> > > > > <
> > >> > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > >> > > > > > > > > > > > > > > > > > > wrote:
> > >> > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > Yes, so correct statement is
> > >> "community
> > >> > > did
> > >> > > > > not
> > >> > > > > > > >
> > >> > > > > > > > make
> > >> > > > > > > > > any
> > >> > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > decisions
> > >> > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > about
> > >> > > > > > > > > > > > > > > > > > > > services not go to 2.7/
> services
> > are
> > >> > out
> > >> > > of
> > >> > > > > scope".
> > >> > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > If so, please forgive me my
> > >> confusion.
> > >> > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:19,
> > >> Vladimir
> > >> > > > > Ozerov <
> > >> > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > vozerov@gridgain.com
> > >> > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > :
> > >> > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > > Exactly. So correct statement
> > is
> > >> “it
> > >> > is
> > >> > > > up
> > >> > > > > to
> > >> > > > > > > > > > >
> > >> > > > > > > > > > > *community*
> > >> > > > > > > > > > > > > to
> > >> > > > > > > > > > > > > > > decide
> > >> > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > whether
> > >> > > > > > > > > > > > > > > > > > > > > something goes to 2.7”.
> > >> > > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:11,
> > >> Dmitriy
> > >> > > > > Pavlov <
> > >> > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > >> > > > > > > > > > > > > > > > > > > :
> > >> > > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > > > No, it is up to the
> > community to
> > >> > > > discuss
> > >> > > > > after
> > >> > > > > > > > >
> > >> > > > > > > > > their
> > >> > > > > > > > > > > > >
> > >> > > > > > > > > > > > > review
> > >> > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > results.
> > >> > > > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в
> 11:09,
> > >> > > Vladimir
> > >> > > > > Ozerov <
> > >> > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > >> > > > > > > > > > > > > > > > > > > > :
> > >> > > > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > > > > Dmitriy,
> > >> > > > > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > > > > Did I read your words
> > correctly
> > >> > > that
> > >> > > > > it is up
> > >> > > > > > > > >
> > >> > > > > > > > > to
> > >> > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > implementor
> > >> > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > of a
> > >> > > > > > > > > > > > > > > > > > > > > single
> > >> > > > > > > > > > > > > > > > > > > > > > > feature to decide whether
> > >> release
> > >> > > of
> > >> > > > > all
> > >> > > > > > > >
> > >> > > > > > > > other
> > >> > > > > > > > > > >
> > >> > > > > > > > > > > features
> > >> > > > > > > > > > > > > > and
> > >> > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > fixes
> > >> > > > > > > > > > > > > > > > > > > to
> > >> > > > > > > > > > > > > > > > > > > > be
> > >> > > > > > > > > > > > > > > > > > > > > > > delayed?
> > >> > > > > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в
> > 11:00,
> > >> > > Dmitriy
> > >> > > > > Pavlov
> > >> > > > > > > >
> > >> > > > > > > > <
> > >> > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > >> > > > > > > > > > > > > > > > > > > > > :
> > >> > > > > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > > > > > My point we can wait a
> > bit
> > >> for
> > >> > > > > services
> > >> > > > > > > > >
> > >> > > > > > > > > because
> > >> > > > > > > > > > > > > > > > > > > > > > > > 1 we are open-minded
> and
> > we
> > >> > > don't
> > >> > > > > have
> > >> > > > > > > > >
> > >> > > > > > > > > outside
> > >> > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > pressure
> > >> > > > > > > > > > > > > > > to
> > >> > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > do
> > >> > > > > > > > > > > > > > > > > > > > > release
> > >> > > > > > > > > > > > > > > > > > > > > > in
> > >> > > > > > > > > > > > > > > > > > > > > > > > October
> > >> > > > > > > > > > > > > > > > > > > > > > > > 2 and services it is
> not
> > >> some
> > >> > > new
> > >> > > > > feature,
> > >> > > > > > > > >
> > >> > > > > > > > > which
> > >> > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > suddenly
> > >> > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > appeared
> > >> > > > > > > > > > > > > > > > > > > > > in
> > >> > > > > > > > > > > > > > > > > > > > > > > > autumn, it is a well
> > known
> > >> and
> > >> > > > > important
> > >> > > > > > > > >
> > >> > > > > > > > > feature.
> > >> > > > > > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > > > > > So it is up to
> > Vyacheslav,
> > >> > Anton
> > >> > > > and
> > >> > > > > > > >
> > >> > > > > > > > Nikolay
> > >> > > > > > > > > to
> > >> > > > > > > > > > > > >
> > >> > > > > > > > > > > > > decide.
> > >> > > > > > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > > > > > Decisions can be
> > services are
> > >> > not
> > >> > > > > > > > >
> > >> > > > > > > > > ready/ready to
> > >> > > > > > > > > > > > >
> > >> > > > > > > > > > > > > merge
> > >> > > > > > > > > > > > > > > only
> > >> > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > to
> > >> > > > > > > > > > > > > > > > > > > > > > > master/ready
> > >> > > > > > > > > > > > > > > > > > > > > > > > to merge to master and
> to
> > >> 2.7.
> > >> > > > > > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в
> > 10:46,
> > >> > > > > Vladimir
> > >> > > > > > > > >
> > >> > > > > > > > > Ozerov <
> > >> > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > >> > > > > > > > > > > > > > > > > > > > > > :
> > >> > > > > > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > > > > > > Dmitry,
> > >> > > > > > > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > > > > > > Community agreement
> > was to
> > >> > > > perform
> > >> > > > > the
> > >> > > > > > > > >
> > >> > > > > > > > > release
> > >> > > > > > > > > > >
> > >> > > > > > > > > > > in
> > >> > > > > > > > > > > > > > > October.
> > >> > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > Of
> > >> > > > > > > > > > > > > > > > > > > > > course
> > >> > > > > > > > > > > > > > > > > > > > > > we
> > >> > > > > > > > > > > > > > > > > > > > > > > > can
> > >> > > > > > > > > > > > > > > > > > > > > > > > > wait a bit for
> > services.
> > >> Then
> > >> > > we
> > >> > > > > wait a
> > >> > > > > > > > >
> > >> > > > > > > > > bit for
> > >> > > > > > > > > > > > >
> > >> > > > > > > > > > > > > other
> > >> > > > > > > > > > > > > > > cool
> > >> > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > features
> > >> > > > > > > > > > > > > > > > > > > > > > > ready
> > >> > > > > > > > > > > > > > > > > > > > > > > > > by that time, then
> > again
> > >> and
> > >> > > > > again, and
> > >> > > > > > > > >
> > >> > > > > > > > > release
> > >> > > > > > > > > > > > >
> > >> > > > > > > > > > > > > will
> > >> > > > > > > > > > > > > > > never
> > >> > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > happen.
> > >> > > > > > > > > > > > > > > > > > > > > > And
> > >> > > > > > > > > > > > > > > > > > > > > > > > > while we are waiting
> > for
> > >> new
> > >> > > > > features to
> > >> > > > > > > > >
> > >> > > > > > > > > come,
> > >> > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > already
> > >> > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > completerd
> > >> > > > > > > > > > > > > > > > > > > > > > > > features
> > >> > > > > > > > > > > > > > > > > > > > > > > > > cannot be used by
> > anyone.
> > >> > > > > > > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > > > > > > This is why we have
> an
> > >> > > agreement
> > >> > > > > that if
> > >> > > > > > > > > > >
> > >> > > > > > > > > > > feature is
> > >> > > > > > > > > > > > > > not
> > >> > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > ready,
> > >> > > > > > > > > > > > > > > > > > > it
> > >> > > > > > > > > > > > > > > > > > > > > > > should
> > >> > > > > > > > > > > > > > > > > > > > > > > > be
> > >> > > > > > > > > > > > > > > > > > > > > > > > > moved to future
> > release,
> > >> > > instead
> > >> > > > of
> > >> > > > > > > > >
> > >> > > > > > > > > shifting
> > >> > > > > > > > > > > > >
> > >> > > > > > > > > > > > > release.
> > >> > > > > > > > > > > > > > > The
> > >> > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > sole
> > >> > > > > > > > > > > > > > > > > > > > > reason
> > >> > > > > > > > > > > > > > > > > > > > > > > to
> > >> > > > > > > > > > > > > > > > > > > > > > > > > have strict dates
> when
> > >> > > decisions
> > >> > > > > are made
> > >> > > > > > > > >
> > >> > > > > > > > > is
> > >> > > > > > > > > > >
> > >> > > > > > > > > > > to let
> > >> > > > > > > > > > > > > > > release
> > >> > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > happen.
> > >> > > > > > > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018
> at
> > >> 2:22
> > >> > AM
> > >> > > > > Dmitriy
> > >> > > > > > > > >
> > >> > > > > > > > > Pavlov
> > >> > > > > > > > > > >
> > >> > > > > > > > > > > <
> > >> > > > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > >> > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > >> > > > > > > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > > > > > > > Vladimir, I'm not
> > >> > searching
> > >> > > > for
> > >> > > > > enemy,
> > >> > > > > > > > >
> > >> > > > > > > > > and
> > >> > > > > > > > > > >
> > >> > > > > > > > > > > not
> > >> > > > > > > > > > > > > > > fighting
> > >> > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > with
> > >> > > > > > > > > > > > > > > > > > > > > you.
> > >> > > > > > > > > > > > > > > > > > > > > > > I'm
> > >> > > > > > > > > > > > > > > > > > > > > > > > > not
> > >> > > > > > > > > > > > > > > > > > > > > > > > > > happy about cases
> > when we
> > >> > are
> > >> > > > > hurrying.
> > >> > > > > > > > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > > > > > > > We can't fix test,
> > fill
> > >> > > ticket
> > >> > > > > details,
> > >> > > > > > > > >
> > >> > > > > > > > > can't
> > >> > > > > > > > > > > > >
> > >> > > > > > > > > > > > > wait
> > >> > > > > > > > > > > > > > > for
> > >> > > > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > > > contributions
> > >> > > > > > > > > > > > > > > > > > > > > > > to
> > >> > > > > > > > > > > > > > > > > > > > > > > > > > finish their tasks.
> > It
> > >> is
> > >> > > not
> > >> > > > > best
> > >> > > > > > > >
> > >> > > > > > > > idea
> > >> > > > > > > > > to
> > >> > > > > > > > > > >
> > >> > > > > > > > > > > use
> > >> > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > experience
> > >> > > > > > > > > > > > > > > > > > > from
> > >> > > > > > > > > > > > > > > > > > > > > > > > > commercial
> > >> > > > > > > > > > > > > > > > > > > > > > > > > > companies in open
> > source.
> > >> > Are
> > >> > > > > there any
> > >> > > > > > > > > > >
> > >> > > > > > > > > > > pressure
> > >> > > > > > > > > > > > > > > outside
> > >> > > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > > community?
> > >> > > > > > > > > > > > > > > > > > > > > > > Did
> > >> > > > > > > > > > > > > > > > > > > > > > > > > > someone promised
> > rest of
> > >> > > > > features to be
> > >> > > > > > > > > > >
> > >> > > > > > > > > > > released
> > >> > > > > > > > > > > > > at
> > >> > > > > > > > > > > > > > > 30
> > >> > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > September?
> > >> > > > > > > > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > > > > > > > Let's remember
> > principle
> > >> > > > > do-orcracy,
> > >> > > > > > > > >
> > >> > > > > > > > > power of
> > >> > > > > > > > > > > > >
> > >> > > > > > > > > > > > > those
> > >> > > > > > > > > > > > > > > who
> > >> > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > do.
> > >> > > > > > > > > > > > > > > > > > > If
> > >> > > > > > > > > > > > > > > > > > > > > > > > contribor
> > >> > > > > > > > > > > > > > > > > > > > > > > > > > does change and
> > reviewer
> > >> > does
> > >> > > > > review,
> > >> > > > > > > > >
> > >> > > > > > > > > let's
> > >> > > > > > > > > > >
> > >> > > > > > > > > > > give
> > >> > > > > > > > > > > > > > > right of
> > >> > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > making
> > >> > > > > > > > > > > > > > > > > > > > > > > > decision
> > >> > > > > > > > > > > > > > > > > > > > > > > > > > to them, but not to
> > some
> > >> > > closed
> > >> > > > > club of
> > >> > > > > > > > > > >
> > >> > > > > > > > > > > people
> > >> > > > > > > > > > > > > who
> > >> > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > privately
> > >> > > > > > > > > > > > > > > > > > > > > > discuss
> > >> > > > > > > > > > > > > > > > > > > > > > > > > > something.
> > >> > > > > > > > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > > > > > > > Sincerely
> > >> > > > > > > > > > > > > > > > > > > > > > > > > > Dmitriy Pavlov
> > >> > > > > > > > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018
> г.,
> > >> 23:42
> > >> > > > > Vyacheslav
> > >> > > > > > > > > > >
> > >> > > > > > > > > > > Daradur <
> > >> > > > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > > > daradurvs@gmail.com
> > >> > > > > > > > > > > > > > > > > > > > > > > > :
> > >> > > > > > > > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > > > > > > > > Hi Igniters!
> > >> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > > > > > > > > As I have written
> > about
> > >> > > > > Service Grid
> > >> > > > > > > > > > >
> > >> > > > > > > > > > > before [1]
> > >> > > > > > > > > > > > > > I'm
> > >> > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > finalizing
> > >> > > > > > > > > > > > > > > > > > > > > > the
> > >> > > > > > > > > > > > > > > > > > > > > > > > > > > solution to be
> sure
> > >> that
> > >> > > > > > > > >
> > >> > > > > > > > > implementation is
> > >> > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > reliable.
> > >> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > > > > > > > > About including
> it
> > in
> > >> > 2.7,
> > >> > > if
> > >> > > > > we talk
> > >> > > > > > > > >
> > >> > > > > > > > > that
> > >> > > > > > > > > > >
> > >> > > > > > > > > > > code
> > >> > > > > > > > > > > > > > > freeze
> > >> > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > tomorrow
> > >> > > > > > > > > > > > > > > > > > > > > > > then
> > >> > > > > > > > > > > > > > > > > > > > > > > > > > > the solution is
> not
> > >> ready
> > >> > > to
> > >> > > > > merge
> > >> > > > > > > >
> > >> > > > > > > > yet.
> > >> > > > > > > > > > > > > > > > > > > > > > > > > > > I hope that
> > >> prereviewers
> > >> > > > Anton
> > >> > > > > > > > >
> > >> > > > > > > > > Vinogradov
> > >> > > > > > > > > > >
> > >> > > > > > > > > > > and
> > >> > > > > > > > > > > > > > > Nikolay
> > >> > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > Izhikov
> > >> > > > > > > > > > > > > > > > > > > > > > will
> > >> > > > > > > > > > > > > > > > > > > > > > > be
> > >> > > > > > > > > > > > > > > > > > > > > > > > > > > able to answer if
> > >> > solution
> > >> > > > out
> > >> > > > > of
> > >> > > > > > > > >
> > >> > > > > > > > > scope or
> > >> > > > > > > > > > >
> > >> > > > > > > > > > > not
> > >> > > > > > > > > > > > > > in a
> > >> > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > couple
> > >> > > > > > > > > > > > > > > > > > > of
> > >> > > > > > > > > > > > > > > > > > > > > > days.
> > >> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > > > > > > > > > > > > > > > [1]
> > >> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > >> > > > > > > > > > > > > >
--
Best regards,
Andrey Kuznetsov.
Re: Apache Ignite 2.7 release
Posted by Dmitriy Pavlov <dp...@gmail.com>.
Hi Anton,
I definitely agree it is a blocker.
Sincerely,
Dmitriy Pavlov
вт, 2 окт. 2018 г. в 13:09, Anton Kalashnikov <ka...@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" <ds...@apache.org>:
> > Thanks, got it.
> >
> > On Mon, Oct 1, 2018 at 1:14 PM Dmitriy Pavlov <dp...@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 <vo...@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 <
> dsetrakyan@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 <
> vozerov@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 <
> nizhikov@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 <
> >> stkuzma@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.spb@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 <
> >> > > nizhikov@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 <
> >> > > > > > > >
> >> > > > > > > > daradurvs@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 <
> >> > > > > > > > >
> >> > > > > > > > > dsetrakyan@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.spb@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 <
> >> > > > > dmagda@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
> >> <
> >> > > > > > > > > > >
> >> > > > > > > > > > > nizhikov@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 <
> >> > > > > > > > > > > > >
> >> > > > > > > > > > > > > dsetrakyan@apache.org
> >> > > > > > > > > > > > > > > :
> >> > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > Dmitriy,
> >> > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > We agreed in the beginning of this
> thread
> >> > that
> >> > > > > Service
> >> > > > > > > >
> >> > > > > > > > Grid
> >> > > > > > > > > > >
> >> > > > > > > > > > > changes
> >> > > > > > > > > > > > > > > are not
> >> > > > > > > > > > > > > > > > > going to make the release because the
> >> > community
> >> > > > > still did
> >> > > > > > > > >
> >> > > > > > > > > not
> >> > > > > > > > > > > > >
> >> > > > > > > > > > > > > approve
> >> > > > > > > > > > > > > > > the
> >> > > > > > > > > > > > > > > > > design. Nothing has changed since. I
> have
> >> not
> >> > > > seen
> >> > > > > any
> >> > > > > > > > >
> >> > > > > > > > > design
> >> > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > discussions.
> >> > > > > > > > > > > > > > > > > At this point, I have no confidence
> that
> >> the
> >> > > > > Service Grid
> >> > > > > > > > > > >
> >> > > > > > > > > > > changes
> >> > > > > > > > > > > > > > will
> >> > > > > > > > > > > > > > > make
> >> > > > > > > > > > > > > > > > > it into the 2.8 release. The 2.7
> release
> >> > seems
> >> > > > out
> >> > > > > of
> >> > > > > > > > >
> >> > > > > > > > > question
> >> > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > altogether.
> >> > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > Also, Nikolay is a release manager. We
> >> should
> >> > > let
> >> > > > > him
> >> > > > > > > > >
> >> > > > > > > > > drive the
> >> > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > release. To
> >> > > > > > > > > > > > > > > > > my knowledge, he is doing a great job
> and
> >> the
> >> > > > > release is
> >> > > > > > > > >
> >> > > > > > > > > going
> >> > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > according to
> >> > > > > > > > > > > > > > > > > the schedule he proposed.
> >> > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > D.
> >> > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at 4:31 AM Dmitriy
> >> > Pavlov
> >> > > <
> >> > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> >> > > > > > > > > > > > > > > > > wrote:
> >> > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > Hi Dmitriy, Vladimir,
> >> > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > I suggest we stop this nonsense with
> >> > release
> >> > > > > > > > >
> >> > > > > > > > > dates-pushing
> >> > > > > > > > > > > > >
> >> > > > > > > > > > > > > because
> >> > > > > > > > > > > > > > of
> >> > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > some
> >> > > > > > > > > > > > > > > > > > open question.
> >> > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > Just because you disagreed with any
> >> > > > > include/exclude
> >> > > > > > > > >
> >> > > > > > > > > something
> >> > > > > > > > > > > > >
> >> > > > > > > > > > > > > into
> >> > > > > > > > > > > > > > > scope,
> >> > > > > > > > > > > > > > > > > > does not mean that whole community
> >> > disagreed.
> >> > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > If folks will start a separate
> discussion
> >> > > with
> >> > > > > results
> >> > > > > > > > >
> >> > > > > > > > > of the
> >> > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > review, I
> >> > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > see
> >> > > > > > > > > > > > > > > > > > no reasons to reject their
> contribution,
> >> > even
> >> > > > if
> >> > > > > we
> >> > > > > > > >
> >> > > > > > > > need
> >> > > > > > > > > to
> >> > > > > > > > > > > > >
> >> > > > > > > > > > > > > revisit
> >> > > > > > > > > > > > > > > our
> >> > > > > > > > > > > > > > > > > > agreements and wait for a couple of
> days
> >> > > more.
> >> > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > Am I missing some reason why dates
> are so
> >> > > > > fundamentally
> >> > > > > > > > > > >
> >> > > > > > > > > > > important
> >> > > > > > > > > > > > > > to
> >> > > > > > > > > > > > > > > you?
> >> > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > Sincerely,
> >> > > > > > > > > > > > > > > > > > Dmitriy Pavlov
> >> > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 12:20, Dmitriy
> >> > > > Setrakyan <
> >> > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > dsetrakyan@apache.org>:
> >> > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > If services is not ready, which it
> is
> >> > not,
> >> > > > > then we
> >> > > > > > > > >
> >> > > > > > > > > should
> >> > > > > > > > > > > > >
> >> > > > > > > > > > > > > include
> >> > > > > > > > > > > > > > > them
> >> > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > into
> >> > > > > > > > > > > > > > > > > > > the next release. There is no need
> to
> >> > force
> >> > > > > them into
> >> > > > > > > > >
> >> > > > > > > > > 2.7.
> >> > > > > > > > > > >
> >> > > > > > > > > > > I
> >> > > > > > > > > > > > > > > suggest we
> >> > > > > > > > > > > > > > > > > > > move according to the schedule we
> all
> >> > > agreed
> >> > > > > on.
> >> > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > D.
> >> > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at 1:22 AM
> Dmitriy
> >> > > > Pavlov
> >> > > > > <
> >> > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> >> > > > > > > > > > > > > > > > > > > wrote:
> >> > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > Yes, so correct statement is
> >> "community
> >> > > did
> >> > > > > not
> >> > > > > > > >
> >> > > > > > > > make
> >> > > > > > > > > any
> >> > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > decisions
> >> > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > about
> >> > > > > > > > > > > > > > > > > > > > services not go to 2.7/ services
> are
> >> > out
> >> > > of
> >> > > > > scope".
> >> > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > If so, please forgive me my
> >> confusion.
> >> > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:19,
> >> Vladimir
> >> > > > > Ozerov <
> >> > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > vozerov@gridgain.com
> >> > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > :
> >> > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > > Exactly. So correct statement
> is
> >> “it
> >> > is
> >> > > > up
> >> > > > > to
> >> > > > > > > > > > >
> >> > > > > > > > > > > *community*
> >> > > > > > > > > > > > > to
> >> > > > > > > > > > > > > > > decide
> >> > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > whether
> >> > > > > > > > > > > > > > > > > > > > > something goes to 2.7”.
> >> > > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:11,
> >> Dmitriy
> >> > > > > Pavlov <
> >> > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> >> > > > > > > > > > > > > > > > > > > :
> >> > > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > > > No, it is up to the
> community to
> >> > > > discuss
> >> > > > > after
> >> > > > > > > > >
> >> > > > > > > > > their
> >> > > > > > > > > > > > >
> >> > > > > > > > > > > > > review
> >> > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > results.
> >> > > > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:09,
> >> > > Vladimir
> >> > > > > Ozerov <
> >> > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> >> > > > > > > > > > > > > > > > > > > > :
> >> > > > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > > > > Dmitriy,
> >> > > > > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > > > > Did I read your words
> correctly
> >> > > that
> >> > > > > it is up
> >> > > > > > > > >
> >> > > > > > > > > to
> >> > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > implementor
> >> > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > of a
> >> > > > > > > > > > > > > > > > > > > > > single
> >> > > > > > > > > > > > > > > > > > > > > > > feature to decide whether
> >> release
> >> > > of
> >> > > > > all
> >> > > > > > > >
> >> > > > > > > > other
> >> > > > > > > > > > >
> >> > > > > > > > > > > features
> >> > > > > > > > > > > > > > and
> >> > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > fixes
> >> > > > > > > > > > > > > > > > > > > to
> >> > > > > > > > > > > > > > > > > > > > be
> >> > > > > > > > > > > > > > > > > > > > > > > delayed?
> >> > > > > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в
> 11:00,
> >> > > Dmitriy
> >> > > > > Pavlov
> >> > > > > > > >
> >> > > > > > > > <
> >> > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> >> > > > > > > > > > > > > > > > > > > > > :
> >> > > > > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > > > > > My point we can wait a
> bit
> >> for
> >> > > > > services
> >> > > > > > > > >
> >> > > > > > > > > because
> >> > > > > > > > > > > > > > > > > > > > > > > > 1 we are open-minded and
> we
> >> > > don't
> >> > > > > have
> >> > > > > > > > >
> >> > > > > > > > > outside
> >> > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > pressure
> >> > > > > > > > > > > > > > > to
> >> > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > do
> >> > > > > > > > > > > > > > > > > > > > > release
> >> > > > > > > > > > > > > > > > > > > > > > in
> >> > > > > > > > > > > > > > > > > > > > > > > > October
> >> > > > > > > > > > > > > > > > > > > > > > > > 2 and services it is not
> >> some
> >> > > new
> >> > > > > feature,
> >> > > > > > > > >
> >> > > > > > > > > which
> >> > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > suddenly
> >> > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > appeared
> >> > > > > > > > > > > > > > > > > > > > > in
> >> > > > > > > > > > > > > > > > > > > > > > > > autumn, it is a well
> known
> >> and
> >> > > > > important
> >> > > > > > > > >
> >> > > > > > > > > feature.
> >> > > > > > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > > > > > So it is up to
> Vyacheslav,
> >> > Anton
> >> > > > and
> >> > > > > > > >
> >> > > > > > > > Nikolay
> >> > > > > > > > > to
> >> > > > > > > > > > > > >
> >> > > > > > > > > > > > > decide.
> >> > > > > > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > > > > > Decisions can be
> services are
> >> > not
> >> > > > > > > > >
> >> > > > > > > > > ready/ready to
> >> > > > > > > > > > > > >
> >> > > > > > > > > > > > > merge
> >> > > > > > > > > > > > > > > only
> >> > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > to
> >> > > > > > > > > > > > > > > > > > > > > > > master/ready
> >> > > > > > > > > > > > > > > > > > > > > > > > to merge to master and to
> >> 2.7.
> >> > > > > > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в
> 10:46,
> >> > > > > Vladimir
> >> > > > > > > > >
> >> > > > > > > > > Ozerov <
> >> > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> >> > > > > > > > > > > > > > > > > > > > > > :
> >> > > > > > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > > > > > > Dmitry,
> >> > > > > > > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > > > > > > Community agreement
> was to
> >> > > > perform
> >> > > > > the
> >> > > > > > > > >
> >> > > > > > > > > release
> >> > > > > > > > > > >
> >> > > > > > > > > > > in
> >> > > > > > > > > > > > > > > October.
> >> > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > Of
> >> > > > > > > > > > > > > > > > > > > > > course
> >> > > > > > > > > > > > > > > > > > > > > > we
> >> > > > > > > > > > > > > > > > > > > > > > > > can
> >> > > > > > > > > > > > > > > > > > > > > > > > > wait a bit for
> services.
> >> Then
> >> > > we
> >> > > > > wait a
> >> > > > > > > > >
> >> > > > > > > > > bit for
> >> > > > > > > > > > > > >
> >> > > > > > > > > > > > > other
> >> > > > > > > > > > > > > > > cool
> >> > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > features
> >> > > > > > > > > > > > > > > > > > > > > > > ready
> >> > > > > > > > > > > > > > > > > > > > > > > > > by that time, then
> again
> >> and
> >> > > > > again, and
> >> > > > > > > > >
> >> > > > > > > > > release
> >> > > > > > > > > > > > >
> >> > > > > > > > > > > > > will
> >> > > > > > > > > > > > > > > never
> >> > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > happen.
> >> > > > > > > > > > > > > > > > > > > > > > And
> >> > > > > > > > > > > > > > > > > > > > > > > > > while we are waiting
> for
> >> new
> >> > > > > features to
> >> > > > > > > > >
> >> > > > > > > > > come,
> >> > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > already
> >> > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > completerd
> >> > > > > > > > > > > > > > > > > > > > > > > > features
> >> > > > > > > > > > > > > > > > > > > > > > > > > cannot be used by
> anyone.
> >> > > > > > > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > > > > > > This is why we have an
> >> > > agreement
> >> > > > > that if
> >> > > > > > > > > > >
> >> > > > > > > > > > > feature is
> >> > > > > > > > > > > > > > not
> >> > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > ready,
> >> > > > > > > > > > > > > > > > > > > it
> >> > > > > > > > > > > > > > > > > > > > > > > should
> >> > > > > > > > > > > > > > > > > > > > > > > > be
> >> > > > > > > > > > > > > > > > > > > > > > > > > moved to future
> release,
> >> > > instead
> >> > > > of
> >> > > > > > > > >
> >> > > > > > > > > shifting
> >> > > > > > > > > > > > >
> >> > > > > > > > > > > > > release.
> >> > > > > > > > > > > > > > > The
> >> > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > sole
> >> > > > > > > > > > > > > > > > > > > > > reason
> >> > > > > > > > > > > > > > > > > > > > > > > to
> >> > > > > > > > > > > > > > > > > > > > > > > > > have strict dates when
> >> > > decisions
> >> > > > > are made
> >> > > > > > > > >
> >> > > > > > > > > is
> >> > > > > > > > > > >
> >> > > > > > > > > > > to let
> >> > > > > > > > > > > > > > > release
> >> > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > happen.
> >> > > > > > > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at
> >> 2:22
> >> > AM
> >> > > > > Dmitriy
> >> > > > > > > > >
> >> > > > > > > > > Pavlov
> >> > > > > > > > > > >
> >> > > > > > > > > > > <
> >> > > > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> >> > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> >> > > > > > > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > > > > > > > Vladimir, I'm not
> >> > searching
> >> > > > for
> >> > > > > enemy,
> >> > > > > > > > >
> >> > > > > > > > > and
> >> > > > > > > > > > >
> >> > > > > > > > > > > not
> >> > > > > > > > > > > > > > > fighting
> >> > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > with
> >> > > > > > > > > > > > > > > > > > > > > you.
> >> > > > > > > > > > > > > > > > > > > > > > > I'm
> >> > > > > > > > > > > > > > > > > > > > > > > > > not
> >> > > > > > > > > > > > > > > > > > > > > > > > > > happy about cases
> when we
> >> > are
> >> > > > > hurrying.
> >> > > > > > > > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > > > > > > > We can't fix test,
> fill
> >> > > ticket
> >> > > > > details,
> >> > > > > > > > >
> >> > > > > > > > > can't
> >> > > > > > > > > > > > >
> >> > > > > > > > > > > > > wait
> >> > > > > > > > > > > > > > > for
> >> > > > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > > > contributions
> >> > > > > > > > > > > > > > > > > > > > > > > to
> >> > > > > > > > > > > > > > > > > > > > > > > > > > finish their tasks.
> It
> >> is
> >> > > not
> >> > > > > best
> >> > > > > > > >
> >> > > > > > > > idea
> >> > > > > > > > > to
> >> > > > > > > > > > >
> >> > > > > > > > > > > use
> >> > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > experience
> >> > > > > > > > > > > > > > > > > > > from
> >> > > > > > > > > > > > > > > > > > > > > > > > > commercial
> >> > > > > > > > > > > > > > > > > > > > > > > > > > companies in open
> source.
> >> > Are
> >> > > > > there any
> >> > > > > > > > > > >
> >> > > > > > > > > > > pressure
> >> > > > > > > > > > > > > > > outside
> >> > > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > > community?
> >> > > > > > > > > > > > > > > > > > > > > > > Did
> >> > > > > > > > > > > > > > > > > > > > > > > > > > someone promised
> rest of
> >> > > > > features to be
> >> > > > > > > > > > >
> >> > > > > > > > > > > released
> >> > > > > > > > > > > > > at
> >> > > > > > > > > > > > > > > 30
> >> > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > September?
> >> > > > > > > > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > > > > > > > Let's remember
> principle
> >> > > > > do-orcracy,
> >> > > > > > > > >
> >> > > > > > > > > power of
> >> > > > > > > > > > > > >
> >> > > > > > > > > > > > > those
> >> > > > > > > > > > > > > > > who
> >> > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > do.
> >> > > > > > > > > > > > > > > > > > > If
> >> > > > > > > > > > > > > > > > > > > > > > > > contribor
> >> > > > > > > > > > > > > > > > > > > > > > > > > > does change and
> reviewer
> >> > does
> >> > > > > review,
> >> > > > > > > > >
> >> > > > > > > > > let's
> >> > > > > > > > > > >
> >> > > > > > > > > > > give
> >> > > > > > > > > > > > > > > right of
> >> > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > making
> >> > > > > > > > > > > > > > > > > > > > > > > > decision
> >> > > > > > > > > > > > > > > > > > > > > > > > > > to them, but not to
> some
> >> > > closed
> >> > > > > club of
> >> > > > > > > > > > >
> >> > > > > > > > > > > people
> >> > > > > > > > > > > > > who
> >> > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > privately
> >> > > > > > > > > > > > > > > > > > > > > > discuss
> >> > > > > > > > > > > > > > > > > > > > > > > > > > something.
> >> > > > > > > > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > > > > > > > Sincerely
> >> > > > > > > > > > > > > > > > > > > > > > > > > > Dmitriy Pavlov
> >> > > > > > > > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г.,
> >> 23:42
> >> > > > > Vyacheslav
> >> > > > > > > > > > >
> >> > > > > > > > > > > Daradur <
> >> > > > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > > > daradurvs@gmail.com
> >> > > > > > > > > > > > > > > > > > > > > > > > :
> >> > > > > > > > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > > > > > > > > Hi Igniters!
> >> > > > > > > > > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > > > > > > > > As I have written
> about
> >> > > > > Service Grid
> >> > > > > > > > > > >
> >> > > > > > > > > > > before [1]
> >> > > > > > > > > > > > > > I'm
> >> > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > finalizing
> >> > > > > > > > > > > > > > > > > > > > > > the
> >> > > > > > > > > > > > > > > > > > > > > > > > > > > solution to be sure
> >> that
> >> > > > > > > > >
> >> > > > > > > > > implementation is
> >> > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > reliable.
> >> > > > > > > > > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > > > > > > > > About including it
> in
> >> > 2.7,
> >> > > if
> >> > > > > we talk
> >> > > > > > > > >
> >> > > > > > > > > that
> >> > > > > > > > > > >
> >> > > > > > > > > > > code
> >> > > > > > > > > > > > > > > freeze
> >> > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > tomorrow
> >> > > > > > > > > > > > > > > > > > > > > > > then
> >> > > > > > > > > > > > > > > > > > > > > > > > > > > the solution is not
> >> ready
> >> > > to
> >> > > > > merge
> >> > > > > > > >
> >> > > > > > > > yet.
> >> > > > > > > > > > > > > > > > > > > > > > > > > > > I hope that
> >> prereviewers
> >> > > > Anton
> >> > > > > > > > >
> >> > > > > > > > > Vinogradov
> >> > > > > > > > > > >
> >> > > > > > > > > > > and
> >> > > > > > > > > > > > > > > Nikolay
> >> > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > Izhikov
> >> > > > > > > > > > > > > > > > > > > > > > will
> >> > > > > > > > > > > > > > > > > > > > > > > be
> >> > > > > > > > > > > > > > > > > > > > > > > > > > > able to answer if
> >> > solution
> >> > > > out
> >> > > > > of
> >> > > > > > > > >
> >> > > > > > > > > scope or
> >> > > > > > > > > > >
> >> > > > > > > > > > > not
> >> > > > > > > > > > > > > > in a
> >> > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > couple
> >> > > > > > > > > > > > > > > > > > > of
> >> > > > > > > > > > > > > > > > > > > > > > days.
> >> > > > > > > > > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > > > > > > > > [1]
> >> > > > > > > > > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > >
> >> > > > > > > > > > >
> >> > > > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-release-td34076.html#a34485
> >> > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27,
> 2018 at
> >> > > 11:14
> >> > > > > PM
> >> > > > > > > > >
> >> > > > > > > > > Dmitriy
> >> > > > > > > > > > > > >
> >> > > > > > > > > > > > > Pavlov <
> >> > > > > > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> >> > > > > > > > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> >> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > > > > > > > > > Yes, I agree, NPE
> >> > during
> >> > > > WAL
> >> > > > > flush
> >> > > > > > > >
> >> > > > > > > > is
> >> > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > definitely
> >> > > > > > > > > > > > > > > a
> >> > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > blocker.
> >> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > > > > > > > > > It is strange
> why the
> >> > > > > current test
> >> > > > > > > > >
> >> > > > > > > > > set
> >> > > > > > > > > > >
> >> > > > > > > > > > > did
> >> > > > > > > > > > > > > not
> >> > > > > > > > > > > > > > > fail
> >> > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > after
> >> > > > > > > > > > > > > > > > > > > > > > commit.
> >> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент.
> 2018 г.
> >> в
> >> > > > 21:45,
> >> > > > > > > >
> >> > > > > > > > Andrey
> >> > > > > > > > > > > > >
> >> > > > > > > > > > > > > Kuznetsov
> >> > > > > > > > > > > > > > <
> >> > > > > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > > > > stkuzma@gmail.com
> >> > > > > > > > > > > > > > > > > > > > > > > > > :
> >> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > > > > > > > > > > Igniters,
> >> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > > > > > > > > > > > > I've bumped
> into a
> >> > new
> >> > > > bug
> >> > > > > in WAL
> >> > > > > > > > > > >
> >> > > > > > > > > > > manager
> >> > > > > > > > > > > > > > > recently,
> >> > > > > > > > > > > > > > > > > >
> >> > > > > > > > > > > > > > > > > > see
> >> > > > > > > > > > > > > > > > > > >
Re: Apache Ignite 2.7 release
Posted by Anton Kalashnikov <ka...@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" <ds...@apache.org>:
> Thanks, got it.
>
> On Mon, Oct 1, 2018 at 1:14 PM Dmitriy Pavlov <dp...@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 <vo...@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 <ds...@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 <vo...@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 <ni...@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 <
>> stkuzma@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.spb@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 <
>> > > nizhikov@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 <
>> > > > > > > >
>> > > > > > > > daradurvs@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 <
>> > > > > > > > >
>> > > > > > > > > dsetrakyan@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.spb@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 <
>> > > > > dmagda@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
>> <
>> > > > > > > > > > >
>> > > > > > > > > > > nizhikov@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 <
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > dsetrakyan@apache.org
>> > > > > > > > > > > > > > > :
>> > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > Dmitriy,
>> > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > We agreed in the beginning of this thread
>> > that
>> > > > > Service
>> > > > > > > >
>> > > > > > > > Grid
>> > > > > > > > > > >
>> > > > > > > > > > > changes
>> > > > > > > > > > > > > > > are not
>> > > > > > > > > > > > > > > > > going to make the release because the
>> > community
>> > > > > still did
>> > > > > > > > >
>> > > > > > > > > not
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > approve
>> > > > > > > > > > > > > > > the
>> > > > > > > > > > > > > > > > > design. Nothing has changed since. I have
>> not
>> > > > seen
>> > > > > any
>> > > > > > > > >
>> > > > > > > > > design
>> > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > discussions.
>> > > > > > > > > > > > > > > > > At this point, I have no confidence that
>> the
>> > > > > Service Grid
>> > > > > > > > > > >
>> > > > > > > > > > > changes
>> > > > > > > > > > > > > > will
>> > > > > > > > > > > > > > > make
>> > > > > > > > > > > > > > > > > it into the 2.8 release. The 2.7 release
>> > seems
>> > > > out
>> > > > > of
>> > > > > > > > >
>> > > > > > > > > question
>> > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > altogether.
>> > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > Also, Nikolay is a release manager. We
>> should
>> > > let
>> > > > > him
>> > > > > > > > >
>> > > > > > > > > drive the
>> > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > release. To
>> > > > > > > > > > > > > > > > > my knowledge, he is doing a great job and
>> the
>> > > > > release is
>> > > > > > > > >
>> > > > > > > > > going
>> > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > according to
>> > > > > > > > > > > > > > > > > the schedule he proposed.
>> > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > D.
>> > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at 4:31 AM Dmitriy
>> > Pavlov
>> > > <
>> > > > > > > > > > > > > >
>> > > > > > > > > > > > > > dpavlov.spb@gmail.com>
>> > > > > > > > > > > > > > > > > wrote:
>> > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > Hi Dmitriy, Vladimir,
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > I suggest we stop this nonsense with
>> > release
>> > > > > > > > >
>> > > > > > > > > dates-pushing
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > because
>> > > > > > > > > > > > > > of
>> > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > some
>> > > > > > > > > > > > > > > > > > open question.
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > Just because you disagreed with any
>> > > > > include/exclude
>> > > > > > > > >
>> > > > > > > > > something
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > into
>> > > > > > > > > > > > > > > scope,
>> > > > > > > > > > > > > > > > > > does not mean that whole community
>> > disagreed.
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > If folks will start a separate discussion
>> > > with
>> > > > > results
>> > > > > > > > >
>> > > > > > > > > of the
>> > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > review, I
>> > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > see
>> > > > > > > > > > > > > > > > > > no reasons to reject their contribution,
>> > even
>> > > > if
>> > > > > we
>> > > > > > > >
>> > > > > > > > need
>> > > > > > > > > to
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > revisit
>> > > > > > > > > > > > > > > our
>> > > > > > > > > > > > > > > > > > agreements and wait for a couple of days
>> > > more.
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > Am I missing some reason why dates are so
>> > > > > fundamentally
>> > > > > > > > > > >
>> > > > > > > > > > > important
>> > > > > > > > > > > > > > to
>> > > > > > > > > > > > > > > you?
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > Sincerely,
>> > > > > > > > > > > > > > > > > > Dmitriy Pavlov
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 12:20, Dmitriy
>> > > > Setrakyan <
>> > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > dsetrakyan@apache.org>:
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > If services is not ready, which it is
>> > not,
>> > > > > then we
>> > > > > > > > >
>> > > > > > > > > should
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > include
>> > > > > > > > > > > > > > > them
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > into
>> > > > > > > > > > > > > > > > > > > the next release. There is no need to
>> > force
>> > > > > them into
>> > > > > > > > >
>> > > > > > > > > 2.7.
>> > > > > > > > > > >
>> > > > > > > > > > > I
>> > > > > > > > > > > > > > > suggest we
>> > > > > > > > > > > > > > > > > > > move according to the schedule we all
>> > > agreed
>> > > > > on.
>> > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > D.
>> > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at 1:22 AM Dmitriy
>> > > > Pavlov
>> > > > > <
>> > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
>> > > > > > > > > > > > > > > > > > > wrote:
>> > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > Yes, so correct statement is
>> "community
>> > > did
>> > > > > not
>> > > > > > > >
>> > > > > > > > make
>> > > > > > > > > any
>> > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > decisions
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > about
>> > > > > > > > > > > > > > > > > > > > services not go to 2.7/ services are
>> > out
>> > > of
>> > > > > scope".
>> > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > If so, please forgive me my
>> confusion.
>> > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:19,
>> Vladimir
>> > > > > Ozerov <
>> > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > vozerov@gridgain.com
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > :
>> > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > Exactly. So correct statement is
>> “it
>> > is
>> > > > up
>> > > > > to
>> > > > > > > > > > >
>> > > > > > > > > > > *community*
>> > > > > > > > > > > > > to
>> > > > > > > > > > > > > > > decide
>> > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > whether
>> > > > > > > > > > > > > > > > > > > > > something goes to 2.7”.
>> > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:11,
>> Dmitriy
>> > > > > Pavlov <
>> > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
>> > > > > > > > > > > > > > > > > > > :
>> > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > No, it is up to the community to
>> > > > discuss
>> > > > > after
>> > > > > > > > >
>> > > > > > > > > their
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > review
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > results.
>> > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:09,
>> > > Vladimir
>> > > > > Ozerov <
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > vozerov@gridgain.com
>> > > > > > > > > > > > > > > > > > > > :
>> > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > Dmitriy,
>> > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > Did I read your words correctly
>> > > that
>> > > > > it is up
>> > > > > > > > >
>> > > > > > > > > to
>> > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > implementor
>> > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > of a
>> > > > > > > > > > > > > > > > > > > > > single
>> > > > > > > > > > > > > > > > > > > > > > > feature to decide whether
>> release
>> > > of
>> > > > > all
>> > > > > > > >
>> > > > > > > > other
>> > > > > > > > > > >
>> > > > > > > > > > > features
>> > > > > > > > > > > > > > and
>> > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > fixes
>> > > > > > > > > > > > > > > > > > > to
>> > > > > > > > > > > > > > > > > > > > be
>> > > > > > > > > > > > > > > > > > > > > > > delayed?
>> > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:00,
>> > > Dmitriy
>> > > > > Pavlov
>> > > > > > > >
>> > > > > > > > <
>> > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
>> > > > > > > > > > > > > > > > > > > > > :
>> > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > My point we can wait a bit
>> for
>> > > > > services
>> > > > > > > > >
>> > > > > > > > > because
>> > > > > > > > > > > > > > > > > > > > > > > > 1 we are open-minded and we
>> > > don't
>> > > > > have
>> > > > > > > > >
>> > > > > > > > > outside
>> > > > > > > > > > > > > >
>> > > > > > > > > > > > > > pressure
>> > > > > > > > > > > > > > > to
>> > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > do
>> > > > > > > > > > > > > > > > > > > > > release
>> > > > > > > > > > > > > > > > > > > > > > in
>> > > > > > > > > > > > > > > > > > > > > > > > October
>> > > > > > > > > > > > > > > > > > > > > > > > 2 and services it is not
>> some
>> > > new
>> > > > > feature,
>> > > > > > > > >
>> > > > > > > > > which
>> > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > suddenly
>> > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > appeared
>> > > > > > > > > > > > > > > > > > > > > in
>> > > > > > > > > > > > > > > > > > > > > > > > autumn, it is a well known
>> and
>> > > > > important
>> > > > > > > > >
>> > > > > > > > > feature.
>> > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > So it is up to Vyacheslav,
>> > Anton
>> > > > and
>> > > > > > > >
>> > > > > > > > Nikolay
>> > > > > > > > > to
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > decide.
>> > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > Decisions can be services are
>> > not
>> > > > > > > > >
>> > > > > > > > > ready/ready to
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > merge
>> > > > > > > > > > > > > > > only
>> > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > to
>> > > > > > > > > > > > > > > > > > > > > > > master/ready
>> > > > > > > > > > > > > > > > > > > > > > > > to merge to master and to
>> 2.7.
>> > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 10:46,
>> > > > > Vladimir
>> > > > > > > > >
>> > > > > > > > > Ozerov <
>> > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
>> > > > > > > > > > > > > > > > > > > > > > :
>> > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > Dmitry,
>> > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > Community agreement was to
>> > > > perform
>> > > > > the
>> > > > > > > > >
>> > > > > > > > > release
>> > > > > > > > > > >
>> > > > > > > > > > > in
>> > > > > > > > > > > > > > > October.
>> > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > Of
>> > > > > > > > > > > > > > > > > > > > > course
>> > > > > > > > > > > > > > > > > > > > > > we
>> > > > > > > > > > > > > > > > > > > > > > > > can
>> > > > > > > > > > > > > > > > > > > > > > > > > wait a bit for services.
>> Then
>> > > we
>> > > > > wait a
>> > > > > > > > >
>> > > > > > > > > bit for
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > other
>> > > > > > > > > > > > > > > cool
>> > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > features
>> > > > > > > > > > > > > > > > > > > > > > > ready
>> > > > > > > > > > > > > > > > > > > > > > > > > by that time, then again
>> and
>> > > > > again, and
>> > > > > > > > >
>> > > > > > > > > release
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > will
>> > > > > > > > > > > > > > > never
>> > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > happen.
>> > > > > > > > > > > > > > > > > > > > > > And
>> > > > > > > > > > > > > > > > > > > > > > > > > while we are waiting for
>> new
>> > > > > features to
>> > > > > > > > >
>> > > > > > > > > come,
>> > > > > > > > > > > > > >
>> > > > > > > > > > > > > > already
>> > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > completerd
>> > > > > > > > > > > > > > > > > > > > > > > > features
>> > > > > > > > > > > > > > > > > > > > > > > > > cannot be used by anyone.
>> > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > This is why we have an
>> > > agreement
>> > > > > that if
>> > > > > > > > > > >
>> > > > > > > > > > > feature is
>> > > > > > > > > > > > > > not
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > ready,
>> > > > > > > > > > > > > > > > > > > it
>> > > > > > > > > > > > > > > > > > > > > > > should
>> > > > > > > > > > > > > > > > > > > > > > > > be
>> > > > > > > > > > > > > > > > > > > > > > > > > moved to future release,
>> > > instead
>> > > > of
>> > > > > > > > >
>> > > > > > > > > shifting
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > release.
>> > > > > > > > > > > > > > > The
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > sole
>> > > > > > > > > > > > > > > > > > > > > reason
>> > > > > > > > > > > > > > > > > > > > > > > to
>> > > > > > > > > > > > > > > > > > > > > > > > > have strict dates when
>> > > decisions
>> > > > > are made
>> > > > > > > > >
>> > > > > > > > > is
>> > > > > > > > > > >
>> > > > > > > > > > > to let
>> > > > > > > > > > > > > > > release
>> > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > happen.
>> > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at
>> 2:22
>> > AM
>> > > > > Dmitriy
>> > > > > > > > >
>> > > > > > > > > Pavlov
>> > > > > > > > > > >
>> > > > > > > > > > > <
>> > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
>> > > > > > > > > > > > > > > > > > > > > > > > > wrote:
>> > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > Vladimir, I'm not
>> > searching
>> > > > for
>> > > > > enemy,
>> > > > > > > > >
>> > > > > > > > > and
>> > > > > > > > > > >
>> > > > > > > > > > > not
>> > > > > > > > > > > > > > > fighting
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > with
>> > > > > > > > > > > > > > > > > > > > > you.
>> > > > > > > > > > > > > > > > > > > > > > > I'm
>> > > > > > > > > > > > > > > > > > > > > > > > > not
>> > > > > > > > > > > > > > > > > > > > > > > > > > happy about cases when we
>> > are
>> > > > > hurrying.
>> > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > We can't fix test, fill
>> > > ticket
>> > > > > details,
>> > > > > > > > >
>> > > > > > > > > can't
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > wait
>> > > > > > > > > > > > > > > for
>> > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > contributions
>> > > > > > > > > > > > > > > > > > > > > > > to
>> > > > > > > > > > > > > > > > > > > > > > > > > > finish their tasks. It
>> is
>> > > not
>> > > > > best
>> > > > > > > >
>> > > > > > > > idea
>> > > > > > > > > to
>> > > > > > > > > > >
>> > > > > > > > > > > use
>> > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > experience
>> > > > > > > > > > > > > > > > > > > from
>> > > > > > > > > > > > > > > > > > > > > > > > > commercial
>> > > > > > > > > > > > > > > > > > > > > > > > > > companies in open source.
>> > Are
>> > > > > there any
>> > > > > > > > > > >
>> > > > > > > > > > > pressure
>> > > > > > > > > > > > > > > outside
>> > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > community?
>> > > > > > > > > > > > > > > > > > > > > > > Did
>> > > > > > > > > > > > > > > > > > > > > > > > > > someone promised rest of
>> > > > > features to be
>> > > > > > > > > > >
>> > > > > > > > > > > released
>> > > > > > > > > > > > > at
>> > > > > > > > > > > > > > > 30
>> > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > September?
>> > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > Let's remember principle
>> > > > > do-orcracy,
>> > > > > > > > >
>> > > > > > > > > power of
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > those
>> > > > > > > > > > > > > > > who
>> > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > do.
>> > > > > > > > > > > > > > > > > > > If
>> > > > > > > > > > > > > > > > > > > > > > > > contribor
>> > > > > > > > > > > > > > > > > > > > > > > > > > does change and reviewer
>> > does
>> > > > > review,
>> > > > > > > > >
>> > > > > > > > > let's
>> > > > > > > > > > >
>> > > > > > > > > > > give
>> > > > > > > > > > > > > > > right of
>> > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > making
>> > > > > > > > > > > > > > > > > > > > > > > > decision
>> > > > > > > > > > > > > > > > > > > > > > > > > > to them, but not to some
>> > > closed
>> > > > > club of
>> > > > > > > > > > >
>> > > > > > > > > > > people
>> > > > > > > > > > > > > who
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > privately
>> > > > > > > > > > > > > > > > > > > > > > discuss
>> > > > > > > > > > > > > > > > > > > > > > > > > > something.
>> > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > Sincerely
>> > > > > > > > > > > > > > > > > > > > > > > > > > Dmitriy Pavlov
>> > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г.,
>> 23:42
>> > > > > Vyacheslav
>> > > > > > > > > > >
>> > > > > > > > > > > Daradur <
>> > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > daradurvs@gmail.com
>> > > > > > > > > > > > > > > > > > > > > > > > :
>> > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > Hi Igniters!
>> > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > As I have written about
>> > > > > Service Grid
>> > > > > > > > > > >
>> > > > > > > > > > > before [1]
>> > > > > > > > > > > > > > I'm
>> > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > finalizing
>> > > > > > > > > > > > > > > > > > > > > > the
>> > > > > > > > > > > > > > > > > > > > > > > > > > > solution to be sure
>> that
>> > > > > > > > >
>> > > > > > > > > implementation is
>> > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > reliable.
>> > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > About including it in
>> > 2.7,
>> > > if
>> > > > > we talk
>> > > > > > > > >
>> > > > > > > > > that
>> > > > > > > > > > >
>> > > > > > > > > > > code
>> > > > > > > > > > > > > > > freeze
>> > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > tomorrow
>> > > > > > > > > > > > > > > > > > > > > > > then
>> > > > > > > > > > > > > > > > > > > > > > > > > > > the solution is not
>> ready
>> > > to
>> > > > > merge
>> > > > > > > >
>> > > > > > > > yet.
>> > > > > > > > > > > > > > > > > > > > > > > > > > > I hope that
>> prereviewers
>> > > > Anton
>> > > > > > > > >
>> > > > > > > > > Vinogradov
>> > > > > > > > > > >
>> > > > > > > > > > > and
>> > > > > > > > > > > > > > > Nikolay
>> > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > Izhikov
>> > > > > > > > > > > > > > > > > > > > > > will
>> > > > > > > > > > > > > > > > > > > > > > > be
>> > > > > > > > > > > > > > > > > > > > > > > > > > > able to answer if
>> > solution
>> > > > out
>> > > > > of
>> > > > > > > > >
>> > > > > > > > > scope or
>> > > > > > > > > > >
>> > > > > > > > > > > not
>> > > > > > > > > > > > > > in a
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > couple
>> > > > > > > > > > > > > > > > > > > of
>> > > > > > > > > > > > > > > > > > > > > > days.
>> > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > [1]
>> > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > >
>> > > > > > > > > > >
>> > > > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > >
>> > > >
>> > >
>> >
>> http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-release-td34076.html#a34485
>> > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at
>> > > 11:14
>> > > > > PM
>> > > > > > > > >
>> > > > > > > > > Dmitriy
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > Pavlov <
>> > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
>> > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
>> > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > Yes, I agree, NPE
>> > during
>> > > > WAL
>> > > > > flush
>> > > > > > > >
>> > > > > > > > is
>> > > > > > > > > > > > > >
>> > > > > > > > > > > > > > definitely
>> > > > > > > > > > > > > > > a
>> > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > blocker.
>> > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > It is strange why the
>> > > > > current test
>> > > > > > > > >
>> > > > > > > > > set
>> > > > > > > > > > >
>> > > > > > > > > > > did
>> > > > > > > > > > > > > not
>> > > > > > > > > > > > > > > fail
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > after
>> > > > > > > > > > > > > > > > > > > > > > commit.
>> > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г.
>> в
>> > > > 21:45,
>> > > > > > > >
>> > > > > > > > Andrey
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > Kuznetsov
>> > > > > > > > > > > > > > <
>> > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > stkuzma@gmail.com
>> > > > > > > > > > > > > > > > > > > > > > > > > :
>> > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > Igniters,
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > I've bumped into a
>> > new
>> > > > bug
>> > > > > in WAL
>> > > > > > > > > > >
>> > > > > > > > > > > manager
>> > > > > > > > > > > > > > > recently,
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > see
>> > > > > > > > > > > > > > > > > > > > > [1].
>> > > > > > > > > > > > > > > > > > > > > > It
>> > > > > > > > > > > > > > > > > > > > > > > > > looks
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > critical enough,
>> and
>> > > can
>> > > > > be a
>> > > > > > > >
>> > > > > > > > good
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > candidate
>> > > > > > > > > > > > > > > for
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > fixing
>> > > > > > > > > > > > > > > > > > > > > > before
>> > > > > > > > > > > > > > > > > > > > > > > > 2.7
>> > > > > > > > > > > > > > > > > > > > > > > > > > > release.
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > Do you agree?
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > [1]
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > >
>> > > > > https://issues.apache.org/jira/browse/IGNITE-9731
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018
>> г.
>> > в
>> > > > > 19:45,
>> > > > > > > > >
>> > > > > > > > > Dmitriy
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > Pavlov
>> > > > > > > > > > > > > > <
>> > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
>> > > > > > > > > > > > > > > > > > > > > > > > > > > :
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I need
>> > Vhyacheslav's
>> > > > > opinion to
>> > > > > > > > >
>> > > > > > > > > be
>> > > > > > > > > > > > > >
>> > > > > > > > > > > > > > absolutely
>> > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > sure
>> > > > > > > > > > > > > > > > > > > what
>> > > > > > > > > > > > > > > > > > > > > > > status
>> > > > > > > > > > > > > > > > > > > > > > > > is
>> > > > > > > > > > > > > > > > > > > > > > > > > > > now.
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > We never
>> committed
>> > to
>> > > > > dates of
>> > > > > > > > > > >
>> > > > > > > > > > > release,
>> > > > > > > > > > > > > as
>> > > > > > > > > > > > > > > well.
>> > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > I
>> > > > > > > > > > > > > > > > > > > > don't
>> > > > > > > > > > > > > > > > > > > > > > > quite
>> > > > > > > > > > > > > > > > > > > > > > > > > > > understand
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > what can mean
>> 'the
>> > > > > community
>> > > > > > > > > > >
>> > > > > > > > > > > committed to
>> > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > doing/releasing
>> > > > > > > > > > > > > > > > > > > > > > > > > > something'.
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > About SG, I also
>> > > > > concerned why
>> > > > > > > > >
>> > > > > > > > > such
>> > > > > > > > > > >
>> > > > > > > > > > > a big
>> > > > > > > > > > > > > > > feature
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > has
>> > > > > > > > > > > > > > > > > > > > > > quite a
>> > > > > > > > > > > > > > > > > > > > > > > > few
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > discussions on
>> the
>> > > > list.
>> > > > > But it
>> > > > > > > > >
>> > > > > > > > > is
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > another
>> > > > > > > > > > > > > > > story.
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018
>> > г.
>> > > в
>> > > > > 19:33,
>> > > > > > > > > > >
>> > > > > > > > > > > Vladimir
>> > > > > > > > > > > > > > > Ozerov <
>> > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > :
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Folks,
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Please stop
>> > looking
>> > > > for
>> > > > > > > >
>> > > > > > > > enemies
>> > > > > > > > > > > > > >
>> > > > > > > > > > > > > > everywhere.
>> > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > Just
>> > > > > > > > > > > > > > > > > > > went
>> > > > > > > > > > > > > > > > > > > > > > > through
>> > > > > > > > > > > > > > > > > > > > > > > > > > this
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > thread
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > and search for
>> > > > > "service"
>> > > > > > > >
>> > > > > > > > word.
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27,
>> > > 2018
>> > > > > at 7:30
>> > > > > > > >
>> > > > > > > > PM
>> > > > > > > > > > >
>> > > > > > > > > > > Denis
>> > > > > > > > > > > > > > > Magda <
>> > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > dmagda@apache.org
>> > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Denis, as
>> PMC
>> > > > > Chair,
>> > > > > > > >
>> > > > > > > > could
>> > > > > > > > > you
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > please
>> > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > control,
>> > > > > > > > > > > > > > > > > > > > that
>> > > > > > > > > > > > > > > > > > > > > > > > Service
>> > > > > > > > > > > > > > > > > > > > > > > > > > Grid
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > inclusion/exclusion is
>> > > > > > > > > > >
>> > > > > > > > > > > discussed
>> > > > > > > > > > > > > > > properly
>> > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > according
>> > > > > > > > > > > > > > > > > > > > > to
>> > > > > > > > > > > > > > > > > > > > > > > the
>> > > > > > > > > > > > > > > > > > > > > > > > > > > Apache
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > Way.
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > It's fine
>> when
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > committers/contributors
>> > > > > > > > > > > > > > > have
>> > > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > > private
>> > > > > > > > > > > > > > > > > > > > > > > > > discussions
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > related
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > to
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > a feature
>> > they've
>> > > > > been
>> > > > > > > > >
>> > > > > > > > > working
>> > > > > > > > > > >
>> > > > > > > > > > > on.
>> > > > > > > > > > > > > Not
>> > > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > > everything
>> > > > > > > > > > > > > > > > > > > > > should
>> > > > > > > > > > > > > > > > > > > > > > > go
>> > > > > > > > > > > > > > > > > > > > > > > > > > > through
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > the
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > dev
>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > list.
>> > Otherwise,
>> > > it
>> > > > > will be
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > inundated.
>> > > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > > However,
>> > > > > > > > > > > > > > > > > > > > > agree,
>> >
Re: Apache Ignite 2.7 release
Posted by Dmitriy Setrakyan <ds...@apache.org>.
Thanks, got it.
On Mon, Oct 1, 2018 at 1:14 PM Dmitriy Pavlov <dp...@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 <vo...@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 <ds...@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 <vo...@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 <ni...@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 <
> stkuzma@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.spb@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 <
> > > nizhikov@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 <
> > > > > > > >
> > > > > > > > daradurvs@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 <
> > > > > > > > >
> > > > > > > > > dsetrakyan@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.spb@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 <
> > > > > dmagda@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
> <
> > > > > > > > > > >
> > > > > > > > > > > nizhikov@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 <
> > > > > > > > > > > > >
> > > > > > > > > > > > > dsetrakyan@apache.org
> > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > We agreed in the beginning of this thread
> > that
> > > > > Service
> > > > > > > >
> > > > > > > > Grid
> > > > > > > > > > >
> > > > > > > > > > > changes
> > > > > > > > > > > > > > > are not
> > > > > > > > > > > > > > > > > going to make the release because the
> > community
> > > > > still did
> > > > > > > > >
> > > > > > > > > not
> > > > > > > > > > > > >
> > > > > > > > > > > > > approve
> > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > design. Nothing has changed since. I have
> not
> > > > seen
> > > > > any
> > > > > > > > >
> > > > > > > > > design
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > discussions.
> > > > > > > > > > > > > > > > > At this point, I have no confidence that
> the
> > > > > Service Grid
> > > > > > > > > > >
> > > > > > > > > > > changes
> > > > > > > > > > > > > > will
> > > > > > > > > > > > > > > make
> > > > > > > > > > > > > > > > > it into the 2.8 release. The 2.7 release
> > seems
> > > > out
> > > > > of
> > > > > > > > >
> > > > > > > > > question
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > altogether.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Also, Nikolay is a release manager. We
> should
> > > let
> > > > > him
> > > > > > > > >
> > > > > > > > > drive the
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > release. To
> > > > > > > > > > > > > > > > > my knowledge, he is doing a great job and
> the
> > > > > release is
> > > > > > > > >
> > > > > > > > > going
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > according to
> > > > > > > > > > > > > > > > > the schedule he proposed.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > D.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at 4:31 AM Dmitriy
> > Pavlov
> > > <
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Hi Dmitriy, Vladimir,
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > I suggest we stop this nonsense with
> > release
> > > > > > > > >
> > > > > > > > > dates-pushing
> > > > > > > > > > > > >
> > > > > > > > > > > > > because
> > > > > > > > > > > > > > of
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > some
> > > > > > > > > > > > > > > > > > open question.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Just because you disagreed with any
> > > > > include/exclude
> > > > > > > > >
> > > > > > > > > something
> > > > > > > > > > > > >
> > > > > > > > > > > > > into
> > > > > > > > > > > > > > > scope,
> > > > > > > > > > > > > > > > > > does not mean that whole community
> > disagreed.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > If folks will start a separate discussion
> > > with
> > > > > results
> > > > > > > > >
> > > > > > > > > of the
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > review, I
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > see
> > > > > > > > > > > > > > > > > > no reasons to reject their contribution,
> > even
> > > > if
> > > > > we
> > > > > > > >
> > > > > > > > need
> > > > > > > > > to
> > > > > > > > > > > > >
> > > > > > > > > > > > > revisit
> > > > > > > > > > > > > > > our
> > > > > > > > > > > > > > > > > > agreements and wait for a couple of days
> > > more.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Am I missing some reason why dates are so
> > > > > fundamentally
> > > > > > > > > > >
> > > > > > > > > > > important
> > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > you?
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Sincerely,
> > > > > > > > > > > > > > > > > > Dmitriy Pavlov
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 12:20, Dmitriy
> > > > Setrakyan <
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > dsetrakyan@apache.org>:
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > If services is not ready, which it is
> > not,
> > > > > then we
> > > > > > > > >
> > > > > > > > > should
> > > > > > > > > > > > >
> > > > > > > > > > > > > include
> > > > > > > > > > > > > > > them
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > into
> > > > > > > > > > > > > > > > > > > the next release. There is no need to
> > force
> > > > > them into
> > > > > > > > >
> > > > > > > > > 2.7.
> > > > > > > > > > >
> > > > > > > > > > > I
> > > > > > > > > > > > > > > suggest we
> > > > > > > > > > > > > > > > > > > move according to the schedule we all
> > > agreed
> > > > > on.
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > D.
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at 1:22 AM Dmitriy
> > > > Pavlov
> > > > > <
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > Yes, so correct statement is
> "community
> > > did
> > > > > not
> > > > > > > >
> > > > > > > > make
> > > > > > > > > any
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > decisions
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > about
> > > > > > > > > > > > > > > > > > > > services not go to 2.7/ services are
> > out
> > > of
> > > > > scope".
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > If so, please forgive me my
> confusion.
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:19,
> Vladimir
> > > > > Ozerov <
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > Exactly. So correct statement is
> “it
> > is
> > > > up
> > > > > to
> > > > > > > > > > >
> > > > > > > > > > > *community*
> > > > > > > > > > > > > to
> > > > > > > > > > > > > > > decide
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > whether
> > > > > > > > > > > > > > > > > > > > > something goes to 2.7”.
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:11,
> Dmitriy
> > > > > Pavlov <
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > No, it is up to the community to
> > > > discuss
> > > > > after
> > > > > > > > >
> > > > > > > > > their
> > > > > > > > > > > > >
> > > > > > > > > > > > > review
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > results.
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:09,
> > > Vladimir
> > > > > Ozerov <
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > Did I read your words correctly
> > > that
> > > > > it is up
> > > > > > > > >
> > > > > > > > > to
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > implementor
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > of a
> > > > > > > > > > > > > > > > > > > > > single
> > > > > > > > > > > > > > > > > > > > > > > feature to decide whether
> release
> > > of
> > > > > all
> > > > > > > >
> > > > > > > > other
> > > > > > > > > > >
> > > > > > > > > > > features
> > > > > > > > > > > > > > and
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > fixes
> > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > > > > > > delayed?
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:00,
> > > Dmitriy
> > > > > Pavlov
> > > > > > > >
> > > > > > > > <
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > My point we can wait a bit
> for
> > > > > services
> > > > > > > > >
> > > > > > > > > because
> > > > > > > > > > > > > > > > > > > > > > > > 1 we are open-minded and we
> > > don't
> > > > > have
> > > > > > > > >
> > > > > > > > > outside
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > pressure
> > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > do
> > > > > > > > > > > > > > > > > > > > > release
> > > > > > > > > > > > > > > > > > > > > > in
> > > > > > > > > > > > > > > > > > > > > > > > October
> > > > > > > > > > > > > > > > > > > > > > > > 2 and services it is not
> some
> > > new
> > > > > feature,
> > > > > > > > >
> > > > > > > > > which
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > suddenly
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > appeared
> > > > > > > > > > > > > > > > > > > > > in
> > > > > > > > > > > > > > > > > > > > > > > > autumn, it is a well known
> and
> > > > > important
> > > > > > > > >
> > > > > > > > > feature.
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > So it is up to Vyacheslav,
> > Anton
> > > > and
> > > > > > > >
> > > > > > > > Nikolay
> > > > > > > > > to
> > > > > > > > > > > > >
> > > > > > > > > > > > > decide.
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > Decisions can be services are
> > not
> > > > > > > > >
> > > > > > > > > ready/ready to
> > > > > > > > > > > > >
> > > > > > > > > > > > > merge
> > > > > > > > > > > > > > > only
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > > master/ready
> > > > > > > > > > > > > > > > > > > > > > > > to merge to master and to
> 2.7.
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 10:46,
> > > > > Vladimir
> > > > > > > > >
> > > > > > > > > Ozerov <
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > Dmitry,
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > Community agreement was to
> > > > perform
> > > > > the
> > > > > > > > >
> > > > > > > > > release
> > > > > > > > > > >
> > > > > > > > > > > in
> > > > > > > > > > > > > > > October.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Of
> > > > > > > > > > > > > > > > > > > > > course
> > > > > > > > > > > > > > > > > > > > > > we
> > > > > > > > > > > > > > > > > > > > > > > > can
> > > > > > > > > > > > > > > > > > > > > > > > > wait a bit for services.
> Then
> > > we
> > > > > wait a
> > > > > > > > >
> > > > > > > > > bit for
> > > > > > > > > > > > >
> > > > > > > > > > > > > other
> > > > > > > > > > > > > > > cool
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > features
> > > > > > > > > > > > > > > > > > > > > > > ready
> > > > > > > > > > > > > > > > > > > > > > > > > by that time, then again
> and
> > > > > again, and
> > > > > > > > >
> > > > > > > > > release
> > > > > > > > > > > > >
> > > > > > > > > > > > > will
> > > > > > > > > > > > > > > never
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > happen.
> > > > > > > > > > > > > > > > > > > > > > And
> > > > > > > > > > > > > > > > > > > > > > > > > while we are waiting for
> new
> > > > > features to
> > > > > > > > >
> > > > > > > > > come,
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > already
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > completerd
> > > > > > > > > > > > > > > > > > > > > > > > features
> > > > > > > > > > > > > > > > > > > > > > > > > cannot be used by anyone.
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > This is why we have an
> > > agreement
> > > > > that if
> > > > > > > > > > >
> > > > > > > > > > > feature is
> > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > ready,
> > > > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > > > > should
> > > > > > > > > > > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > > > > > > > > moved to future release,
> > > instead
> > > > of
> > > > > > > > >
> > > > > > > > > shifting
> > > > > > > > > > > > >
> > > > > > > > > > > > > release.
> > > > > > > > > > > > > > > The
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > sole
> > > > > > > > > > > > > > > > > > > > > reason
> > > > > > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > > > > have strict dates when
> > > decisions
> > > > > are made
> > > > > > > > >
> > > > > > > > > is
> > > > > > > > > > >
> > > > > > > > > > > to let
> > > > > > > > > > > > > > > release
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > happen.
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at
> 2:22
> > AM
> > > > > Dmitriy
> > > > > > > > >
> > > > > > > > > Pavlov
> > > > > > > > > > >
> > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > Vladimir, I'm not
> > searching
> > > > for
> > > > > enemy,
> > > > > > > > >
> > > > > > > > > and
> > > > > > > > > > >
> > > > > > > > > > > not
> > > > > > > > > > > > > > > fighting
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > with
> > > > > > > > > > > > > > > > > > > > > you.
> > > > > > > > > > > > > > > > > > > > > > > I'm
> > > > > > > > > > > > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > > > > > > > > > > happy about cases when we
> > are
> > > > > hurrying.
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > We can't fix test, fill
> > > ticket
> > > > > details,
> > > > > > > > >
> > > > > > > > > can't
> > > > > > > > > > > > >
> > > > > > > > > > > > > wait
> > > > > > > > > > > > > > > for
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > contributions
> > > > > > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > > > > > finish their tasks. It
> is
> > > not
> > > > > best
> > > > > > > >
> > > > > > > > idea
> > > > > > > > > to
> > > > > > > > > > >
> > > > > > > > > > > use
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > experience
> > > > > > > > > > > > > > > > > > > from
> > > > > > > > > > > > > > > > > > > > > > > > > commercial
> > > > > > > > > > > > > > > > > > > > > > > > > > companies in open source.
> > Are
> > > > > there any
> > > > > > > > > > >
> > > > > > > > > > > pressure
> > > > > > > > > > > > > > > outside
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > community?
> > > > > > > > > > > > > > > > > > > > > > > Did
> > > > > > > > > > > > > > > > > > > > > > > > > > someone promised rest of
> > > > > features to be
> > > > > > > > > > >
> > > > > > > > > > > released
> > > > > > > > > > > > > at
> > > > > > > > > > > > > > > 30
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > September?
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > Let's remember principle
> > > > > do-orcracy,
> > > > > > > > >
> > > > > > > > > power of
> > > > > > > > > > > > >
> > > > > > > > > > > > > those
> > > > > > > > > > > > > > > who
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > do.
> > > > > > > > > > > > > > > > > > > If
> > > > > > > > > > > > > > > > > > > > > > > > contribor
> > > > > > > > > > > > > > > > > > > > > > > > > > does change and reviewer
> > does
> > > > > review,
> > > > > > > > >
> > > > > > > > > let's
> > > > > > > > > > >
> > > > > > > > > > > give
> > > > > > > > > > > > > > > right of
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > making
> > > > > > > > > > > > > > > > > > > > > > > > decision
> > > > > > > > > > > > > > > > > > > > > > > > > > to them, but not to some
> > > closed
> > > > > club of
> > > > > > > > > > >
> > > > > > > > > > > people
> > > > > > > > > > > > > who
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > privately
> > > > > > > > > > > > > > > > > > > > > > discuss
> > > > > > > > > > > > > > > > > > > > > > > > > > something.
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > Sincerely
> > > > > > > > > > > > > > > > > > > > > > > > > > Dmitriy Pavlov
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г.,
> 23:42
> > > > > Vyacheslav
> > > > > > > > > > >
> > > > > > > > > > > Daradur <
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > daradurvs@gmail.com
> > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > Hi Igniters!
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > As I have written about
> > > > > Service Grid
> > > > > > > > > > >
> > > > > > > > > > > before [1]
> > > > > > > > > > > > > > I'm
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > finalizing
> > > > > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > > > > > solution to be sure
> that
> > > > > > > > >
> > > > > > > > > implementation is
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > reliable.
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > About including it in
> > 2.7,
> > > if
> > > > > we talk
> > > > > > > > >
> > > > > > > > > that
> > > > > > > > > > >
> > > > > > > > > > > code
> > > > > > > > > > > > > > > freeze
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > tomorrow
> > > > > > > > > > > > > > > > > > > > > > > then
> > > > > > > > > > > > > > > > > > > > > > > > > > > the solution is not
> ready
> > > to
> > > > > merge
> > > > > > > >
> > > > > > > > yet.
> > > > > > > > > > > > > > > > > > > > > > > > > > > I hope that
> prereviewers
> > > > Anton
> > > > > > > > >
> > > > > > > > > Vinogradov
> > > > > > > > > > >
> > > > > > > > > > > and
> > > > > > > > > > > > > > > Nikolay
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > Izhikov
> > > > > > > > > > > > > > > > > > > > > > will
> > > > > > > > > > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > > > > > > > > > > able to answer if
> > solution
> > > > out
> > > > > of
> > > > > > > > >
> > > > > > > > > scope or
> > > > > > > > > > >
> > > > > > > > > > > not
> > > > > > > > > > > > > > in a
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > couple
> > > > > > > > > > > > > > > > > > > of
> > > > > > > > > > > > > > > > > > > > > > days.
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > [1]
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > >
> > > >
> > >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-release-td34076.html#a34485
> > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at
> > > 11:14
> > > > > PM
> > > > > > > > >
> > > > > > > > > Dmitriy
> > > > > > > > > > > > >
> > > > > > > > > > > > > Pavlov <
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > Yes, I agree, NPE
> > during
> > > > WAL
> > > > > flush
> > > > > > > >
> > > > > > > > is
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > definitely
> > > > > > > > > > > > > > > a
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > blocker.
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > It is strange why the
> > > > > current test
> > > > > > > > >
> > > > > > > > > set
> > > > > > > > > > >
> > > > > > > > > > > did
> > > > > > > > > > > > > not
> > > > > > > > > > > > > > > fail
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > after
> > > > > > > > > > > > > > > > > > > > > > commit.
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г.
> в
> > > > 21:45,
> > > > > > > >
> > > > > > > > Andrey
> > > > > > > > > > > > >
> > > > > > > > > > > > > Kuznetsov
> > > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > stkuzma@gmail.com
> > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > Igniters,
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > I've bumped into a
> > new
> > > > bug
> > > > > in WAL
> > > > > > > > > > >
> > > > > > > > > > > manager
> > > > > > > > > > > > > > > recently,
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > see
> > > > > > > > > > > > > > > > > > > > > [1].
> > > > > > > > > > > > > > > > > > > > > > It
> > > > > > > > > > > > > > > > > > > > > > > > > looks
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > critical enough,
> and
> > > can
> > > > > be a
> > > > > > > >
> > > > > > > > good
> > > > > > > > > > > > >
> > > > > > > > > > > > > candidate
> > > > > > > > > > > > > > > for
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > fixing
> > > > > > > > > > > > > > > > > > > > > > before
> > > > > > > > > > > > > > > > > > > > > > > > 2.7
> > > > > > > > > > > > > > > > > > > > > > > > > > > release.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > Do you agree?
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > [1]
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > >
> > > > > https://issues.apache.org/jira/browse/IGNITE-9731
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018
> г.
> > в
> > > > > 19:45,
> > > > > > > > >
> > > > > > > > > Dmitriy
> > > > > > > > > > > > >
> > > > > > > > > > > > > Pavlov
> > > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I need
> > Vhyacheslav's
> > > > > opinion to
> > > > > > > > >
> > > > > > > > > be
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > absolutely
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > sure
> > > > > > > > > > > > > > > > > > > what
> > > > > > > > > > > > > > > > > > > > > > > status
> > > > > > > > > > > > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > > > > > > > > > > > > now.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > We never
> committed
> > to
> > > > > dates of
> > > > > > > > > > >
> > > > > > > > > > > release,
> > > > > > > > > > > > > as
> > > > > > > > > > > > > > > well.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > I
> > > > > > > > > > > > > > > > > > > > don't
> > > > > > > > > > > > > > > > > > > > > > > quite
> > > > > > > > > > > > > > > > > > > > > > > > > > > understand
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > what can mean
> 'the
> > > > > community
> > > > > > > > > > >
> > > > > > > > > > > committed to
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > doing/releasing
> > > > > > > > > > > > > > > > > > > > > > > > > > something'.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > About SG, I also
> > > > > concerned why
> > > > > > > > >
> > > > > > > > > such
> > > > > > > > > > >
> > > > > > > > > > > a big
> > > > > > > > > > > > > > > feature
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > has
> > > > > > > > > > > > > > > > > > > > > > quite a
> > > > > > > > > > > > > > > > > > > > > > > > few
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > discussions on
> the
> > > > list.
> > > > > But it
> > > > > > > > >
> > > > > > > > > is
> > > > > > > > > > > > >
> > > > > > > > > > > > > another
> > > > > > > > > > > > > > > story.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018
> > г.
> > > в
> > > > > 19:33,
> > > > > > > > > > >
> > > > > > > > > > > Vladimir
> > > > > > > > > > > > > > > Ozerov <
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Folks,
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Please stop
> > looking
> > > > for
> > > > > > > >
> > > > > > > > enemies
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > everywhere.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Just
> > > > > > > > > > > > > > > > > > > went
> > > > > > > > > > > > > > > > > > > > > > > through
> > > > > > > > > > > > > > > > > > > > > > > > > > this
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > thread
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > and search for
> > > > > "service"
> > > > > > > >
> > > > > > > > word.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27,
> > > 2018
> > > > > at 7:30
> > > > > > > >
> > > > > > > > PM
> > > > > > > > > > >
> > > > > > > > > > > Denis
> > > > > > > > > > > > > > > Magda <
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > dmagda@apache.org
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Denis, as
> PMC
> > > > > Chair,
> > > > > > > >
> > > > > > > > could
> > > > > > > > > you
> > > > > > > > > > > > >
> > > > > > > > > > > > > please
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > control,
> > > > > > > > > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > > > > > > > > Service
> > > > > > > > > > > > > > > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > inclusion/exclusion is
> > > > > > > > > > >
> > > > > > > > > > > discussed
> > > > > > > > > > > > > > > properly
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > according
> > > > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > > > > > Apache
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > Way.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > It's fine
> when
> > > > > > > > > > > > >
> > > > > > > > > > > > > committers/contributors
> > > > > > > > > > > > > > > have
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > private
> > > > > > > > > > > > > > > > > > > > > > > > > discussions
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > related
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > a feature
> > they've
> > > > > been
> > > > > > > > >
> > > > > > > > > working
> > > > > > > > > > >
> > > > > > > > > > > on.
> > > > > > > > > > > > > Not
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > everything
> > > > > > > > > > > > > > > > > > > > > should
> > > > > > > > > > > > > > > > > > > > > > > go
> > > > > > > > > > > > > > > > > > > > > > > > > > > through
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > dev
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > list.
> > Otherwise,
> > > it
> > > > > will be
> > > > > > > > > > > > >
> > > > > > > > > > > > > inundated.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > However,
> > > > > > > > > > > > > > > > > > > > > agree,
> >
Re: Apache Ignite 2.7 release
Posted by Dmitriy Pavlov <dp...@gmail.com>.
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 <vo...@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 <ds...@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 <vo...@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 <ni...@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 <stkuzma@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.spb@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 <
> > nizhikov@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 <
> > > > > > >
> > > > > > > daradurvs@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 <
> > > > > > > >
> > > > > > > > dsetrakyan@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.spb@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 <
> > > > dmagda@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 <
> > > > > > > > > >
> > > > > > > > > > nizhikov@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 <
> > > > > > > > > > > >
> > > > > > > > > > > > dsetrakyan@apache.org
> > > > > > > > > > > > > > :
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > We agreed in the beginning of this thread
> that
> > > > Service
> > > > > > >
> > > > > > > Grid
> > > > > > > > > >
> > > > > > > > > > changes
> > > > > > > > > > > > > > are not
> > > > > > > > > > > > > > > > going to make the release because the
> community
> > > > still did
> > > > > > > >
> > > > > > > > not
> > > > > > > > > > > >
> > > > > > > > > > > > approve
> > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > design. Nothing has changed since. I have not
> > > seen
> > > > any
> > > > > > > >
> > > > > > > > design
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > discussions.
> > > > > > > > > > > > > > > > At this point, I have no confidence that the
> > > > Service Grid
> > > > > > > > > >
> > > > > > > > > > changes
> > > > > > > > > > > > > will
> > > > > > > > > > > > > > make
> > > > > > > > > > > > > > > > it into the 2.8 release. The 2.7 release
> seems
> > > out
> > > > of
> > > > > > > >
> > > > > > > > question
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > altogether.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Also, Nikolay is a release manager. We should
> > let
> > > > him
> > > > > > > >
> > > > > > > > drive the
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > release. To
> > > > > > > > > > > > > > > > my knowledge, he is doing a great job and the
> > > > release is
> > > > > > > >
> > > > > > > > going
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > according to
> > > > > > > > > > > > > > > > the schedule he proposed.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > D.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at 4:31 AM Dmitriy
> Pavlov
> > <
> > > > > > > > > > > > >
> > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Hi Dmitriy, Vladimir,
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > I suggest we stop this nonsense with
> release
> > > > > > > >
> > > > > > > > dates-pushing
> > > > > > > > > > > >
> > > > > > > > > > > > because
> > > > > > > > > > > > > of
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > some
> > > > > > > > > > > > > > > > > open question.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Just because you disagreed with any
> > > > include/exclude
> > > > > > > >
> > > > > > > > something
> > > > > > > > > > > >
> > > > > > > > > > > > into
> > > > > > > > > > > > > > scope,
> > > > > > > > > > > > > > > > > does not mean that whole community
> disagreed.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > If folks will start a separate discussion
> > with
> > > > results
> > > > > > > >
> > > > > > > > of the
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > review, I
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > see
> > > > > > > > > > > > > > > > > no reasons to reject their contribution,
> even
> > > if
> > > > we
> > > > > > >
> > > > > > > need
> > > > > > > > to
> > > > > > > > > > > >
> > > > > > > > > > > > revisit
> > > > > > > > > > > > > > our
> > > > > > > > > > > > > > > > > agreements and wait for a couple of days
> > more.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Am I missing some reason why dates are so
> > > > fundamentally
> > > > > > > > > >
> > > > > > > > > > important
> > > > > > > > > > > > > to
> > > > > > > > > > > > > > you?
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Sincerely,
> > > > > > > > > > > > > > > > > Dmitriy Pavlov
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 12:20, Dmitriy
> > > Setrakyan <
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > dsetrakyan@apache.org>:
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > If services is not ready, which it is
> not,
> > > > then we
> > > > > > > >
> > > > > > > > should
> > > > > > > > > > > >
> > > > > > > > > > > > include
> > > > > > > > > > > > > > them
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > into
> > > > > > > > > > > > > > > > > > the next release. There is no need to
> force
> > > > them into
> > > > > > > >
> > > > > > > > 2.7.
> > > > > > > > > >
> > > > > > > > > > I
> > > > > > > > > > > > > > suggest we
> > > > > > > > > > > > > > > > > > move according to the schedule we all
> > agreed
> > > > on.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > D.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at 1:22 AM Dmitriy
> > > Pavlov
> > > > <
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > Yes, so correct statement is "community
> > did
> > > > not
> > > > > > >
> > > > > > > make
> > > > > > > > any
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > decisions
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > about
> > > > > > > > > > > > > > > > > > > services not go to 2.7/ services are
> out
> > of
> > > > scope".
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > If so, please forgive me my confusion.
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:19, Vladimir
> > > > Ozerov <
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > Exactly. So correct statement is “it
> is
> > > up
> > > > to
> > > > > > > > > >
> > > > > > > > > > *community*
> > > > > > > > > > > > to
> > > > > > > > > > > > > > decide
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > whether
> > > > > > > > > > > > > > > > > > > > something goes to 2.7”.
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:11, Dmitriy
> > > > Pavlov <
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > No, it is up to the community to
> > > discuss
> > > > after
> > > > > > > >
> > > > > > > > their
> > > > > > > > > > > >
> > > > > > > > > > > > review
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > results.
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:09,
> > Vladimir
> > > > Ozerov <
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > Did I read your words correctly
> > that
> > > > it is up
> > > > > > > >
> > > > > > > > to
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > implementor
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > of a
> > > > > > > > > > > > > > > > > > > > single
> > > > > > > > > > > > > > > > > > > > > > feature to decide whether release
> > of
> > > > all
> > > > > > >
> > > > > > > other
> > > > > > > > > >
> > > > > > > > > > features
> > > > > > > > > > > > > and
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > fixes
> > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > > > > > delayed?
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:00,
> > Dmitriy
> > > > Pavlov
> > > > > > >
> > > > > > > <
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > My point we can wait a bit for
> > > > services
> > > > > > > >
> > > > > > > > because
> > > > > > > > > > > > > > > > > > > > > > > 1 we are open-minded and we
> > don't
> > > > have
> > > > > > > >
> > > > > > > > outside
> > > > > > > > > > > > >
> > > > > > > > > > > > > pressure
> > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > do
> > > > > > > > > > > > > > > > > > > > release
> > > > > > > > > > > > > > > > > > > > > in
> > > > > > > > > > > > > > > > > > > > > > > October
> > > > > > > > > > > > > > > > > > > > > > > 2 and services it is not some
> > new
> > > > feature,
> > > > > > > >
> > > > > > > > which
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > suddenly
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > appeared
> > > > > > > > > > > > > > > > > > > > in
> > > > > > > > > > > > > > > > > > > > > > > autumn, it is a well known and
> > > > important
> > > > > > > >
> > > > > > > > feature.
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > So it is up to Vyacheslav,
> Anton
> > > and
> > > > > > >
> > > > > > > Nikolay
> > > > > > > > to
> > > > > > > > > > > >
> > > > > > > > > > > > decide.
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > Decisions can be services are
> not
> > > > > > > >
> > > > > > > > ready/ready to
> > > > > > > > > > > >
> > > > > > > > > > > > merge
> > > > > > > > > > > > > > only
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > master/ready
> > > > > > > > > > > > > > > > > > > > > > > to merge to master and to 2.7.
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 10:46,
> > > > Vladimir
> > > > > > > >
> > > > > > > > Ozerov <
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > Dmitry,
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > Community agreement was to
> > > perform
> > > > the
> > > > > > > >
> > > > > > > > release
> > > > > > > > > >
> > > > > > > > > > in
> > > > > > > > > > > > > > October.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Of
> > > > > > > > > > > > > > > > > > > > course
> > > > > > > > > > > > > > > > > > > > > we
> > > > > > > > > > > > > > > > > > > > > > > can
> > > > > > > > > > > > > > > > > > > > > > > > wait a bit for services. Then
> > we
> > > > wait a
> > > > > > > >
> > > > > > > > bit for
> > > > > > > > > > > >
> > > > > > > > > > > > other
> > > > > > > > > > > > > > cool
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > features
> > > > > > > > > > > > > > > > > > > > > > ready
> > > > > > > > > > > > > > > > > > > > > > > > by that time, then again and
> > > > again, and
> > > > > > > >
> > > > > > > > release
> > > > > > > > > > > >
> > > > > > > > > > > > will
> > > > > > > > > > > > > > never
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > happen.
> > > > > > > > > > > > > > > > > > > > > And
> > > > > > > > > > > > > > > > > > > > > > > > while we are waiting for new
> > > > features to
> > > > > > > >
> > > > > > > > come,
> > > > > > > > > > > > >
> > > > > > > > > > > > > already
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > completerd
> > > > > > > > > > > > > > > > > > > > > > > features
> > > > > > > > > > > > > > > > > > > > > > > > cannot be used by anyone.
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > This is why we have an
> > agreement
> > > > that if
> > > > > > > > > >
> > > > > > > > > > feature is
> > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > ready,
> > > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > > > should
> > > > > > > > > > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > > > > > > > moved to future release,
> > instead
> > > of
> > > > > > > >
> > > > > > > > shifting
> > > > > > > > > > > >
> > > > > > > > > > > > release.
> > > > > > > > > > > > > > The
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > sole
> > > > > > > > > > > > > > > > > > > > reason
> > > > > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > > > have strict dates when
> > decisions
> > > > are made
> > > > > > > >
> > > > > > > > is
> > > > > > > > > >
> > > > > > > > > > to let
> > > > > > > > > > > > > > release
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > happen.
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at 2:22
> AM
> > > > Dmitriy
> > > > > > > >
> > > > > > > > Pavlov
> > > > > > > > > >
> > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > Vladimir, I'm not
> searching
> > > for
> > > > enemy,
> > > > > > > >
> > > > > > > > and
> > > > > > > > > >
> > > > > > > > > > not
> > > > > > > > > > > > > > fighting
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > with
> > > > > > > > > > > > > > > > > > > > you.
> > > > > > > > > > > > > > > > > > > > > > I'm
> > > > > > > > > > > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > > > > > > > > > happy about cases when we
> are
> > > > hurrying.
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > We can't fix test, fill
> > ticket
> > > > details,
> > > > > > > >
> > > > > > > > can't
> > > > > > > > > > > >
> > > > > > > > > > > > wait
> > > > > > > > > > > > > > for
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > contributions
> > > > > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > > > > finish their tasks. It is
> > not
> > > > best
> > > > > > >
> > > > > > > idea
> > > > > > > > to
> > > > > > > > > >
> > > > > > > > > > use
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > experience
> > > > > > > > > > > > > > > > > > from
> > > > > > > > > > > > > > > > > > > > > > > > commercial
> > > > > > > > > > > > > > > > > > > > > > > > > companies in open source.
> Are
> > > > there any
> > > > > > > > > >
> > > > > > > > > > pressure
> > > > > > > > > > > > > > outside
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > community?
> > > > > > > > > > > > > > > > > > > > > > Did
> > > > > > > > > > > > > > > > > > > > > > > > > someone promised rest of
> > > > features to be
> > > > > > > > > >
> > > > > > > > > > released
> > > > > > > > > > > > at
> > > > > > > > > > > > > > 30
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > September?
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > Let's remember principle
> > > > do-orcracy,
> > > > > > > >
> > > > > > > > power of
> > > > > > > > > > > >
> > > > > > > > > > > > those
> > > > > > > > > > > > > > who
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > do.
> > > > > > > > > > > > > > > > > > If
> > > > > > > > > > > > > > > > > > > > > > > contribor
> > > > > > > > > > > > > > > > > > > > > > > > > does change and reviewer
> does
> > > > review,
> > > > > > > >
> > > > > > > > let's
> > > > > > > > > >
> > > > > > > > > > give
> > > > > > > > > > > > > > right of
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > making
> > > > > > > > > > > > > > > > > > > > > > > decision
> > > > > > > > > > > > > > > > > > > > > > > > > to them, but not to some
> > closed
> > > > club of
> > > > > > > > > >
> > > > > > > > > > people
> > > > > > > > > > > > who
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > privately
> > > > > > > > > > > > > > > > > > > > > discuss
> > > > > > > > > > > > > > > > > > > > > > > > > something.
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > Sincerely
> > > > > > > > > > > > > > > > > > > > > > > > > Dmitriy Pavlov
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г., 23:42
> > > > Vyacheslav
> > > > > > > > > >
> > > > > > > > > > Daradur <
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > daradurvs@gmail.com
> > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > Hi Igniters!
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > As I have written about
> > > > Service Grid
> > > > > > > > > >
> > > > > > > > > > before [1]
> > > > > > > > > > > > > I'm
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > finalizing
> > > > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > > > > solution to be sure that
> > > > > > > >
> > > > > > > > implementation is
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > reliable.
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > About including it in
> 2.7,
> > if
> > > > we talk
> > > > > > > >
> > > > > > > > that
> > > > > > > > > >
> > > > > > > > > > code
> > > > > > > > > > > > > > freeze
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > tomorrow
> > > > > > > > > > > > > > > > > > > > > > then
> > > > > > > > > > > > > > > > > > > > > > > > > > the solution is not ready
> > to
> > > > merge
> > > > > > >
> > > > > > > yet.
> > > > > > > > > > > > > > > > > > > > > > > > > > I hope that prereviewers
> > > Anton
> > > > > > > >
> > > > > > > > Vinogradov
> > > > > > > > > >
> > > > > > > > > > and
> > > > > > > > > > > > > > Nikolay
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Izhikov
> > > > > > > > > > > > > > > > > > > > > will
> > > > > > > > > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > > > > > > > > > able to answer if
> solution
> > > out
> > > > of
> > > > > > > >
> > > > > > > > scope or
> > > > > > > > > >
> > > > > > > > > > not
> > > > > > > > > > > > > in a
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > couple
> > > > > > > > > > > > > > > > > > of
> > > > > > > > > > > > > > > > > > > > > days.
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > [1]
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > >
> > > > > > >
> > > >
> > >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-release-td34076.html#a34485
> > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at
> > 11:14
> > > > PM
> > > > > > > >
> > > > > > > > Dmitriy
> > > > > > > > > > > >
> > > > > > > > > > > > Pavlov <
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > Yes, I agree, NPE
> during
> > > WAL
> > > > flush
> > > > > > >
> > > > > > > is
> > > > > > > > > > > > >
> > > > > > > > > > > > > definitely
> > > > > > > > > > > > > > a
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > blocker.
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > It is strange why the
> > > > current test
> > > > > > > >
> > > > > > > > set
> > > > > > > > > >
> > > > > > > > > > did
> > > > > > > > > > > > not
> > > > > > > > > > > > > > fail
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > after
> > > > > > > > > > > > > > > > > > > > > commit.
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в
> > > 21:45,
> > > > > > >
> > > > > > > Andrey
> > > > > > > > > > > >
> > > > > > > > > > > > Kuznetsov
> > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > stkuzma@gmail.com
> > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > Igniters,
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > I've bumped into a
> new
> > > bug
> > > > in WAL
> > > > > > > > > >
> > > > > > > > > > manager
> > > > > > > > > > > > > > recently,
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > see
> > > > > > > > > > > > > > > > > > > > [1].
> > > > > > > > > > > > > > > > > > > > > It
> > > > > > > > > > > > > > > > > > > > > > > > looks
> > > > > > > > > > > > > > > > > > > > > > > > > > > > critical enough, and
> > can
> > > > be a
> > > > > > >
> > > > > > > good
> > > > > > > > > > > >
> > > > > > > > > > > > candidate
> > > > > > > > > > > > > > for
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > fixing
> > > > > > > > > > > > > > > > > > > > > before
> > > > > > > > > > > > > > > > > > > > > > > 2.7
> > > > > > > > > > > > > > > > > > > > > > > > > > release.
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > Do you agree?
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > [1]
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-9731
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г.
> в
> > > > 19:45,
> > > > > > > >
> > > > > > > > Dmitriy
> > > > > > > > > > > >
> > > > > > > > > > > > Pavlov
> > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > I need
> Vhyacheslav's
> > > > opinion to
> > > > > > > >
> > > > > > > > be
> > > > > > > > > > > > >
> > > > > > > > > > > > > absolutely
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > sure
> > > > > > > > > > > > > > > > > > what
> > > > > > > > > > > > > > > > > > > > > > status
> > > > > > > > > > > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > > > > > > > > > > > now.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > We never committed
> to
> > > > dates of
> > > > > > > > > >
> > > > > > > > > > release,
> > > > > > > > > > > > as
> > > > > > > > > > > > > > well.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > I
> > > > > > > > > > > > > > > > > > > don't
> > > > > > > > > > > > > > > > > > > > > > quite
> > > > > > > > > > > > > > > > > > > > > > > > > > understand
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > what can mean 'the
> > > > community
> > > > > > > > > >
> > > > > > > > > > committed to
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > doing/releasing
> > > > > > > > > > > > > > > > > > > > > > > > > something'.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > About SG, I also
> > > > concerned why
> > > > > > > >
> > > > > > > > such
> > > > > > > > > >
> > > > > > > > > > a big
> > > > > > > > > > > > > > feature
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > has
> > > > > > > > > > > > > > > > > > > > > quite a
> > > > > > > > > > > > > > > > > > > > > > > few
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > discussions on the
> > > list.
> > > > But it
> > > > > > > >
> > > > > > > > is
> > > > > > > > > > > >
> > > > > > > > > > > > another
> > > > > > > > > > > > > > story.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018
> г.
> > в
> > > > 19:33,
> > > > > > > > > >
> > > > > > > > > > Vladimir
> > > > > > > > > > > > > > Ozerov <
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Folks,
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Please stop
> looking
> > > for
> > > > > > >
> > > > > > > enemies
> > > > > > > > > > > > >
> > > > > > > > > > > > > everywhere.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Just
> > > > > > > > > > > > > > > > > > went
> > > > > > > > > > > > > > > > > > > > > > through
> > > > > > > > > > > > > > > > > > > > > > > > > this
> > > > > > > > > > > > > > > > > > > > > > > > > > > > thread
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > and search for
> > > > "service"
> > > > > > >
> > > > > > > word.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27,
> > 2018
> > > > at 7:30
> > > > > > >
> > > > > > > PM
> > > > > > > > > >
> > > > > > > > > > Denis
> > > > > > > > > > > > > > Magda <
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > dmagda@apache.org
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Denis, as PMC
> > > > Chair,
> > > > > > >
> > > > > > > could
> > > > > > > > you
> > > > > > > > > > > >
> > > > > > > > > > > > please
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > control,
> > > > > > > > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > > > > > > > Service
> > > > > > > > > > > > > > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > inclusion/exclusion is
> > > > > > > > > >
> > > > > > > > > > discussed
> > > > > > > > > > > > > > properly
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > according
> > > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > > > > Apache
> > > > > > > > > > > > > > > > > > > > > > > > > > > > Way.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > It's fine when
> > > > > > > > > > > >
> > > > > > > > > > > > committers/contributors
> > > > > > > > > > > > > > have
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > private
> > > > > > > > > > > > > > > > > > > > > > > > discussions
> > > > > > > > > > > > > > > > > > > > > > > > > > > > related
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > a feature
> they've
> > > > been
> > > > > > > >
> > > > > > > > working
> > > > > > > > > >
> > > > > > > > > > on.
> > > > > > > > > > > > Not
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > everything
> > > > > > > > > > > > > > > > > > > > should
> > > > > > > > > > > > > > > > > > > > > > go
> > > > > > > > > > > > > > > > > > > > > > > > > > through
> > > > > > > > > > > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > dev
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > list.
> Otherwise,
> > it
> > > > will be
> > > > > > > > > > > >
> > > > > > > > > > > > inundated.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > However,
> > > > > > > > > > > > > > > > > > > > agree,
> > > > > > > > > > > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > architectural
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > and release
> > > > decisions need
> > > > > > > >
> > > > > > > > to be
> > > > > > > > > >
> > > > > > > > > > done
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > publicly.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Speaking about
> > > > Service
> > > > > > >
> > > > > > > Grid,
> > > > > > > > > >
> > > > > > > > > > there
> > > > > > > > > > > > was
> > > > > > > > > > > > > a
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > discussion
> > > > > > > > > > > > > > > > > > > > > where
> > > > > > > > > > > > > > > > > > > > > > I
> > > > > > > > > > > > > > > > > > > > > > > > saw
> > > > > > > > > > > > > > > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > was
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > questionable
> > > whether
> > > > it
> > > > > > >
> > > > > > > gets
> > > > > > > > > >
> > > > > > > > > > added to
> > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > release
> > > > > > > > > > > > > > > > > > or
> > > > > > > > > > > > > > > > > > > > > not.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > *Vladislav*,
> > could
> > > > you
> > > > > > >
> > > > > > > please
> > > > > > > > > >
> > > > > > > > > > shed
> > > > > > > > > > > > some
> > > > > > > > > > > > > > light
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > on
> > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > current
> > > > > > > > > > > > > > > > > > > > > > > > > > status of
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > service grid?
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27,
> > > 2018
> > > > at
> > > > > > >
> > > > > > > 9:12
> > > > > > > > AM
> > > > > > > > > > > >
> > > > > > > > > > > > Dmitriy
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Pavlov <
> > > > > > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Ok, let's
> wait
> > > for
> > > > > > >
> > > > > > > feedback
> > > > > > > > > >
> > > > > > > > > > from SG
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > Author(s)/Reviewer(s)
> > > > > > > > > > > > > > > > > > > > > > > > > > first. If
> > > > > > > > > > > > > > > > > > > > > >
Re: Apache Ignite 2.7 release
Posted by Vladimir Ozerov <vo...@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 <ds...@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 <vo...@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 <ni...@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 <st...@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.spb@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 <
> nizhikov@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 <
> > > > > >
> > > > > > daradurvs@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 <
> > > > > > >
> > > > > > > dsetrakyan@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.spb@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 <
> > > dmagda@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 <
> > > > > > > > >
> > > > > > > > > nizhikov@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 <
> > > > > > > > > > >
> > > > > > > > > > > dsetrakyan@apache.org
> > > > > > > > > > > > > :
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > We agreed in the beginning of this thread that
> > > Service
> > > > > >
> > > > > > Grid
> > > > > > > > >
> > > > > > > > > changes
> > > > > > > > > > > > > are not
> > > > > > > > > > > > > > > going to make the release because the community
> > > still did
> > > > > > >
> > > > > > > not
> > > > > > > > > > >
> > > > > > > > > > > approve
> > > > > > > > > > > > > the
> > > > > > > > > > > > > > > design. Nothing has changed since. I have not
> > seen
> > > any
> > > > > > >
> > > > > > > design
> > > > > > > > > > > > >
> > > > > > > > > > > > > discussions.
> > > > > > > > > > > > > > > At this point, I have no confidence that the
> > > Service Grid
> > > > > > > > >
> > > > > > > > > changes
> > > > > > > > > > > > will
> > > > > > > > > > > > > make
> > > > > > > > > > > > > > > it into the 2.8 release. The 2.7 release seems
> > out
> > > of
> > > > > > >
> > > > > > > question
> > > > > > > > > > > > >
> > > > > > > > > > > > > altogether.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Also, Nikolay is a release manager. We should
> let
> > > him
> > > > > > >
> > > > > > > drive the
> > > > > > > > > > > > >
> > > > > > > > > > > > > release. To
> > > > > > > > > > > > > > > my knowledge, he is doing a great job and the
> > > release is
> > > > > > >
> > > > > > > going
> > > > > > > > > > > > >
> > > > > > > > > > > > > according to
> > > > > > > > > > > > > > > the schedule he proposed.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > D.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at 4:31 AM Dmitriy Pavlov
> <
> > > > > > > > > > > >
> > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Hi Dmitriy, Vladimir,
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > I suggest we stop this nonsense with release
> > > > > > >
> > > > > > > dates-pushing
> > > > > > > > > > >
> > > > > > > > > > > because
> > > > > > > > > > > > of
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > some
> > > > > > > > > > > > > > > > open question.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Just because you disagreed with any
> > > include/exclude
> > > > > > >
> > > > > > > something
> > > > > > > > > > >
> > > > > > > > > > > into
> > > > > > > > > > > > > scope,
> > > > > > > > > > > > > > > > does not mean that whole community disagreed.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > If folks will start a separate discussion
> with
> > > results
> > > > > > >
> > > > > > > of the
> > > > > > > > > > > > >
> > > > > > > > > > > > > review, I
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > see
> > > > > > > > > > > > > > > > no reasons to reject their contribution, even
> > if
> > > we
> > > > > >
> > > > > > need
> > > > > > > to
> > > > > > > > > > >
> > > > > > > > > > > revisit
> > > > > > > > > > > > > our
> > > > > > > > > > > > > > > > agreements and wait for a couple of days
> more.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Am I missing some reason why dates are so
> > > fundamentally
> > > > > > > > >
> > > > > > > > > important
> > > > > > > > > > > > to
> > > > > > > > > > > > > you?
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Sincerely,
> > > > > > > > > > > > > > > > Dmitriy Pavlov
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 12:20, Dmitriy
> > Setrakyan <
> > > > > > > > > > > > >
> > > > > > > > > > > > > dsetrakyan@apache.org>:
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > If services is not ready, which it is not,
> > > then we
> > > > > > >
> > > > > > > should
> > > > > > > > > > >
> > > > > > > > > > > include
> > > > > > > > > > > > > them
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > into
> > > > > > > > > > > > > > > > > the next release. There is no need to force
> > > them into
> > > > > > >
> > > > > > > 2.7.
> > > > > > > > >
> > > > > > > > > I
> > > > > > > > > > > > > suggest we
> > > > > > > > > > > > > > > > > move according to the schedule we all
> agreed
> > > on.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > D.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at 1:22 AM Dmitriy
> > Pavlov
> > > <
> > > > > > > > > > > > >
> > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Yes, so correct statement is "community
> did
> > > not
> > > > > >
> > > > > > make
> > > > > > > any
> > > > > > > > > > > > >
> > > > > > > > > > > > > decisions
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > about
> > > > > > > > > > > > > > > > > > services not go to 2.7/ services are out
> of
> > > scope".
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > If so, please forgive me my confusion.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:19, Vladimir
> > > Ozerov <
> > > > > > > > > > > > >
> > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > Exactly. So correct statement is “it is
> > up
> > > to
> > > > > > > > >
> > > > > > > > > *community*
> > > > > > > > > > > to
> > > > > > > > > > > > > decide
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > whether
> > > > > > > > > > > > > > > > > > > something goes to 2.7”.
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:11, Dmitriy
> > > Pavlov <
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > No, it is up to the community to
> > discuss
> > > after
> > > > > > >
> > > > > > > their
> > > > > > > > > > >
> > > > > > > > > > > review
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > results.
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:09,
> Vladimir
> > > Ozerov <
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > Did I read your words correctly
> that
> > > it is up
> > > > > > >
> > > > > > > to
> > > > > > > > > > > > >
> > > > > > > > > > > > > implementor
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > of a
> > > > > > > > > > > > > > > > > > > single
> > > > > > > > > > > > > > > > > > > > > feature to decide whether release
> of
> > > all
> > > > > >
> > > > > > other
> > > > > > > > >
> > > > > > > > > features
> > > > > > > > > > > > and
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > fixes
> > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > > > > delayed?
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:00,
> Dmitriy
> > > Pavlov
> > > > > >
> > > > > > <
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > My point we can wait a bit for
> > > services
> > > > > > >
> > > > > > > because
> > > > > > > > > > > > > > > > > > > > > > 1 we are open-minded and we
> don't
> > > have
> > > > > > >
> > > > > > > outside
> > > > > > > > > > > >
> > > > > > > > > > > > pressure
> > > > > > > > > > > > > to
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > do
> > > > > > > > > > > > > > > > > > > release
> > > > > > > > > > > > > > > > > > > > in
> > > > > > > > > > > > > > > > > > > > > > October
> > > > > > > > > > > > > > > > > > > > > > 2 and services it is not some
> new
> > > feature,
> > > > > > >
> > > > > > > which
> > > > > > > > > > > > >
> > > > > > > > > > > > > suddenly
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > appeared
> > > > > > > > > > > > > > > > > > > in
> > > > > > > > > > > > > > > > > > > > > > autumn, it is a well known and
> > > important
> > > > > > >
> > > > > > > feature.
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > So it is up to Vyacheslav, Anton
> > and
> > > > > >
> > > > > > Nikolay
> > > > > > > to
> > > > > > > > > > >
> > > > > > > > > > > decide.
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > Decisions can be services are not
> > > > > > >
> > > > > > > ready/ready to
> > > > > > > > > > >
> > > > > > > > > > > merge
> > > > > > > > > > > > > only
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > master/ready
> > > > > > > > > > > > > > > > > > > > > > to merge to master and to 2.7.
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 10:46,
> > > Vladimir
> > > > > > >
> > > > > > > Ozerov <
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > Dmitry,
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > Community agreement was to
> > perform
> > > the
> > > > > > >
> > > > > > > release
> > > > > > > > >
> > > > > > > > > in
> > > > > > > > > > > > > October.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Of
> > > > > > > > > > > > > > > > > > > course
> > > > > > > > > > > > > > > > > > > > we
> > > > > > > > > > > > > > > > > > > > > > can
> > > > > > > > > > > > > > > > > > > > > > > wait a bit for services. Then
> we
> > > wait a
> > > > > > >
> > > > > > > bit for
> > > > > > > > > > >
> > > > > > > > > > > other
> > > > > > > > > > > > > cool
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > features
> > > > > > > > > > > > > > > > > > > > > ready
> > > > > > > > > > > > > > > > > > > > > > > by that time, then again and
> > > again, and
> > > > > > >
> > > > > > > release
> > > > > > > > > > >
> > > > > > > > > > > will
> > > > > > > > > > > > > never
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > happen.
> > > > > > > > > > > > > > > > > > > > And
> > > > > > > > > > > > > > > > > > > > > > > while we are waiting for new
> > > features to
> > > > > > >
> > > > > > > come,
> > > > > > > > > > > >
> > > > > > > > > > > > already
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > completerd
> > > > > > > > > > > > > > > > > > > > > > features
> > > > > > > > > > > > > > > > > > > > > > > cannot be used by anyone.
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > This is why we have an
> agreement
> > > that if
> > > > > > > > >
> > > > > > > > > feature is
> > > > > > > > > > > > not
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > ready,
> > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > > should
> > > > > > > > > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > > > > > > moved to future release,
> instead
> > of
> > > > > > >
> > > > > > > shifting
> > > > > > > > > > >
> > > > > > > > > > > release.
> > > > > > > > > > > > > The
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > sole
> > > > > > > > > > > > > > > > > > > reason
> > > > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > > have strict dates when
> decisions
> > > are made
> > > > > > >
> > > > > > > is
> > > > > > > > >
> > > > > > > > > to let
> > > > > > > > > > > > > release
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > happen.
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at 2:22 AM
> > > Dmitriy
> > > > > > >
> > > > > > > Pavlov
> > > > > > > > >
> > > > > > > > > <
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > Vladimir, I'm not searching
> > for
> > > enemy,
> > > > > > >
> > > > > > > and
> > > > > > > > >
> > > > > > > > > not
> > > > > > > > > > > > > fighting
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > with
> > > > > > > > > > > > > > > > > > > you.
> > > > > > > > > > > > > > > > > > > > > I'm
> > > > > > > > > > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > > > > > > > > happy about cases when we are
> > > hurrying.
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > We can't fix test, fill
> ticket
> > > details,
> > > > > > >
> > > > > > > can't
> > > > > > > > > > >
> > > > > > > > > > > wait
> > > > > > > > > > > > > for
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > contributions
> > > > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > > > finish their tasks. It is
> not
> > > best
> > > > > >
> > > > > > idea
> > > > > > > to
> > > > > > > > >
> > > > > > > > > use
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > experience
> > > > > > > > > > > > > > > > > from
> > > > > > > > > > > > > > > > > > > > > > > commercial
> > > > > > > > > > > > > > > > > > > > > > > > companies in open source. Are
> > > there any
> > > > > > > > >
> > > > > > > > > pressure
> > > > > > > > > > > > > outside
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > community?
> > > > > > > > > > > > > > > > > > > > > Did
> > > > > > > > > > > > > > > > > > > > > > > > someone promised rest of
> > > features to be
> > > > > > > > >
> > > > > > > > > released
> > > > > > > > > > > at
> > > > > > > > > > > > > 30
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > September?
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > Let's remember principle
> > > do-orcracy,
> > > > > > >
> > > > > > > power of
> > > > > > > > > > >
> > > > > > > > > > > those
> > > > > > > > > > > > > who
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > do.
> > > > > > > > > > > > > > > > > If
> > > > > > > > > > > > > > > > > > > > > > contribor
> > > > > > > > > > > > > > > > > > > > > > > > does change and reviewer does
> > > review,
> > > > > > >
> > > > > > > let's
> > > > > > > > >
> > > > > > > > > give
> > > > > > > > > > > > > right of
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > making
> > > > > > > > > > > > > > > > > > > > > > decision
> > > > > > > > > > > > > > > > > > > > > > > > to them, but not to some
> closed
> > > club of
> > > > > > > > >
> > > > > > > > > people
> > > > > > > > > > > who
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > privately
> > > > > > > > > > > > > > > > > > > > discuss
> > > > > > > > > > > > > > > > > > > > > > > > something.
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > Sincerely
> > > > > > > > > > > > > > > > > > > > > > > > Dmitriy Pavlov
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г., 23:42
> > > Vyacheslav
> > > > > > > > >
> > > > > > > > > Daradur <
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > daradurvs@gmail.com
> > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > Hi Igniters!
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > As I have written about
> > > Service Grid
> > > > > > > > >
> > > > > > > > > before [1]
> > > > > > > > > > > > I'm
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > finalizing
> > > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > > > solution to be sure that
> > > > > > >
> > > > > > > implementation is
> > > > > > > > > > > > >
> > > > > > > > > > > > > reliable.
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > About including it in 2.7,
> if
> > > we talk
> > > > > > >
> > > > > > > that
> > > > > > > > >
> > > > > > > > > code
> > > > > > > > > > > > > freeze
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > tomorrow
> > > > > > > > > > > > > > > > > > > > > then
> > > > > > > > > > > > > > > > > > > > > > > > > the solution is not ready
> to
> > > merge
> > > > > >
> > > > > > yet.
> > > > > > > > > > > > > > > > > > > > > > > > > I hope that prereviewers
> > Anton
> > > > > > >
> > > > > > > Vinogradov
> > > > > > > > >
> > > > > > > > > and
> > > > > > > > > > > > > Nikolay
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Izhikov
> > > > > > > > > > > > > > > > > > > > will
> > > > > > > > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > > > > > > > > able to answer if solution
> > out
> > > of
> > > > > > >
> > > > > > > scope or
> > > > > > > > >
> > > > > > > > > not
> > > > > > > > > > > > in a
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > couple
> > > > > > > > > > > > > > > > > of
> > > > > > > > > > > > > > > > > > > > days.
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > [1]
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > >
> > > > > >
> > >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-release-td34076.html#a34485
> > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at
> 11:14
> > > PM
> > > > > > >
> > > > > > > Dmitriy
> > > > > > > > > > >
> > > > > > > > > > > Pavlov <
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > Yes, I agree, NPE during
> > WAL
> > > flush
> > > > > >
> > > > > > is
> > > > > > > > > > > >
> > > > > > > > > > > > definitely
> > > > > > > > > > > > > a
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > blocker.
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > It is strange why the
> > > current test
> > > > > > >
> > > > > > > set
> > > > > > > > >
> > > > > > > > > did
> > > > > > > > > > > not
> > > > > > > > > > > > > fail
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > after
> > > > > > > > > > > > > > > > > > > > commit.
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в
> > 21:45,
> > > > > >
> > > > > > Andrey
> > > > > > > > > > >
> > > > > > > > > > > Kuznetsov
> > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > stkuzma@gmail.com
> > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > Igniters,
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > I've bumped into a new
> > bug
> > > in WAL
> > > > > > > > >
> > > > > > > > > manager
> > > > > > > > > > > > > recently,
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > see
> > > > > > > > > > > > > > > > > > > [1].
> > > > > > > > > > > > > > > > > > > > It
> > > > > > > > > > > > > > > > > > > > > > > looks
> > > > > > > > > > > > > > > > > > > > > > > > > > > critical enough, and
> can
> > > be a
> > > > > >
> > > > > > good
> > > > > > > > > > >
> > > > > > > > > > > candidate
> > > > > > > > > > > > > for
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > fixing
> > > > > > > > > > > > > > > > > > > > before
> > > > > > > > > > > > > > > > > > > > > > 2.7
> > > > > > > > > > > > > > > > > > > > > > > > > release.
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > Do you agree?
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > [1]
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > https://issues.apache.org/jira/browse/IGNITE-9731
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в
> > > 19:45,
> > > > > > >
> > > > > > > Dmitriy
> > > > > > > > > > >
> > > > > > > > > > > Pavlov
> > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > I need Vhyacheslav's
> > > opinion to
> > > > > > >
> > > > > > > be
> > > > > > > > > > > >
> > > > > > > > > > > > absolutely
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > sure
> > > > > > > > > > > > > > > > > what
> > > > > > > > > > > > > > > > > > > > > status
> > > > > > > > > > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > > > > > > > > > > now.
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > We never committed to
> > > dates of
> > > > > > > > >
> > > > > > > > > release,
> > > > > > > > > > > as
> > > > > > > > > > > > > well.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > I
> > > > > > > > > > > > > > > > > > don't
> > > > > > > > > > > > > > > > > > > > > quite
> > > > > > > > > > > > > > > > > > > > > > > > > understand
> > > > > > > > > > > > > > > > > > > > > > > > > > > > what can mean 'the
> > > community
> > > > > > > > >
> > > > > > > > > committed to
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > doing/releasing
> > > > > > > > > > > > > > > > > > > > > > > > something'.
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > About SG, I also
> > > concerned why
> > > > > > >
> > > > > > > such
> > > > > > > > >
> > > > > > > > > a big
> > > > > > > > > > > > > feature
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > has
> > > > > > > > > > > > > > > > > > > > quite a
> > > > > > > > > > > > > > > > > > > > > > few
> > > > > > > > > > > > > > > > > > > > > > > > > > > > discussions on the
> > list.
> > > But it
> > > > > > >
> > > > > > > is
> > > > > > > > > > >
> > > > > > > > > > > another
> > > > > > > > > > > > > story.
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г.
> в
> > > 19:33,
> > > > > > > > >
> > > > > > > > > Vladimir
> > > > > > > > > > > > > Ozerov <
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > Folks,
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > Please stop looking
> > for
> > > > > >
> > > > > > enemies
> > > > > > > > > > > >
> > > > > > > > > > > > everywhere.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Just
> > > > > > > > > > > > > > > > > went
> > > > > > > > > > > > > > > > > > > > > through
> > > > > > > > > > > > > > > > > > > > > > > > this
> > > > > > > > > > > > > > > > > > > > > > > > > > > thread
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > and search for
> > > "service"
> > > > > >
> > > > > > word.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27,
> 2018
> > > at 7:30
> > > > > >
> > > > > > PM
> > > > > > > > >
> > > > > > > > > Denis
> > > > > > > > > > > > > Magda <
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > dmagda@apache.org
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Denis, as PMC
> > > Chair,
> > > > > >
> > > > > > could
> > > > > > > you
> > > > > > > > > > >
> > > > > > > > > > > please
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > control,
> > > > > > > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > > > > > > Service
> > > > > > > > > > > > > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > inclusion/exclusion is
> > > > > > > > >
> > > > > > > > > discussed
> > > > > > > > > > > > > properly
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > according
> > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > > > Apache
> > > > > > > > > > > > > > > > > > > > > > > > > > > Way.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > It's fine when
> > > > > > > > > > >
> > > > > > > > > > > committers/contributors
> > > > > > > > > > > > > have
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > private
> > > > > > > > > > > > > > > > > > > > > > > discussions
> > > > > > > > > > > > > > > > > > > > > > > > > > > related
> > > > > > > > > > > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > a feature they've
> > > been
> > > > > > >
> > > > > > > working
> > > > > > > > >
> > > > > > > > > on.
> > > > > > > > > > > Not
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > everything
> > > > > > > > > > > > > > > > > > > should
> > > > > > > > > > > > > > > > > > > > > go
> > > > > > > > > > > > > > > > > > > > > > > > > through
> > > > > > > > > > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > dev
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > list. Otherwise,
> it
> > > will be
> > > > > > > > > > >
> > > > > > > > > > > inundated.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > However,
> > > > > > > > > > > > > > > > > > > agree,
> > > > > > > > > > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > > > > > > > > > > > > architectural
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > and release
> > > decisions need
> > > > > > >
> > > > > > > to be
> > > > > > > > >
> > > > > > > > > done
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > publicly.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Speaking about
> > > Service
> > > > > >
> > > > > > Grid,
> > > > > > > > >
> > > > > > > > > there
> > > > > > > > > > > was
> > > > > > > > > > > > a
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > discussion
> > > > > > > > > > > > > > > > > > > > where
> > > > > > > > > > > > > > > > > > > > > I
> > > > > > > > > > > > > > > > > > > > > > > saw
> > > > > > > > > > > > > > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > was
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > questionable
> > whether
> > > it
> > > > > >
> > > > > > gets
> > > > > > > > >
> > > > > > > > > added to
> > > > > > > > > > > > the
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > release
> > > > > > > > > > > > > > > > > or
> > > > > > > > > > > > > > > > > > > > not.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > *Vladislav*,
> could
> > > you
> > > > > >
> > > > > > please
> > > > > > > > >
> > > > > > > > > shed
> > > > > > > > > > > some
> > > > > > > > > > > > > light
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > on
> > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > current
> > > > > > > > > > > > > > > > > > > > > > > > > status of
> > > > > > > > > > > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > service grid?
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27,
> > 2018
> > > at
> > > > > >
> > > > > > 9:12
> > > > > > > AM
> > > > > > > > > > >
> > > > > > > > > > > Dmitriy
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Pavlov <
> > > > > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Ok, let's wait
> > for
> > > > > >
> > > > > > feedback
> > > > > > > > >
> > > > > > > > > from SG
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > Author(s)/Reviewer(s)
> > > > > > > > > > > > > > > > > > > > > > > > > first. If
> > > > > > > > > > > > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > not ready, ok.
> > But
> > > I
> > > > > > >
> > > > > > > thought
> > > > > > > > >
> > > > > > > > > it is
> > > > > > > > > > > > > almost
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > done.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I apologize if
> I
> > > missed
> > > > > > >
> > > > > > > some
> > > > > > > > > > > > >
> > > > > > > > > > > > > discussion (it
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > can
> > > > > > > > > > > > > > > > > > > > happen),
> > > > > > > > > > > > > > > > > > > > > > but
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > According to
> the
> > > > > >
> > > > > > statement
> > > > > > > "our
> > > > > > > > > > > >
> > > > > > > > > > > > current
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > agreement"
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I can suspect
> > some
> > > > > >
> > > > > > members
> > > > > > > are
> > > > > > > > > > >
> > > > > > > > > > > making
> > > > > > > > > > > > > some
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > sort
> > > > > > > > > > > > > > > > > of
> > > > > > > > > > > > > > > > > > > > > private
> > > > > > > > > > > > > > > > > > > > > > > > > > > agreements,
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > and
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > do not to
> discuss
> > > it on
> > > > > >
> > > > > > the
> > > > > > > > >
> > > > > > > > > list.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Let's build
> > > consensus
> > > > > >
> > > > > > here
> > > > > > > > >
> > > > > > > > > first,
> > > > > > > > > > > and
> > > > > > > > > > > > > then
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > name
> > > > > > > > > > > > > > > > > an
> > > > > > > > > > > > > > > > > > > > > > > agreement.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Denis, as PMC
> > > Chair,
> > > > > >
> > > > > > could
> > > > > > > you
> > > > > > > > > > >
> > > > > > > > > > > please
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > control,
> > > > > > > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > > > > > > Service
> > > > > > > > > > > > > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > inclusion/exclusion is
> > > > > > > > >
> > > > > > > > > discussed
> > > > > > > > > > > > > properly
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > according
> > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > > > Apache
> > > > > > > > > > > > > > > > > > > > > > > > > > > Way.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент.
> 2018
> > > г. в
> > > > > > >
> > > > > > > 18:55,
> > > > > > > > > > > >
> > > > > > > > > > > > Vladimir
> > > > > > > > > > > > >
Re: Apache Ignite 2.7 release
Posted by Dmitriy Setrakyan <ds...@apache.org>.
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 <vo...@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 <ni...@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 <st...@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 <dp...@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 <nizhikov@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 <
> > > > >
> > > > > daradurvs@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 <
> > > > > >
> > > > > > dsetrakyan@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.spb@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 <
> > dmagda@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 <
> > > > > > > >
> > > > > > > > nizhikov@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 <
> > > > > > > > > >
> > > > > > > > > > dsetrakyan@apache.org
> > > > > > > > > > > > :
> > > > > > > > > > > > >
> > > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > We agreed in the beginning of this thread that
> > Service
> > > > >
> > > > > Grid
> > > > > > > >
> > > > > > > > changes
> > > > > > > > > > > > are not
> > > > > > > > > > > > > > going to make the release because the community
> > still did
> > > > > >
> > > > > > not
> > > > > > > > > >
> > > > > > > > > > approve
> > > > > > > > > > > > the
> > > > > > > > > > > > > > design. Nothing has changed since. I have not
> seen
> > any
> > > > > >
> > > > > > design
> > > > > > > > > > > >
> > > > > > > > > > > > discussions.
> > > > > > > > > > > > > > At this point, I have no confidence that the
> > Service Grid
> > > > > > > >
> > > > > > > > changes
> > > > > > > > > > > will
> > > > > > > > > > > > make
> > > > > > > > > > > > > > it into the 2.8 release. The 2.7 release seems
> out
> > of
> > > > > >
> > > > > > question
> > > > > > > > > > > >
> > > > > > > > > > > > altogether.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Also, Nikolay is a release manager. We should let
> > him
> > > > > >
> > > > > > drive the
> > > > > > > > > > > >
> > > > > > > > > > > > release. To
> > > > > > > > > > > > > > my knowledge, he is doing a great job and the
> > release is
> > > > > >
> > > > > > going
> > > > > > > > > > > >
> > > > > > > > > > > > according to
> > > > > > > > > > > > > > the schedule he proposed.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > D.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > On Fri, Sep 28, 2018 at 4:31 AM Dmitriy Pavlov <
> > > > > > > > > > >
> > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Hi Dmitriy, Vladimir,
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > I suggest we stop this nonsense with release
> > > > > >
> > > > > > dates-pushing
> > > > > > > > > >
> > > > > > > > > > because
> > > > > > > > > > > of
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > some
> > > > > > > > > > > > > > > open question.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Just because you disagreed with any
> > include/exclude
> > > > > >
> > > > > > something
> > > > > > > > > >
> > > > > > > > > > into
> > > > > > > > > > > > scope,
> > > > > > > > > > > > > > > does not mean that whole community disagreed.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > If folks will start a separate discussion with
> > results
> > > > > >
> > > > > > of the
> > > > > > > > > > > >
> > > > > > > > > > > > review, I
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > see
> > > > > > > > > > > > > > > no reasons to reject their contribution, even
> if
> > we
> > > > >
> > > > > need
> > > > > > to
> > > > > > > > > >
> > > > > > > > > > revisit
> > > > > > > > > > > > our
> > > > > > > > > > > > > > > agreements and wait for a couple of days more.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Am I missing some reason why dates are so
> > fundamentally
> > > > > > > >
> > > > > > > > important
> > > > > > > > > > > to
> > > > > > > > > > > > you?
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Sincerely,
> > > > > > > > > > > > > > > Dmitriy Pavlov
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 12:20, Dmitriy
> Setrakyan <
> > > > > > > > > > > >
> > > > > > > > > > > > dsetrakyan@apache.org>:
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > If services is not ready, which it is not,
> > then we
> > > > > >
> > > > > > should
> > > > > > > > > >
> > > > > > > > > > include
> > > > > > > > > > > > them
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > into
> > > > > > > > > > > > > > > > the next release. There is no need to force
> > them into
> > > > > >
> > > > > > 2.7.
> > > > > > > >
> > > > > > > > I
> > > > > > > > > > > > suggest we
> > > > > > > > > > > > > > > > move according to the schedule we all agreed
> > on.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > D.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at 1:22 AM Dmitriy
> Pavlov
> > <
> > > > > > > > > > > >
> > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Yes, so correct statement is "community did
> > not
> > > > >
> > > > > make
> > > > > > any
> > > > > > > > > > > >
> > > > > > > > > > > > decisions
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > about
> > > > > > > > > > > > > > > > > services not go to 2.7/ services are out of
> > scope".
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > If so, please forgive me my confusion.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:19, Vladimir
> > Ozerov <
> > > > > > > > > > > >
> > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Exactly. So correct statement is “it is
> up
> > to
> > > > > > > >
> > > > > > > > *community*
> > > > > > > > > > to
> > > > > > > > > > > > decide
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > whether
> > > > > > > > > > > > > > > > > > something goes to 2.7”.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:11, Dmitriy
> > Pavlov <
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > No, it is up to the community to
> discuss
> > after
> > > > > >
> > > > > > their
> > > > > > > > > >
> > > > > > > > > > review
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > results.
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:09, Vladimir
> > Ozerov <
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > Did I read your words correctly that
> > it is up
> > > > > >
> > > > > > to
> > > > > > > > > > > >
> > > > > > > > > > > > implementor
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > of a
> > > > > > > > > > > > > > > > > > single
> > > > > > > > > > > > > > > > > > > > feature to decide whether release of
> > all
> > > > >
> > > > > other
> > > > > > > >
> > > > > > > > features
> > > > > > > > > > > and
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > fixes
> > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > > > delayed?
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:00, Dmitriy
> > Pavlov
> > > > >
> > > > > <
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > My point we can wait a bit for
> > services
> > > > > >
> > > > > > because
> > > > > > > > > > > > > > > > > > > > > 1 we are open-minded and we don't
> > have
> > > > > >
> > > > > > outside
> > > > > > > > > > >
> > > > > > > > > > > pressure
> > > > > > > > > > > > to
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > do
> > > > > > > > > > > > > > > > > > release
> > > > > > > > > > > > > > > > > > > in
> > > > > > > > > > > > > > > > > > > > > October
> > > > > > > > > > > > > > > > > > > > > 2 and services it is not some new
> > feature,
> > > > > >
> > > > > > which
> > > > > > > > > > > >
> > > > > > > > > > > > suddenly
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > appeared
> > > > > > > > > > > > > > > > > > in
> > > > > > > > > > > > > > > > > > > > > autumn, it is a well known and
> > important
> > > > > >
> > > > > > feature.
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > So it is up to Vyacheslav, Anton
> and
> > > > >
> > > > > Nikolay
> > > > > > to
> > > > > > > > > >
> > > > > > > > > > decide.
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > Decisions can be services are not
> > > > > >
> > > > > > ready/ready to
> > > > > > > > > >
> > > > > > > > > > merge
> > > > > > > > > > > > only
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > master/ready
> > > > > > > > > > > > > > > > > > > > > to merge to master and to 2.7.
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 10:46,
> > Vladimir
> > > > > >
> > > > > > Ozerov <
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > Dmitry,
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > Community agreement was to
> perform
> > the
> > > > > >
> > > > > > release
> > > > > > > >
> > > > > > > > in
> > > > > > > > > > > > October.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Of
> > > > > > > > > > > > > > > > > > course
> > > > > > > > > > > > > > > > > > > we
> > > > > > > > > > > > > > > > > > > > > can
> > > > > > > > > > > > > > > > > > > > > > wait a bit for services. Then we
> > wait a
> > > > > >
> > > > > > bit for
> > > > > > > > > >
> > > > > > > > > > other
> > > > > > > > > > > > cool
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > features
> > > > > > > > > > > > > > > > > > > > ready
> > > > > > > > > > > > > > > > > > > > > > by that time, then again and
> > again, and
> > > > > >
> > > > > > release
> > > > > > > > > >
> > > > > > > > > > will
> > > > > > > > > > > > never
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > happen.
> > > > > > > > > > > > > > > > > > > And
> > > > > > > > > > > > > > > > > > > > > > while we are waiting for new
> > features to
> > > > > >
> > > > > > come,
> > > > > > > > > > >
> > > > > > > > > > > already
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > completerd
> > > > > > > > > > > > > > > > > > > > > features
> > > > > > > > > > > > > > > > > > > > > > cannot be used by anyone.
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > This is why we have an agreement
> > that if
> > > > > > > >
> > > > > > > > feature is
> > > > > > > > > > > not
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > ready,
> > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > should
> > > > > > > > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > > > > > moved to future release, instead
> of
> > > > > >
> > > > > > shifting
> > > > > > > > > >
> > > > > > > > > > release.
> > > > > > > > > > > > The
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > sole
> > > > > > > > > > > > > > > > > > reason
> > > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > have strict dates when decisions
> > are made
> > > > > >
> > > > > > is
> > > > > > > >
> > > > > > > > to let
> > > > > > > > > > > > release
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > happen.
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at 2:22 AM
> > Dmitriy
> > > > > >
> > > > > > Pavlov
> > > > > > > >
> > > > > > > > <
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > Vladimir, I'm not searching
> for
> > enemy,
> > > > > >
> > > > > > and
> > > > > > > >
> > > > > > > > not
> > > > > > > > > > > > fighting
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > with
> > > > > > > > > > > > > > > > > > you.
> > > > > > > > > > > > > > > > > > > > I'm
> > > > > > > > > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > > > > > > > happy about cases when we are
> > hurrying.
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > We can't fix test, fill ticket
> > details,
> > > > > >
> > > > > > can't
> > > > > > > > > >
> > > > > > > > > > wait
> > > > > > > > > > > > for
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > contributions
> > > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > > finish their tasks. It is not
> > best
> > > > >
> > > > > idea
> > > > > > to
> > > > > > > >
> > > > > > > > use
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > experience
> > > > > > > > > > > > > > > > from
> > > > > > > > > > > > > > > > > > > > > > commercial
> > > > > > > > > > > > > > > > > > > > > > > companies in open source. Are
> > there any
> > > > > > > >
> > > > > > > > pressure
> > > > > > > > > > > > outside
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > community?
> > > > > > > > > > > > > > > > > > > > Did
> > > > > > > > > > > > > > > > > > > > > > > someone promised rest of
> > features to be
> > > > > > > >
> > > > > > > > released
> > > > > > > > > > at
> > > > > > > > > > > > 30
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > September?
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > Let's remember principle
> > do-orcracy,
> > > > > >
> > > > > > power of
> > > > > > > > > >
> > > > > > > > > > those
> > > > > > > > > > > > who
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > do.
> > > > > > > > > > > > > > > > If
> > > > > > > > > > > > > > > > > > > > > contribor
> > > > > > > > > > > > > > > > > > > > > > > does change and reviewer does
> > review,
> > > > > >
> > > > > > let's
> > > > > > > >
> > > > > > > > give
> > > > > > > > > > > > right of
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > making
> > > > > > > > > > > > > > > > > > > > > decision
> > > > > > > > > > > > > > > > > > > > > > > to them, but not to some closed
> > club of
> > > > > > > >
> > > > > > > > people
> > > > > > > > > > who
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > privately
> > > > > > > > > > > > > > > > > > > discuss
> > > > > > > > > > > > > > > > > > > > > > > something.
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > Sincerely
> > > > > > > > > > > > > > > > > > > > > > > Dmitriy Pavlov
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г., 23:42
> > Vyacheslav
> > > > > > > >
> > > > > > > > Daradur <
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > daradurvs@gmail.com
> > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > Hi Igniters!
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > As I have written about
> > Service Grid
> > > > > > > >
> > > > > > > > before [1]
> > > > > > > > > > > I'm
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > finalizing
> > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > > solution to be sure that
> > > > > >
> > > > > > implementation is
> > > > > > > > > > > >
> > > > > > > > > > > > reliable.
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > About including it in 2.7, if
> > we talk
> > > > > >
> > > > > > that
> > > > > > > >
> > > > > > > > code
> > > > > > > > > > > > freeze
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > tomorrow
> > > > > > > > > > > > > > > > > > > > then
> > > > > > > > > > > > > > > > > > > > > > > > the solution is not ready to
> > merge
> > > > >
> > > > > yet.
> > > > > > > > > > > > > > > > > > > > > > > > I hope that prereviewers
> Anton
> > > > > >
> > > > > > Vinogradov
> > > > > > > >
> > > > > > > > and
> > > > > > > > > > > > Nikolay
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Izhikov
> > > > > > > > > > > > > > > > > > > will
> > > > > > > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > > > > > > > able to answer if solution
> out
> > of
> > > > > >
> > > > > > scope or
> > > > > > > >
> > > > > > > > not
> > > > > > > > > > > in a
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > couple
> > > > > > > > > > > > > > > > of
> > > > > > > > > > > > > > > > > > > days.
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > [1]
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > >
> > > > >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-release-td34076.html#a34485
> > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 11:14
> > PM
> > > > > >
> > > > > > Dmitriy
> > > > > > > > > >
> > > > > > > > > > Pavlov <
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > Yes, I agree, NPE during
> WAL
> > flush
> > > > >
> > > > > is
> > > > > > > > > > >
> > > > > > > > > > > definitely
> > > > > > > > > > > > a
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > blocker.
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > It is strange why the
> > current test
> > > > > >
> > > > > > set
> > > > > > > >
> > > > > > > > did
> > > > > > > > > > not
> > > > > > > > > > > > fail
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > after
> > > > > > > > > > > > > > > > > > > commit.
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в
> 21:45,
> > > > >
> > > > > Andrey
> > > > > > > > > >
> > > > > > > > > > Kuznetsov
> > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > stkuzma@gmail.com
> > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > Igniters,
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > I've bumped into a new
> bug
> > in WAL
> > > > > > > >
> > > > > > > > manager
> > > > > > > > > > > > recently,
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > see
> > > > > > > > > > > > > > > > > > [1].
> > > > > > > > > > > > > > > > > > > It
> > > > > > > > > > > > > > > > > > > > > > looks
> > > > > > > > > > > > > > > > > > > > > > > > > > critical enough, and can
> > be a
> > > > >
> > > > > good
> > > > > > > > > >
> > > > > > > > > > candidate
> > > > > > > > > > > > for
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > fixing
> > > > > > > > > > > > > > > > > > > before
> > > > > > > > > > > > > > > > > > > > > 2.7
> > > > > > > > > > > > > > > > > > > > > > > > release.
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > Do you agree?
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > [1]
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > https://issues.apache.org/jira/browse/IGNITE-9731
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в
> > 19:45,
> > > > > >
> > > > > > Dmitriy
> > > > > > > > > >
> > > > > > > > > > Pavlov
> > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > I need Vhyacheslav's
> > opinion to
> > > > > >
> > > > > > be
> > > > > > > > > > >
> > > > > > > > > > > absolutely
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > sure
> > > > > > > > > > > > > > > > what
> > > > > > > > > > > > > > > > > > > > status
> > > > > > > > > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > > > > > > > > > now.
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > We never committed to
> > dates of
> > > > > > > >
> > > > > > > > release,
> > > > > > > > > > as
> > > > > > > > > > > > well.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > I
> > > > > > > > > > > > > > > > > don't
> > > > > > > > > > > > > > > > > > > > quite
> > > > > > > > > > > > > > > > > > > > > > > > understand
> > > > > > > > > > > > > > > > > > > > > > > > > > > what can mean 'the
> > community
> > > > > > > >
> > > > > > > > committed to
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > doing/releasing
> > > > > > > > > > > > > > > > > > > > > > > something'.
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > About SG, I also
> > concerned why
> > > > > >
> > > > > > such
> > > > > > > >
> > > > > > > > a big
> > > > > > > > > > > > feature
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > has
> > > > > > > > > > > > > > > > > > > quite a
> > > > > > > > > > > > > > > > > > > > > few
> > > > > > > > > > > > > > > > > > > > > > > > > > > discussions on the
> list.
> > But it
> > > > > >
> > > > > > is
> > > > > > > > > >
> > > > > > > > > > another
> > > > > > > > > > > > story.
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в
> > 19:33,
> > > > > > > >
> > > > > > > > Vladimir
> > > > > > > > > > > > Ozerov <
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > Folks,
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > Please stop looking
> for
> > > > >
> > > > > enemies
> > > > > > > > > > >
> > > > > > > > > > > everywhere.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Just
> > > > > > > > > > > > > > > > went
> > > > > > > > > > > > > > > > > > > > through
> > > > > > > > > > > > > > > > > > > > > > > this
> > > > > > > > > > > > > > > > > > > > > > > > > > thread
> > > > > > > > > > > > > > > > > > > > > > > > > > > > and search for
> > "service"
> > > > >
> > > > > word.
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018
> > at 7:30
> > > > >
> > > > > PM
> > > > > > > >
> > > > > > > > Denis
> > > > > > > > > > > > Magda <
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > dmagda@apache.org
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Denis, as PMC
> > Chair,
> > > > >
> > > > > could
> > > > > > you
> > > > > > > > > >
> > > > > > > > > > please
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > control,
> > > > > > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > > > > > Service
> > > > > > > > > > > > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > inclusion/exclusion is
> > > > > > > >
> > > > > > > > discussed
> > > > > > > > > > > > properly
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > according
> > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > > Apache
> > > > > > > > > > > > > > > > > > > > > > > > > > Way.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > It's fine when
> > > > > > > > > >
> > > > > > > > > > committers/contributors
> > > > > > > > > > > > have
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > private
> > > > > > > > > > > > > > > > > > > > > > discussions
> > > > > > > > > > > > > > > > > > > > > > > > > > related
> > > > > > > > > > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > a feature they've
> > been
> > > > > >
> > > > > > working
> > > > > > > >
> > > > > > > > on.
> > > > > > > > > > Not
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > everything
> > > > > > > > > > > > > > > > > > should
> > > > > > > > > > > > > > > > > > > > go
> > > > > > > > > > > > > > > > > > > > > > > > through
> > > > > > > > > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > dev
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > list. Otherwise, it
> > will be
> > > > > > > > > >
> > > > > > > > > > inundated.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > However,
> > > > > > > > > > > > > > > > > > agree,
> > > > > > > > > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > > > > > > > > > > > architectural
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > and release
> > decisions need
> > > > > >
> > > > > > to be
> > > > > > > >
> > > > > > > > done
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > publicly.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > Speaking about
> > Service
> > > > >
> > > > > Grid,
> > > > > > > >
> > > > > > > > there
> > > > > > > > > > was
> > > > > > > > > > > a
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > discussion
> > > > > > > > > > > > > > > > > > > where
> > > > > > > > > > > > > > > > > > > > I
> > > > > > > > > > > > > > > > > > > > > > saw
> > > > > > > > > > > > > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > was
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > questionable
> whether
> > it
> > > > >
> > > > > gets
> > > > > > > >
> > > > > > > > added to
> > > > > > > > > > > the
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > release
> > > > > > > > > > > > > > > > or
> > > > > > > > > > > > > > > > > > > not.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > *Vladislav*, could
> > you
> > > > >
> > > > > please
> > > > > > > >
> > > > > > > > shed
> > > > > > > > > > some
> > > > > > > > > > > > light
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > on
> > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > current
> > > > > > > > > > > > > > > > > > > > > > > > status of
> > > > > > > > > > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > service grid?
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27,
> 2018
> > at
> > > > >
> > > > > 9:12
> > > > > > AM
> > > > > > > > > >
> > > > > > > > > > Dmitriy
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Pavlov <
> > > > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Ok, let's wait
> for
> > > > >
> > > > > feedback
> > > > > > > >
> > > > > > > > from SG
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > Author(s)/Reviewer(s)
> > > > > > > > > > > > > > > > > > > > > > > > first. If
> > > > > > > > > > > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > not ready, ok.
> But
> > I
> > > > > >
> > > > > > thought
> > > > > > > >
> > > > > > > > it is
> > > > > > > > > > > > almost
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > done.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I apologize if I
> > missed
> > > > > >
> > > > > > some
> > > > > > > > > > > >
> > > > > > > > > > > > discussion (it
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > can
> > > > > > > > > > > > > > > > > > > happen),
> > > > > > > > > > > > > > > > > > > > > but
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > According to the
> > > > >
> > > > > statement
> > > > > > "our
> > > > > > > > > > >
> > > > > > > > > > > current
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > agreement"
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I can suspect
> some
> > > > >
> > > > > members
> > > > > > are
> > > > > > > > > >
> > > > > > > > > > making
> > > > > > > > > > > > some
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > sort
> > > > > > > > > > > > > > > > of
> > > > > > > > > > > > > > > > > > > > private
> > > > > > > > > > > > > > > > > > > > > > > > > > agreements,
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > and
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > do not to discuss
> > it on
> > > > >
> > > > > the
> > > > > > > >
> > > > > > > > list.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Let's build
> > consensus
> > > > >
> > > > > here
> > > > > > > >
> > > > > > > > first,
> > > > > > > > > > and
> > > > > > > > > > > > then
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > name
> > > > > > > > > > > > > > > > an
> > > > > > > > > > > > > > > > > > > > > > agreement.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Denis, as PMC
> > Chair,
> > > > >
> > > > > could
> > > > > > you
> > > > > > > > > >
> > > > > > > > > > please
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > control,
> > > > > > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > > > > > Service
> > > > > > > > > > > > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > inclusion/exclusion is
> > > > > > > >
> > > > > > > > discussed
> > > > > > > > > > > > properly
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > according
> > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > > Apache
> > > > > > > > > > > > > > > > > > > > > > > > > > Way.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018
> > г. в
> > > > > >
> > > > > > 18:55,
> > > > > > > > > > >
> > > > > > > > > > > Vladimir
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Ozerov
> > > > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > This is an
> > outcome of
> > > > > >
> > > > > > current
> > > > > > > > > >
> > > > > > > > > > state
> > > > > > > > > > > > of
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Service
> > > > > > > > > > > > > > > > > > Grid -
> > > > > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > > > > > > > > > > > ready.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > We
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > never committed
> > to have
> > > > > >
> > > > > > it to
> > > > > > > > > >
> > > > > > > > > > 2.7.
> > > > > > > > > > > > Our goal
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > was
> > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > try
> > > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > > > include
> > > > > > > > > > > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > into
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 2.7.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27,
> > 2018 at
> > > > > >
> > > > > > 6:48
> > > > > > > >
> > > > > > > > PM
> > > > > > > > > > > > Dmitriy
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Pavlov
> > > > > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Could you
> > please
> > > > > >
> > > > > > provide a
> > > > > > > > > > > >
> > > > > > > > > > > > reference to
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > some
> > > > > > > > > > > > > > > > > > > thread?
> > > > > > > > > > > > > > > > > > > > > > > > Probably I
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > missed
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > it.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент.
> > 2018 г.
> > > > >
> > > > > в
> > > > > > > >
> > > > > > > > 18:46,
> > > > > > > > > > > > Vladimir
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Ozerov <
> > > > > > > > > > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > >
Re: Apache Ignite 2.7 release
Posted by Vladimir Ozerov <vo...@gridgain.com>.
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 <ni...@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 <st...@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 <dp...@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 <ni...@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 <
> > > >
> > > > daradurvs@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 <
> > > > >
> > > > > dsetrakyan@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.spb@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 <
> dmagda@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 <
> > > > > > >
> > > > > > > nizhikov@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 <
> > > > > > > > >
> > > > > > > > > dsetrakyan@apache.org
> > > > > > > > > > > :
> > > > > > > > > > > >
> > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > >
> > > > > > > > > > > > > We agreed in the beginning of this thread that
> Service
> > > >
> > > > Grid
> > > > > > >
> > > > > > > changes
> > > > > > > > > > > are not
> > > > > > > > > > > > > going to make the release because the community
> still did
> > > > >
> > > > > not
> > > > > > > > >
> > > > > > > > > approve
> > > > > > > > > > > the
> > > > > > > > > > > > > design. Nothing has changed since. I have not seen
> any
> > > > >
> > > > > design
> > > > > > > > > > >
> > > > > > > > > > > discussions.
> > > > > > > > > > > > > At this point, I have no confidence that the
> Service Grid
> > > > > > >
> > > > > > > changes
> > > > > > > > > > will
> > > > > > > > > > > make
> > > > > > > > > > > > > it into the 2.8 release. The 2.7 release seems out
> of
> > > > >
> > > > > question
> > > > > > > > > > >
> > > > > > > > > > > altogether.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Also, Nikolay is a release manager. We should let
> him
> > > > >
> > > > > drive the
> > > > > > > > > > >
> > > > > > > > > > > release. To
> > > > > > > > > > > > > my knowledge, he is doing a great job and the
> release is
> > > > >
> > > > > going
> > > > > > > > > > >
> > > > > > > > > > > according to
> > > > > > > > > > > > > the schedule he proposed.
> > > > > > > > > > > > >
> > > > > > > > > > > > > D.
> > > > > > > > > > > > >
> > > > > > > > > > > > > On Fri, Sep 28, 2018 at 4:31 AM Dmitriy Pavlov <
> > > > > > > > > >
> > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > > > Hi Dmitriy, Vladimir,
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > I suggest we stop this nonsense with release
> > > > >
> > > > > dates-pushing
> > > > > > > > >
> > > > > > > > > because
> > > > > > > > > > of
> > > > > > > > > > > > >
> > > > > > > > > > > > > some
> > > > > > > > > > > > > > open question.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Just because you disagreed with any
> include/exclude
> > > > >
> > > > > something
> > > > > > > > >
> > > > > > > > > into
> > > > > > > > > > > scope,
> > > > > > > > > > > > > > does not mean that whole community disagreed.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > If folks will start a separate discussion with
> results
> > > > >
> > > > > of the
> > > > > > > > > > >
> > > > > > > > > > > review, I
> > > > > > > > > > > > >
> > > > > > > > > > > > > see
> > > > > > > > > > > > > > no reasons to reject their contribution, even if
> we
> > > >
> > > > need
> > > > > to
> > > > > > > > >
> > > > > > > > > revisit
> > > > > > > > > > > our
> > > > > > > > > > > > > > agreements and wait for a couple of days more.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Am I missing some reason why dates are so
> fundamentally
> > > > > > >
> > > > > > > important
> > > > > > > > > > to
> > > > > > > > > > > you?
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Sincerely,
> > > > > > > > > > > > > > Dmitriy Pavlov
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 12:20, Dmitriy Setrakyan <
> > > > > > > > > > >
> > > > > > > > > > > dsetrakyan@apache.org>:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > > If services is not ready, which it is not,
> then we
> > > > >
> > > > > should
> > > > > > > > >
> > > > > > > > > include
> > > > > > > > > > > them
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > into
> > > > > > > > > > > > > > > the next release. There is no need to force
> them into
> > > > >
> > > > > 2.7.
> > > > > > >
> > > > > > > I
> > > > > > > > > > > suggest we
> > > > > > > > > > > > > > > move according to the schedule we all agreed
> on.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > D.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at 1:22 AM Dmitriy Pavlov
> <
> > > > > > > > > > >
> > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Yes, so correct statement is "community did
> not
> > > >
> > > > make
> > > > > any
> > > > > > > > > > >
> > > > > > > > > > > decisions
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > about
> > > > > > > > > > > > > > > > services not go to 2.7/ services are out of
> scope".
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > If so, please forgive me my confusion.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:19, Vladimir
> Ozerov <
> > > > > > > > > > >
> > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Exactly. So correct statement is “it is up
> to
> > > > > > >
> > > > > > > *community*
> > > > > > > > > to
> > > > > > > > > > > decide
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > whether
> > > > > > > > > > > > > > > > > something goes to 2.7”.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:11, Dmitriy
> Pavlov <
> > > > > > > > > > > > >
> > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > No, it is up to the community to discuss
> after
> > > > >
> > > > > their
> > > > > > > > >
> > > > > > > > > review
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > results.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:09, Vladimir
> Ozerov <
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > Did I read your words correctly that
> it is up
> > > > >
> > > > > to
> > > > > > > > > > >
> > > > > > > > > > > implementor
> > > > > > > > > > > > >
> > > > > > > > > > > > > of a
> > > > > > > > > > > > > > > > > single
> > > > > > > > > > > > > > > > > > > feature to decide whether release of
> all
> > > >
> > > > other
> > > > > > >
> > > > > > > features
> > > > > > > > > > and
> > > > > > > > > > > > >
> > > > > > > > > > > > > fixes
> > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > > delayed?
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:00, Dmitriy
> Pavlov
> > > >
> > > > <
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > My point we can wait a bit for
> services
> > > > >
> > > > > because
> > > > > > > > > > > > > > > > > > > > 1 we are open-minded and we don't
> have
> > > > >
> > > > > outside
> > > > > > > > > >
> > > > > > > > > > pressure
> > > > > > > > > > > to
> > > > > > > > > > > > >
> > > > > > > > > > > > > do
> > > > > > > > > > > > > > > > > release
> > > > > > > > > > > > > > > > > > in
> > > > > > > > > > > > > > > > > > > > October
> > > > > > > > > > > > > > > > > > > > 2 and services it is not some new
> feature,
> > > > >
> > > > > which
> > > > > > > > > > >
> > > > > > > > > > > suddenly
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > appeared
> > > > > > > > > > > > > > > > > in
> > > > > > > > > > > > > > > > > > > > autumn, it is a well known and
> important
> > > > >
> > > > > feature.
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > So it is up to Vyacheslav, Anton and
> > > >
> > > > Nikolay
> > > > > to
> > > > > > > > >
> > > > > > > > > decide.
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > Decisions can be services are not
> > > > >
> > > > > ready/ready to
> > > > > > > > >
> > > > > > > > > merge
> > > > > > > > > > > only
> > > > > > > > > > > > >
> > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > master/ready
> > > > > > > > > > > > > > > > > > > > to merge to master and to 2.7.
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 10:46,
> Vladimir
> > > > >
> > > > > Ozerov <
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > Dmitry,
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > Community agreement was to perform
> the
> > > > >
> > > > > release
> > > > > > >
> > > > > > > in
> > > > > > > > > > > October.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Of
> > > > > > > > > > > > > > > > > course
> > > > > > > > > > > > > > > > > > we
> > > > > > > > > > > > > > > > > > > > can
> > > > > > > > > > > > > > > > > > > > > wait a bit for services. Then we
> wait a
> > > > >
> > > > > bit for
> > > > > > > > >
> > > > > > > > > other
> > > > > > > > > > > cool
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > features
> > > > > > > > > > > > > > > > > > > ready
> > > > > > > > > > > > > > > > > > > > > by that time, then again and
> again, and
> > > > >
> > > > > release
> > > > > > > > >
> > > > > > > > > will
> > > > > > > > > > > never
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > happen.
> > > > > > > > > > > > > > > > > > And
> > > > > > > > > > > > > > > > > > > > > while we are waiting for new
> features to
> > > > >
> > > > > come,
> > > > > > > > > >
> > > > > > > > > > already
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > completerd
> > > > > > > > > > > > > > > > > > > > features
> > > > > > > > > > > > > > > > > > > > > cannot be used by anyone.
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > This is why we have an agreement
> that if
> > > > > > >
> > > > > > > feature is
> > > > > > > > > > not
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > ready,
> > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > should
> > > > > > > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > > > > moved to future release, instead of
> > > > >
> > > > > shifting
> > > > > > > > >
> > > > > > > > > release.
> > > > > > > > > > > The
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > sole
> > > > > > > > > > > > > > > > > reason
> > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > have strict dates when decisions
> are made
> > > > >
> > > > > is
> > > > > > >
> > > > > > > to let
> > > > > > > > > > > release
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > happen.
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at 2:22 AM
> Dmitriy
> > > > >
> > > > > Pavlov
> > > > > > >
> > > > > > > <
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > Vladimir, I'm not searching for
> enemy,
> > > > >
> > > > > and
> > > > > > >
> > > > > > > not
> > > > > > > > > > > fighting
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > with
> > > > > > > > > > > > > > > > > you.
> > > > > > > > > > > > > > > > > > > I'm
> > > > > > > > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > > > > > > happy about cases when we are
> hurrying.
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > We can't fix test, fill ticket
> details,
> > > > >
> > > > > can't
> > > > > > > > >
> > > > > > > > > wait
> > > > > > > > > > > for
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > contributions
> > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > finish their tasks. It is not
> best
> > > >
> > > > idea
> > > > > to
> > > > > > >
> > > > > > > use
> > > > > > > > > > > > >
> > > > > > > > > > > > > experience
> > > > > > > > > > > > > > > from
> > > > > > > > > > > > > > > > > > > > > commercial
> > > > > > > > > > > > > > > > > > > > > > companies in open source. Are
> there any
> > > > > > >
> > > > > > > pressure
> > > > > > > > > > > outside
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > community?
> > > > > > > > > > > > > > > > > > > Did
> > > > > > > > > > > > > > > > > > > > > > someone promised rest of
> features to be
> > > > > > >
> > > > > > > released
> > > > > > > > > at
> > > > > > > > > > > 30
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > September?
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > Let's remember principle
> do-orcracy,
> > > > >
> > > > > power of
> > > > > > > > >
> > > > > > > > > those
> > > > > > > > > > > who
> > > > > > > > > > > > >
> > > > > > > > > > > > > do.
> > > > > > > > > > > > > > > If
> > > > > > > > > > > > > > > > > > > > contribor
> > > > > > > > > > > > > > > > > > > > > > does change and reviewer does
> review,
> > > > >
> > > > > let's
> > > > > > >
> > > > > > > give
> > > > > > > > > > > right of
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > making
> > > > > > > > > > > > > > > > > > > > decision
> > > > > > > > > > > > > > > > > > > > > > to them, but not to some closed
> club of
> > > > > > >
> > > > > > > people
> > > > > > > > > who
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > privately
> > > > > > > > > > > > > > > > > > discuss
> > > > > > > > > > > > > > > > > > > > > > something.
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > Sincerely
> > > > > > > > > > > > > > > > > > > > > > Dmitriy Pavlov
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г., 23:42
> Vyacheslav
> > > > > > >
> > > > > > > Daradur <
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > daradurvs@gmail.com
> > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > Hi Igniters!
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > As I have written about
> Service Grid
> > > > > > >
> > > > > > > before [1]
> > > > > > > > > > I'm
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > finalizing
> > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > solution to be sure that
> > > > >
> > > > > implementation is
> > > > > > > > > > >
> > > > > > > > > > > reliable.
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > About including it in 2.7, if
> we talk
> > > > >
> > > > > that
> > > > > > >
> > > > > > > code
> > > > > > > > > > > freeze
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > tomorrow
> > > > > > > > > > > > > > > > > > > then
> > > > > > > > > > > > > > > > > > > > > > > the solution is not ready to
> merge
> > > >
> > > > yet.
> > > > > > > > > > > > > > > > > > > > > > > I hope that prereviewers Anton
> > > > >
> > > > > Vinogradov
> > > > > > >
> > > > > > > and
> > > > > > > > > > > Nikolay
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Izhikov
> > > > > > > > > > > > > > > > > > will
> > > > > > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > > > > > > able to answer if solution out
> of
> > > > >
> > > > > scope or
> > > > > > >
> > > > > > > not
> > > > > > > > > > in a
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > couple
> > > > > > > > > > > > > > > of
> > > > > > > > > > > > > > > > > > days.
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > [1]
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > >
> > > > > > >
> > > >
> > > >
> http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-release-td34076.html#a34485
> > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 11:14
> PM
> > > > >
> > > > > Dmitriy
> > > > > > > > >
> > > > > > > > > Pavlov <
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > Yes, I agree, NPE during WAL
> flush
> > > >
> > > > is
> > > > > > > > > >
> > > > > > > > > > definitely
> > > > > > > > > > > a
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > blocker.
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > It is strange why the
> current test
> > > > >
> > > > > set
> > > > > > >
> > > > > > > did
> > > > > > > > > not
> > > > > > > > > > > fail
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > after
> > > > > > > > > > > > > > > > > > commit.
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 21:45,
> > > >
> > > > Andrey
> > > > > > > > >
> > > > > > > > > Kuznetsov
> > > > > > > > > > <
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > stkuzma@gmail.com
> > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > Igniters,
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > I've bumped into a new bug
> in WAL
> > > > > > >
> > > > > > > manager
> > > > > > > > > > > recently,
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > see
> > > > > > > > > > > > > > > > > [1].
> > > > > > > > > > > > > > > > > > It
> > > > > > > > > > > > > > > > > > > > > looks
> > > > > > > > > > > > > > > > > > > > > > > > > critical enough, and can
> be a
> > > >
> > > > good
> > > > > > > > >
> > > > > > > > > candidate
> > > > > > > > > > > for
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > fixing
> > > > > > > > > > > > > > > > > > before
> > > > > > > > > > > > > > > > > > > > 2.7
> > > > > > > > > > > > > > > > > > > > > > > release.
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > Do you agree?
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > [1]
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> https://issues.apache.org/jira/browse/IGNITE-9731
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в
> 19:45,
> > > > >
> > > > > Dmitriy
> > > > > > > > >
> > > > > > > > > Pavlov
> > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > I need Vhyacheslav's
> opinion to
> > > > >
> > > > > be
> > > > > > > > > >
> > > > > > > > > > absolutely
> > > > > > > > > > > > >
> > > > > > > > > > > > > sure
> > > > > > > > > > > > > > > what
> > > > > > > > > > > > > > > > > > > status
> > > > > > > > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > > > > > > > > now.
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > We never committed to
> dates of
> > > > > > >
> > > > > > > release,
> > > > > > > > > as
> > > > > > > > > > > well.
> > > > > > > > > > > > >
> > > > > > > > > > > > > I
> > > > > > > > > > > > > > > > don't
> > > > > > > > > > > > > > > > > > > quite
> > > > > > > > > > > > > > > > > > > > > > > understand
> > > > > > > > > > > > > > > > > > > > > > > > > > what can mean 'the
> community
> > > > > > >
> > > > > > > committed to
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > doing/releasing
> > > > > > > > > > > > > > > > > > > > > > something'.
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > About SG, I also
> concerned why
> > > > >
> > > > > such
> > > > > > >
> > > > > > > a big
> > > > > > > > > > > feature
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > has
> > > > > > > > > > > > > > > > > > quite a
> > > > > > > > > > > > > > > > > > > > few
> > > > > > > > > > > > > > > > > > > > > > > > > > discussions on the list.
> But it
> > > > >
> > > > > is
> > > > > > > > >
> > > > > > > > > another
> > > > > > > > > > > story.
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в
> 19:33,
> > > > > > >
> > > > > > > Vladimir
> > > > > > > > > > > Ozerov <
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > Folks,
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > Please stop looking for
> > > >
> > > > enemies
> > > > > > > > > >
> > > > > > > > > > everywhere.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Just
> > > > > > > > > > > > > > > went
> > > > > > > > > > > > > > > > > > > through
> > > > > > > > > > > > > > > > > > > > > > this
> > > > > > > > > > > > > > > > > > > > > > > > > thread
> > > > > > > > > > > > > > > > > > > > > > > > > > > and search for
> "service"
> > > >
> > > > word.
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018
> at 7:30
> > > >
> > > > PM
> > > > > > >
> > > > > > > Denis
> > > > > > > > > > > Magda <
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > dmagda@apache.org
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > Denis, as PMC
> Chair,
> > > >
> > > > could
> > > > > you
> > > > > > > > >
> > > > > > > > > please
> > > > > > > > > > > > >
> > > > > > > > > > > > > control,
> > > > > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > > > > Service
> > > > > > > > > > > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> inclusion/exclusion is
> > > > > > >
> > > > > > > discussed
> > > > > > > > > > > properly
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > according
> > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > Apache
> > > > > > > > > > > > > > > > > > > > > > > > > Way.
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > It's fine when
> > > > > > > > >
> > > > > > > > > committers/contributors
> > > > > > > > > > > have
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > private
> > > > > > > > > > > > > > > > > > > > > discussions
> > > > > > > > > > > > > > > > > > > > > > > > > related
> > > > > > > > > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > > > > > > > a feature they've
> been
> > > > >
> > > > > working
> > > > > > >
> > > > > > > on.
> > > > > > > > > Not
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > everything
> > > > > > > > > > > > > > > > > should
> > > > > > > > > > > > > > > > > > > go
> > > > > > > > > > > > > > > > > > > > > > > through
> > > > > > > > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > > > > > > dev
> > > > > > > > > > > > > > > > > > > > > > > > > > > > list. Otherwise, it
> will be
> > > > > > > > >
> > > > > > > > > inundated.
> > > > > > > > > > > > >
> > > > > > > > > > > > > However,
> > > > > > > > > > > > > > > > > agree,
> > > > > > > > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > > > > > > > > > > architectural
> > > > > > > > > > > > > > > > > > > > > > > > > > > > and release
> decisions need
> > > > >
> > > > > to be
> > > > > > >
> > > > > > > done
> > > > > > > > > > > > >
> > > > > > > > > > > > > publicly.
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > Speaking about
> Service
> > > >
> > > > Grid,
> > > > > > >
> > > > > > > there
> > > > > > > > > was
> > > > > > > > > > a
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > discussion
> > > > > > > > > > > > > > > > > > where
> > > > > > > > > > > > > > > > > > > I
> > > > > > > > > > > > > > > > > > > > > saw
> > > > > > > > > > > > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > > > > > > > > > was
> > > > > > > > > > > > > > > > > > > > > > > > > > > > questionable whether
> it
> > > >
> > > > gets
> > > > > > >
> > > > > > > added to
> > > > > > > > > > the
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > release
> > > > > > > > > > > > > > > or
> > > > > > > > > > > > > > > > > > not.
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > *Vladislav*, could
> you
> > > >
> > > > please
> > > > > > >
> > > > > > > shed
> > > > > > > > > some
> > > > > > > > > > > light
> > > > > > > > > > > > >
> > > > > > > > > > > > > on
> > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > current
> > > > > > > > > > > > > > > > > > > > > > > status of
> > > > > > > > > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > > > > > > service grid?
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018
> at
> > > >
> > > > 9:12
> > > > > AM
> > > > > > > > >
> > > > > > > > > Dmitriy
> > > > > > > > > > > > >
> > > > > > > > > > > > > Pavlov <
> > > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > Ok, let's wait for
> > > >
> > > > feedback
> > > > > > >
> > > > > > > from SG
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > Author(s)/Reviewer(s)
> > > > > > > > > > > > > > > > > > > > > > > first. If
> > > > > > > > > > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > not ready, ok. But
> I
> > > > >
> > > > > thought
> > > > > > >
> > > > > > > it is
> > > > > > > > > > > almost
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > done.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > I apologize if I
> missed
> > > > >
> > > > > some
> > > > > > > > > > >
> > > > > > > > > > > discussion (it
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > can
> > > > > > > > > > > > > > > > > > happen),
> > > > > > > > > > > > > > > > > > > > but
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > According to the
> > > >
> > > > statement
> > > > > "our
> > > > > > > > > >
> > > > > > > > > > current
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > agreement"
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > I can suspect some
> > > >
> > > > members
> > > > > are
> > > > > > > > >
> > > > > > > > > making
> > > > > > > > > > > some
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > sort
> > > > > > > > > > > > > > > of
> > > > > > > > > > > > > > > > > > > private
> > > > > > > > > > > > > > > > > > > > > > > > > agreements,
> > > > > > > > > > > > > > > > > > > > > > > > > > > > and
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > do not to discuss
> it on
> > > >
> > > > the
> > > > > > >
> > > > > > > list.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > Let's build
> consensus
> > > >
> > > > here
> > > > > > >
> > > > > > > first,
> > > > > > > > > and
> > > > > > > > > > > then
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > name
> > > > > > > > > > > > > > > an
> > > > > > > > > > > > > > > > > > > > > agreement.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > Denis, as PMC
> Chair,
> > > >
> > > > could
> > > > > you
> > > > > > > > >
> > > > > > > > > please
> > > > > > > > > > > > >
> > > > > > > > > > > > > control,
> > > > > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > > > > Service
> > > > > > > > > > > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> inclusion/exclusion is
> > > > > > >
> > > > > > > discussed
> > > > > > > > > > > properly
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > according
> > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > Apache
> > > > > > > > > > > > > > > > > > > > > > > > > Way.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018
> г. в
> > > > >
> > > > > 18:55,
> > > > > > > > > >
> > > > > > > > > > Vladimir
> > > > > > > > > > > > >
> > > > > > > > > > > > > Ozerov
> > > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > This is an
> outcome of
> > > > >
> > > > > current
> > > > > > > > >
> > > > > > > > > state
> > > > > > > > > > > of
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Service
> > > > > > > > > > > > > > > > > Grid -
> > > > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > > > > > > > > > > ready.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > We
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > never committed
> to have
> > > > >
> > > > > it to
> > > > > > > > >
> > > > > > > > > 2.7.
> > > > > > > > > > > Our goal
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > was
> > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > try
> > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > > include
> > > > > > > > > > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > > > > > > > > > into
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 2.7.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27,
> 2018 at
> > > > >
> > > > > 6:48
> > > > > > >
> > > > > > > PM
> > > > > > > > > > > Dmitriy
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Pavlov
> > > > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Could you
> please
> > > > >
> > > > > provide a
> > > > > > > > > > >
> > > > > > > > > > > reference to
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > some
> > > > > > > > > > > > > > > > > > thread?
> > > > > > > > > > > > > > > > > > > > > > > Probably I
> > > > > > > > > > > > > > > > > > > > > > > > > > > > missed
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > it.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент.
> 2018 г.
> > > >
> > > > в
> > > > > > >
> > > > > > > 18:46,
> > > > > > > > > > > Vladimir
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Ozerov <
> > > > > > > > > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Our current
> > > > >
> > > > > agreement is
> > > > > > >
> > > > > > > that
> > > > > > > > > > > Service
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > > out
> > > > > > > > > > > > > > > > > > > of
> > > > > > > > > > > > > > > > > > > > > > scope.
> > > > > > > > > > > > > > > > > > > > > > > > > This
> > > > > > > > > > > > > > > > > > > > > > > > > > > > is a
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > huge
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > feature,
> which
> > > >
> > > > hasn't
> > > > > > >
> > > > > > > entered
> > > > > > > > > > > review
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > stage
> > > > > > > > > > > > > > > so
> > > > > > > > > > > > > > > > > > far,
> > > > > > > > > > > > > > > > > > > We
> > > > > > > > > > > > > > > > > > > > > > will
> > > > > > > > > > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > able to
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> review/fix/test it
> > > > > > >
> > > > > > > properly.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep
> 27,
> > > >
> > > > 2018
> > > > > at
> > > > > > >
> > > > > > > 6:32
> > > > > > > > > PM
> > > > > > > > > > > Dmitriy
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Pavlov
> > > > > > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I agree,
> and I
> > > > >
> > > > > prefer
> > > > > > >
> > > > > > > four
> > > > > > > > > > > weeks for
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > stabilization*
> > > > > > > > > > > > > > > > > > > > > (1
> > > > > > > > > > > > > > > > > > > > > > > Oct -
> > > > > > > > > > > > > > > > > > > > > > > > > 29
> > > > > > > > > > > > > > > > > > > > > > > > > > > > Oct)
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Do I
> understand
> > > >
> > > > it
> > > > > > > > >
> > > > > > > > > correctly:
> > > > > > > > > > > Service
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > > > > still
> > > > > > > > > > > > > > > > > > > > > in
> > > > > > > > > > > > > > > > > > > > > > > scope,
> > > > > > > > > > > > > > > > > > > > > > > > > > > > isn't
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > it? I
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > find it
> very
> > > > >
> > > > > important.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27
> сент. 2018
> > > > >
> > > > > г. в
> > > > > > > > >
> > > > > > > > > 18:28,
> > > > > > > > > > > Nikolay
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Izhikov <
> > > > > > > > > > > > > > > > > > > > > > > > > > > > nizhikov@apache.org
> >
Re: Apache Ignite 2.7 release
Posted by Nikolay Izhikov <ni...@apache.org>.
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 <st...@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 <dp...@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 <ni...@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 <
> > >
> > > daradurvs@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 <
> > > >
> > > > dsetrakyan@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.spb@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 <dm...@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 <
> > > > > >
> > > > > > nizhikov@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 <
> > > > > > > >
> > > > > > > > dsetrakyan@apache.org
> > > > > > > > > > :
> > > > > > > > > > >
> > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > >
> > > > > > > > > > > > We agreed in the beginning of this thread that Service
> > >
> > > Grid
> > > > > >
> > > > > > changes
> > > > > > > > > > are not
> > > > > > > > > > > > going to make the release because the community still did
> > > >
> > > > not
> > > > > > > >
> > > > > > > > approve
> > > > > > > > > > the
> > > > > > > > > > > > design. Nothing has changed since. I have not seen any
> > > >
> > > > design
> > > > > > > > > >
> > > > > > > > > > discussions.
> > > > > > > > > > > > At this point, I have no confidence that the Service Grid
> > > > > >
> > > > > > changes
> > > > > > > > > will
> > > > > > > > > > make
> > > > > > > > > > > > it into the 2.8 release. The 2.7 release seems out of
> > > >
> > > > question
> > > > > > > > > >
> > > > > > > > > > altogether.
> > > > > > > > > > > >
> > > > > > > > > > > > Also, Nikolay is a release manager. We should let him
> > > >
> > > > drive the
> > > > > > > > > >
> > > > > > > > > > release. To
> > > > > > > > > > > > my knowledge, he is doing a great job and the release is
> > > >
> > > > going
> > > > > > > > > >
> > > > > > > > > > according to
> > > > > > > > > > > > the schedule he proposed.
> > > > > > > > > > > >
> > > > > > > > > > > > D.
> > > > > > > > > > > >
> > > > > > > > > > > > On Fri, Sep 28, 2018 at 4:31 AM Dmitriy Pavlov <
> > > > > > > > >
> > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > > Hi Dmitriy, Vladimir,
> > > > > > > > > > > > >
> > > > > > > > > > > > > I suggest we stop this nonsense with release
> > > >
> > > > dates-pushing
> > > > > > > >
> > > > > > > > because
> > > > > > > > > of
> > > > > > > > > > > >
> > > > > > > > > > > > some
> > > > > > > > > > > > > open question.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Just because you disagreed with any include/exclude
> > > >
> > > > something
> > > > > > > >
> > > > > > > > into
> > > > > > > > > > scope,
> > > > > > > > > > > > > does not mean that whole community disagreed.
> > > > > > > > > > > > >
> > > > > > > > > > > > > If folks will start a separate discussion with results
> > > >
> > > > of the
> > > > > > > > > >
> > > > > > > > > > review, I
> > > > > > > > > > > >
> > > > > > > > > > > > see
> > > > > > > > > > > > > no reasons to reject their contribution, even if we
> > >
> > > need
> > > > to
> > > > > > > >
> > > > > > > > revisit
> > > > > > > > > > our
> > > > > > > > > > > > > agreements and wait for a couple of days more.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Am I missing some reason why dates are so fundamentally
> > > > > >
> > > > > > important
> > > > > > > > > to
> > > > > > > > > > you?
> > > > > > > > > > > > >
> > > > > > > > > > > > > Sincerely,
> > > > > > > > > > > > > Dmitriy Pavlov
> > > > > > > > > > > > >
> > > > > > > > > > > > > пт, 28 сент. 2018 г. в 12:20, Dmitriy Setrakyan <
> > > > > > > > > >
> > > > > > > > > > dsetrakyan@apache.org>:
> > > > > > > > > > > > >
> > > > > > > > > > > > > > If services is not ready, which it is not, then we
> > > >
> > > > should
> > > > > > > >
> > > > > > > > include
> > > > > > > > > > them
> > > > > > > > > > > > >
> > > > > > > > > > > > > into
> > > > > > > > > > > > > > the next release. There is no need to force them into
> > > >
> > > > 2.7.
> > > > > >
> > > > > > I
> > > > > > > > > > suggest we
> > > > > > > > > > > > > > move according to the schedule we all agreed on.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > D.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > On Fri, Sep 28, 2018 at 1:22 AM Dmitriy Pavlov <
> > > > > > > > > >
> > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Yes, so correct statement is "community did not
> > >
> > > make
> > > > any
> > > > > > > > > >
> > > > > > > > > > decisions
> > > > > > > > > > > > >
> > > > > > > > > > > > > about
> > > > > > > > > > > > > > > services not go to 2.7/ services are out of scope".
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > If so, please forgive me my confusion.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:19, Vladimir Ozerov <
> > > > > > > > > >
> > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > >
> > > > > > > > > > > > > :
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Exactly. So correct statement is “it is up to
> > > > > >
> > > > > > *community*
> > > > > > > > to
> > > > > > > > > > decide
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > whether
> > > > > > > > > > > > > > > > something goes to 2.7”.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:11, Dmitriy Pavlov <
> > > > > > > > > > > >
> > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > No, it is up to the community to discuss after
> > > >
> > > > their
> > > > > > > >
> > > > > > > > review
> > > > > > > > > > > > >
> > > > > > > > > > > > > results.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:09, Vladimir Ozerov <
> > > > > > > > > > > > >
> > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Did I read your words correctly that it is up
> > > >
> > > > to
> > > > > > > > > >
> > > > > > > > > > implementor
> > > > > > > > > > > >
> > > > > > > > > > > > of a
> > > > > > > > > > > > > > > > single
> > > > > > > > > > > > > > > > > > feature to decide whether release of all
> > >
> > > other
> > > > > >
> > > > > > features
> > > > > > > > > and
> > > > > > > > > > > >
> > > > > > > > > > > > fixes
> > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > delayed?
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:00, Dmitriy Pavlov
> > >
> > > <
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > My point we can wait a bit for services
> > > >
> > > > because
> > > > > > > > > > > > > > > > > > > 1 we are open-minded and we don't have
> > > >
> > > > outside
> > > > > > > > >
> > > > > > > > > pressure
> > > > > > > > > > to
> > > > > > > > > > > >
> > > > > > > > > > > > do
> > > > > > > > > > > > > > > > release
> > > > > > > > > > > > > > > > > in
> > > > > > > > > > > > > > > > > > > October
> > > > > > > > > > > > > > > > > > > 2 and services it is not some new feature,
> > > >
> > > > which
> > > > > > > > > >
> > > > > > > > > > suddenly
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > appeared
> > > > > > > > > > > > > > > > in
> > > > > > > > > > > > > > > > > > > autumn, it is a well known and important
> > > >
> > > > feature.
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > So it is up to Vyacheslav, Anton and
> > >
> > > Nikolay
> > > > to
> > > > > > > >
> > > > > > > > decide.
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > Decisions can be services are not
> > > >
> > > > ready/ready to
> > > > > > > >
> > > > > > > > merge
> > > > > > > > > > only
> > > > > > > > > > > >
> > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > master/ready
> > > > > > > > > > > > > > > > > > > to merge to master and to 2.7.
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 10:46, Vladimir
> > > >
> > > > Ozerov <
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > Dmitry,
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > Community agreement was to perform the
> > > >
> > > > release
> > > > > >
> > > > > > in
> > > > > > > > > > October.
> > > > > > > > > > > >
> > > > > > > > > > > > Of
> > > > > > > > > > > > > > > > course
> > > > > > > > > > > > > > > > > we
> > > > > > > > > > > > > > > > > > > can
> > > > > > > > > > > > > > > > > > > > wait a bit for services. Then we wait a
> > > >
> > > > bit for
> > > > > > > >
> > > > > > > > other
> > > > > > > > > > cool
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > features
> > > > > > > > > > > > > > > > > > ready
> > > > > > > > > > > > > > > > > > > > by that time, then again and again, and
> > > >
> > > > release
> > > > > > > >
> > > > > > > > will
> > > > > > > > > > never
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > happen.
> > > > > > > > > > > > > > > > > And
> > > > > > > > > > > > > > > > > > > > while we are waiting for new features to
> > > >
> > > > come,
> > > > > > > > >
> > > > > > > > > already
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > completerd
> > > > > > > > > > > > > > > > > > > features
> > > > > > > > > > > > > > > > > > > > cannot be used by anyone.
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > This is why we have an agreement that if
> > > > > >
> > > > > > feature is
> > > > > > > > > not
> > > > > > > > > > > > >
> > > > > > > > > > > > > ready,
> > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > should
> > > > > > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > > > moved to future release, instead of
> > > >
> > > > shifting
> > > > > > > >
> > > > > > > > release.
> > > > > > > > > > The
> > > > > > > > > > > > >
> > > > > > > > > > > > > sole
> > > > > > > > > > > > > > > > reason
> > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > have strict dates when decisions are made
> > > >
> > > > is
> > > > > >
> > > > > > to let
> > > > > > > > > > release
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > happen.
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at 2:22 AM Dmitriy
> > > >
> > > > Pavlov
> > > > > >
> > > > > > <
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > Vladimir, I'm not searching for enemy,
> > > >
> > > > and
> > > > > >
> > > > > > not
> > > > > > > > > > fighting
> > > > > > > > > > > > >
> > > > > > > > > > > > > with
> > > > > > > > > > > > > > > > you.
> > > > > > > > > > > > > > > > > > I'm
> > > > > > > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > > > > > happy about cases when we are hurrying.
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > We can't fix test, fill ticket details,
> > > >
> > > > can't
> > > > > > > >
> > > > > > > > wait
> > > > > > > > > > for
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > contributions
> > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > finish their tasks. It is not best
> > >
> > > idea
> > > > to
> > > > > >
> > > > > > use
> > > > > > > > > > > >
> > > > > > > > > > > > experience
> > > > > > > > > > > > > > from
> > > > > > > > > > > > > > > > > > > > commercial
> > > > > > > > > > > > > > > > > > > > > companies in open source. Are there any
> > > > > >
> > > > > > pressure
> > > > > > > > > > outside
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > community?
> > > > > > > > > > > > > > > > > > Did
> > > > > > > > > > > > > > > > > > > > > someone promised rest of features to be
> > > > > >
> > > > > > released
> > > > > > > > at
> > > > > > > > > > 30
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > September?
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > Let's remember principle do-orcracy,
> > > >
> > > > power of
> > > > > > > >
> > > > > > > > those
> > > > > > > > > > who
> > > > > > > > > > > >
> > > > > > > > > > > > do.
> > > > > > > > > > > > > > If
> > > > > > > > > > > > > > > > > > > contribor
> > > > > > > > > > > > > > > > > > > > > does change and reviewer does review,
> > > >
> > > > let's
> > > > > >
> > > > > > give
> > > > > > > > > > right of
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > making
> > > > > > > > > > > > > > > > > > > decision
> > > > > > > > > > > > > > > > > > > > > to them, but not to some closed club of
> > > > > >
> > > > > > people
> > > > > > > > who
> > > > > > > > > > > > >
> > > > > > > > > > > > > privately
> > > > > > > > > > > > > > > > > discuss
> > > > > > > > > > > > > > > > > > > > > something.
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > Sincerely
> > > > > > > > > > > > > > > > > > > > > Dmitriy Pavlov
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г., 23:42 Vyacheslav
> > > > > >
> > > > > > Daradur <
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > daradurvs@gmail.com
> > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > Hi Igniters!
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > As I have written about Service Grid
> > > > > >
> > > > > > before [1]
> > > > > > > > > I'm
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > finalizing
> > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > solution to be sure that
> > > >
> > > > implementation is
> > > > > > > > > >
> > > > > > > > > > reliable.
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > About including it in 2.7, if we talk
> > > >
> > > > that
> > > > > >
> > > > > > code
> > > > > > > > > > freeze
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > tomorrow
> > > > > > > > > > > > > > > > > > then
> > > > > > > > > > > > > > > > > > > > > > the solution is not ready to merge
> > >
> > > yet.
> > > > > > > > > > > > > > > > > > > > > > I hope that prereviewers Anton
> > > >
> > > > Vinogradov
> > > > > >
> > > > > > and
> > > > > > > > > > Nikolay
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Izhikov
> > > > > > > > > > > > > > > > > will
> > > > > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > > > > > able to answer if solution out of
> > > >
> > > > scope or
> > > > > >
> > > > > > not
> > > > > > > > > in a
> > > > > > > > > > > > >
> > > > > > > > > > > > > couple
> > > > > > > > > > > > > > of
> > > > > > > > > > > > > > > > > days.
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > [1]
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > >
> > > > > >
> > >
> > > http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-release-td34076.html#a34485
> > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 11:14 PM
> > > >
> > > > Dmitriy
> > > > > > > >
> > > > > > > > Pavlov <
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > Yes, I agree, NPE during WAL flush
> > >
> > > is
> > > > > > > > >
> > > > > > > > > definitely
> > > > > > > > > > a
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > blocker.
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > It is strange why the current test
> > > >
> > > > set
> > > > > >
> > > > > > did
> > > > > > > > not
> > > > > > > > > > fail
> > > > > > > > > > > > >
> > > > > > > > > > > > > after
> > > > > > > > > > > > > > > > > commit.
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 21:45,
> > >
> > > Andrey
> > > > > > > >
> > > > > > > > Kuznetsov
> > > > > > > > > <
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > stkuzma@gmail.com
> > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > Igniters,
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > I've bumped into a new bug in WAL
> > > > > >
> > > > > > manager
> > > > > > > > > > recently,
> > > > > > > > > > > > >
> > > > > > > > > > > > > see
> > > > > > > > > > > > > > > > [1].
> > > > > > > > > > > > > > > > > It
> > > > > > > > > > > > > > > > > > > > looks
> > > > > > > > > > > > > > > > > > > > > > > > critical enough, and can be a
> > >
> > > good
> > > > > > > >
> > > > > > > > candidate
> > > > > > > > > > for
> > > > > > > > > > > > >
> > > > > > > > > > > > > fixing
> > > > > > > > > > > > > > > > > before
> > > > > > > > > > > > > > > > > > > 2.7
> > > > > > > > > > > > > > > > > > > > > > release.
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > Do you agree?
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > [1]
> > > > > > > > > > > > >
> > > > > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-9731
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 19:45,
> > > >
> > > > Dmitriy
> > > > > > > >
> > > > > > > > Pavlov
> > > > > > > > > <
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > I need Vhyacheslav's opinion to
> > > >
> > > > be
> > > > > > > > >
> > > > > > > > > absolutely
> > > > > > > > > > > >
> > > > > > > > > > > > sure
> > > > > > > > > > > > > > what
> > > > > > > > > > > > > > > > > > status
> > > > > > > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > > > > > > > now.
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > We never committed to dates of
> > > > > >
> > > > > > release,
> > > > > > > > as
> > > > > > > > > > well.
> > > > > > > > > > > >
> > > > > > > > > > > > I
> > > > > > > > > > > > > > > don't
> > > > > > > > > > > > > > > > > > quite
> > > > > > > > > > > > > > > > > > > > > > understand
> > > > > > > > > > > > > > > > > > > > > > > > > what can mean 'the community
> > > > > >
> > > > > > committed to
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > doing/releasing
> > > > > > > > > > > > > > > > > > > > > something'.
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > About SG, I also concerned why
> > > >
> > > > such
> > > > > >
> > > > > > a big
> > > > > > > > > > feature
> > > > > > > > > > > > >
> > > > > > > > > > > > > has
> > > > > > > > > > > > > > > > > quite a
> > > > > > > > > > > > > > > > > > > few
> > > > > > > > > > > > > > > > > > > > > > > > > discussions on the list. But it
> > > >
> > > > is
> > > > > > > >
> > > > > > > > another
> > > > > > > > > > story.
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 19:33,
> > > > > >
> > > > > > Vladimir
> > > > > > > > > > Ozerov <
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > Folks,
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > Please stop looking for
> > >
> > > enemies
> > > > > > > > >
> > > > > > > > > everywhere.
> > > > > > > > > > > >
> > > > > > > > > > > > Just
> > > > > > > > > > > > > > went
> > > > > > > > > > > > > > > > > > through
> > > > > > > > > > > > > > > > > > > > > this
> > > > > > > > > > > > > > > > > > > > > > > > thread
> > > > > > > > > > > > > > > > > > > > > > > > > > and search for "service"
> > >
> > > word.
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 7:30
> > >
> > > PM
> > > > > >
> > > > > > Denis
> > > > > > > > > > Magda <
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > dmagda@apache.org
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > Denis, as PMC Chair,
> > >
> > > could
> > > > you
> > > > > > > >
> > > > > > > > please
> > > > > > > > > > > >
> > > > > > > > > > > > control,
> > > > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > > > Service
> > > > > > > > > > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > > > > > > > > > > > > > inclusion/exclusion is
> > > > > >
> > > > > > discussed
> > > > > > > > > > properly
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > according
> > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > Apache
> > > > > > > > > > > > > > > > > > > > > > > > Way.
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > It's fine when
> > > > > > > >
> > > > > > > > committers/contributors
> > > > > > > > > > have
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > private
> > > > > > > > > > > > > > > > > > > > discussions
> > > > > > > > > > > > > > > > > > > > > > > > related
> > > > > > > > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > > > > > > a feature they've been
> > > >
> > > > working
> > > > > >
> > > > > > on.
> > > > > > > > Not
> > > > > > > > > > > > >
> > > > > > > > > > > > > everything
> > > > > > > > > > > > > > > > should
> > > > > > > > > > > > > > > > > > go
> > > > > > > > > > > > > > > > > > > > > > through
> > > > > > > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > > > > > dev
> > > > > > > > > > > > > > > > > > > > > > > > > > > list. Otherwise, it will be
> > > > > > > >
> > > > > > > > inundated.
> > > > > > > > > > > >
> > > > > > > > > > > > However,
> > > > > > > > > > > > > > > > agree,
> > > > > > > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > > > > > > > > > architectural
> > > > > > > > > > > > > > > > > > > > > > > > > > > and release decisions need
> > > >
> > > > to be
> > > > > >
> > > > > > done
> > > > > > > > > > > >
> > > > > > > > > > > > publicly.
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > Speaking about Service
> > >
> > > Grid,
> > > > > >
> > > > > > there
> > > > > > > > was
> > > > > > > > > a
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > discussion
> > > > > > > > > > > > > > > > > where
> > > > > > > > > > > > > > > > > > I
> > > > > > > > > > > > > > > > > > > > saw
> > > > > > > > > > > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > > > > > > > > was
> > > > > > > > > > > > > > > > > > > > > > > > > > > questionable whether it
> > >
> > > gets
> > > > > >
> > > > > > added to
> > > > > > > > > the
> > > > > > > > > > > > >
> > > > > > > > > > > > > release
> > > > > > > > > > > > > > or
> > > > > > > > > > > > > > > > > not.
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > *Vladislav*, could you
> > >
> > > please
> > > > > >
> > > > > > shed
> > > > > > > > some
> > > > > > > > > > light
> > > > > > > > > > > >
> > > > > > > > > > > > on
> > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > current
> > > > > > > > > > > > > > > > > > > > > > status of
> > > > > > > > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > > > > > service grid?
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at
> > >
> > > 9:12
> > > > AM
> > > > > > > >
> > > > > > > > Dmitriy
> > > > > > > > > > > >
> > > > > > > > > > > > Pavlov <
> > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > Ok, let's wait for
> > >
> > > feedback
> > > > > >
> > > > > > from SG
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Author(s)/Reviewer(s)
> > > > > > > > > > > > > > > > > > > > > > first. If
> > > > > > > > > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > > > > > > > > > > > > > not ready, ok. But I
> > > >
> > > > thought
> > > > > >
> > > > > > it is
> > > > > > > > > > almost
> > > > > > > > > > > > >
> > > > > > > > > > > > > done.
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > I apologize if I missed
> > > >
> > > > some
> > > > > > > > > >
> > > > > > > > > > discussion (it
> > > > > > > > > > > > >
> > > > > > > > > > > > > can
> > > > > > > > > > > > > > > > > happen),
> > > > > > > > > > > > > > > > > > > but
> > > > > > > > > > > > > > > > > > > > > > > > > > > > According to the
> > >
> > > statement
> > > > "our
> > > > > > > > >
> > > > > > > > > current
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > agreement"
> > > > > > > > > > > > > > > > > > > > > > > > > > > > I can suspect some
> > >
> > > members
> > > > are
> > > > > > > >
> > > > > > > > making
> > > > > > > > > > some
> > > > > > > > > > > > >
> > > > > > > > > > > > > sort
> > > > > > > > > > > > > > of
> > > > > > > > > > > > > > > > > > private
> > > > > > > > > > > > > > > > > > > > > > > > agreements,
> > > > > > > > > > > > > > > > > > > > > > > > > > > and
> > > > > > > > > > > > > > > > > > > > > > > > > > > > do not to discuss it on
> > >
> > > the
> > > > > >
> > > > > > list.
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > Let's build consensus
> > >
> > > here
> > > > > >
> > > > > > first,
> > > > > > > > and
> > > > > > > > > > then
> > > > > > > > > > > > >
> > > > > > > > > > > > > name
> > > > > > > > > > > > > > an
> > > > > > > > > > > > > > > > > > > > agreement.
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > Denis, as PMC Chair,
> > >
> > > could
> > > > you
> > > > > > > >
> > > > > > > > please
> > > > > > > > > > > >
> > > > > > > > > > > > control,
> > > > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > > > Service
> > > > > > > > > > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > > > > > > > > > > > > > inclusion/exclusion is
> > > > > >
> > > > > > discussed
> > > > > > > > > > properly
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > according
> > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > Apache
> > > > > > > > > > > > > > > > > > > > > > > > Way.
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в
> > > >
> > > > 18:55,
> > > > > > > > >
> > > > > > > > > Vladimir
> > > > > > > > > > > >
> > > > > > > > > > > > Ozerov
> > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > This is an outcome of
> > > >
> > > > current
> > > > > > > >
> > > > > > > > state
> > > > > > > > > > of
> > > > > > > > > > > > >
> > > > > > > > > > > > > Service
> > > > > > > > > > > > > > > > Grid -
> > > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > > > > > > > > > ready.
> > > > > > > > > > > > > > > > > > > > > > > > > > > We
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > never committed to have
> > > >
> > > > it to
> > > > > > > >
> > > > > > > > 2.7.
> > > > > > > > > > Our goal
> > > > > > > > > > > > >
> > > > > > > > > > > > > was
> > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > try
> > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > include
> > > > > > > > > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > > > > > > > > into
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > 2.7.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at
> > > >
> > > > 6:48
> > > > > >
> > > > > > PM
> > > > > > > > > > Dmitriy
> > > > > > > > > > > > >
> > > > > > > > > > > > > Pavlov
> > > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Could you please
> > > >
> > > > provide a
> > > > > > > > > >
> > > > > > > > > > reference to
> > > > > > > > > > > > >
> > > > > > > > > > > > > some
> > > > > > > > > > > > > > > > > thread?
> > > > > > > > > > > > > > > > > > > > > > Probably I
> > > > > > > > > > > > > > > > > > > > > > > > > > > missed
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > it.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г.
> > >
> > > в
> > > > > >
> > > > > > 18:46,
> > > > > > > > > > Vladimir
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Ozerov <
> > > > > > > > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Our current
> > > >
> > > > agreement is
> > > > > >
> > > > > > that
> > > > > > > > > > Service
> > > > > > > > > > > > >
> > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > out
> > > > > > > > > > > > > > > > > > of
> > > > > > > > > > > > > > > > > > > > > scope.
> > > > > > > > > > > > > > > > > > > > > > > > This
> > > > > > > > > > > > > > > > > > > > > > > > > > > is a
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > huge
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > feature, which
> > >
> > > hasn't
> > > > > >
> > > > > > entered
> > > > > > > > > > review
> > > > > > > > > > > > >
> > > > > > > > > > > > > stage
> > > > > > > > > > > > > > so
> > > > > > > > > > > > > > > > > far,
> > > > > > > > > > > > > > > > > > We
> > > > > > > > > > > > > > > > > > > > > will
> > > > > > > > > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > able to
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > review/fix/test it
> > > > > >
> > > > > > properly.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27,
> > >
> > > 2018
> > > > at
> > > > > >
> > > > > > 6:32
> > > > > > > > PM
> > > > > > > > > > Dmitriy
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Pavlov
> > > > > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I agree, and I
> > > >
> > > > prefer
> > > > > >
> > > > > > four
> > > > > > > > > > weeks for
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > stabilization*
> > > > > > > > > > > > > > > > > > > > (1
> > > > > > > > > > > > > > > > > > > > > > Oct -
> > > > > > > > > > > > > > > > > > > > > > > > 29
> > > > > > > > > > > > > > > > > > > > > > > > > > > Oct)
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Do I understand
> > >
> > > it
> > > > > > > >
> > > > > > > > correctly:
> > > > > > > > > > Service
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > > > still
> > > > > > > > > > > > > > > > > > > > in
> > > > > > > > > > > > > > > > > > > > > > scope,
> > > > > > > > > > > > > > > > > > > > > > > > > > > isn't
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > it? I
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > find it very
> > > >
> > > > important.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018
> > > >
> > > > г. в
> > > > > > > >
> > > > > > > > 18:28,
> > > > > > > > > > Nikolay
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Izhikov <
> > > > > > > > > > > > > > > > > > > > > > > > > > > nizhikov@apache.org
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hello, Vova.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Thank you for
> > > >
> > > > clear
> > > > > > > >
> > > > > > > > release
> > > > > > > > > > status.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I'm +1 for your
> > > > > >
> > > > > > proposal.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент.
> > > >
> > > > 2018 г.,
> > > > > > > >
> > > > > > > > 18:25
> > > > > > > > > > Alexey
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Kuznetsov
> > > > > > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > akuznetsov@apache.org
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Vova,
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Huge +1 to
> > >
> > > do a
> > > > > > > > > >
> > > > > > > > > > stabilization.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Alexey
> > > >
> > > > Kuznetsov
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > > > > > > > > > Best regards,
> > > > > > > > > > > > > > > > > > > > > > > > Andrey Kuznetsov.
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > > > > > > > Best Regards, Vyacheslav D.
> > > > > > > > > > > > > > > > > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Best Regards, Vyacheslav D.
> > > > > >
> >
> >
> > --
> > Best regards,
> > Andrey Kuznetsov.
Re: Apache Ignite 2.7 release
Posted by Andrey Gura <ag...@apache.org>.
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 <st...@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 <dp...@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 <ni...@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 <
> > daradurvs@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 <
> > > dsetrakyan@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.spb@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 <dm...@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 <
> > > > >
> > > > > nizhikov@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 <
> > > > > > >
> > > > > > > dsetrakyan@apache.org
> > > > > > > > > :
> > > > > > > > > >
> > > > > > > > > > > Dmitriy,
> > > > > > > > > > >
> > > > > > > > > > > We agreed in the beginning of this thread that Service
> > Grid
> > > > >
> > > > > changes
> > > > > > > > > are not
> > > > > > > > > > > going to make the release because the community still did
> > > not
> > > > > > >
> > > > > > > approve
> > > > > > > > > the
> > > > > > > > > > > design. Nothing has changed since. I have not seen any
> > > design
> > > > > > > > >
> > > > > > > > > discussions.
> > > > > > > > > > > At this point, I have no confidence that the Service Grid
> > > > >
> > > > > changes
> > > > > > > > will
> > > > > > > > > make
> > > > > > > > > > > it into the 2.8 release. The 2.7 release seems out of
> > > question
> > > > > > > > >
> > > > > > > > > altogether.
> > > > > > > > > > >
> > > > > > > > > > > Also, Nikolay is a release manager. We should let him
> > > drive the
> > > > > > > > >
> > > > > > > > > release. To
> > > > > > > > > > > my knowledge, he is doing a great job and the release is
> > > going
> > > > > > > > >
> > > > > > > > > according to
> > > > > > > > > > > the schedule he proposed.
> > > > > > > > > > >
> > > > > > > > > > > D.
> > > > > > > > > > >
> > > > > > > > > > > On Fri, Sep 28, 2018 at 4:31 AM Dmitriy Pavlov <
> > > > > > > >
> > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > > Hi Dmitriy, Vladimir,
> > > > > > > > > > > >
> > > > > > > > > > > > I suggest we stop this nonsense with release
> > > dates-pushing
> > > > > > >
> > > > > > > because
> > > > > > > > of
> > > > > > > > > > >
> > > > > > > > > > > some
> > > > > > > > > > > > open question.
> > > > > > > > > > > >
> > > > > > > > > > > > Just because you disagreed with any include/exclude
> > > something
> > > > > > >
> > > > > > > into
> > > > > > > > > scope,
> > > > > > > > > > > > does not mean that whole community disagreed.
> > > > > > > > > > > >
> > > > > > > > > > > > If folks will start a separate discussion with results
> > > of the
> > > > > > > > >
> > > > > > > > > review, I
> > > > > > > > > > >
> > > > > > > > > > > see
> > > > > > > > > > > > no reasons to reject their contribution, even if we
> > need
> > > to
> > > > > > >
> > > > > > > revisit
> > > > > > > > > our
> > > > > > > > > > > > agreements and wait for a couple of days more.
> > > > > > > > > > > >
> > > > > > > > > > > > Am I missing some reason why dates are so fundamentally
> > > > >
> > > > > important
> > > > > > > > to
> > > > > > > > > you?
> > > > > > > > > > > >
> > > > > > > > > > > > Sincerely,
> > > > > > > > > > > > Dmitriy Pavlov
> > > > > > > > > > > >
> > > > > > > > > > > > пт, 28 сент. 2018 г. в 12:20, Dmitriy Setrakyan <
> > > > > > > > >
> > > > > > > > > dsetrakyan@apache.org>:
> > > > > > > > > > > >
> > > > > > > > > > > > > If services is not ready, which it is not, then we
> > > should
> > > > > > >
> > > > > > > include
> > > > > > > > > them
> > > > > > > > > > > >
> > > > > > > > > > > > into
> > > > > > > > > > > > > the next release. There is no need to force them into
> > > 2.7.
> > > > >
> > > > > I
> > > > > > > > > suggest we
> > > > > > > > > > > > > move according to the schedule we all agreed on.
> > > > > > > > > > > > >
> > > > > > > > > > > > > D.
> > > > > > > > > > > > >
> > > > > > > > > > > > > On Fri, Sep 28, 2018 at 1:22 AM Dmitriy Pavlov <
> > > > > > > > >
> > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > > > Yes, so correct statement is "community did not
> > make
> > > any
> > > > > > > > >
> > > > > > > > > decisions
> > > > > > > > > > > >
> > > > > > > > > > > > about
> > > > > > > > > > > > > > services not go to 2.7/ services are out of scope".
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > If so, please forgive me my confusion.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:19, Vladimir Ozerov <
> > > > > > > > >
> > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > >
> > > > > > > > > > > > :
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Exactly. So correct statement is “it is up to
> > > > >
> > > > > *community*
> > > > > > > to
> > > > > > > > > decide
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > whether
> > > > > > > > > > > > > > > something goes to 2.7”.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:11, Dmitriy Pavlov <
> > > > > > > > > > >
> > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > :
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > No, it is up to the community to discuss after
> > > their
> > > > > > >
> > > > > > > review
> > > > > > > > > > > >
> > > > > > > > > > > > results.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:09, Vladimir Ozerov <
> > > > > > > > > > > >
> > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Did I read your words correctly that it is up
> > > to
> > > > > > > > >
> > > > > > > > > implementor
> > > > > > > > > > >
> > > > > > > > > > > of a
> > > > > > > > > > > > > > > single
> > > > > > > > > > > > > > > > > feature to decide whether release of all
> > other
> > > > >
> > > > > features
> > > > > > > > and
> > > > > > > > > > >
> > > > > > > > > > > fixes
> > > > > > > > > > > > > to
> > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > delayed?
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:00, Dmitriy Pavlov
> > <
> > > > > > > > > > > > >
> > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > My point we can wait a bit for services
> > > because
> > > > > > > > > > > > > > > > > > 1 we are open-minded and we don't have
> > > outside
> > > > > > > >
> > > > > > > > pressure
> > > > > > > > > to
> > > > > > > > > > >
> > > > > > > > > > > do
> > > > > > > > > > > > > > > release
> > > > > > > > > > > > > > > > in
> > > > > > > > > > > > > > > > > > October
> > > > > > > > > > > > > > > > > > 2 and services it is not some new feature,
> > > which
> > > > > > > > >
> > > > > > > > > suddenly
> > > > > > > > > > > > >
> > > > > > > > > > > > > appeared
> > > > > > > > > > > > > > > in
> > > > > > > > > > > > > > > > > > autumn, it is a well known and important
> > > feature.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > So it is up to Vyacheslav, Anton and
> > Nikolay
> > > to
> > > > > > >
> > > > > > > decide.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Decisions can be services are not
> > > ready/ready to
> > > > > > >
> > > > > > > merge
> > > > > > > > > only
> > > > > > > > > > >
> > > > > > > > > > > to
> > > > > > > > > > > > > > > > > master/ready
> > > > > > > > > > > > > > > > > > to merge to master and to 2.7.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 10:46, Vladimir
> > > Ozerov <
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > Dmitry,
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > Community agreement was to perform the
> > > release
> > > > >
> > > > > in
> > > > > > > > > October.
> > > > > > > > > > >
> > > > > > > > > > > Of
> > > > > > > > > > > > > > > course
> > > > > > > > > > > > > > > > we
> > > > > > > > > > > > > > > > > > can
> > > > > > > > > > > > > > > > > > > wait a bit for services. Then we wait a
> > > bit for
> > > > > > >
> > > > > > > other
> > > > > > > > > cool
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > features
> > > > > > > > > > > > > > > > > ready
> > > > > > > > > > > > > > > > > > > by that time, then again and again, and
> > > release
> > > > > > >
> > > > > > > will
> > > > > > > > > never
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > happen.
> > > > > > > > > > > > > > > > And
> > > > > > > > > > > > > > > > > > > while we are waiting for new features to
> > > come,
> > > > > > > >
> > > > > > > > already
> > > > > > > > > > > > >
> > > > > > > > > > > > > completerd
> > > > > > > > > > > > > > > > > > features
> > > > > > > > > > > > > > > > > > > cannot be used by anyone.
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > This is why we have an agreement that if
> > > > >
> > > > > feature is
> > > > > > > > not
> > > > > > > > > > > >
> > > > > > > > > > > > ready,
> > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > should
> > > > > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > > moved to future release, instead of
> > > shifting
> > > > > > >
> > > > > > > release.
> > > > > > > > > The
> > > > > > > > > > > >
> > > > > > > > > > > > sole
> > > > > > > > > > > > > > > reason
> > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > have strict dates when decisions are made
> > > is
> > > > >
> > > > > to let
> > > > > > > > > release
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > happen.
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at 2:22 AM Dmitriy
> > > Pavlov
> > > > >
> > > > > <
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > Vladimir, I'm not searching for enemy,
> > > and
> > > > >
> > > > > not
> > > > > > > > > fighting
> > > > > > > > > > > >
> > > > > > > > > > > > with
> > > > > > > > > > > > > > > you.
> > > > > > > > > > > > > > > > > I'm
> > > > > > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > > > > happy about cases when we are hurrying.
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > We can't fix test, fill ticket details,
> > > can't
> > > > > > >
> > > > > > > wait
> > > > > > > > > for
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > contributions
> > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > finish their tasks. It is not best
> > idea
> > > to
> > > > >
> > > > > use
> > > > > > > > > > >
> > > > > > > > > > > experience
> > > > > > > > > > > > > from
> > > > > > > > > > > > > > > > > > > commercial
> > > > > > > > > > > > > > > > > > > > companies in open source. Are there any
> > > > >
> > > > > pressure
> > > > > > > > > outside
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > community?
> > > > > > > > > > > > > > > > > Did
> > > > > > > > > > > > > > > > > > > > someone promised rest of features to be
> > > > >
> > > > > released
> > > > > > > at
> > > > > > > > > 30
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > September?
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > Let's remember principle do-orcracy,
> > > power of
> > > > > > >
> > > > > > > those
> > > > > > > > > who
> > > > > > > > > > >
> > > > > > > > > > > do.
> > > > > > > > > > > > > If
> > > > > > > > > > > > > > > > > > contribor
> > > > > > > > > > > > > > > > > > > > does change and reviewer does review,
> > > let's
> > > > >
> > > > > give
> > > > > > > > > right of
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > making
> > > > > > > > > > > > > > > > > > decision
> > > > > > > > > > > > > > > > > > > > to them, but not to some closed club of
> > > > >
> > > > > people
> > > > > > > who
> > > > > > > > > > > >
> > > > > > > > > > > > privately
> > > > > > > > > > > > > > > > discuss
> > > > > > > > > > > > > > > > > > > > something.
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > Sincerely
> > > > > > > > > > > > > > > > > > > > Dmitriy Pavlov
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г., 23:42 Vyacheslav
> > > > >
> > > > > Daradur <
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > daradurvs@gmail.com
> > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > Hi Igniters!
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > As I have written about Service Grid
> > > > >
> > > > > before [1]
> > > > > > > > I'm
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > finalizing
> > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > solution to be sure that
> > > implementation is
> > > > > > > > >
> > > > > > > > > reliable.
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > About including it in 2.7, if we talk
> > > that
> > > > >
> > > > > code
> > > > > > > > > freeze
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > tomorrow
> > > > > > > > > > > > > > > > > then
> > > > > > > > > > > > > > > > > > > > > the solution is not ready to merge
> > yet.
> > > > > > > > > > > > > > > > > > > > > I hope that prereviewers Anton
> > > Vinogradov
> > > > >
> > > > > and
> > > > > > > > > Nikolay
> > > > > > > > > > > > >
> > > > > > > > > > > > > Izhikov
> > > > > > > > > > > > > > > > will
> > > > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > > > > able to answer if solution out of
> > > scope or
> > > > >
> > > > > not
> > > > > > > > in a
> > > > > > > > > > > >
> > > > > > > > > > > > couple
> > > > > > > > > > > > > of
> > > > > > > > > > > > > > > > days.
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > [1]
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > >
> > > > >
> > >
> > http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-release-td34076.html#a34485
> > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 11:14 PM
> > > Dmitriy
> > > > > > >
> > > > > > > Pavlov <
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > Yes, I agree, NPE during WAL flush
> > is
> > > > > > > >
> > > > > > > > definitely
> > > > > > > > > a
> > > > > > > > > > > > >
> > > > > > > > > > > > > blocker.
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > It is strange why the current test
> > > set
> > > > >
> > > > > did
> > > > > > > not
> > > > > > > > > fail
> > > > > > > > > > > >
> > > > > > > > > > > > after
> > > > > > > > > > > > > > > > commit.
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 21:45,
> > Andrey
> > > > > > >
> > > > > > > Kuznetsov
> > > > > > > > <
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > stkuzma@gmail.com
> > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > Igniters,
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > I've bumped into a new bug in WAL
> > > > >
> > > > > manager
> > > > > > > > > recently,
> > > > > > > > > > > >
> > > > > > > > > > > > see
> > > > > > > > > > > > > > > [1].
> > > > > > > > > > > > > > > > It
> > > > > > > > > > > > > > > > > > > looks
> > > > > > > > > > > > > > > > > > > > > > > critical enough, and can be a
> > good
> > > > > > >
> > > > > > > candidate
> > > > > > > > > for
> > > > > > > > > > > >
> > > > > > > > > > > > fixing
> > > > > > > > > > > > > > > > before
> > > > > > > > > > > > > > > > > > 2.7
> > > > > > > > > > > > > > > > > > > > > release.
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > Do you agree?
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > [1]
> > > > > > > > > > > >
> > > > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-9731
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 19:45,
> > > Dmitriy
> > > > > > >
> > > > > > > Pavlov
> > > > > > > > <
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > I need Vhyacheslav's opinion to
> > > be
> > > > > > > >
> > > > > > > > absolutely
> > > > > > > > > > >
> > > > > > > > > > > sure
> > > > > > > > > > > > > what
> > > > > > > > > > > > > > > > > status
> > > > > > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > > > > > > now.
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > We never committed to dates of
> > > > >
> > > > > release,
> > > > > > > as
> > > > > > > > > well.
> > > > > > > > > > >
> > > > > > > > > > > I
> > > > > > > > > > > > > > don't
> > > > > > > > > > > > > > > > > quite
> > > > > > > > > > > > > > > > > > > > > understand
> > > > > > > > > > > > > > > > > > > > > > > > what can mean 'the community
> > > > >
> > > > > committed to
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > doing/releasing
> > > > > > > > > > > > > > > > > > > > something'.
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > About SG, I also concerned why
> > > such
> > > > >
> > > > > a big
> > > > > > > > > feature
> > > > > > > > > > > >
> > > > > > > > > > > > has
> > > > > > > > > > > > > > > > quite a
> > > > > > > > > > > > > > > > > > few
> > > > > > > > > > > > > > > > > > > > > > > > discussions on the list. But it
> > > is
> > > > > > >
> > > > > > > another
> > > > > > > > > story.
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 19:33,
> > > > >
> > > > > Vladimir
> > > > > > > > > Ozerov <
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > Folks,
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > Please stop looking for
> > enemies
> > > > > > > >
> > > > > > > > everywhere.
> > > > > > > > > > >
> > > > > > > > > > > Just
> > > > > > > > > > > > > went
> > > > > > > > > > > > > > > > > through
> > > > > > > > > > > > > > > > > > > > this
> > > > > > > > > > > > > > > > > > > > > > > thread
> > > > > > > > > > > > > > > > > > > > > > > > > and search for "service"
> > word.
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 7:30
> > PM
> > > > >
> > > > > Denis
> > > > > > > > > Magda <
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > dmagda@apache.org
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > Denis, as PMC Chair,
> > could
> > > you
> > > > > > >
> > > > > > > please
> > > > > > > > > > >
> > > > > > > > > > > control,
> > > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > > Service
> > > > > > > > > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > > > > > > > > > > > > inclusion/exclusion is
> > > > >
> > > > > discussed
> > > > > > > > > properly
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > according
> > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > Apache
> > > > > > > > > > > > > > > > > > > > > > > Way.
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > It's fine when
> > > > > > >
> > > > > > > committers/contributors
> > > > > > > > > have
> > > > > > > > > > > > >
> > > > > > > > > > > > > private
> > > > > > > > > > > > > > > > > > > discussions
> > > > > > > > > > > > > > > > > > > > > > > related
> > > > > > > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > > > > > a feature they've been
> > > working
> > > > >
> > > > > on.
> > > > > > > Not
> > > > > > > > > > > >
> > > > > > > > > > > > everything
> > > > > > > > > > > > > > > should
> > > > > > > > > > > > > > > > > go
> > > > > > > > > > > > > > > > > > > > > through
> > > > > > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > > > > dev
> > > > > > > > > > > > > > > > > > > > > > > > > > list. Otherwise, it will be
> > > > > > >
> > > > > > > inundated.
> > > > > > > > > > >
> > > > > > > > > > > However,
> > > > > > > > > > > > > > > agree,
> > > > > > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > > > > > > > > architectural
> > > > > > > > > > > > > > > > > > > > > > > > > > and release decisions need
> > > to be
> > > > >
> > > > > done
> > > > > > > > > > >
> > > > > > > > > > > publicly.
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > Speaking about Service
> > Grid,
> > > > >
> > > > > there
> > > > > > > was
> > > > > > > > a
> > > > > > > > > > > > >
> > > > > > > > > > > > > discussion
> > > > > > > > > > > > > > > > where
> > > > > > > > > > > > > > > > > I
> > > > > > > > > > > > > > > > > > > saw
> > > > > > > > > > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > > > > > > > was
> > > > > > > > > > > > > > > > > > > > > > > > > > questionable whether it
> > gets
> > > > >
> > > > > added to
> > > > > > > > the
> > > > > > > > > > > >
> > > > > > > > > > > > release
> > > > > > > > > > > > > or
> > > > > > > > > > > > > > > > not.
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > *Vladislav*, could you
> > please
> > > > >
> > > > > shed
> > > > > > > some
> > > > > > > > > light
> > > > > > > > > > >
> > > > > > > > > > > on
> > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > current
> > > > > > > > > > > > > > > > > > > > > status of
> > > > > > > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > > > > service grid?
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at
> > 9:12
> > > AM
> > > > > > >
> > > > > > > Dmitriy
> > > > > > > > > > >
> > > > > > > > > > > Pavlov <
> > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > Ok, let's wait for
> > feedback
> > > > >
> > > > > from SG
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Author(s)/Reviewer(s)
> > > > > > > > > > > > > > > > > > > > > first. If
> > > > > > > > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > > > > > > > > > > > > not ready, ok. But I
> > > thought
> > > > >
> > > > > it is
> > > > > > > > > almost
> > > > > > > > > > > >
> > > > > > > > > > > > done.
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > I apologize if I missed
> > > some
> > > > > > > > >
> > > > > > > > > discussion (it
> > > > > > > > > > > >
> > > > > > > > > > > > can
> > > > > > > > > > > > > > > > happen),
> > > > > > > > > > > > > > > > > > but
> > > > > > > > > > > > > > > > > > > > > > > > > > > According to the
> > statement
> > > "our
> > > > > > > >
> > > > > > > > current
> > > > > > > > > > > > >
> > > > > > > > > > > > > agreement"
> > > > > > > > > > > > > > > > > > > > > > > > > > > I can suspect some
> > members
> > > are
> > > > > > >
> > > > > > > making
> > > > > > > > > some
> > > > > > > > > > > >
> > > > > > > > > > > > sort
> > > > > > > > > > > > > of
> > > > > > > > > > > > > > > > > private
> > > > > > > > > > > > > > > > > > > > > > > agreements,
> > > > > > > > > > > > > > > > > > > > > > > > > > and
> > > > > > > > > > > > > > > > > > > > > > > > > > > do not to discuss it on
> > the
> > > > >
> > > > > list.
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > Let's build consensus
> > here
> > > > >
> > > > > first,
> > > > > > > and
> > > > > > > > > then
> > > > > > > > > > > >
> > > > > > > > > > > > name
> > > > > > > > > > > > > an
> > > > > > > > > > > > > > > > > > > agreement.
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > Denis, as PMC Chair,
> > could
> > > you
> > > > > > >
> > > > > > > please
> > > > > > > > > > >
> > > > > > > > > > > control,
> > > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > > Service
> > > > > > > > > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > > > > > > > > > > > > inclusion/exclusion is
> > > > >
> > > > > discussed
> > > > > > > > > properly
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > according
> > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > Apache
> > > > > > > > > > > > > > > > > > > > > > > Way.
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в
> > > 18:55,
> > > > > > > >
> > > > > > > > Vladimir
> > > > > > > > > > >
> > > > > > > > > > > Ozerov
> > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > This is an outcome of
> > > current
> > > > > > >
> > > > > > > state
> > > > > > > > > of
> > > > > > > > > > > >
> > > > > > > > > > > > Service
> > > > > > > > > > > > > > > Grid -
> > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > > > > > > > > ready.
> > > > > > > > > > > > > > > > > > > > > > > > > > We
> > > > > > > > > > > > > > > > > > > > > > > > > > > > never committed to have
> > > it to
> > > > > > >
> > > > > > > 2.7.
> > > > > > > > > Our goal
> > > > > > > > > > > >
> > > > > > > > > > > > was
> > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > try
> > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > include
> > > > > > > > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > > > > > > > into
> > > > > > > > > > > > > > > > > > > > > > > > > > > > 2.7.
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at
> > > 6:48
> > > > >
> > > > > PM
> > > > > > > > > Dmitriy
> > > > > > > > > > > >
> > > > > > > > > > > > Pavlov
> > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > Could you please
> > > provide a
> > > > > > > > >
> > > > > > > > > reference to
> > > > > > > > > > > >
> > > > > > > > > > > > some
> > > > > > > > > > > > > > > > thread?
> > > > > > > > > > > > > > > > > > > > > Probably I
> > > > > > > > > > > > > > > > > > > > > > > > > > missed
> > > > > > > > > > > > > > > > > > > > > > > > > > > > it.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г.
> > в
> > > > >
> > > > > 18:46,
> > > > > > > > > Vladimir
> > > > > > > > > > > > >
> > > > > > > > > > > > > Ozerov <
> > > > > > > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Our current
> > > agreement is
> > > > >
> > > > > that
> > > > > > > > > Service
> > > > > > > > > > > >
> > > > > > > > > > > > Grid
> > > > > > > > > > > > > is
> > > > > > > > > > > > > > > out
> > > > > > > > > > > > > > > > > of
> > > > > > > > > > > > > > > > > > > > scope.
> > > > > > > > > > > > > > > > > > > > > > > This
> > > > > > > > > > > > > > > > > > > > > > > > > > is a
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > huge
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > feature, which
> > hasn't
> > > > >
> > > > > entered
> > > > > > > > > review
> > > > > > > > > > > >
> > > > > > > > > > > > stage
> > > > > > > > > > > > > so
> > > > > > > > > > > > > > > > far,
> > > > > > > > > > > > > > > > > We
> > > > > > > > > > > > > > > > > > > > will
> > > > > > > > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > > > > > > > > > > > able to
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > review/fix/test it
> > > > >
> > > > > properly.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27,
> > 2018
> > > at
> > > > >
> > > > > 6:32
> > > > > > > PM
> > > > > > > > > Dmitriy
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Pavlov
> > > > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I agree, and I
> > > prefer
> > > > >
> > > > > four
> > > > > > > > > weeks for
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > stabilization*
> > > > > > > > > > > > > > > > > > > (1
> > > > > > > > > > > > > > > > > > > > > Oct -
> > > > > > > > > > > > > > > > > > > > > > > 29
> > > > > > > > > > > > > > > > > > > > > > > > > > Oct)
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Do I understand
> > it
> > > > > > >
> > > > > > > correctly:
> > > > > > > > > Service
> > > > > > > > > > > > >
> > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > > still
> > > > > > > > > > > > > > > > > > > in
> > > > > > > > > > > > > > > > > > > > > scope,
> > > > > > > > > > > > > > > > > > > > > > > > > > isn't
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > it? I
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > find it very
> > > important.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018
> > > г. в
> > > > > > >
> > > > > > > 18:28,
> > > > > > > > > Nikolay
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Izhikov <
> > > > > > > > > > > > > > > > > > > > > > > > > > nizhikov@apache.org
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hello, Vova.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Thank you for
> > > clear
> > > > > > >
> > > > > > > release
> > > > > > > > > status.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I'm +1 for your
> > > > >
> > > > > proposal.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент.
> > > 2018 г.,
> > > > > > >
> > > > > > > 18:25
> > > > > > > > > Alexey
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Kuznetsov
> > > > > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > > > > > > > akuznetsov@apache.org
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Vova,
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Huge +1 to
> > do a
> > > > > > > > >
> > > > > > > > > stabilization.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Alexey
> > > Kuznetsov
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > > > > > > > > Best regards,
> > > > > > > > > > > > > > > > > > > > > > > Andrey Kuznetsov.
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > > > > > > Best Regards, Vyacheslav D.
> > > > > > > > > > > > > > > > > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Best Regards, Vyacheslav D.
> > > > >
> > >
> >
>
>
> --
> Best regards,
> Andrey Kuznetsov.
Re: Apache Ignite 2.7 release
Posted by Andrey Kuznetsov <st...@gmail.com>.
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 <dp...@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 <ni...@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 <
> daradurvs@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 <
> > dsetrakyan@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.spb@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 <dm...@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 <
> > > >
> > > > nizhikov@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 <
> > > > > >
> > > > > > dsetrakyan@apache.org
> > > > > > > > :
> > > > > > > > >
> > > > > > > > > > Dmitriy,
> > > > > > > > > >
> > > > > > > > > > We agreed in the beginning of this thread that Service
> Grid
> > > >
> > > > changes
> > > > > > > > are not
> > > > > > > > > > going to make the release because the community still did
> > not
> > > > > >
> > > > > > approve
> > > > > > > > the
> > > > > > > > > > design. Nothing has changed since. I have not seen any
> > design
> > > > > > > >
> > > > > > > > discussions.
> > > > > > > > > > At this point, I have no confidence that the Service Grid
> > > >
> > > > changes
> > > > > > > will
> > > > > > > > make
> > > > > > > > > > it into the 2.8 release. The 2.7 release seems out of
> > question
> > > > > > > >
> > > > > > > > altogether.
> > > > > > > > > >
> > > > > > > > > > Also, Nikolay is a release manager. We should let him
> > drive the
> > > > > > > >
> > > > > > > > release. To
> > > > > > > > > > my knowledge, he is doing a great job and the release is
> > going
> > > > > > > >
> > > > > > > > according to
> > > > > > > > > > the schedule he proposed.
> > > > > > > > > >
> > > > > > > > > > D.
> > > > > > > > > >
> > > > > > > > > > On Fri, Sep 28, 2018 at 4:31 AM Dmitriy Pavlov <
> > > > > > >
> > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Hi Dmitriy, Vladimir,
> > > > > > > > > > >
> > > > > > > > > > > I suggest we stop this nonsense with release
> > dates-pushing
> > > > > >
> > > > > > because
> > > > > > > of
> > > > > > > > > >
> > > > > > > > > > some
> > > > > > > > > > > open question.
> > > > > > > > > > >
> > > > > > > > > > > Just because you disagreed with any include/exclude
> > something
> > > > > >
> > > > > > into
> > > > > > > > scope,
> > > > > > > > > > > does not mean that whole community disagreed.
> > > > > > > > > > >
> > > > > > > > > > > If folks will start a separate discussion with results
> > of the
> > > > > > > >
> > > > > > > > review, I
> > > > > > > > > >
> > > > > > > > > > see
> > > > > > > > > > > no reasons to reject their contribution, even if we
> need
> > to
> > > > > >
> > > > > > revisit
> > > > > > > > our
> > > > > > > > > > > agreements and wait for a couple of days more.
> > > > > > > > > > >
> > > > > > > > > > > Am I missing some reason why dates are so fundamentally
> > > >
> > > > important
> > > > > > > to
> > > > > > > > you?
> > > > > > > > > > >
> > > > > > > > > > > Sincerely,
> > > > > > > > > > > Dmitriy Pavlov
> > > > > > > > > > >
> > > > > > > > > > > пт, 28 сент. 2018 г. в 12:20, Dmitriy Setrakyan <
> > > > > > > >
> > > > > > > > dsetrakyan@apache.org>:
> > > > > > > > > > >
> > > > > > > > > > > > If services is not ready, which it is not, then we
> > should
> > > > > >
> > > > > > include
> > > > > > > > them
> > > > > > > > > > >
> > > > > > > > > > > into
> > > > > > > > > > > > the next release. There is no need to force them into
> > 2.7.
> > > >
> > > > I
> > > > > > > > suggest we
> > > > > > > > > > > > move according to the schedule we all agreed on.
> > > > > > > > > > > >
> > > > > > > > > > > > D.
> > > > > > > > > > > >
> > > > > > > > > > > > On Fri, Sep 28, 2018 at 1:22 AM Dmitriy Pavlov <
> > > > > > > >
> > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > > Yes, so correct statement is "community did not
> make
> > any
> > > > > > > >
> > > > > > > > decisions
> > > > > > > > > > >
> > > > > > > > > > > about
> > > > > > > > > > > > > services not go to 2.7/ services are out of scope".
> > > > > > > > > > > > >
> > > > > > > > > > > > > If so, please forgive me my confusion.
> > > > > > > > > > > > >
> > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:19, Vladimir Ozerov <
> > > > > > > >
> > > > > > > > vozerov@gridgain.com
> > > > > > > > > > >
> > > > > > > > > > > :
> > > > > > > > > > > > >
> > > > > > > > > > > > > > Exactly. So correct statement is “it is up to
> > > >
> > > > *community*
> > > > > > to
> > > > > > > > decide
> > > > > > > > > > > > >
> > > > > > > > > > > > > whether
> > > > > > > > > > > > > > something goes to 2.7”.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:11, Dmitriy Pavlov <
> > > > > > > > > >
> > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > :
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > > No, it is up to the community to discuss after
> > their
> > > > > >
> > > > > > review
> > > > > > > > > > >
> > > > > > > > > > > results.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:09, Vladimir Ozerov <
> > > > > > > > > > >
> > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > :
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Did I read your words correctly that it is up
> > to
> > > > > > > >
> > > > > > > > implementor
> > > > > > > > > >
> > > > > > > > > > of a
> > > > > > > > > > > > > > single
> > > > > > > > > > > > > > > > feature to decide whether release of all
> other
> > > >
> > > > features
> > > > > > > and
> > > > > > > > > >
> > > > > > > > > > fixes
> > > > > > > > > > > > to
> > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > delayed?
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:00, Dmitriy Pavlov
> <
> > > > > > > > > > > >
> > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > My point we can wait a bit for services
> > because
> > > > > > > > > > > > > > > > > 1 we are open-minded and we don't have
> > outside
> > > > > > >
> > > > > > > pressure
> > > > > > > > to
> > > > > > > > > >
> > > > > > > > > > do
> > > > > > > > > > > > > > release
> > > > > > > > > > > > > > > in
> > > > > > > > > > > > > > > > > October
> > > > > > > > > > > > > > > > > 2 and services it is not some new feature,
> > which
> > > > > > > >
> > > > > > > > suddenly
> > > > > > > > > > > >
> > > > > > > > > > > > appeared
> > > > > > > > > > > > > > in
> > > > > > > > > > > > > > > > > autumn, it is a well known and important
> > feature.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > So it is up to Vyacheslav, Anton and
> Nikolay
> > to
> > > > > >
> > > > > > decide.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Decisions can be services are not
> > ready/ready to
> > > > > >
> > > > > > merge
> > > > > > > > only
> > > > > > > > > >
> > > > > > > > > > to
> > > > > > > > > > > > > > > > master/ready
> > > > > > > > > > > > > > > > > to merge to master and to 2.7.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 10:46, Vladimir
> > Ozerov <
> > > > > > > > > > > > >
> > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Dmitry,
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Community agreement was to perform the
> > release
> > > >
> > > > in
> > > > > > > > October.
> > > > > > > > > >
> > > > > > > > > > Of
> > > > > > > > > > > > > > course
> > > > > > > > > > > > > > > we
> > > > > > > > > > > > > > > > > can
> > > > > > > > > > > > > > > > > > wait a bit for services. Then we wait a
> > bit for
> > > > > >
> > > > > > other
> > > > > > > > cool
> > > > > > > > > > > > >
> > > > > > > > > > > > > features
> > > > > > > > > > > > > > > > ready
> > > > > > > > > > > > > > > > > > by that time, then again and again, and
> > release
> > > > > >
> > > > > > will
> > > > > > > > never
> > > > > > > > > > > > >
> > > > > > > > > > > > > happen.
> > > > > > > > > > > > > > > And
> > > > > > > > > > > > > > > > > > while we are waiting for new features to
> > come,
> > > > > > >
> > > > > > > already
> > > > > > > > > > > >
> > > > > > > > > > > > completerd
> > > > > > > > > > > > > > > > > features
> > > > > > > > > > > > > > > > > > cannot be used by anyone.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > This is why we have an agreement that if
> > > >
> > > > feature is
> > > > > > > not
> > > > > > > > > > >
> > > > > > > > > > > ready,
> > > > > > > > > > > > it
> > > > > > > > > > > > > > > > should
> > > > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > moved to future release, instead of
> > shifting
> > > > > >
> > > > > > release.
> > > > > > > > The
> > > > > > > > > > >
> > > > > > > > > > > sole
> > > > > > > > > > > > > > reason
> > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > have strict dates when decisions are made
> > is
> > > >
> > > > to let
> > > > > > > > release
> > > > > > > > > > > > >
> > > > > > > > > > > > > happen.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at 2:22 AM Dmitriy
> > Pavlov
> > > >
> > > > <
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > Vladimir, I'm not searching for enemy,
> > and
> > > >
> > > > not
> > > > > > > > fighting
> > > > > > > > > > >
> > > > > > > > > > > with
> > > > > > > > > > > > > > you.
> > > > > > > > > > > > > > > > I'm
> > > > > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > > > happy about cases when we are hurrying.
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > We can't fix test, fill ticket details,
> > can't
> > > > > >
> > > > > > wait
> > > > > > > > for
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > contributions
> > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > finish their tasks. It is not best
> idea
> > to
> > > >
> > > > use
> > > > > > > > > >
> > > > > > > > > > experience
> > > > > > > > > > > > from
> > > > > > > > > > > > > > > > > > commercial
> > > > > > > > > > > > > > > > > > > companies in open source. Are there any
> > > >
> > > > pressure
> > > > > > > > outside
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > community?
> > > > > > > > > > > > > > > > Did
> > > > > > > > > > > > > > > > > > > someone promised rest of features to be
> > > >
> > > > released
> > > > > > at
> > > > > > > > 30
> > > > > > > > > > > > >
> > > > > > > > > > > > > September?
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > Let's remember principle do-orcracy,
> > power of
> > > > > >
> > > > > > those
> > > > > > > > who
> > > > > > > > > >
> > > > > > > > > > do.
> > > > > > > > > > > > If
> > > > > > > > > > > > > > > > > contribor
> > > > > > > > > > > > > > > > > > > does change and reviewer does review,
> > let's
> > > >
> > > > give
> > > > > > > > right of
> > > > > > > > > > > > >
> > > > > > > > > > > > > making
> > > > > > > > > > > > > > > > > decision
> > > > > > > > > > > > > > > > > > > to them, but not to some closed club of
> > > >
> > > > people
> > > > > > who
> > > > > > > > > > >
> > > > > > > > > > > privately
> > > > > > > > > > > > > > > discuss
> > > > > > > > > > > > > > > > > > > something.
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > Sincerely
> > > > > > > > > > > > > > > > > > > Dmitriy Pavlov
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г., 23:42 Vyacheslav
> > > >
> > > > Daradur <
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > daradurvs@gmail.com
> > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > Hi Igniters!
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > As I have written about Service Grid
> > > >
> > > > before [1]
> > > > > > > I'm
> > > > > > > > > > > > >
> > > > > > > > > > > > > finalizing
> > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > solution to be sure that
> > implementation is
> > > > > > > >
> > > > > > > > reliable.
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > About including it in 2.7, if we talk
> > that
> > > >
> > > > code
> > > > > > > > freeze
> > > > > > > > > > > > >
> > > > > > > > > > > > > tomorrow
> > > > > > > > > > > > > > > > then
> > > > > > > > > > > > > > > > > > > > the solution is not ready to merge
> yet.
> > > > > > > > > > > > > > > > > > > > I hope that prereviewers Anton
> > Vinogradov
> > > >
> > > > and
> > > > > > > > Nikolay
> > > > > > > > > > > >
> > > > > > > > > > > > Izhikov
> > > > > > > > > > > > > > > will
> > > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > > > able to answer if solution out of
> > scope or
> > > >
> > > > not
> > > > > > > in a
> > > > > > > > > > >
> > > > > > > > > > > couple
> > > > > > > > > > > > of
> > > > > > > > > > > > > > > days.
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > [1]
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > >
> > > >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-release-td34076.html#a34485
> > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 11:14 PM
> > Dmitriy
> > > > > >
> > > > > > Pavlov <
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > Yes, I agree, NPE during WAL flush
> is
> > > > > > >
> > > > > > > definitely
> > > > > > > > a
> > > > > > > > > > > >
> > > > > > > > > > > > blocker.
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > It is strange why the current test
> > set
> > > >
> > > > did
> > > > > > not
> > > > > > > > fail
> > > > > > > > > > >
> > > > > > > > > > > after
> > > > > > > > > > > > > > > commit.
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 21:45,
> Andrey
> > > > > >
> > > > > > Kuznetsov
> > > > > > > <
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > stkuzma@gmail.com
> > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > Igniters,
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > I've bumped into a new bug in WAL
> > > >
> > > > manager
> > > > > > > > recently,
> > > > > > > > > > >
> > > > > > > > > > > see
> > > > > > > > > > > > > > [1].
> > > > > > > > > > > > > > > It
> > > > > > > > > > > > > > > > > > looks
> > > > > > > > > > > > > > > > > > > > > > critical enough, and can be a
> good
> > > > > >
> > > > > > candidate
> > > > > > > > for
> > > > > > > > > > >
> > > > > > > > > > > fixing
> > > > > > > > > > > > > > > before
> > > > > > > > > > > > > > > > > 2.7
> > > > > > > > > > > > > > > > > > > > release.
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > Do you agree?
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > [1]
> > > > > > > > > > >
> > > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-9731
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 19:45,
> > Dmitriy
> > > > > >
> > > > > > Pavlov
> > > > > > > <
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > I need Vhyacheslav's opinion to
> > be
> > > > > > >
> > > > > > > absolutely
> > > > > > > > > >
> > > > > > > > > > sure
> > > > > > > > > > > > what
> > > > > > > > > > > > > > > > status
> > > > > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > > > > > now.
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > We never committed to dates of
> > > >
> > > > release,
> > > > > > as
> > > > > > > > well.
> > > > > > > > > >
> > > > > > > > > > I
> > > > > > > > > > > > > don't
> > > > > > > > > > > > > > > > quite
> > > > > > > > > > > > > > > > > > > > understand
> > > > > > > > > > > > > > > > > > > > > > > what can mean 'the community
> > > >
> > > > committed to
> > > > > > > > > > > > >
> > > > > > > > > > > > > doing/releasing
> > > > > > > > > > > > > > > > > > > something'.
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > About SG, I also concerned why
> > such
> > > >
> > > > a big
> > > > > > > > feature
> > > > > > > > > > >
> > > > > > > > > > > has
> > > > > > > > > > > > > > > quite a
> > > > > > > > > > > > > > > > > few
> > > > > > > > > > > > > > > > > > > > > > > discussions on the list. But it
> > is
> > > > > >
> > > > > > another
> > > > > > > > story.
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 19:33,
> > > >
> > > > Vladimir
> > > > > > > > Ozerov <
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > Folks,
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > Please stop looking for
> enemies
> > > > > > >
> > > > > > > everywhere.
> > > > > > > > > >
> > > > > > > > > > Just
> > > > > > > > > > > > went
> > > > > > > > > > > > > > > > through
> > > > > > > > > > > > > > > > > > > this
> > > > > > > > > > > > > > > > > > > > > > thread
> > > > > > > > > > > > > > > > > > > > > > > > and search for "service"
> word.
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 7:30
> PM
> > > >
> > > > Denis
> > > > > > > > Magda <
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > dmagda@apache.org
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > Denis, as PMC Chair,
> could
> > you
> > > > > >
> > > > > > please
> > > > > > > > > >
> > > > > > > > > > control,
> > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > Service
> > > > > > > > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > > > > > > > > > > > inclusion/exclusion is
> > > >
> > > > discussed
> > > > > > > > properly
> > > > > > > > > > > > >
> > > > > > > > > > > > > according
> > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > Apache
> > > > > > > > > > > > > > > > > > > > > > Way.
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > It's fine when
> > > > > >
> > > > > > committers/contributors
> > > > > > > > have
> > > > > > > > > > > >
> > > > > > > > > > > > private
> > > > > > > > > > > > > > > > > > discussions
> > > > > > > > > > > > > > > > > > > > > > related
> > > > > > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > > > > a feature they've been
> > working
> > > >
> > > > on.
> > > > > > Not
> > > > > > > > > > >
> > > > > > > > > > > everything
> > > > > > > > > > > > > > should
> > > > > > > > > > > > > > > > go
> > > > > > > > > > > > > > > > > > > > through
> > > > > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > > > dev
> > > > > > > > > > > > > > > > > > > > > > > > > list. Otherwise, it will be
> > > > > >
> > > > > > inundated.
> > > > > > > > > >
> > > > > > > > > > However,
> > > > > > > > > > > > > > agree,
> > > > > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > > > > > > > architectural
> > > > > > > > > > > > > > > > > > > > > > > > > and release decisions need
> > to be
> > > >
> > > > done
> > > > > > > > > >
> > > > > > > > > > publicly.
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > Speaking about Service
> Grid,
> > > >
> > > > there
> > > > > > was
> > > > > > > a
> > > > > > > > > > > >
> > > > > > > > > > > > discussion
> > > > > > > > > > > > > > > where
> > > > > > > > > > > > > > > > I
> > > > > > > > > > > > > > > > > > saw
> > > > > > > > > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > > > > > > was
> > > > > > > > > > > > > > > > > > > > > > > > > questionable whether it
> gets
> > > >
> > > > added to
> > > > > > > the
> > > > > > > > > > >
> > > > > > > > > > > release
> > > > > > > > > > > > or
> > > > > > > > > > > > > > > not.
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > *Vladislav*, could you
> please
> > > >
> > > > shed
> > > > > > some
> > > > > > > > light
> > > > > > > > > >
> > > > > > > > > > on
> > > > > > > > > > > > the
> > > > > > > > > > > > > > > > current
> > > > > > > > > > > > > > > > > > > > status of
> > > > > > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > > > service grid?
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at
> 9:12
> > AM
> > > > > >
> > > > > > Dmitriy
> > > > > > > > > >
> > > > > > > > > > Pavlov <
> > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > Ok, let's wait for
> feedback
> > > >
> > > > from SG
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Author(s)/Reviewer(s)
> > > > > > > > > > > > > > > > > > > > first. If
> > > > > > > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > > > > > > > > > > > not ready, ok. But I
> > thought
> > > >
> > > > it is
> > > > > > > > almost
> > > > > > > > > > >
> > > > > > > > > > > done.
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > I apologize if I missed
> > some
> > > > > > > >
> > > > > > > > discussion (it
> > > > > > > > > > >
> > > > > > > > > > > can
> > > > > > > > > > > > > > > happen),
> > > > > > > > > > > > > > > > > but
> > > > > > > > > > > > > > > > > > > > > > > > > > According to the
> statement
> > "our
> > > > > > >
> > > > > > > current
> > > > > > > > > > > >
> > > > > > > > > > > > agreement"
> > > > > > > > > > > > > > > > > > > > > > > > > > I can suspect some
> members
> > are
> > > > > >
> > > > > > making
> > > > > > > > some
> > > > > > > > > > >
> > > > > > > > > > > sort
> > > > > > > > > > > > of
> > > > > > > > > > > > > > > > private
> > > > > > > > > > > > > > > > > > > > > > agreements,
> > > > > > > > > > > > > > > > > > > > > > > > > and
> > > > > > > > > > > > > > > > > > > > > > > > > > do not to discuss it on
> the
> > > >
> > > > list.
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > Let's build consensus
> here
> > > >
> > > > first,
> > > > > > and
> > > > > > > > then
> > > > > > > > > > >
> > > > > > > > > > > name
> > > > > > > > > > > > an
> > > > > > > > > > > > > > > > > > agreement.
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > Denis, as PMC Chair,
> could
> > you
> > > > > >
> > > > > > please
> > > > > > > > > >
> > > > > > > > > > control,
> > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > Service
> > > > > > > > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > > > > > > > > > > > inclusion/exclusion is
> > > >
> > > > discussed
> > > > > > > > properly
> > > > > > > > > > > > >
> > > > > > > > > > > > > according
> > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > Apache
> > > > > > > > > > > > > > > > > > > > > > Way.
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в
> > 18:55,
> > > > > > >
> > > > > > > Vladimir
> > > > > > > > > >
> > > > > > > > > > Ozerov
> > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > This is an outcome of
> > current
> > > > > >
> > > > > > state
> > > > > > > > of
> > > > > > > > > > >
> > > > > > > > > > > Service
> > > > > > > > > > > > > > Grid -
> > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > > > > > > > ready.
> > > > > > > > > > > > > > > > > > > > > > > > > We
> > > > > > > > > > > > > > > > > > > > > > > > > > > never committed to have
> > it to
> > > > > >
> > > > > > 2.7.
> > > > > > > > Our goal
> > > > > > > > > > >
> > > > > > > > > > > was
> > > > > > > > > > > > > to
> > > > > > > > > > > > > > > try
> > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > include
> > > > > > > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > > > > > > into
> > > > > > > > > > > > > > > > > > > > > > > > > > > 2.7.
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at
> > 6:48
> > > >
> > > > PM
> > > > > > > > Dmitriy
> > > > > > > > > > >
> > > > > > > > > > > Pavlov
> > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > Could you please
> > provide a
> > > > > > > >
> > > > > > > > reference to
> > > > > > > > > > >
> > > > > > > > > > > some
> > > > > > > > > > > > > > > thread?
> > > > > > > > > > > > > > > > > > > > Probably I
> > > > > > > > > > > > > > > > > > > > > > > > > missed
> > > > > > > > > > > > > > > > > > > > > > > > > > > it.
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г.
> в
> > > >
> > > > 18:46,
> > > > > > > > Vladimir
> > > > > > > > > > > >
> > > > > > > > > > > > Ozerov <
> > > > > > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > Our current
> > agreement is
> > > >
> > > > that
> > > > > > > > Service
> > > > > > > > > > >
> > > > > > > > > > > Grid
> > > > > > > > > > > > is
> > > > > > > > > > > > > > out
> > > > > > > > > > > > > > > > of
> > > > > > > > > > > > > > > > > > > scope.
> > > > > > > > > > > > > > > > > > > > > > This
> > > > > > > > > > > > > > > > > > > > > > > > > is a
> > > > > > > > > > > > > > > > > > > > > > > > > > > > huge
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > feature, which
> hasn't
> > > >
> > > > entered
> > > > > > > > review
> > > > > > > > > > >
> > > > > > > > > > > stage
> > > > > > > > > > > > so
> > > > > > > > > > > > > > > far,
> > > > > > > > > > > > > > > > We
> > > > > > > > > > > > > > > > > > > will
> > > > > > > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > > > > > > > > > > able to
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > review/fix/test it
> > > >
> > > > properly.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27,
> 2018
> > at
> > > >
> > > > 6:32
> > > > > > PM
> > > > > > > > Dmitriy
> > > > > > > > > > > > >
> > > > > > > > > > > > > Pavlov
> > > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I agree, and I
> > prefer
> > > >
> > > > four
> > > > > > > > weeks for
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > stabilization*
> > > > > > > > > > > > > > > > > > (1
> > > > > > > > > > > > > > > > > > > > Oct -
> > > > > > > > > > > > > > > > > > > > > > 29
> > > > > > > > > > > > > > > > > > > > > > > > > Oct)
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Do I understand
> it
> > > > > >
> > > > > > correctly:
> > > > > > > > Service
> > > > > > > > > > > >
> > > > > > > > > > > > Grid
> > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > still
> > > > > > > > > > > > > > > > > > in
> > > > > > > > > > > > > > > > > > > > scope,
> > > > > > > > > > > > > > > > > > > > > > > > > isn't
> > > > > > > > > > > > > > > > > > > > > > > > > > > > it? I
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > find it very
> > important.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018
> > г. в
> > > > > >
> > > > > > 18:28,
> > > > > > > > Nikolay
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Izhikov <
> > > > > > > > > > > > > > > > > > > > > > > > > nizhikov@apache.org
> > > > > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hello, Vova.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Thank you for
> > clear
> > > > > >
> > > > > > release
> > > > > > > > status.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I'm +1 for your
> > > >
> > > > proposal.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент.
> > 2018 г.,
> > > > > >
> > > > > > 18:25
> > > > > > > > Alexey
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Kuznetsov
> > > > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > > > > > > akuznetsov@apache.org
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Vova,
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Huge +1 to
> do a
> > > > > > > >
> > > > > > > > stabilization.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Alexey
> > Kuznetsov
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > > > > > > > Best regards,
> > > > > > > > > > > > > > > > > > > > > > Andrey Kuznetsov.
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > > > > > Best Regards, Vyacheslav D.
> > > > > > > > > > > > > > > > > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Best Regards, Vyacheslav D.
> > > >
> >
>
--
Best regards,
Andrey Kuznetsov.
Re: Apache Ignite 2.7 release
Posted by Dmitriy Pavlov <dp...@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 <ni...@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 <da...@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 <
> dsetrakyan@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.spb@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 <dm...@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 <
> > >
> > > nizhikov@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 <
> > > > >
> > > > > dsetrakyan@apache.org
> > > > > > > :
> > > > > > > >
> > > > > > > > > Dmitriy,
> > > > > > > > >
> > > > > > > > > We agreed in the beginning of this thread that Service Grid
> > >
> > > changes
> > > > > > > are not
> > > > > > > > > going to make the release because the community still did
> not
> > > > >
> > > > > approve
> > > > > > > the
> > > > > > > > > design. Nothing has changed since. I have not seen any
> design
> > > > > > >
> > > > > > > discussions.
> > > > > > > > > At this point, I have no confidence that the Service Grid
> > >
> > > changes
> > > > > > will
> > > > > > > make
> > > > > > > > > it into the 2.8 release. The 2.7 release seems out of
> question
> > > > > > >
> > > > > > > altogether.
> > > > > > > > >
> > > > > > > > > Also, Nikolay is a release manager. We should let him
> drive the
> > > > > > >
> > > > > > > release. To
> > > > > > > > > my knowledge, he is doing a great job and the release is
> going
> > > > > > >
> > > > > > > according to
> > > > > > > > > the schedule he proposed.
> > > > > > > > >
> > > > > > > > > D.
> > > > > > > > >
> > > > > > > > > On Fri, Sep 28, 2018 at 4:31 AM Dmitriy Pavlov <
> > > > > >
> > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Hi Dmitriy, Vladimir,
> > > > > > > > > >
> > > > > > > > > > I suggest we stop this nonsense with release
> dates-pushing
> > > > >
> > > > > because
> > > > > > of
> > > > > > > > >
> > > > > > > > > some
> > > > > > > > > > open question.
> > > > > > > > > >
> > > > > > > > > > Just because you disagreed with any include/exclude
> something
> > > > >
> > > > > into
> > > > > > > scope,
> > > > > > > > > > does not mean that whole community disagreed.
> > > > > > > > > >
> > > > > > > > > > If folks will start a separate discussion with results
> of the
> > > > > > >
> > > > > > > review, I
> > > > > > > > >
> > > > > > > > > see
> > > > > > > > > > no reasons to reject their contribution, even if we need
> to
> > > > >
> > > > > revisit
> > > > > > > our
> > > > > > > > > > agreements and wait for a couple of days more.
> > > > > > > > > >
> > > > > > > > > > Am I missing some reason why dates are so fundamentally
> > >
> > > important
> > > > > > to
> > > > > > > you?
> > > > > > > > > >
> > > > > > > > > > Sincerely,
> > > > > > > > > > Dmitriy Pavlov
> > > > > > > > > >
> > > > > > > > > > пт, 28 сент. 2018 г. в 12:20, Dmitriy Setrakyan <
> > > > > > >
> > > > > > > dsetrakyan@apache.org>:
> > > > > > > > > >
> > > > > > > > > > > If services is not ready, which it is not, then we
> should
> > > > >
> > > > > include
> > > > > > > them
> > > > > > > > > >
> > > > > > > > > > into
> > > > > > > > > > > the next release. There is no need to force them into
> 2.7.
> > >
> > > I
> > > > > > > suggest we
> > > > > > > > > > > move according to the schedule we all agreed on.
> > > > > > > > > > >
> > > > > > > > > > > D.
> > > > > > > > > > >
> > > > > > > > > > > On Fri, Sep 28, 2018 at 1:22 AM Dmitriy Pavlov <
> > > > > > >
> > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > > Yes, so correct statement is "community did not make
> any
> > > > > > >
> > > > > > > decisions
> > > > > > > > > >
> > > > > > > > > > about
> > > > > > > > > > > > services not go to 2.7/ services are out of scope".
> > > > > > > > > > > >
> > > > > > > > > > > > If so, please forgive me my confusion.
> > > > > > > > > > > >
> > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:19, Vladimir Ozerov <
> > > > > > >
> > > > > > > vozerov@gridgain.com
> > > > > > > > > >
> > > > > > > > > > :
> > > > > > > > > > > >
> > > > > > > > > > > > > Exactly. So correct statement is “it is up to
> > >
> > > *community*
> > > > > to
> > > > > > > decide
> > > > > > > > > > > >
> > > > > > > > > > > > whether
> > > > > > > > > > > > > something goes to 2.7”.
> > > > > > > > > > > > >
> > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:11, Dmitriy Pavlov <
> > > > > > > > >
> > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > :
> > > > > > > > > > > > >
> > > > > > > > > > > > > > No, it is up to the community to discuss after
> their
> > > > >
> > > > > review
> > > > > > > > > >
> > > > > > > > > > results.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:09, Vladimir Ozerov <
> > > > > > > > > >
> > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > :
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Did I read your words correctly that it is up
> to
> > > > > > >
> > > > > > > implementor
> > > > > > > > >
> > > > > > > > > of a
> > > > > > > > > > > > > single
> > > > > > > > > > > > > > > feature to decide whether release of all other
> > >
> > > features
> > > > > > and
> > > > > > > > >
> > > > > > > > > fixes
> > > > > > > > > > > to
> > > > > > > > > > > > be
> > > > > > > > > > > > > > > delayed?
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:00, Dmitriy Pavlov <
> > > > > > > > > > >
> > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > :
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > My point we can wait a bit for services
> because
> > > > > > > > > > > > > > > > 1 we are open-minded and we don't have
> outside
> > > > > >
> > > > > > pressure
> > > > > > > to
> > > > > > > > >
> > > > > > > > > do
> > > > > > > > > > > > > release
> > > > > > > > > > > > > > in
> > > > > > > > > > > > > > > > October
> > > > > > > > > > > > > > > > 2 and services it is not some new feature,
> which
> > > > > > >
> > > > > > > suddenly
> > > > > > > > > > >
> > > > > > > > > > > appeared
> > > > > > > > > > > > > in
> > > > > > > > > > > > > > > > autumn, it is a well known and important
> feature.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > So it is up to Vyacheslav, Anton and Nikolay
> to
> > > > >
> > > > > decide.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Decisions can be services are not
> ready/ready to
> > > > >
> > > > > merge
> > > > > > > only
> > > > > > > > >
> > > > > > > > > to
> > > > > > > > > > > > > > > master/ready
> > > > > > > > > > > > > > > > to merge to master and to 2.7.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 10:46, Vladimir
> Ozerov <
> > > > > > > > > > > >
> > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Dmitry,
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Community agreement was to perform the
> release
> > >
> > > in
> > > > > > > October.
> > > > > > > > >
> > > > > > > > > Of
> > > > > > > > > > > > > course
> > > > > > > > > > > > > > we
> > > > > > > > > > > > > > > > can
> > > > > > > > > > > > > > > > > wait a bit for services. Then we wait a
> bit for
> > > > >
> > > > > other
> > > > > > > cool
> > > > > > > > > > > >
> > > > > > > > > > > > features
> > > > > > > > > > > > > > > ready
> > > > > > > > > > > > > > > > > by that time, then again and again, and
> release
> > > > >
> > > > > will
> > > > > > > never
> > > > > > > > > > > >
> > > > > > > > > > > > happen.
> > > > > > > > > > > > > > And
> > > > > > > > > > > > > > > > > while we are waiting for new features to
> come,
> > > > > >
> > > > > > already
> > > > > > > > > > >
> > > > > > > > > > > completerd
> > > > > > > > > > > > > > > > features
> > > > > > > > > > > > > > > > > cannot be used by anyone.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > This is why we have an agreement that if
> > >
> > > feature is
> > > > > > not
> > > > > > > > > >
> > > > > > > > > > ready,
> > > > > > > > > > > it
> > > > > > > > > > > > > > > should
> > > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > moved to future release, instead of
> shifting
> > > > >
> > > > > release.
> > > > > > > The
> > > > > > > > > >
> > > > > > > > > > sole
> > > > > > > > > > > > > reason
> > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > have strict dates when decisions are made
> is
> > >
> > > to let
> > > > > > > release
> > > > > > > > > > > >
> > > > > > > > > > > > happen.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at 2:22 AM Dmitriy
> Pavlov
> > >
> > > <
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Vladimir, I'm not searching for enemy,
> and
> > >
> > > not
> > > > > > > fighting
> > > > > > > > > >
> > > > > > > > > > with
> > > > > > > > > > > > > you.
> > > > > > > > > > > > > > > I'm
> > > > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > > happy about cases when we are hurrying.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > We can't fix test, fill ticket details,
> can't
> > > > >
> > > > > wait
> > > > > > > for
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > contributions
> > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > finish their tasks. It is not best idea
> to
> > >
> > > use
> > > > > > > > >
> > > > > > > > > experience
> > > > > > > > > > > from
> > > > > > > > > > > > > > > > > commercial
> > > > > > > > > > > > > > > > > > companies in open source. Are there any
> > >
> > > pressure
> > > > > > > outside
> > > > > > > > > > > > >
> > > > > > > > > > > > > community?
> > > > > > > > > > > > > > > Did
> > > > > > > > > > > > > > > > > > someone promised rest of features to be
> > >
> > > released
> > > > > at
> > > > > > > 30
> > > > > > > > > > > >
> > > > > > > > > > > > September?
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Let's remember principle do-orcracy,
> power of
> > > > >
> > > > > those
> > > > > > > who
> > > > > > > > >
> > > > > > > > > do.
> > > > > > > > > > > If
> > > > > > > > > > > > > > > > contribor
> > > > > > > > > > > > > > > > > > does change and reviewer does review,
> let's
> > >
> > > give
> > > > > > > right of
> > > > > > > > > > > >
> > > > > > > > > > > > making
> > > > > > > > > > > > > > > > decision
> > > > > > > > > > > > > > > > > > to them, but not to some closed club of
> > >
> > > people
> > > > > who
> > > > > > > > > >
> > > > > > > > > > privately
> > > > > > > > > > > > > > discuss
> > > > > > > > > > > > > > > > > > something.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Sincerely
> > > > > > > > > > > > > > > > > > Dmitriy Pavlov
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г., 23:42 Vyacheslav
> > >
> > > Daradur <
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > daradurvs@gmail.com
> > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > Hi Igniters!
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > As I have written about Service Grid
> > >
> > > before [1]
> > > > > > I'm
> > > > > > > > > > > >
> > > > > > > > > > > > finalizing
> > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > solution to be sure that
> implementation is
> > > > > > >
> > > > > > > reliable.
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > About including it in 2.7, if we talk
> that
> > >
> > > code
> > > > > > > freeze
> > > > > > > > > > > >
> > > > > > > > > > > > tomorrow
> > > > > > > > > > > > > > > then
> > > > > > > > > > > > > > > > > > > the solution is not ready to merge yet.
> > > > > > > > > > > > > > > > > > > I hope that prereviewers Anton
> Vinogradov
> > >
> > > and
> > > > > > > Nikolay
> > > > > > > > > > >
> > > > > > > > > > > Izhikov
> > > > > > > > > > > > > > will
> > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > > able to answer if solution out of
> scope or
> > >
> > > not
> > > > > > in a
> > > > > > > > > >
> > > > > > > > > > couple
> > > > > > > > > > > of
> > > > > > > > > > > > > > days.
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > [1]
> > > > > > > > > > > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > >
> > >
> http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-release-td34076.html#a34485
> > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 11:14 PM
> Dmitriy
> > > > >
> > > > > Pavlov <
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > Yes, I agree, NPE during WAL flush is
> > > > > >
> > > > > > definitely
> > > > > > > a
> > > > > > > > > > >
> > > > > > > > > > > blocker.
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > It is strange why the current test
> set
> > >
> > > did
> > > > > not
> > > > > > > fail
> > > > > > > > > >
> > > > > > > > > > after
> > > > > > > > > > > > > > commit.
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 21:45, Andrey
> > > > >
> > > > > Kuznetsov
> > > > > > <
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > stkuzma@gmail.com
> > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > Igniters,
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > I've bumped into a new bug in WAL
> > >
> > > manager
> > > > > > > recently,
> > > > > > > > > >
> > > > > > > > > > see
> > > > > > > > > > > > > [1].
> > > > > > > > > > > > > > It
> > > > > > > > > > > > > > > > > looks
> > > > > > > > > > > > > > > > > > > > > critical enough, and can be a good
> > > > >
> > > > > candidate
> > > > > > > for
> > > > > > > > > >
> > > > > > > > > > fixing
> > > > > > > > > > > > > > before
> > > > > > > > > > > > > > > > 2.7
> > > > > > > > > > > > > > > > > > > release.
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > Do you agree?
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > [1]
> > > > > > > > > >
> > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-9731
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 19:45,
> Dmitriy
> > > > >
> > > > > Pavlov
> > > > > > <
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > I need Vhyacheslav's opinion to
> be
> > > > > >
> > > > > > absolutely
> > > > > > > > >
> > > > > > > > > sure
> > > > > > > > > > > what
> > > > > > > > > > > > > > > status
> > > > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > > > > now.
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > We never committed to dates of
> > >
> > > release,
> > > > > as
> > > > > > > well.
> > > > > > > > >
> > > > > > > > > I
> > > > > > > > > > > > don't
> > > > > > > > > > > > > > > quite
> > > > > > > > > > > > > > > > > > > understand
> > > > > > > > > > > > > > > > > > > > > > what can mean 'the community
> > >
> > > committed to
> > > > > > > > > > > >
> > > > > > > > > > > > doing/releasing
> > > > > > > > > > > > > > > > > > something'.
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > About SG, I also concerned why
> such
> > >
> > > a big
> > > > > > > feature
> > > > > > > > > >
> > > > > > > > > > has
> > > > > > > > > > > > > > quite a
> > > > > > > > > > > > > > > > few
> > > > > > > > > > > > > > > > > > > > > > discussions on the list. But it
> is
> > > > >
> > > > > another
> > > > > > > story.
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 19:33,
> > >
> > > Vladimir
> > > > > > > Ozerov <
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > Folks,
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > Please stop looking for enemies
> > > > > >
> > > > > > everywhere.
> > > > > > > > >
> > > > > > > > > Just
> > > > > > > > > > > went
> > > > > > > > > > > > > > > through
> > > > > > > > > > > > > > > > > > this
> > > > > > > > > > > > > > > > > > > > > thread
> > > > > > > > > > > > > > > > > > > > > > > and search for "service" word.
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 7:30 PM
> > >
> > > Denis
> > > > > > > Magda <
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > dmagda@apache.org
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > Denis, as PMC Chair, could
> you
> > > > >
> > > > > please
> > > > > > > > >
> > > > > > > > > control,
> > > > > > > > > > > > that
> > > > > > > > > > > > > > > > Service
> > > > > > > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > > > > > > > > > > inclusion/exclusion is
> > >
> > > discussed
> > > > > > > properly
> > > > > > > > > > > >
> > > > > > > > > > > > according
> > > > > > > > > > > > > to
> > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > Apache
> > > > > > > > > > > > > > > > > > > > > Way.
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > It's fine when
> > > > >
> > > > > committers/contributors
> > > > > > > have
> > > > > > > > > > >
> > > > > > > > > > > private
> > > > > > > > > > > > > > > > > discussions
> > > > > > > > > > > > > > > > > > > > > related
> > > > > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > > > a feature they've been
> working
> > >
> > > on.
> > > > > Not
> > > > > > > > > >
> > > > > > > > > > everything
> > > > > > > > > > > > > should
> > > > > > > > > > > > > > > go
> > > > > > > > > > > > > > > > > > > through
> > > > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > > dev
> > > > > > > > > > > > > > > > > > > > > > > > list. Otherwise, it will be
> > > > >
> > > > > inundated.
> > > > > > > > >
> > > > > > > > > However,
> > > > > > > > > > > > > agree,
> > > > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > > > > > > architectural
> > > > > > > > > > > > > > > > > > > > > > > > and release decisions need
> to be
> > >
> > > done
> > > > > > > > >
> > > > > > > > > publicly.
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > Speaking about Service Grid,
> > >
> > > there
> > > > > was
> > > > > > a
> > > > > > > > > > >
> > > > > > > > > > > discussion
> > > > > > > > > > > > > > where
> > > > > > > > > > > > > > > I
> > > > > > > > > > > > > > > > > saw
> > > > > > > > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > > > > > was
> > > > > > > > > > > > > > > > > > > > > > > > questionable whether it gets
> > >
> > > added to
> > > > > > the
> > > > > > > > > >
> > > > > > > > > > release
> > > > > > > > > > > or
> > > > > > > > > > > > > > not.
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > *Vladislav*, could you please
> > >
> > > shed
> > > > > some
> > > > > > > light
> > > > > > > > >
> > > > > > > > > on
> > > > > > > > > > > the
> > > > > > > > > > > > > > > current
> > > > > > > > > > > > > > > > > > > status of
> > > > > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > > service grid?
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 9:12
> AM
> > > > >
> > > > > Dmitriy
> > > > > > > > >
> > > > > > > > > Pavlov <
> > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > Ok, let's wait for feedback
> > >
> > > from SG
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Author(s)/Reviewer(s)
> > > > > > > > > > > > > > > > > > > first. If
> > > > > > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > > > > > > > > > > not ready, ok. But I
> thought
> > >
> > > it is
> > > > > > > almost
> > > > > > > > > >
> > > > > > > > > > done.
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > I apologize if I missed
> some
> > > > > > >
> > > > > > > discussion (it
> > > > > > > > > >
> > > > > > > > > > can
> > > > > > > > > > > > > > happen),
> > > > > > > > > > > > > > > > but
> > > > > > > > > > > > > > > > > > > > > > > > > According to the statement
> "our
> > > > > >
> > > > > > current
> > > > > > > > > > >
> > > > > > > > > > > agreement"
> > > > > > > > > > > > > > > > > > > > > > > > > I can suspect some members
> are
> > > > >
> > > > > making
> > > > > > > some
> > > > > > > > > >
> > > > > > > > > > sort
> > > > > > > > > > > of
> > > > > > > > > > > > > > > private
> > > > > > > > > > > > > > > > > > > > > agreements,
> > > > > > > > > > > > > > > > > > > > > > > > and
> > > > > > > > > > > > > > > > > > > > > > > > > do not to discuss it on the
> > >
> > > list.
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > Let's build consensus here
> > >
> > > first,
> > > > > and
> > > > > > > then
> > > > > > > > > >
> > > > > > > > > > name
> > > > > > > > > > > an
> > > > > > > > > > > > > > > > > agreement.
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > Denis, as PMC Chair, could
> you
> > > > >
> > > > > please
> > > > > > > > >
> > > > > > > > > control,
> > > > > > > > > > > > that
> > > > > > > > > > > > > > > > Service
> > > > > > > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > > > > > > > > > > inclusion/exclusion is
> > >
> > > discussed
> > > > > > > properly
> > > > > > > > > > > >
> > > > > > > > > > > > according
> > > > > > > > > > > > > to
> > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > Apache
> > > > > > > > > > > > > > > > > > > > > Way.
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в
> 18:55,
> > > > > >
> > > > > > Vladimir
> > > > > > > > >
> > > > > > > > > Ozerov
> > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > This is an outcome of
> current
> > > > >
> > > > > state
> > > > > > > of
> > > > > > > > > >
> > > > > > > > > > Service
> > > > > > > > > > > > > Grid -
> > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > > > > > > ready.
> > > > > > > > > > > > > > > > > > > > > > > > We
> > > > > > > > > > > > > > > > > > > > > > > > > > never committed to have
> it to
> > > > >
> > > > > 2.7.
> > > > > > > Our goal
> > > > > > > > > >
> > > > > > > > > > was
> > > > > > > > > > > > to
> > > > > > > > > > > > > > try
> > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > include
> > > > > > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > > > > > into
> > > > > > > > > > > > > > > > > > > > > > > > > > 2.7.
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at
> 6:48
> > >
> > > PM
> > > > > > > Dmitriy
> > > > > > > > > >
> > > > > > > > > > Pavlov
> > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > Could you please
> provide a
> > > > > > >
> > > > > > > reference to
> > > > > > > > > >
> > > > > > > > > > some
> > > > > > > > > > > > > > thread?
> > > > > > > > > > > > > > > > > > > Probably I
> > > > > > > > > > > > > > > > > > > > > > > > missed
> > > > > > > > > > > > > > > > > > > > > > > > > > it.
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в
> > >
> > > 18:46,
> > > > > > > Vladimir
> > > > > > > > > > >
> > > > > > > > > > > Ozerov <
> > > > > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > Our current
> agreement is
> > >
> > > that
> > > > > > > Service
> > > > > > > > > >
> > > > > > > > > > Grid
> > > > > > > > > > > is
> > > > > > > > > > > > > out
> > > > > > > > > > > > > > > of
> > > > > > > > > > > > > > > > > > scope.
> > > > > > > > > > > > > > > > > > > > > This
> > > > > > > > > > > > > > > > > > > > > > > > is a
> > > > > > > > > > > > > > > > > > > > > > > > > > > huge
> > > > > > > > > > > > > > > > > > > > > > > > > > > > feature, which hasn't
> > >
> > > entered
> > > > > > > review
> > > > > > > > > >
> > > > > > > > > > stage
> > > > > > > > > > > so
> > > > > > > > > > > > > > far,
> > > > > > > > > > > > > > > We
> > > > > > > > > > > > > > > > > > will
> > > > > > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > > > > > > > > > able to
> > > > > > > > > > > > > > > > > > > > > > > > > > > > review/fix/test it
> > >
> > > properly.
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018
> at
> > >
> > > 6:32
> > > > > PM
> > > > > > > Dmitriy
> > > > > > > > > > > >
> > > > > > > > > > > > Pavlov
> > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > I agree, and I
> prefer
> > >
> > > four
> > > > > > > weeks for
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > stabilization*
> > > > > > > > > > > > > > > > > (1
> > > > > > > > > > > > > > > > > > > Oct -
> > > > > > > > > > > > > > > > > > > > > 29
> > > > > > > > > > > > > > > > > > > > > > > > Oct)
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > Do I understand it
> > > > >
> > > > > correctly:
> > > > > > > Service
> > > > > > > > > > >
> > > > > > > > > > > Grid
> > > > > > > > > > > > is
> > > > > > > > > > > > > > > still
> > > > > > > > > > > > > > > > > in
> > > > > > > > > > > > > > > > > > > scope,
> > > > > > > > > > > > > > > > > > > > > > > > isn't
> > > > > > > > > > > > > > > > > > > > > > > > > > > it? I
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > find it very
> important.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018
> г. в
> > > > >
> > > > > 18:28,
> > > > > > > Nikolay
> > > > > > > > > > > > >
> > > > > > > > > > > > > Izhikov <
> > > > > > > > > > > > > > > > > > > > > > > > nizhikov@apache.org
> > > > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hello, Vova.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Thank you for
> clear
> > > > >
> > > > > release
> > > > > > > status.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I'm +1 for your
> > >
> > > proposal.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент.
> 2018 г.,
> > > > >
> > > > > 18:25
> > > > > > > Alexey
> > > > > > > > > > > > >
> > > > > > > > > > > > > Kuznetsov
> > > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > > > > > akuznetsov@apache.org
> > > > > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Vova,
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Huge +1 to do a
> > > > > > >
> > > > > > > stabilization.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Alexey
> Kuznetsov
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > > > > > > Best regards,
> > > > > > > > > > > > > > > > > > > > > Andrey Kuznetsov.
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > > > > Best Regards, Vyacheslav D.
> > > > > > > > > > > > > > > > > > >
> > >
> > >
> > >
> > > --
> > > Best Regards, Vyacheslav D.
> > >
>
Re: Apache Ignite 2.7 release
Posted by Nikolay Izhikov <ni...@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 <da...@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 <ds...@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 <dp...@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 <dm...@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 <
> >
> > nizhikov@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 <
> > > >
> > > > dsetrakyan@apache.org
> > > > > > :
> > > > > > >
> > > > > > > > Dmitriy,
> > > > > > > >
> > > > > > > > We agreed in the beginning of this thread that Service Grid
> >
> > changes
> > > > > > are not
> > > > > > > > going to make the release because the community still did not
> > > >
> > > > approve
> > > > > > the
> > > > > > > > design. Nothing has changed since. I have not seen any design
> > > > > >
> > > > > > discussions.
> > > > > > > > At this point, I have no confidence that the Service Grid
> >
> > changes
> > > > > will
> > > > > > make
> > > > > > > > it into the 2.8 release. The 2.7 release seems out of question
> > > > > >
> > > > > > altogether.
> > > > > > > >
> > > > > > > > Also, Nikolay is a release manager. We should let him drive the
> > > > > >
> > > > > > release. To
> > > > > > > > my knowledge, he is doing a great job and the release is going
> > > > > >
> > > > > > according to
> > > > > > > > the schedule he proposed.
> > > > > > > >
> > > > > > > > D.
> > > > > > > >
> > > > > > > > On Fri, Sep 28, 2018 at 4:31 AM Dmitriy Pavlov <
> > > > >
> > > > > dpavlov.spb@gmail.com>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Hi Dmitriy, Vladimir,
> > > > > > > > >
> > > > > > > > > I suggest we stop this nonsense with release dates-pushing
> > > >
> > > > because
> > > > > of
> > > > > > > >
> > > > > > > > some
> > > > > > > > > open question.
> > > > > > > > >
> > > > > > > > > Just because you disagreed with any include/exclude something
> > > >
> > > > into
> > > > > > scope,
> > > > > > > > > does not mean that whole community disagreed.
> > > > > > > > >
> > > > > > > > > If folks will start a separate discussion with results of the
> > > > > >
> > > > > > review, I
> > > > > > > >
> > > > > > > > see
> > > > > > > > > no reasons to reject their contribution, even if we need to
> > > >
> > > > revisit
> > > > > > our
> > > > > > > > > agreements and wait for a couple of days more.
> > > > > > > > >
> > > > > > > > > Am I missing some reason why dates are so fundamentally
> >
> > important
> > > > > to
> > > > > > you?
> > > > > > > > >
> > > > > > > > > Sincerely,
> > > > > > > > > Dmitriy Pavlov
> > > > > > > > >
> > > > > > > > > пт, 28 сент. 2018 г. в 12:20, Dmitriy Setrakyan <
> > > > > >
> > > > > > dsetrakyan@apache.org>:
> > > > > > > > >
> > > > > > > > > > If services is not ready, which it is not, then we should
> > > >
> > > > include
> > > > > > them
> > > > > > > > >
> > > > > > > > > into
> > > > > > > > > > the next release. There is no need to force them into 2.7.
> >
> > I
> > > > > > suggest we
> > > > > > > > > > move according to the schedule we all agreed on.
> > > > > > > > > >
> > > > > > > > > > D.
> > > > > > > > > >
> > > > > > > > > > On Fri, Sep 28, 2018 at 1:22 AM Dmitriy Pavlov <
> > > > > >
> > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Yes, so correct statement is "community did not make any
> > > > > >
> > > > > > decisions
> > > > > > > > >
> > > > > > > > > about
> > > > > > > > > > > services not go to 2.7/ services are out of scope".
> > > > > > > > > > >
> > > > > > > > > > > If so, please forgive me my confusion.
> > > > > > > > > > >
> > > > > > > > > > > пт, 28 сент. 2018 г. в 11:19, Vladimir Ozerov <
> > > > > >
> > > > > > vozerov@gridgain.com
> > > > > > > > >
> > > > > > > > > :
> > > > > > > > > > >
> > > > > > > > > > > > Exactly. So correct statement is “it is up to
> >
> > *community*
> > > > to
> > > > > > decide
> > > > > > > > > > >
> > > > > > > > > > > whether
> > > > > > > > > > > > something goes to 2.7”.
> > > > > > > > > > > >
> > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:11, Dmitriy Pavlov <
> > > > > > > >
> > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > :
> > > > > > > > > > > >
> > > > > > > > > > > > > No, it is up to the community to discuss after their
> > > >
> > > > review
> > > > > > > > >
> > > > > > > > > results.
> > > > > > > > > > > > >
> > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:09, Vladimir Ozerov <
> > > > > > > > >
> > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > :
> > > > > > > > > > > > >
> > > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Did I read your words correctly that it is up to
> > > > > >
> > > > > > implementor
> > > > > > > >
> > > > > > > > of a
> > > > > > > > > > > > single
> > > > > > > > > > > > > > feature to decide whether release of all other
> >
> > features
> > > > > and
> > > > > > > >
> > > > > > > > fixes
> > > > > > > > > > to
> > > > > > > > > > > be
> > > > > > > > > > > > > > delayed?
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:00, Dmitriy Pavlov <
> > > > > > > > > >
> > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > :
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > > My point we can wait a bit for services because
> > > > > > > > > > > > > > > 1 we are open-minded and we don't have outside
> > > > >
> > > > > pressure
> > > > > > to
> > > > > > > >
> > > > > > > > do
> > > > > > > > > > > > release
> > > > > > > > > > > > > in
> > > > > > > > > > > > > > > October
> > > > > > > > > > > > > > > 2 and services it is not some new feature, which
> > > > > >
> > > > > > suddenly
> > > > > > > > > >
> > > > > > > > > > appeared
> > > > > > > > > > > > in
> > > > > > > > > > > > > > > autumn, it is a well known and important feature.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > So it is up to Vyacheslav, Anton and Nikolay to
> > > >
> > > > decide.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Decisions can be services are not ready/ready to
> > > >
> > > > merge
> > > > > > only
> > > > > > > >
> > > > > > > > to
> > > > > > > > > > > > > > master/ready
> > > > > > > > > > > > > > > to merge to master and to 2.7.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 10:46, Vladimir Ozerov <
> > > > > > > > > > >
> > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > :
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Dmitry,
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Community agreement was to perform the release
> >
> > in
> > > > > > October.
> > > > > > > >
> > > > > > > > Of
> > > > > > > > > > > > course
> > > > > > > > > > > > > we
> > > > > > > > > > > > > > > can
> > > > > > > > > > > > > > > > wait a bit for services. Then we wait a bit for
> > > >
> > > > other
> > > > > > cool
> > > > > > > > > > >
> > > > > > > > > > > features
> > > > > > > > > > > > > > ready
> > > > > > > > > > > > > > > > by that time, then again and again, and release
> > > >
> > > > will
> > > > > > never
> > > > > > > > > > >
> > > > > > > > > > > happen.
> > > > > > > > > > > > > And
> > > > > > > > > > > > > > > > while we are waiting for new features to come,
> > > > >
> > > > > already
> > > > > > > > > >
> > > > > > > > > > completerd
> > > > > > > > > > > > > > > features
> > > > > > > > > > > > > > > > cannot be used by anyone.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > This is why we have an agreement that if
> >
> > feature is
> > > > > not
> > > > > > > > >
> > > > > > > > > ready,
> > > > > > > > > > it
> > > > > > > > > > > > > > should
> > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > moved to future release, instead of shifting
> > > >
> > > > release.
> > > > > > The
> > > > > > > > >
> > > > > > > > > sole
> > > > > > > > > > > > reason
> > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > have strict dates when decisions are made is
> >
> > to let
> > > > > > release
> > > > > > > > > > >
> > > > > > > > > > > happen.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at 2:22 AM Dmitriy Pavlov
> >
> > <
> > > > > > > > > > > > >
> > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Vladimir, I'm not searching for enemy, and
> >
> > not
> > > > > > fighting
> > > > > > > > >
> > > > > > > > > with
> > > > > > > > > > > > you.
> > > > > > > > > > > > > > I'm
> > > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > happy about cases when we are hurrying.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > We can't fix test, fill ticket details, can't
> > > >
> > > > wait
> > > > > > for
> > > > > > > > > > > > >
> > > > > > > > > > > > > contributions
> > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > finish their tasks. It is not best idea to
> >
> > use
> > > > > > > >
> > > > > > > > experience
> > > > > > > > > > from
> > > > > > > > > > > > > > > > commercial
> > > > > > > > > > > > > > > > > companies in open source. Are there any
> >
> > pressure
> > > > > > outside
> > > > > > > > > > > >
> > > > > > > > > > > > community?
> > > > > > > > > > > > > > Did
> > > > > > > > > > > > > > > > > someone promised rest of features to be
> >
> > released
> > > > at
> > > > > > 30
> > > > > > > > > > >
> > > > > > > > > > > September?
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Let's remember principle do-orcracy, power of
> > > >
> > > > those
> > > > > > who
> > > > > > > >
> > > > > > > > do.
> > > > > > > > > > If
> > > > > > > > > > > > > > > contribor
> > > > > > > > > > > > > > > > > does change and reviewer does review, let's
> >
> > give
> > > > > > right of
> > > > > > > > > > >
> > > > > > > > > > > making
> > > > > > > > > > > > > > > decision
> > > > > > > > > > > > > > > > > to them, but not to some closed club of
> >
> > people
> > > > who
> > > > > > > > >
> > > > > > > > > privately
> > > > > > > > > > > > > discuss
> > > > > > > > > > > > > > > > > something.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Sincerely
> > > > > > > > > > > > > > > > > Dmitriy Pavlov
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г., 23:42 Vyacheslav
> >
> > Daradur <
> > > > > > > > > > > > >
> > > > > > > > > > > > > daradurvs@gmail.com
> > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Hi Igniters!
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > As I have written about Service Grid
> >
> > before [1]
> > > > > I'm
> > > > > > > > > > >
> > > > > > > > > > > finalizing
> > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > solution to be sure that implementation is
> > > > > >
> > > > > > reliable.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > About including it in 2.7, if we talk that
> >
> > code
> > > > > > freeze
> > > > > > > > > > >
> > > > > > > > > > > tomorrow
> > > > > > > > > > > > > > then
> > > > > > > > > > > > > > > > > > the solution is not ready to merge yet.
> > > > > > > > > > > > > > > > > > I hope that prereviewers Anton Vinogradov
> >
> > and
> > > > > > Nikolay
> > > > > > > > > >
> > > > > > > > > > Izhikov
> > > > > > > > > > > > > will
> > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > able to answer if solution out of scope or
> >
> > not
> > > > > in a
> > > > > > > > >
> > > > > > > > > couple
> > > > > > > > > > of
> > > > > > > > > > > > > days.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > [1]
> > > > > > > > > > > > > > > > > >
> > > > > > > >
> > > > > > > >
> >
> > http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-release-td34076.html#a34485
> > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 11:14 PM Dmitriy
> > > >
> > > > Pavlov <
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > Yes, I agree, NPE during WAL flush is
> > > > >
> > > > > definitely
> > > > > > a
> > > > > > > > > >
> > > > > > > > > > blocker.
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > It is strange why the current test set
> >
> > did
> > > > not
> > > > > > fail
> > > > > > > > >
> > > > > > > > > after
> > > > > > > > > > > > > commit.
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 21:45, Andrey
> > > >
> > > > Kuznetsov
> > > > > <
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > stkuzma@gmail.com
> > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > Igniters,
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > I've bumped into a new bug in WAL
> >
> > manager
> > > > > > recently,
> > > > > > > > >
> > > > > > > > > see
> > > > > > > > > > > > [1].
> > > > > > > > > > > > > It
> > > > > > > > > > > > > > > > looks
> > > > > > > > > > > > > > > > > > > > critical enough, and can be a good
> > > >
> > > > candidate
> > > > > > for
> > > > > > > > >
> > > > > > > > > fixing
> > > > > > > > > > > > > before
> > > > > > > > > > > > > > > 2.7
> > > > > > > > > > > > > > > > > > release.
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > Do you agree?
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > [1]
> > > > > > > > >
> > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-9731
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 19:45, Dmitriy
> > > >
> > > > Pavlov
> > > > > <
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > I need Vhyacheslav's opinion to be
> > > > >
> > > > > absolutely
> > > > > > > >
> > > > > > > > sure
> > > > > > > > > > what
> > > > > > > > > > > > > > status
> > > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > > > now.
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > We never committed to dates of
> >
> > release,
> > > > as
> > > > > > well.
> > > > > > > >
> > > > > > > > I
> > > > > > > > > > > don't
> > > > > > > > > > > > > > quite
> > > > > > > > > > > > > > > > > > understand
> > > > > > > > > > > > > > > > > > > > > what can mean 'the community
> >
> > committed to
> > > > > > > > > > >
> > > > > > > > > > > doing/releasing
> > > > > > > > > > > > > > > > > something'.
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > About SG, I also concerned why such
> >
> > a big
> > > > > > feature
> > > > > > > > >
> > > > > > > > > has
> > > > > > > > > > > > > quite a
> > > > > > > > > > > > > > > few
> > > > > > > > > > > > > > > > > > > > > discussions on the list. But it is
> > > >
> > > > another
> > > > > > story.
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 19:33,
> >
> > Vladimir
> > > > > > Ozerov <
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > Folks,
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > Please stop looking for enemies
> > > > >
> > > > > everywhere.
> > > > > > > >
> > > > > > > > Just
> > > > > > > > > > went
> > > > > > > > > > > > > > through
> > > > > > > > > > > > > > > > > this
> > > > > > > > > > > > > > > > > > > > thread
> > > > > > > > > > > > > > > > > > > > > > and search for "service" word.
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 7:30 PM
> >
> > Denis
> > > > > > Magda <
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > dmagda@apache.org
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > Denis, as PMC Chair, could you
> > > >
> > > > please
> > > > > > > >
> > > > > > > > control,
> > > > > > > > > > > that
> > > > > > > > > > > > > > > Service
> > > > > > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > > > > > > > > > inclusion/exclusion is
> >
> > discussed
> > > > > > properly
> > > > > > > > > > >
> > > > > > > > > > > according
> > > > > > > > > > > > to
> > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > Apache
> > > > > > > > > > > > > > > > > > > > Way.
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > It's fine when
> > > >
> > > > committers/contributors
> > > > > > have
> > > > > > > > > >
> > > > > > > > > > private
> > > > > > > > > > > > > > > > discussions
> > > > > > > > > > > > > > > > > > > > related
> > > > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > > a feature they've been working
> >
> > on.
> > > > Not
> > > > > > > > >
> > > > > > > > > everything
> > > > > > > > > > > > should
> > > > > > > > > > > > > > go
> > > > > > > > > > > > > > > > > > through
> > > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > dev
> > > > > > > > > > > > > > > > > > > > > > > list. Otherwise, it will be
> > > >
> > > > inundated.
> > > > > > > >
> > > > > > > > However,
> > > > > > > > > > > > agree,
> > > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > > > > > architectural
> > > > > > > > > > > > > > > > > > > > > > > and release decisions need to be
> >
> > done
> > > > > > > >
> > > > > > > > publicly.
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > Speaking about Service Grid,
> >
> > there
> > > > was
> > > > > a
> > > > > > > > > >
> > > > > > > > > > discussion
> > > > > > > > > > > > > where
> > > > > > > > > > > > > > I
> > > > > > > > > > > > > > > > saw
> > > > > > > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > > > > was
> > > > > > > > > > > > > > > > > > > > > > > questionable whether it gets
> >
> > added to
> > > > > the
> > > > > > > > >
> > > > > > > > > release
> > > > > > > > > > or
> > > > > > > > > > > > > not.
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > *Vladislav*, could you please
> >
> > shed
> > > > some
> > > > > > light
> > > > > > > >
> > > > > > > > on
> > > > > > > > > > the
> > > > > > > > > > > > > > current
> > > > > > > > > > > > > > > > > > status of
> > > > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > > service grid?
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 9:12 AM
> > > >
> > > > Dmitriy
> > > > > > > >
> > > > > > > > Pavlov <
> > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > Ok, let's wait for feedback
> >
> > from SG
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Author(s)/Reviewer(s)
> > > > > > > > > > > > > > > > > > first. If
> > > > > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > > > > > > > > > not ready, ok. But I thought
> >
> > it is
> > > > > > almost
> > > > > > > > >
> > > > > > > > > done.
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > I apologize if I missed some
> > > > > >
> > > > > > discussion (it
> > > > > > > > >
> > > > > > > > > can
> > > > > > > > > > > > > happen),
> > > > > > > > > > > > > > > but
> > > > > > > > > > > > > > > > > > > > > > > > According to the statement "our
> > > > >
> > > > > current
> > > > > > > > > >
> > > > > > > > > > agreement"
> > > > > > > > > > > > > > > > > > > > > > > > I can suspect some members are
> > > >
> > > > making
> > > > > > some
> > > > > > > > >
> > > > > > > > > sort
> > > > > > > > > > of
> > > > > > > > > > > > > > private
> > > > > > > > > > > > > > > > > > > > agreements,
> > > > > > > > > > > > > > > > > > > > > > > and
> > > > > > > > > > > > > > > > > > > > > > > > do not to discuss it on the
> >
> > list.
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > Let's build consensus here
> >
> > first,
> > > > and
> > > > > > then
> > > > > > > > >
> > > > > > > > > name
> > > > > > > > > > an
> > > > > > > > > > > > > > > > agreement.
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > Denis, as PMC Chair, could you
> > > >
> > > > please
> > > > > > > >
> > > > > > > > control,
> > > > > > > > > > > that
> > > > > > > > > > > > > > > Service
> > > > > > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > > > > > > > > > inclusion/exclusion is
> >
> > discussed
> > > > > > properly
> > > > > > > > > > >
> > > > > > > > > > > according
> > > > > > > > > > > > to
> > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > Apache
> > > > > > > > > > > > > > > > > > > > Way.
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 18:55,
> > > > >
> > > > > Vladimir
> > > > > > > >
> > > > > > > > Ozerov
> > > > > > > > > <
> > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > This is an outcome of current
> > > >
> > > > state
> > > > > > of
> > > > > > > > >
> > > > > > > > > Service
> > > > > > > > > > > > Grid -
> > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > > > > > ready.
> > > > > > > > > > > > > > > > > > > > > > > We
> > > > > > > > > > > > > > > > > > > > > > > > > never committed to have it to
> > > >
> > > > 2.7.
> > > > > > Our goal
> > > > > > > > >
> > > > > > > > > was
> > > > > > > > > > > to
> > > > > > > > > > > > > try
> > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > include
> > > > > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > > > > into
> > > > > > > > > > > > > > > > > > > > > > > > > 2.7.
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 6:48
> >
> > PM
> > > > > > Dmitriy
> > > > > > > > >
> > > > > > > > > Pavlov
> > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > Could you please provide a
> > > > > >
> > > > > > reference to
> > > > > > > > >
> > > > > > > > > some
> > > > > > > > > > > > > thread?
> > > > > > > > > > > > > > > > > > Probably I
> > > > > > > > > > > > > > > > > > > > > > > missed
> > > > > > > > > > > > > > > > > > > > > > > > > it.
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в
> >
> > 18:46,
> > > > > > Vladimir
> > > > > > > > > >
> > > > > > > > > > Ozerov <
> > > > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > Our current agreement is
> >
> > that
> > > > > > Service
> > > > > > > > >
> > > > > > > > > Grid
> > > > > > > > > > is
> > > > > > > > > > > > out
> > > > > > > > > > > > > > of
> > > > > > > > > > > > > > > > > scope.
> > > > > > > > > > > > > > > > > > > > This
> > > > > > > > > > > > > > > > > > > > > > > is a
> > > > > > > > > > > > > > > > > > > > > > > > > > huge
> > > > > > > > > > > > > > > > > > > > > > > > > > > feature, which hasn't
> >
> > entered
> > > > > > review
> > > > > > > > >
> > > > > > > > > stage
> > > > > > > > > > so
> > > > > > > > > > > > > far,
> > > > > > > > > > > > > > We
> > > > > > > > > > > > > > > > > will
> > > > > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > > > > > > > > able to
> > > > > > > > > > > > > > > > > > > > > > > > > > > review/fix/test it
> >
> > properly.
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at
> >
> > 6:32
> > > > PM
> > > > > > Dmitriy
> > > > > > > > > > >
> > > > > > > > > > > Pavlov
> > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > I agree, and I prefer
> >
> > four
> > > > > > weeks for
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > stabilization*
> > > > > > > > > > > > > > > > (1
> > > > > > > > > > > > > > > > > > Oct -
> > > > > > > > > > > > > > > > > > > > 29
> > > > > > > > > > > > > > > > > > > > > > > Oct)
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > Do I understand it
> > > >
> > > > correctly:
> > > > > > Service
> > > > > > > > > >
> > > > > > > > > > Grid
> > > > > > > > > > > is
> > > > > > > > > > > > > > still
> > > > > > > > > > > > > > > > in
> > > > > > > > > > > > > > > > > > scope,
> > > > > > > > > > > > > > > > > > > > > > > isn't
> > > > > > > > > > > > > > > > > > > > > > > > > > it? I
> > > > > > > > > > > > > > > > > > > > > > > > > > > > find it very important.
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в
> > > >
> > > > 18:28,
> > > > > > Nikolay
> > > > > > > > > > > >
> > > > > > > > > > > > Izhikov <
> > > > > > > > > > > > > > > > > > > > > > > nizhikov@apache.org
> > > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hello, Vova.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > Thank you for clear
> > > >
> > > > release
> > > > > > status.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > I'm +1 for your
> >
> > proposal.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г.,
> > > >
> > > > 18:25
> > > > > > Alexey
> > > > > > > > > > > >
> > > > > > > > > > > > Kuznetsov
> > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > > > > akuznetsov@apache.org
> > > > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Vova,
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Huge +1 to do a
> > > > > >
> > > > > > stabilization.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Alexey Kuznetsov
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > > > > > Best regards,
> > > > > > > > > > > > > > > > > > > > Andrey Kuznetsov.
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > > > Best Regards, Vyacheslav D.
> > > > > > > > > > > > > > > > > >
> >
> >
> >
> > --
> > Best Regards, Vyacheslav D.
> >
Re: Apache Ignite 2.7 release
Posted by Vladimir Ozerov <vo...@gridgain.com>.
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 <da...@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 <ds...@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 <dp...@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 <dm...@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 <
> nizhikov@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 <
> > > dsetrakyan@apache.org
> > > > >:
> > > > > >
> > > > > > > Dmitriy,
> > > > > > >
> > > > > > > We agreed in the beginning of this thread that Service Grid
> changes
> > > > > are not
> > > > > > > going to make the release because the community still did not
> > > approve
> > > > > the
> > > > > > > design. Nothing has changed since. I have not seen any design
> > > > > discussions.
> > > > > > > At this point, I have no confidence that the Service Grid
> changes
> > > > will
> > > > > make
> > > > > > > it into the 2.8 release. The 2.7 release seems out of question
> > > > > altogether.
> > > > > > >
> > > > > > > Also, Nikolay is a release manager. We should let him drive the
> > > > > release. To
> > > > > > > my knowledge, he is doing a great job and the release is going
> > > > > according to
> > > > > > > the schedule he proposed.
> > > > > > >
> > > > > > > D.
> > > > > > >
> > > > > > > On Fri, Sep 28, 2018 at 4:31 AM Dmitriy Pavlov <
> > > > dpavlov.spb@gmail.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Hi Dmitriy, Vladimir,
> > > > > > > >
> > > > > > > > I suggest we stop this nonsense with release dates-pushing
> > > because
> > > > of
> > > > > > >
> > > > > > > some
> > > > > > > > open question.
> > > > > > > >
> > > > > > > > Just because you disagreed with any include/exclude something
> > > into
> > > > > scope,
> > > > > > > > does not mean that whole community disagreed.
> > > > > > > >
> > > > > > > > If folks will start a separate discussion with results of the
> > > > > review, I
> > > > > > >
> > > > > > > see
> > > > > > > > no reasons to reject their contribution, even if we need to
> > > revisit
> > > > > our
> > > > > > > > agreements and wait for a couple of days more.
> > > > > > > >
> > > > > > > > Am I missing some reason why dates are so fundamentally
> important
> > > > to
> > > > > you?
> > > > > > > >
> > > > > > > > Sincerely,
> > > > > > > > Dmitriy Pavlov
> > > > > > > >
> > > > > > > > пт, 28 сент. 2018 г. в 12:20, Dmitriy Setrakyan <
> > > > > dsetrakyan@apache.org>:
> > > > > > > >
> > > > > > > > > If services is not ready, which it is not, then we should
> > > include
> > > > > them
> > > > > > > >
> > > > > > > > into
> > > > > > > > > the next release. There is no need to force them into 2.7.
> I
> > > > > suggest we
> > > > > > > > > move according to the schedule we all agreed on.
> > > > > > > > >
> > > > > > > > > D.
> > > > > > > > >
> > > > > > > > > On Fri, Sep 28, 2018 at 1:22 AM Dmitriy Pavlov <
> > > > > dpavlov.spb@gmail.com>
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Yes, so correct statement is "community did not make any
> > > > > decisions
> > > > > > > >
> > > > > > > > about
> > > > > > > > > > services not go to 2.7/ services are out of scope".
> > > > > > > > > >
> > > > > > > > > > If so, please forgive me my confusion.
> > > > > > > > > >
> > > > > > > > > > пт, 28 сент. 2018 г. в 11:19, Vladimir Ozerov <
> > > > > vozerov@gridgain.com
> > > > > > > >
> > > > > > > > :
> > > > > > > > > >
> > > > > > > > > > > Exactly. So correct statement is “it is up to
> *community*
> > > to
> > > > > decide
> > > > > > > > > >
> > > > > > > > > > whether
> > > > > > > > > > > something goes to 2.7”.
> > > > > > > > > > >
> > > > > > > > > > > пт, 28 сент. 2018 г. в 11:11, Dmitriy Pavlov <
> > > > > > >
> > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > :
> > > > > > > > > > >
> > > > > > > > > > > > No, it is up to the community to discuss after their
> > > review
> > > > > > > >
> > > > > > > > results.
> > > > > > > > > > > >
> > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:09, Vladimir Ozerov <
> > > > > > > >
> > > > > > > > vozerov@gridgain.com
> > > > > > > > > > :
> > > > > > > > > > > >
> > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > >
> > > > > > > > > > > > > Did I read your words correctly that it is up to
> > > > > implementor
> > > > > > >
> > > > > > > of a
> > > > > > > > > > > single
> > > > > > > > > > > > > feature to decide whether release of all other
> features
> > > > and
> > > > > > >
> > > > > > > fixes
> > > > > > > > > to
> > > > > > > > > > be
> > > > > > > > > > > > > delayed?
> > > > > > > > > > > > >
> > > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:00, Dmitriy Pavlov <
> > > > > > > > >
> > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > :
> > > > > > > > > > > > >
> > > > > > > > > > > > > > My point we can wait a bit for services because
> > > > > > > > > > > > > > 1 we are open-minded and we don't have outside
> > > > pressure
> > > > > to
> > > > > > >
> > > > > > > do
> > > > > > > > > > > release
> > > > > > > > > > > > in
> > > > > > > > > > > > > > October
> > > > > > > > > > > > > > 2 and services it is not some new feature, which
> > > > > suddenly
> > > > > > > > >
> > > > > > > > > appeared
> > > > > > > > > > > in
> > > > > > > > > > > > > > autumn, it is a well known and important feature.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > So it is up to Vyacheslav, Anton and Nikolay to
> > > decide.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Decisions can be services are not ready/ready to
> > > merge
> > > > > only
> > > > > > >
> > > > > > > to
> > > > > > > > > > > > > master/ready
> > > > > > > > > > > > > > to merge to master and to 2.7.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 10:46, Vladimir Ozerov <
> > > > > > > > > >
> > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > :
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Dmitry,
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Community agreement was to perform the release
> in
> > > > > October.
> > > > > > >
> > > > > > > Of
> > > > > > > > > > > course
> > > > > > > > > > > > we
> > > > > > > > > > > > > > can
> > > > > > > > > > > > > > > wait a bit for services. Then we wait a bit for
> > > other
> > > > > cool
> > > > > > > > > >
> > > > > > > > > > features
> > > > > > > > > > > > > ready
> > > > > > > > > > > > > > > by that time, then again and again, and release
> > > will
> > > > > never
> > > > > > > > > >
> > > > > > > > > > happen.
> > > > > > > > > > > > And
> > > > > > > > > > > > > > > while we are waiting for new features to come,
> > > > already
> > > > > > > > >
> > > > > > > > > completerd
> > > > > > > > > > > > > > features
> > > > > > > > > > > > > > > cannot be used by anyone.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > This is why we have an agreement that if
> feature is
> > > > not
> > > > > > > >
> > > > > > > > ready,
> > > > > > > > > it
> > > > > > > > > > > > > should
> > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > moved to future release, instead of shifting
> > > release.
> > > > > The
> > > > > > > >
> > > > > > > > sole
> > > > > > > > > > > reason
> > > > > > > > > > > > > to
> > > > > > > > > > > > > > > have strict dates when decisions are made is
> to let
> > > > > release
> > > > > > > > > >
> > > > > > > > > > happen.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at 2:22 AM Dmitriy Pavlov
> <
> > > > > > > > > > > >
> > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Vladimir, I'm not searching for enemy, and
> not
> > > > > fighting
> > > > > > > >
> > > > > > > > with
> > > > > > > > > > > you.
> > > > > > > > > > > > > I'm
> > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > happy about cases when we are hurrying.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > We can't fix test, fill ticket details, can't
> > > wait
> > > > > for
> > > > > > > > > > > >
> > > > > > > > > > > > contributions
> > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > finish their tasks. It is not best idea to
> use
> > > > > > >
> > > > > > > experience
> > > > > > > > > from
> > > > > > > > > > > > > > > commercial
> > > > > > > > > > > > > > > > companies in open source. Are there any
> pressure
> > > > > outside
> > > > > > > > > > >
> > > > > > > > > > > community?
> > > > > > > > > > > > > Did
> > > > > > > > > > > > > > > > someone promised rest of features to be
> released
> > > at
> > > > > 30
> > > > > > > > > >
> > > > > > > > > > September?
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Let's remember principle do-orcracy, power of
> > > those
> > > > > who
> > > > > > >
> > > > > > > do.
> > > > > > > > > If
> > > > > > > > > > > > > > contribor
> > > > > > > > > > > > > > > > does change and reviewer does review, let's
> give
> > > > > right of
> > > > > > > > > >
> > > > > > > > > > making
> > > > > > > > > > > > > > decision
> > > > > > > > > > > > > > > > to them, but not to some closed club of
> people
> > > who
> > > > > > > >
> > > > > > > > privately
> > > > > > > > > > > > discuss
> > > > > > > > > > > > > > > > something.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Sincerely
> > > > > > > > > > > > > > > > Dmitriy Pavlov
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > чт, 27 сент. 2018 г., 23:42 Vyacheslav
> Daradur <
> > > > > > > > > > > >
> > > > > > > > > > > > daradurvs@gmail.com
> > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Hi Igniters!
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > As I have written about Service Grid
> before [1]
> > > > I'm
> > > > > > > > > >
> > > > > > > > > > finalizing
> > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > solution to be sure that implementation is
> > > > > reliable.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > About including it in 2.7, if we talk that
> code
> > > > > freeze
> > > > > > > > > >
> > > > > > > > > > tomorrow
> > > > > > > > > > > > > then
> > > > > > > > > > > > > > > > > the solution is not ready to merge yet.
> > > > > > > > > > > > > > > > > I hope that prereviewers Anton Vinogradov
> and
> > > > > Nikolay
> > > > > > > > >
> > > > > > > > > Izhikov
> > > > > > > > > > > > will
> > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > able to answer if solution out of scope or
> not
> > > > in a
> > > > > > > >
> > > > > > > > couple
> > > > > > > > > of
> > > > > > > > > > > > days.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > [1]
> > > > > > > > > > > > > > > > >
> > > > > > >
> > > > > > >
> > > > >
> > > >
> > >
> http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-release-td34076.html#a34485
> > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 11:14 PM Dmitriy
> > > Pavlov <
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Yes, I agree, NPE during WAL flush is
> > > > definitely
> > > > > a
> > > > > > > > >
> > > > > > > > > blocker.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > It is strange why the current test set
> did
> > > not
> > > > > fail
> > > > > > > >
> > > > > > > > after
> > > > > > > > > > > > commit.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 21:45, Andrey
> > > Kuznetsov
> > > > <
> > > > > > > > > > > > >
> > > > > > > > > > > > > stkuzma@gmail.com
> > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > Igniters,
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > I've bumped into a new bug in WAL
> manager
> > > > > recently,
> > > > > > > >
> > > > > > > > see
> > > > > > > > > > > [1].
> > > > > > > > > > > > It
> > > > > > > > > > > > > > > looks
> > > > > > > > > > > > > > > > > > > critical enough, and can be a good
> > > candidate
> > > > > for
> > > > > > > >
> > > > > > > > fixing
> > > > > > > > > > > > before
> > > > > > > > > > > > > > 2.7
> > > > > > > > > > > > > > > > > release.
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > Do you agree?
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > [1]
> > > > > > > >
> > > > > > > > https://issues.apache.org/jira/browse/IGNITE-9731
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 19:45, Dmitriy
> > > Pavlov
> > > > <
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > I need Vhyacheslav's opinion to be
> > > > absolutely
> > > > > > >
> > > > > > > sure
> > > > > > > > > what
> > > > > > > > > > > > > status
> > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > > now.
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > We never committed to dates of
> release,
> > > as
> > > > > well.
> > > > > > >
> > > > > > > I
> > > > > > > > > > don't
> > > > > > > > > > > > > quite
> > > > > > > > > > > > > > > > > understand
> > > > > > > > > > > > > > > > > > > > what can mean 'the community
> committed to
> > > > > > > > > >
> > > > > > > > > > doing/releasing
> > > > > > > > > > > > > > > > something'.
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > About SG, I also concerned why such
> a big
> > > > > feature
> > > > > > > >
> > > > > > > > has
> > > > > > > > > > > > quite a
> > > > > > > > > > > > > > few
> > > > > > > > > > > > > > > > > > > > discussions on the list. But it is
> > > another
> > > > > story.
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 19:33,
> Vladimir
> > > > > Ozerov <
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > Folks,
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > Please stop looking for enemies
> > > > everywhere.
> > > > > > >
> > > > > > > Just
> > > > > > > > > went
> > > > > > > > > > > > > through
> > > > > > > > > > > > > > > > this
> > > > > > > > > > > > > > > > > > > thread
> > > > > > > > > > > > > > > > > > > > > and search for "service" word.
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 7:30 PM
> Denis
> > > > > Magda <
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > dmagda@apache.org
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > Denis, as PMC Chair, could you
> > > please
> > > > > > >
> > > > > > > control,
> > > > > > > > > > that
> > > > > > > > > > > > > > Service
> > > > > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > > > > > > > > inclusion/exclusion is
> discussed
> > > > > properly
> > > > > > > > > >
> > > > > > > > > > according
> > > > > > > > > > > to
> > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > Apache
> > > > > > > > > > > > > > > > > > > Way.
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > It's fine when
> > > committers/contributors
> > > > > have
> > > > > > > > >
> > > > > > > > > private
> > > > > > > > > > > > > > > discussions
> > > > > > > > > > > > > > > > > > > related
> > > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > > a feature they've been working
> on.
> > > Not
> > > > > > > >
> > > > > > > > everything
> > > > > > > > > > > should
> > > > > > > > > > > > > go
> > > > > > > > > > > > > > > > > through
> > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > dev
> > > > > > > > > > > > > > > > > > > > > > list. Otherwise, it will be
> > > inundated.
> > > > > > >
> > > > > > > However,
> > > > > > > > > > > agree,
> > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > > > > architectural
> > > > > > > > > > > > > > > > > > > > > > and release decisions need to be
> done
> > > > > > >
> > > > > > > publicly.
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > Speaking about Service Grid,
> there
> > > was
> > > > a
> > > > > > > > >
> > > > > > > > > discussion
> > > > > > > > > > > > where
> > > > > > > > > > > > > I
> > > > > > > > > > > > > > > saw
> > > > > > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > > > was
> > > > > > > > > > > > > > > > > > > > > > questionable whether it gets
> added to
> > > > the
> > > > > > > >
> > > > > > > > release
> > > > > > > > > or
> > > > > > > > > > > > not.
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > *Vladislav*, could you please
> shed
> > > some
> > > > > light
> > > > > > >
> > > > > > > on
> > > > > > > > > the
> > > > > > > > > > > > > current
> > > > > > > > > > > > > > > > > status of
> > > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > service grid?
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 9:12 AM
> > > Dmitriy
> > > > > > >
> > > > > > > Pavlov <
> > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > Ok, let's wait for feedback
> from SG
> > > > > > > > > > > > >
> > > > > > > > > > > > > Author(s)/Reviewer(s)
> > > > > > > > > > > > > > > > > first. If
> > > > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > > > > > > > > not ready, ok. But I thought
> it is
> > > > > almost
> > > > > > > >
> > > > > > > > done.
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > I apologize if I missed some
> > > > > discussion (it
> > > > > > > >
> > > > > > > > can
> > > > > > > > > > > > happen),
> > > > > > > > > > > > > > but
> > > > > > > > > > > > > > > > > > > > > > > According to the statement "our
> > > > current
> > > > > > > > >
> > > > > > > > > agreement"
> > > > > > > > > > > > > > > > > > > > > > > I can suspect some members are
> > > making
> > > > > some
> > > > > > > >
> > > > > > > > sort
> > > > > > > > > of
> > > > > > > > > > > > > private
> > > > > > > > > > > > > > > > > > > agreements,
> > > > > > > > > > > > > > > > > > > > > > and
> > > > > > > > > > > > > > > > > > > > > > > do not to discuss it on the
> list.
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > Let's build consensus here
> first,
> > > and
> > > > > then
> > > > > > > >
> > > > > > > > name
> > > > > > > > > an
> > > > > > > > > > > > > > > agreement.
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > Denis, as PMC Chair, could you
> > > please
> > > > > > >
> > > > > > > control,
> > > > > > > > > > that
> > > > > > > > > > > > > > Service
> > > > > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > > > > > > > > inclusion/exclusion is
> discussed
> > > > > properly
> > > > > > > > > >
> > > > > > > > > > according
> > > > > > > > > > > to
> > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > Apache
> > > > > > > > > > > > > > > > > > > Way.
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 18:55,
> > > > Vladimir
> > > > > > >
> > > > > > > Ozerov
> > > > > > > > <
> > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > This is an outcome of current
> > > state
> > > > > of
> > > > > > > >
> > > > > > > > Service
> > > > > > > > > > > Grid -
> > > > > > > > > > > > > it
> > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > > > > ready.
> > > > > > > > > > > > > > > > > > > > > > We
> > > > > > > > > > > > > > > > > > > > > > > > never committed to have it to
> > > 2.7.
> > > > > Our goal
> > > > > > > >
> > > > > > > > was
> > > > > > > > > > to
> > > > > > > > > > > > try
> > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > include
> > > > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > > > into
> > > > > > > > > > > > > > > > > > > > > > > > 2.7.
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 6:48
> PM
> > > > > Dmitriy
> > > > > > > >
> > > > > > > > Pavlov
> > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > Could you please provide a
> > > > > reference to
> > > > > > > >
> > > > > > > > some
> > > > > > > > > > > > thread?
> > > > > > > > > > > > > > > > > Probably I
> > > > > > > > > > > > > > > > > > > > > > missed
> > > > > > > > > > > > > > > > > > > > > > > > it.
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в
> 18:46,
> > > > > Vladimir
> > > > > > > > >
> > > > > > > > > Ozerov <
> > > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > Our current agreement is
> that
> > > > > Service
> > > > > > > >
> > > > > > > > Grid
> > > > > > > > > is
> > > > > > > > > > > out
> > > > > > > > > > > > > of
> > > > > > > > > > > > > > > > scope.
> > > > > > > > > > > > > > > > > > > This
> > > > > > > > > > > > > > > > > > > > > > is a
> > > > > > > > > > > > > > > > > > > > > > > > > huge
> > > > > > > > > > > > > > > > > > > > > > > > > > feature, which hasn't
> entered
> > > > > review
> > > > > > > >
> > > > > > > > stage
> > > > > > > > > so
> > > > > > > > > > > > far,
> > > > > > > > > > > > > We
> > > > > > > > > > > > > > > > will
> > > > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > > > > > > > able to
> > > > > > > > > > > > > > > > > > > > > > > > > > review/fix/test it
> properly.
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at
> 6:32
> > > PM
> > > > > Dmitriy
> > > > > > > > > >
> > > > > > > > > > Pavlov
> > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > I agree, and I prefer
> four
> > > > > weeks for
> > > > > > > > > > > > >
> > > > > > > > > > > > > stabilization*
> > > > > > > > > > > > > > > (1
> > > > > > > > > > > > > > > > > Oct -
> > > > > > > > > > > > > > > > > > > 29
> > > > > > > > > > > > > > > > > > > > > > Oct)
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > Do I understand it
> > > correctly:
> > > > > Service
> > > > > > > > >
> > > > > > > > > Grid
> > > > > > > > > > is
> > > > > > > > > > > > > still
> > > > > > > > > > > > > > > in
> > > > > > > > > > > > > > > > > scope,
> > > > > > > > > > > > > > > > > > > > > > isn't
> > > > > > > > > > > > > > > > > > > > > > > > > it? I
> > > > > > > > > > > > > > > > > > > > > > > > > > > find it very important.
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в
> > > 18:28,
> > > > > Nikolay
> > > > > > > > > > >
> > > > > > > > > > > Izhikov <
> > > > > > > > > > > > > > > > > > > > > > nizhikov@apache.org
> > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > Hello, Vova.
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > Thank you for clear
> > > release
> > > > > status.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > I'm +1 for your
> proposal.
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г.,
> > > 18:25
> > > > > Alexey
> > > > > > > > > > >
> > > > > > > > > > > Kuznetsov
> > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > > > akuznetsov@apache.org
> > > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > Vova,
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > Huge +1 to do a
> > > > > stabilization.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > Alexey Kuznetsov
> > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > > > > Best regards,
> > > > > > > > > > > > > > > > > > > Andrey Kuznetsov.
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > > Best Regards, Vyacheslav D.
> > > > > > > > > > > > > > > > >
> > > > >
> > > >
> > >
>
>
>
> --
> Best Regards, Vyacheslav D.
>
Re: Apache Ignite 2.7 release
Posted by Vyacheslav Daradur <da...@gmail.com>.
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 <ds...@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 <dp...@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 <dm...@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 <ni...@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 <
> > dsetrakyan@apache.org
> > > >:
> > > > >
> > > > > > Dmitriy,
> > > > > >
> > > > > > We agreed in the beginning of this thread that Service Grid changes
> > > > are not
> > > > > > going to make the release because the community still did not
> > approve
> > > > the
> > > > > > design. Nothing has changed since. I have not seen any design
> > > > discussions.
> > > > > > At this point, I have no confidence that the Service Grid changes
> > > will
> > > > make
> > > > > > it into the 2.8 release. The 2.7 release seems out of question
> > > > altogether.
> > > > > >
> > > > > > Also, Nikolay is a release manager. We should let him drive the
> > > > release. To
> > > > > > my knowledge, he is doing a great job and the release is going
> > > > according to
> > > > > > the schedule he proposed.
> > > > > >
> > > > > > D.
> > > > > >
> > > > > > On Fri, Sep 28, 2018 at 4:31 AM Dmitriy Pavlov <
> > > dpavlov.spb@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Hi Dmitriy, Vladimir,
> > > > > > >
> > > > > > > I suggest we stop this nonsense with release dates-pushing
> > because
> > > of
> > > > > >
> > > > > > some
> > > > > > > open question.
> > > > > > >
> > > > > > > Just because you disagreed with any include/exclude something
> > into
> > > > scope,
> > > > > > > does not mean that whole community disagreed.
> > > > > > >
> > > > > > > If folks will start a separate discussion with results of the
> > > > review, I
> > > > > >
> > > > > > see
> > > > > > > no reasons to reject their contribution, even if we need to
> > revisit
> > > > our
> > > > > > > agreements and wait for a couple of days more.
> > > > > > >
> > > > > > > Am I missing some reason why dates are so fundamentally important
> > > to
> > > > you?
> > > > > > >
> > > > > > > Sincerely,
> > > > > > > Dmitriy Pavlov
> > > > > > >
> > > > > > > пт, 28 сент. 2018 г. в 12:20, Dmitriy Setrakyan <
> > > > dsetrakyan@apache.org>:
> > > > > > >
> > > > > > > > If services is not ready, which it is not, then we should
> > include
> > > > them
> > > > > > >
> > > > > > > into
> > > > > > > > the next release. There is no need to force them into 2.7. I
> > > > suggest we
> > > > > > > > move according to the schedule we all agreed on.
> > > > > > > >
> > > > > > > > D.
> > > > > > > >
> > > > > > > > On Fri, Sep 28, 2018 at 1:22 AM Dmitriy Pavlov <
> > > > dpavlov.spb@gmail.com>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Yes, so correct statement is "community did not make any
> > > > decisions
> > > > > > >
> > > > > > > about
> > > > > > > > > services not go to 2.7/ services are out of scope".
> > > > > > > > >
> > > > > > > > > If so, please forgive me my confusion.
> > > > > > > > >
> > > > > > > > > пт, 28 сент. 2018 г. в 11:19, Vladimir Ozerov <
> > > > vozerov@gridgain.com
> > > > > > >
> > > > > > > :
> > > > > > > > >
> > > > > > > > > > Exactly. So correct statement is “it is up to *community*
> > to
> > > > decide
> > > > > > > > >
> > > > > > > > > whether
> > > > > > > > > > something goes to 2.7”.
> > > > > > > > > >
> > > > > > > > > > пт, 28 сент. 2018 г. в 11:11, Dmitriy Pavlov <
> > > > > >
> > > > > > dpavlov.spb@gmail.com
> > > > > > > > :
> > > > > > > > > >
> > > > > > > > > > > No, it is up to the community to discuss after their
> > review
> > > > > > >
> > > > > > > results.
> > > > > > > > > > >
> > > > > > > > > > > пт, 28 сент. 2018 г. в 11:09, Vladimir Ozerov <
> > > > > > >
> > > > > > > vozerov@gridgain.com
> > > > > > > > > :
> > > > > > > > > > >
> > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > >
> > > > > > > > > > > > Did I read your words correctly that it is up to
> > > > implementor
> > > > > >
> > > > > > of a
> > > > > > > > > > single
> > > > > > > > > > > > feature to decide whether release of all other features
> > > and
> > > > > >
> > > > > > fixes
> > > > > > > > to
> > > > > > > > > be
> > > > > > > > > > > > delayed?
> > > > > > > > > > > >
> > > > > > > > > > > > пт, 28 сент. 2018 г. в 11:00, Dmitriy Pavlov <
> > > > > > > >
> > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > :
> > > > > > > > > > > >
> > > > > > > > > > > > > My point we can wait a bit for services because
> > > > > > > > > > > > > 1 we are open-minded and we don't have outside
> > > pressure
> > > > to
> > > > > >
> > > > > > do
> > > > > > > > > > release
> > > > > > > > > > > in
> > > > > > > > > > > > > October
> > > > > > > > > > > > > 2 and services it is not some new feature, which
> > > > suddenly
> > > > > > > >
> > > > > > > > appeared
> > > > > > > > > > in
> > > > > > > > > > > > > autumn, it is a well known and important feature.
> > > > > > > > > > > > >
> > > > > > > > > > > > > So it is up to Vyacheslav, Anton and Nikolay to
> > decide.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Decisions can be services are not ready/ready to
> > merge
> > > > only
> > > > > >
> > > > > > to
> > > > > > > > > > > > master/ready
> > > > > > > > > > > > > to merge to master and to 2.7.
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > пт, 28 сент. 2018 г. в 10:46, Vladimir Ozerov <
> > > > > > > > >
> > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > :
> > > > > > > > > > > > >
> > > > > > > > > > > > > > Dmitry,
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Community agreement was to perform the release in
> > > > October.
> > > > > >
> > > > > > Of
> > > > > > > > > > course
> > > > > > > > > > > we
> > > > > > > > > > > > > can
> > > > > > > > > > > > > > wait a bit for services. Then we wait a bit for
> > other
> > > > cool
> > > > > > > > >
> > > > > > > > > features
> > > > > > > > > > > > ready
> > > > > > > > > > > > > > by that time, then again and again, and release
> > will
> > > > never
> > > > > > > > >
> > > > > > > > > happen.
> > > > > > > > > > > And
> > > > > > > > > > > > > > while we are waiting for new features to come,
> > > already
> > > > > > > >
> > > > > > > > completerd
> > > > > > > > > > > > > features
> > > > > > > > > > > > > > cannot be used by anyone.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > This is why we have an agreement that if feature is
> > > not
> > > > > > >
> > > > > > > ready,
> > > > > > > > it
> > > > > > > > > > > > should
> > > > > > > > > > > > > be
> > > > > > > > > > > > > > moved to future release, instead of shifting
> > release.
> > > > The
> > > > > > >
> > > > > > > sole
> > > > > > > > > > reason
> > > > > > > > > > > > to
> > > > > > > > > > > > > > have strict dates when decisions are made is to let
> > > > release
> > > > > > > > >
> > > > > > > > > happen.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > On Fri, Sep 28, 2018 at 2:22 AM Dmitriy Pavlov <
> > > > > > > > > > >
> > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Vladimir, I'm not searching for enemy, and not
> > > > fighting
> > > > > > >
> > > > > > > with
> > > > > > > > > > you.
> > > > > > > > > > > > I'm
> > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > happy about cases when we are hurrying.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > We can't fix test, fill ticket details, can't
> > wait
> > > > for
> > > > > > > > > > >
> > > > > > > > > > > contributions
> > > > > > > > > > > > to
> > > > > > > > > > > > > > > finish their tasks. It is not best idea to use
> > > > > >
> > > > > > experience
> > > > > > > > from
> > > > > > > > > > > > > > commercial
> > > > > > > > > > > > > > > companies in open source. Are there any pressure
> > > > outside
> > > > > > > > > >
> > > > > > > > > > community?
> > > > > > > > > > > > Did
> > > > > > > > > > > > > > > someone promised rest of features to be released
> > at
> > > > 30
> > > > > > > > >
> > > > > > > > > September?
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Let's remember principle do-orcracy, power of
> > those
> > > > who
> > > > > >
> > > > > > do.
> > > > > > > > If
> > > > > > > > > > > > > contribor
> > > > > > > > > > > > > > > does change and reviewer does review, let's give
> > > > right of
> > > > > > > > >
> > > > > > > > > making
> > > > > > > > > > > > > decision
> > > > > > > > > > > > > > > to them, but not to some closed club of people
> > who
> > > > > > >
> > > > > > > privately
> > > > > > > > > > > discuss
> > > > > > > > > > > > > > > something.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Sincerely
> > > > > > > > > > > > > > > Dmitriy Pavlov
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > чт, 27 сент. 2018 г., 23:42 Vyacheslav Daradur <
> > > > > > > > > > >
> > > > > > > > > > > daradurvs@gmail.com
> > > > > > > > > > > > > :
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Hi Igniters!
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > As I have written about Service Grid before [1]
> > > I'm
> > > > > > > > >
> > > > > > > > > finalizing
> > > > > > > > > > > the
> > > > > > > > > > > > > > > > solution to be sure that implementation is
> > > > reliable.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > About including it in 2.7, if we talk that code
> > > > freeze
> > > > > > > > >
> > > > > > > > > tomorrow
> > > > > > > > > > > > then
> > > > > > > > > > > > > > > > the solution is not ready to merge yet.
> > > > > > > > > > > > > > > > I hope that prereviewers Anton Vinogradov and
> > > > Nikolay
> > > > > > > >
> > > > > > > > Izhikov
> > > > > > > > > > > will
> > > > > > > > > > > > be
> > > > > > > > > > > > > > > > able to answer if solution out of scope or not
> > > in a
> > > > > > >
> > > > > > > couple
> > > > > > > > of
> > > > > > > > > > > days.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > [1]
> > > > > > > > > > > > > > > >
> > > > > >
> > > > > >
> > > >
> > >
> > http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-release-td34076.html#a34485
> > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 11:14 PM Dmitriy
> > Pavlov <
> > > > > > > > > > > > >
> > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Yes, I agree, NPE during WAL flush is
> > > definitely
> > > > a
> > > > > > > >
> > > > > > > > blocker.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > It is strange why the current test set did
> > not
> > > > fail
> > > > > > >
> > > > > > > after
> > > > > > > > > > > commit.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 21:45, Andrey
> > Kuznetsov
> > > <
> > > > > > > > > > > >
> > > > > > > > > > > > stkuzma@gmail.com
> > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Igniters,
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > I've bumped into a new bug in WAL manager
> > > > recently,
> > > > > > >
> > > > > > > see
> > > > > > > > > > [1].
> > > > > > > > > > > It
> > > > > > > > > > > > > > looks
> > > > > > > > > > > > > > > > > > critical enough, and can be a good
> > candidate
> > > > for
> > > > > > >
> > > > > > > fixing
> > > > > > > > > > > before
> > > > > > > > > > > > > 2.7
> > > > > > > > > > > > > > > > release.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Do you agree?
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > [1]
> > > > > > >
> > > > > > > https://issues.apache.org/jira/browse/IGNITE-9731
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 19:45, Dmitriy
> > Pavlov
> > > <
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > I need Vhyacheslav's opinion to be
> > > absolutely
> > > > > >
> > > > > > sure
> > > > > > > > what
> > > > > > > > > > > > status
> > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > now.
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > We never committed to dates of release,
> > as
> > > > well.
> > > > > >
> > > > > > I
> > > > > > > > > don't
> > > > > > > > > > > > quite
> > > > > > > > > > > > > > > > understand
> > > > > > > > > > > > > > > > > > > what can mean 'the community committed to
> > > > > > > > >
> > > > > > > > > doing/releasing
> > > > > > > > > > > > > > > something'.
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > About SG, I also concerned why such a big
> > > > feature
> > > > > > >
> > > > > > > has
> > > > > > > > > > > quite a
> > > > > > > > > > > > > few
> > > > > > > > > > > > > > > > > > > discussions on the list. But it is
> > another
> > > > story.
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 19:33, Vladimir
> > > > Ozerov <
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > Folks,
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > Please stop looking for enemies
> > > everywhere.
> > > > > >
> > > > > > Just
> > > > > > > > went
> > > > > > > > > > > > through
> > > > > > > > > > > > > > > this
> > > > > > > > > > > > > > > > > > thread
> > > > > > > > > > > > > > > > > > > > and search for "service" word.
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 7:30 PM Denis
> > > > Magda <
> > > > > > > > > > > > >
> > > > > > > > > > > > > dmagda@apache.org
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > Denis, as PMC Chair, could you
> > please
> > > > > >
> > > > > > control,
> > > > > > > > > that
> > > > > > > > > > > > > Service
> > > > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > > > > > > > inclusion/exclusion is discussed
> > > > properly
> > > > > > > > >
> > > > > > > > > according
> > > > > > > > > > to
> > > > > > > > > > > > the
> > > > > > > > > > > > > > > > Apache
> > > > > > > > > > > > > > > > > > Way.
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > It's fine when
> > committers/contributors
> > > > have
> > > > > > > >
> > > > > > > > private
> > > > > > > > > > > > > > discussions
> > > > > > > > > > > > > > > > > > related
> > > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > > a feature they've been working on.
> > Not
> > > > > > >
> > > > > > > everything
> > > > > > > > > > should
> > > > > > > > > > > > go
> > > > > > > > > > > > > > > > through
> > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > dev
> > > > > > > > > > > > > > > > > > > > > list. Otherwise, it will be
> > inundated.
> > > > > >
> > > > > > However,
> > > > > > > > > > agree,
> > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > > > architectural
> > > > > > > > > > > > > > > > > > > > > and release decisions need to be done
> > > > > >
> > > > > > publicly.
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > Speaking about Service Grid, there
> > was
> > > a
> > > > > > > >
> > > > > > > > discussion
> > > > > > > > > > > where
> > > > > > > > > > > > I
> > > > > > > > > > > > > > saw
> > > > > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > > was
> > > > > > > > > > > > > > > > > > > > > questionable whether it gets added to
> > > the
> > > > > > >
> > > > > > > release
> > > > > > > > or
> > > > > > > > > > > not.
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > *Vladislav*, could you please shed
> > some
> > > > light
> > > > > >
> > > > > > on
> > > > > > > > the
> > > > > > > > > > > > current
> > > > > > > > > > > > > > > > status of
> > > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > service grid?
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 9:12 AM
> > Dmitriy
> > > > > >
> > > > > > Pavlov <
> > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > Ok, let's wait for feedback from SG
> > > > > > > > > > > >
> > > > > > > > > > > > Author(s)/Reviewer(s)
> > > > > > > > > > > > > > > > first. If
> > > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > > > > > > > not ready, ok. But I thought it is
> > > > almost
> > > > > > >
> > > > > > > done.
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > I apologize if I missed some
> > > > discussion (it
> > > > > > >
> > > > > > > can
> > > > > > > > > > > happen),
> > > > > > > > > > > > > but
> > > > > > > > > > > > > > > > > > > > > > According to the statement "our
> > > current
> > > > > > > >
> > > > > > > > agreement"
> > > > > > > > > > > > > > > > > > > > > > I can suspect some members are
> > making
> > > > some
> > > > > > >
> > > > > > > sort
> > > > > > > > of
> > > > > > > > > > > > private
> > > > > > > > > > > > > > > > > > agreements,
> > > > > > > > > > > > > > > > > > > > > and
> > > > > > > > > > > > > > > > > > > > > > do not to discuss it on the list.
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > Let's build consensus here first,
> > and
> > > > then
> > > > > > >
> > > > > > > name
> > > > > > > > an
> > > > > > > > > > > > > > agreement.
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > Denis, as PMC Chair, could you
> > please
> > > > > >
> > > > > > control,
> > > > > > > > > that
> > > > > > > > > > > > > Service
> > > > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > > > > > > > inclusion/exclusion is discussed
> > > > properly
> > > > > > > > >
> > > > > > > > > according
> > > > > > > > > > to
> > > > > > > > > > > > the
> > > > > > > > > > > > > > > > Apache
> > > > > > > > > > > > > > > > > > Way.
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 18:55,
> > > Vladimir
> > > > > >
> > > > > > Ozerov
> > > > > > > <
> > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > This is an outcome of current
> > state
> > > > of
> > > > > > >
> > > > > > > Service
> > > > > > > > > > Grid -
> > > > > > > > > > > > it
> > > > > > > > > > > > > is
> > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > > > ready.
> > > > > > > > > > > > > > > > > > > > > We
> > > > > > > > > > > > > > > > > > > > > > > never committed to have it to
> > 2.7.
> > > > Our goal
> > > > > > >
> > > > > > > was
> > > > > > > > > to
> > > > > > > > > > > try
> > > > > > > > > > > > to
> > > > > > > > > > > > > > > > include
> > > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > > into
> > > > > > > > > > > > > > > > > > > > > > > 2.7.
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 6:48 PM
> > > > Dmitriy
> > > > > > >
> > > > > > > Pavlov
> > > > > > > > <
> > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > Could you please provide a
> > > > reference to
> > > > > > >
> > > > > > > some
> > > > > > > > > > > thread?
> > > > > > > > > > > > > > > > Probably I
> > > > > > > > > > > > > > > > > > > > > missed
> > > > > > > > > > > > > > > > > > > > > > > it.
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 18:46,
> > > > Vladimir
> > > > > > > >
> > > > > > > > Ozerov <
> > > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > Our current agreement is that
> > > > Service
> > > > > > >
> > > > > > > Grid
> > > > > > > > is
> > > > > > > > > > out
> > > > > > > > > > > > of
> > > > > > > > > > > > > > > scope.
> > > > > > > > > > > > > > > > > > This
> > > > > > > > > > > > > > > > > > > > > is a
> > > > > > > > > > > > > > > > > > > > > > > > huge
> > > > > > > > > > > > > > > > > > > > > > > > > feature, which hasn't entered
> > > > review
> > > > > > >
> > > > > > > stage
> > > > > > > > so
> > > > > > > > > > > far,
> > > > > > > > > > > > We
> > > > > > > > > > > > > > > will
> > > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > > > > > > able to
> > > > > > > > > > > > > > > > > > > > > > > > > review/fix/test it properly.
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 6:32
> > PM
> > > > Dmitriy
> > > > > > > > >
> > > > > > > > > Pavlov
> > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > I agree, and I prefer four
> > > > weeks for
> > > > > > > > > > > >
> > > > > > > > > > > > stabilization*
> > > > > > > > > > > > > > (1
> > > > > > > > > > > > > > > > Oct -
> > > > > > > > > > > > > > > > > > 29
> > > > > > > > > > > > > > > > > > > > > Oct)
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > Do I understand it
> > correctly:
> > > > Service
> > > > > > > >
> > > > > > > > Grid
> > > > > > > > > is
> > > > > > > > > > > > still
> > > > > > > > > > > > > > in
> > > > > > > > > > > > > > > > scope,
> > > > > > > > > > > > > > > > > > > > > isn't
> > > > > > > > > > > > > > > > > > > > > > > > it? I
> > > > > > > > > > > > > > > > > > > > > > > > > > find it very important.
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в
> > 18:28,
> > > > Nikolay
> > > > > > > > > >
> > > > > > > > > > Izhikov <
> > > > > > > > > > > > > > > > > > > > > nizhikov@apache.org
> > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > Hello, Vova.
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > Thank you for clear
> > release
> > > > status.
> > > > > > > > > > > > > > > > > > > > > > > > > > > I'm +1 for your proposal.
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г.,
> > 18:25
> > > > Alexey
> > > > > > > > > >
> > > > > > > > > > Kuznetsov
> > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > > akuznetsov@apache.org
> > > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > Vova,
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > Huge +1 to do a
> > > > stabilization.
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > > > > > > > > > > > > > Alexey Kuznetsov
> > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > > > Best regards,
> > > > > > > > > > > > > > > > > > Andrey Kuznetsov.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > Best Regards, Vyacheslav D.
> > > > > > > > > > > > > > > >
> > > >
> > >
> >
--
Best Regards, Vyacheslav D.
Re: Apache Ignite 2.7 release
Posted by Dmitriy Setrakyan <ds...@apache.org>.
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 <dp...@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 <dm...@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 <ni...@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 <
> dsetrakyan@apache.org
> > >:
> > > >
> > > > > Dmitriy,
> > > > >
> > > > > We agreed in the beginning of this thread that Service Grid changes
> > > are not
> > > > > going to make the release because the community still did not
> approve
> > > the
> > > > > design. Nothing has changed since. I have not seen any design
> > > discussions.
> > > > > At this point, I have no confidence that the Service Grid changes
> > will
> > > make
> > > > > it into the 2.8 release. The 2.7 release seems out of question
> > > altogether.
> > > > >
> > > > > Also, Nikolay is a release manager. We should let him drive the
> > > release. To
> > > > > my knowledge, he is doing a great job and the release is going
> > > according to
> > > > > the schedule he proposed.
> > > > >
> > > > > D.
> > > > >
> > > > > On Fri, Sep 28, 2018 at 4:31 AM Dmitriy Pavlov <
> > dpavlov.spb@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Hi Dmitriy, Vladimir,
> > > > > >
> > > > > > I suggest we stop this nonsense with release dates-pushing
> because
> > of
> > > > >
> > > > > some
> > > > > > open question.
> > > > > >
> > > > > > Just because you disagreed with any include/exclude something
> into
> > > scope,
> > > > > > does not mean that whole community disagreed.
> > > > > >
> > > > > > If folks will start a separate discussion with results of the
> > > review, I
> > > > >
> > > > > see
> > > > > > no reasons to reject their contribution, even if we need to
> revisit
> > > our
> > > > > > agreements and wait for a couple of days more.
> > > > > >
> > > > > > Am I missing some reason why dates are so fundamentally important
> > to
> > > you?
> > > > > >
> > > > > > Sincerely,
> > > > > > Dmitriy Pavlov
> > > > > >
> > > > > > пт, 28 сент. 2018 г. в 12:20, Dmitriy Setrakyan <
> > > dsetrakyan@apache.org>:
> > > > > >
> > > > > > > If services is not ready, which it is not, then we should
> include
> > > them
> > > > > >
> > > > > > into
> > > > > > > the next release. There is no need to force them into 2.7. I
> > > suggest we
> > > > > > > move according to the schedule we all agreed on.
> > > > > > >
> > > > > > > D.
> > > > > > >
> > > > > > > On Fri, Sep 28, 2018 at 1:22 AM Dmitriy Pavlov <
> > > dpavlov.spb@gmail.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Yes, so correct statement is "community did not make any
> > > decisions
> > > > > >
> > > > > > about
> > > > > > > > services not go to 2.7/ services are out of scope".
> > > > > > > >
> > > > > > > > If so, please forgive me my confusion.
> > > > > > > >
> > > > > > > > пт, 28 сент. 2018 г. в 11:19, Vladimir Ozerov <
> > > vozerov@gridgain.com
> > > > > >
> > > > > > :
> > > > > > > >
> > > > > > > > > Exactly. So correct statement is “it is up to *community*
> to
> > > decide
> > > > > > > >
> > > > > > > > whether
> > > > > > > > > something goes to 2.7”.
> > > > > > > > >
> > > > > > > > > пт, 28 сент. 2018 г. в 11:11, Dmitriy Pavlov <
> > > > >
> > > > > dpavlov.spb@gmail.com
> > > > > > > :
> > > > > > > > >
> > > > > > > > > > No, it is up to the community to discuss after their
> review
> > > > > >
> > > > > > results.
> > > > > > > > > >
> > > > > > > > > > пт, 28 сент. 2018 г. в 11:09, Vladimir Ozerov <
> > > > > >
> > > > > > vozerov@gridgain.com
> > > > > > > > :
> > > > > > > > > >
> > > > > > > > > > > Dmitriy,
> > > > > > > > > > >
> > > > > > > > > > > Did I read your words correctly that it is up to
> > > implementor
> > > > >
> > > > > of a
> > > > > > > > > single
> > > > > > > > > > > feature to decide whether release of all other features
> > and
> > > > >
> > > > > fixes
> > > > > > > to
> > > > > > > > be
> > > > > > > > > > > delayed?
> > > > > > > > > > >
> > > > > > > > > > > пт, 28 сент. 2018 г. в 11:00, Dmitriy Pavlov <
> > > > > > >
> > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > :
> > > > > > > > > > >
> > > > > > > > > > > > My point we can wait a bit for services because
> > > > > > > > > > > > 1 we are open-minded and we don't have outside
> > pressure
> > > to
> > > > >
> > > > > do
> > > > > > > > > release
> > > > > > > > > > in
> > > > > > > > > > > > October
> > > > > > > > > > > > 2 and services it is not some new feature, which
> > > suddenly
> > > > > > >
> > > > > > > appeared
> > > > > > > > > in
> > > > > > > > > > > > autumn, it is a well known and important feature.
> > > > > > > > > > > >
> > > > > > > > > > > > So it is up to Vyacheslav, Anton and Nikolay to
> decide.
> > > > > > > > > > > >
> > > > > > > > > > > > Decisions can be services are not ready/ready to
> merge
> > > only
> > > > >
> > > > > to
> > > > > > > > > > > master/ready
> > > > > > > > > > > > to merge to master and to 2.7.
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > пт, 28 сент. 2018 г. в 10:46, Vladimir Ozerov <
> > > > > > > >
> > > > > > > > vozerov@gridgain.com
> > > > > > > > > > :
> > > > > > > > > > > >
> > > > > > > > > > > > > Dmitry,
> > > > > > > > > > > > >
> > > > > > > > > > > > > Community agreement was to perform the release in
> > > October.
> > > > >
> > > > > Of
> > > > > > > > > course
> > > > > > > > > > we
> > > > > > > > > > > > can
> > > > > > > > > > > > > wait a bit for services. Then we wait a bit for
> other
> > > cool
> > > > > > > >
> > > > > > > > features
> > > > > > > > > > > ready
> > > > > > > > > > > > > by that time, then again and again, and release
> will
> > > never
> > > > > > > >
> > > > > > > > happen.
> > > > > > > > > > And
> > > > > > > > > > > > > while we are waiting for new features to come,
> > already
> > > > > > >
> > > > > > > completerd
> > > > > > > > > > > > features
> > > > > > > > > > > > > cannot be used by anyone.
> > > > > > > > > > > > >
> > > > > > > > > > > > > This is why we have an agreement that if feature is
> > not
> > > > > >
> > > > > > ready,
> > > > > > > it
> > > > > > > > > > > should
> > > > > > > > > > > > be
> > > > > > > > > > > > > moved to future release, instead of shifting
> release.
> > > The
> > > > > >
> > > > > > sole
> > > > > > > > > reason
> > > > > > > > > > > to
> > > > > > > > > > > > > have strict dates when decisions are made is to let
> > > release
> > > > > > > >
> > > > > > > > happen.
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > On Fri, Sep 28, 2018 at 2:22 AM Dmitriy Pavlov <
> > > > > > > > > >
> > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > > > Vladimir, I'm not searching for enemy, and not
> > > fighting
> > > > > >
> > > > > > with
> > > > > > > > > you.
> > > > > > > > > > > I'm
> > > > > > > > > > > > > not
> > > > > > > > > > > > > > happy about cases when we are hurrying.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > We can't fix test, fill ticket details, can't
> wait
> > > for
> > > > > > > > > >
> > > > > > > > > > contributions
> > > > > > > > > > > to
> > > > > > > > > > > > > > finish their tasks. It is not best idea to use
> > > > >
> > > > > experience
> > > > > > > from
> > > > > > > > > > > > > commercial
> > > > > > > > > > > > > > companies in open source. Are there any pressure
> > > outside
> > > > > > > > >
> > > > > > > > > community?
> > > > > > > > > > > Did
> > > > > > > > > > > > > > someone promised rest of features to be released
> at
> > > 30
> > > > > > > >
> > > > > > > > September?
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Let's remember principle do-orcracy, power of
> those
> > > who
> > > > >
> > > > > do.
> > > > > > > If
> > > > > > > > > > > > contribor
> > > > > > > > > > > > > > does change and reviewer does review, let's give
> > > right of
> > > > > > > >
> > > > > > > > making
> > > > > > > > > > > > decision
> > > > > > > > > > > > > > to them, but not to some closed club of people
> who
> > > > > >
> > > > > > privately
> > > > > > > > > > discuss
> > > > > > > > > > > > > > something.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Sincerely
> > > > > > > > > > > > > > Dmitriy Pavlov
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > чт, 27 сент. 2018 г., 23:42 Vyacheslav Daradur <
> > > > > > > > > >
> > > > > > > > > > daradurvs@gmail.com
> > > > > > > > > > > > :
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Hi Igniters!
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > As I have written about Service Grid before [1]
> > I'm
> > > > > > > >
> > > > > > > > finalizing
> > > > > > > > > > the
> > > > > > > > > > > > > > > solution to be sure that implementation is
> > > reliable.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > About including it in 2.7, if we talk that code
> > > freeze
> > > > > > > >
> > > > > > > > tomorrow
> > > > > > > > > > > then
> > > > > > > > > > > > > > > the solution is not ready to merge yet.
> > > > > > > > > > > > > > > I hope that prereviewers Anton Vinogradov and
> > > Nikolay
> > > > > > >
> > > > > > > Izhikov
> > > > > > > > > > will
> > > > > > > > > > > be
> > > > > > > > > > > > > > > able to answer if solution out of scope or not
> > in a
> > > > > >
> > > > > > couple
> > > > > > > of
> > > > > > > > > > days.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > [1]
> > > > > > > > > > > > > > >
> > > > >
> > > > >
> > >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-release-td34076.html#a34485
> > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 11:14 PM Dmitriy
> Pavlov <
> > > > > > > > > > > >
> > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Yes, I agree, NPE during WAL flush is
> > definitely
> > > a
> > > > > > >
> > > > > > > blocker.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > It is strange why the current test set did
> not
> > > fail
> > > > > >
> > > > > > after
> > > > > > > > > > commit.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 21:45, Andrey
> Kuznetsov
> > <
> > > > > > > > > > >
> > > > > > > > > > > stkuzma@gmail.com
> > > > > > > > > > > > > :
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Igniters,
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > I've bumped into a new bug in WAL manager
> > > recently,
> > > > > >
> > > > > > see
> > > > > > > > > [1].
> > > > > > > > > > It
> > > > > > > > > > > > > looks
> > > > > > > > > > > > > > > > > critical enough, and can be a good
> candidate
> > > for
> > > > > >
> > > > > > fixing
> > > > > > > > > > before
> > > > > > > > > > > > 2.7
> > > > > > > > > > > > > > > release.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Do you agree?
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > [1]
> > > > > >
> > > > > > https://issues.apache.org/jira/browse/IGNITE-9731
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 19:45, Dmitriy
> Pavlov
> > <
> > > > > > > > > > > > >
> > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > I need Vhyacheslav's opinion to be
> > absolutely
> > > > >
> > > > > sure
> > > > > > > what
> > > > > > > > > > > status
> > > > > > > > > > > > is
> > > > > > > > > > > > > > > now.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > We never committed to dates of release,
> as
> > > well.
> > > > >
> > > > > I
> > > > > > > > don't
> > > > > > > > > > > quite
> > > > > > > > > > > > > > > understand
> > > > > > > > > > > > > > > > > > what can mean 'the community committed to
> > > > > > > >
> > > > > > > > doing/releasing
> > > > > > > > > > > > > > something'.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > About SG, I also concerned why such a big
> > > feature
> > > > > >
> > > > > > has
> > > > > > > > > > quite a
> > > > > > > > > > > > few
> > > > > > > > > > > > > > > > > > discussions on the list. But it is
> another
> > > story.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 19:33, Vladimir
> > > Ozerov <
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > Folks,
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > Please stop looking for enemies
> > everywhere.
> > > > >
> > > > > Just
> > > > > > > went
> > > > > > > > > > > through
> > > > > > > > > > > > > > this
> > > > > > > > > > > > > > > > > thread
> > > > > > > > > > > > > > > > > > > and search for "service" word.
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 7:30 PM Denis
> > > Magda <
> > > > > > > > > > > >
> > > > > > > > > > > > dmagda@apache.org
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > Denis, as PMC Chair, could you
> please
> > > > >
> > > > > control,
> > > > > > > > that
> > > > > > > > > > > > Service
> > > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > > > > > > inclusion/exclusion is discussed
> > > properly
> > > > > > > >
> > > > > > > > according
> > > > > > > > > to
> > > > > > > > > > > the
> > > > > > > > > > > > > > > Apache
> > > > > > > > > > > > > > > > > Way.
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > It's fine when
> committers/contributors
> > > have
> > > > > > >
> > > > > > > private
> > > > > > > > > > > > > discussions
> > > > > > > > > > > > > > > > > related
> > > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > > a feature they've been working on.
> Not
> > > > > >
> > > > > > everything
> > > > > > > > > should
> > > > > > > > > > > go
> > > > > > > > > > > > > > > through
> > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > dev
> > > > > > > > > > > > > > > > > > > > list. Otherwise, it will be
> inundated.
> > > > >
> > > > > However,
> > > > > > > > > agree,
> > > > > > > > > > > that
> > > > > > > > > > > > > > > > > > architectural
> > > > > > > > > > > > > > > > > > > > and release decisions need to be done
> > > > >
> > > > > publicly.
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > Speaking about Service Grid, there
> was
> > a
> > > > > > >
> > > > > > > discussion
> > > > > > > > > > where
> > > > > > > > > > > I
> > > > > > > > > > > > > saw
> > > > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > was
> > > > > > > > > > > > > > > > > > > > questionable whether it gets added to
> > the
> > > > > >
> > > > > > release
> > > > > > > or
> > > > > > > > > > not.
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > *Vladislav*, could you please shed
> some
> > > light
> > > > >
> > > > > on
> > > > > > > the
> > > > > > > > > > > current
> > > > > > > > > > > > > > > status of
> > > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > service grid?
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 9:12 AM
> Dmitriy
> > > > >
> > > > > Pavlov <
> > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > Ok, let's wait for feedback from SG
> > > > > > > > > > >
> > > > > > > > > > > Author(s)/Reviewer(s)
> > > > > > > > > > > > > > > first. If
> > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > > > > > > not ready, ok. But I thought it is
> > > almost
> > > > > >
> > > > > > done.
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > I apologize if I missed some
> > > discussion (it
> > > > > >
> > > > > > can
> > > > > > > > > > happen),
> > > > > > > > > > > > but
> > > > > > > > > > > > > > > > > > > > > According to the statement "our
> > current
> > > > > > >
> > > > > > > agreement"
> > > > > > > > > > > > > > > > > > > > > I can suspect some members are
> making
> > > some
> > > > > >
> > > > > > sort
> > > > > > > of
> > > > > > > > > > > private
> > > > > > > > > > > > > > > > > agreements,
> > > > > > > > > > > > > > > > > > > > and
> > > > > > > > > > > > > > > > > > > > > do not to discuss it on the list.
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > Let's build consensus here first,
> and
> > > then
> > > > > >
> > > > > > name
> > > > > > > an
> > > > > > > > > > > > > agreement.
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > Denis, as PMC Chair, could you
> please
> > > > >
> > > > > control,
> > > > > > > > that
> > > > > > > > > > > > Service
> > > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > > > > > > inclusion/exclusion is discussed
> > > properly
> > > > > > > >
> > > > > > > > according
> > > > > > > > > to
> > > > > > > > > > > the
> > > > > > > > > > > > > > > Apache
> > > > > > > > > > > > > > > > > Way.
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 18:55,
> > Vladimir
> > > > >
> > > > > Ozerov
> > > > > > <
> > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > This is an outcome of current
> state
> > > of
> > > > > >
> > > > > > Service
> > > > > > > > > Grid -
> > > > > > > > > > > it
> > > > > > > > > > > > is
> > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > > ready.
> > > > > > > > > > > > > > > > > > > > We
> > > > > > > > > > > > > > > > > > > > > > never committed to have it to
> 2.7.
> > > Our goal
> > > > > >
> > > > > > was
> > > > > > > > to
> > > > > > > > > > try
> > > > > > > > > > > to
> > > > > > > > > > > > > > > include
> > > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > into
> > > > > > > > > > > > > > > > > > > > > > 2.7.
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 6:48 PM
> > > Dmitriy
> > > > > >
> > > > > > Pavlov
> > > > > > > <
> > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > Could you please provide a
> > > reference to
> > > > > >
> > > > > > some
> > > > > > > > > > thread?
> > > > > > > > > > > > > > > Probably I
> > > > > > > > > > > > > > > > > > > > missed
> > > > > > > > > > > > > > > > > > > > > > it.
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 18:46,
> > > Vladimir
> > > > > > >
> > > > > > > Ozerov <
> > > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > Our current agreement is that
> > > Service
> > > > > >
> > > > > > Grid
> > > > > > > is
> > > > > > > > > out
> > > > > > > > > > > of
> > > > > > > > > > > > > > scope.
> > > > > > > > > > > > > > > > > This
> > > > > > > > > > > > > > > > > > > > is a
> > > > > > > > > > > > > > > > > > > > > > > huge
> > > > > > > > > > > > > > > > > > > > > > > > feature, which hasn't entered
> > > review
> > > > > >
> > > > > > stage
> > > > > > > so
> > > > > > > > > > far,
> > > > > > > > > > > We
> > > > > > > > > > > > > > will
> > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > > > > > able to
> > > > > > > > > > > > > > > > > > > > > > > > review/fix/test it properly.
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 6:32
> PM
> > > Dmitriy
> > > > > > > >
> > > > > > > > Pavlov
> > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > I agree, and I prefer four
> > > weeks for
> > > > > > > > > > >
> > > > > > > > > > > stabilization*
> > > > > > > > > > > > > (1
> > > > > > > > > > > > > > > Oct -
> > > > > > > > > > > > > > > > > 29
> > > > > > > > > > > > > > > > > > > > Oct)
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > Do I understand it
> correctly:
> > > Service
> > > > > > >
> > > > > > > Grid
> > > > > > > > is
> > > > > > > > > > > still
> > > > > > > > > > > > > in
> > > > > > > > > > > > > > > scope,
> > > > > > > > > > > > > > > > > > > > isn't
> > > > > > > > > > > > > > > > > > > > > > > it? I
> > > > > > > > > > > > > > > > > > > > > > > > > find it very important.
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в
> 18:28,
> > > Nikolay
> > > > > > > > >
> > > > > > > > > Izhikov <
> > > > > > > > > > > > > > > > > > > > nizhikov@apache.org
> > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > Hello, Vova.
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > Thank you for clear
> release
> > > status.
> > > > > > > > > > > > > > > > > > > > > > > > > > I'm +1 for your proposal.
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г.,
> 18:25
> > > Alexey
> > > > > > > > >
> > > > > > > > > Kuznetsov
> > > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > > akuznetsov@apache.org
> > > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > Vova,
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > Huge +1 to do a
> > > stabilization.
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > > > > > > > > > > > > Alexey Kuznetsov
> > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > > Best regards,
> > > > > > > > > > > > > > > > > Andrey Kuznetsov.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > Best Regards, Vyacheslav D.
> > > > > > > > > > > > > > >
> > >
> >
>
Re: Apache Ignite 2.7 release
Posted by Dmitriy Pavlov <dp...@gmail.com>.
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 <dm...@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 <ni...@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 <dsetrakyan@apache.org
> >:
> > >
> > > > Dmitriy,
> > > >
> > > > We agreed in the beginning of this thread that Service Grid changes
> > are not
> > > > going to make the release because the community still did not approve
> > the
> > > > design. Nothing has changed since. I have not seen any design
> > discussions.
> > > > At this point, I have no confidence that the Service Grid changes
> will
> > make
> > > > it into the 2.8 release. The 2.7 release seems out of question
> > altogether.
> > > >
> > > > Also, Nikolay is a release manager. We should let him drive the
> > release. To
> > > > my knowledge, he is doing a great job and the release is going
> > according to
> > > > the schedule he proposed.
> > > >
> > > > D.
> > > >
> > > > On Fri, Sep 28, 2018 at 4:31 AM Dmitriy Pavlov <
> dpavlov.spb@gmail.com>
> > > > wrote:
> > > >
> > > > > Hi Dmitriy, Vladimir,
> > > > >
> > > > > I suggest we stop this nonsense with release dates-pushing because
> of
> > > >
> > > > some
> > > > > open question.
> > > > >
> > > > > Just because you disagreed with any include/exclude something into
> > scope,
> > > > > does not mean that whole community disagreed.
> > > > >
> > > > > If folks will start a separate discussion with results of the
> > review, I
> > > >
> > > > see
> > > > > no reasons to reject their contribution, even if we need to revisit
> > our
> > > > > agreements and wait for a couple of days more.
> > > > >
> > > > > Am I missing some reason why dates are so fundamentally important
> to
> > you?
> > > > >
> > > > > Sincerely,
> > > > > Dmitriy Pavlov
> > > > >
> > > > > пт, 28 сент. 2018 г. в 12:20, Dmitriy Setrakyan <
> > dsetrakyan@apache.org>:
> > > > >
> > > > > > If services is not ready, which it is not, then we should include
> > them
> > > > >
> > > > > into
> > > > > > the next release. There is no need to force them into 2.7. I
> > suggest we
> > > > > > move according to the schedule we all agreed on.
> > > > > >
> > > > > > D.
> > > > > >
> > > > > > On Fri, Sep 28, 2018 at 1:22 AM Dmitriy Pavlov <
> > dpavlov.spb@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Yes, so correct statement is "community did not make any
> > decisions
> > > > >
> > > > > about
> > > > > > > services not go to 2.7/ services are out of scope".
> > > > > > >
> > > > > > > If so, please forgive me my confusion.
> > > > > > >
> > > > > > > пт, 28 сент. 2018 г. в 11:19, Vladimir Ozerov <
> > vozerov@gridgain.com
> > > > >
> > > > > :
> > > > > > >
> > > > > > > > Exactly. So correct statement is “it is up to *community* to
> > decide
> > > > > > >
> > > > > > > whether
> > > > > > > > something goes to 2.7”.
> > > > > > > >
> > > > > > > > пт, 28 сент. 2018 г. в 11:11, Dmitriy Pavlov <
> > > >
> > > > dpavlov.spb@gmail.com
> > > > > > :
> > > > > > > >
> > > > > > > > > No, it is up to the community to discuss after their review
> > > > >
> > > > > results.
> > > > > > > > >
> > > > > > > > > пт, 28 сент. 2018 г. в 11:09, Vladimir Ozerov <
> > > > >
> > > > > vozerov@gridgain.com
> > > > > > > :
> > > > > > > > >
> > > > > > > > > > Dmitriy,
> > > > > > > > > >
> > > > > > > > > > Did I read your words correctly that it is up to
> > implementor
> > > >
> > > > of a
> > > > > > > > single
> > > > > > > > > > feature to decide whether release of all other features
> and
> > > >
> > > > fixes
> > > > > > to
> > > > > > > be
> > > > > > > > > > delayed?
> > > > > > > > > >
> > > > > > > > > > пт, 28 сент. 2018 г. в 11:00, Dmitriy Pavlov <
> > > > > >
> > > > > > dpavlov.spb@gmail.com
> > > > > > > > :
> > > > > > > > > >
> > > > > > > > > > > My point we can wait a bit for services because
> > > > > > > > > > > 1 we are open-minded and we don't have outside
> pressure
> > to
> > > >
> > > > do
> > > > > > > > release
> > > > > > > > > in
> > > > > > > > > > > October
> > > > > > > > > > > 2 and services it is not some new feature, which
> > suddenly
> > > > > >
> > > > > > appeared
> > > > > > > > in
> > > > > > > > > > > autumn, it is a well known and important feature.
> > > > > > > > > > >
> > > > > > > > > > > So it is up to Vyacheslav, Anton and Nikolay to decide.
> > > > > > > > > > >
> > > > > > > > > > > Decisions can be services are not ready/ready to merge
> > only
> > > >
> > > > to
> > > > > > > > > > master/ready
> > > > > > > > > > > to merge to master and to 2.7.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > пт, 28 сент. 2018 г. в 10:46, Vladimir Ozerov <
> > > > > > >
> > > > > > > vozerov@gridgain.com
> > > > > > > > > :
> > > > > > > > > > >
> > > > > > > > > > > > Dmitry,
> > > > > > > > > > > >
> > > > > > > > > > > > Community agreement was to perform the release in
> > October.
> > > >
> > > > Of
> > > > > > > > course
> > > > > > > > > we
> > > > > > > > > > > can
> > > > > > > > > > > > wait a bit for services. Then we wait a bit for other
> > cool
> > > > > > >
> > > > > > > features
> > > > > > > > > > ready
> > > > > > > > > > > > by that time, then again and again, and release will
> > never
> > > > > > >
> > > > > > > happen.
> > > > > > > > > And
> > > > > > > > > > > > while we are waiting for new features to come,
> already
> > > > > >
> > > > > > completerd
> > > > > > > > > > > features
> > > > > > > > > > > > cannot be used by anyone.
> > > > > > > > > > > >
> > > > > > > > > > > > This is why we have an agreement that if feature is
> not
> > > > >
> > > > > ready,
> > > > > > it
> > > > > > > > > > should
> > > > > > > > > > > be
> > > > > > > > > > > > moved to future release, instead of shifting release.
> > The
> > > > >
> > > > > sole
> > > > > > > > reason
> > > > > > > > > > to
> > > > > > > > > > > > have strict dates when decisions are made is to let
> > release
> > > > > > >
> > > > > > > happen.
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > On Fri, Sep 28, 2018 at 2:22 AM Dmitriy Pavlov <
> > > > > > > > >
> > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > > Vladimir, I'm not searching for enemy, and not
> > fighting
> > > > >
> > > > > with
> > > > > > > > you.
> > > > > > > > > > I'm
> > > > > > > > > > > > not
> > > > > > > > > > > > > happy about cases when we are hurrying.
> > > > > > > > > > > > >
> > > > > > > > > > > > > We can't fix test, fill ticket details, can't wait
> > for
> > > > > > > > >
> > > > > > > > > contributions
> > > > > > > > > > to
> > > > > > > > > > > > > finish their tasks. It is not best idea to use
> > > >
> > > > experience
> > > > > > from
> > > > > > > > > > > > commercial
> > > > > > > > > > > > > companies in open source. Are there any pressure
> > outside
> > > > > > > >
> > > > > > > > community?
> > > > > > > > > > Did
> > > > > > > > > > > > > someone promised rest of features to be released at
> > 30
> > > > > > >
> > > > > > > September?
> > > > > > > > > > > > >
> > > > > > > > > > > > > Let's remember principle do-orcracy, power of those
> > who
> > > >
> > > > do.
> > > > > > If
> > > > > > > > > > > contribor
> > > > > > > > > > > > > does change and reviewer does review, let's give
> > right of
> > > > > > >
> > > > > > > making
> > > > > > > > > > > decision
> > > > > > > > > > > > > to them, but not to some closed club of people who
> > > > >
> > > > > privately
> > > > > > > > > discuss
> > > > > > > > > > > > > something.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Sincerely
> > > > > > > > > > > > > Dmitriy Pavlov
> > > > > > > > > > > > >
> > > > > > > > > > > > > чт, 27 сент. 2018 г., 23:42 Vyacheslav Daradur <
> > > > > > > > >
> > > > > > > > > daradurvs@gmail.com
> > > > > > > > > > > :
> > > > > > > > > > > > >
> > > > > > > > > > > > > > Hi Igniters!
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > As I have written about Service Grid before [1]
> I'm
> > > > > > >
> > > > > > > finalizing
> > > > > > > > > the
> > > > > > > > > > > > > > solution to be sure that implementation is
> > reliable.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > About including it in 2.7, if we talk that code
> > freeze
> > > > > > >
> > > > > > > tomorrow
> > > > > > > > > > then
> > > > > > > > > > > > > > the solution is not ready to merge yet.
> > > > > > > > > > > > > > I hope that prereviewers Anton Vinogradov and
> > Nikolay
> > > > > >
> > > > > > Izhikov
> > > > > > > > > will
> > > > > > > > > > be
> > > > > > > > > > > > > > able to answer if solution out of scope or not
> in a
> > > > >
> > > > > couple
> > > > > > of
> > > > > > > > > days.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > [1]
> > > > > > > > > > > > > >
> > > >
> > > >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-release-td34076.html#a34485
> > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 11:14 PM Dmitriy Pavlov <
> > > > > > > > > > >
> > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > >
> > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Yes, I agree, NPE during WAL flush is
> definitely
> > a
> > > > > >
> > > > > > blocker.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > It is strange why the current test set did not
> > fail
> > > > >
> > > > > after
> > > > > > > > > commit.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 21:45, Andrey Kuznetsov
> <
> > > > > > > > > >
> > > > > > > > > > stkuzma@gmail.com
> > > > > > > > > > > > :
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Igniters,
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > I've bumped into a new bug in WAL manager
> > recently,
> > > > >
> > > > > see
> > > > > > > > [1].
> > > > > > > > > It
> > > > > > > > > > > > looks
> > > > > > > > > > > > > > > > critical enough, and can be a good candidate
> > for
> > > > >
> > > > > fixing
> > > > > > > > > before
> > > > > > > > > > > 2.7
> > > > > > > > > > > > > > release.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Do you agree?
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > [1]
> > > > >
> > > > > https://issues.apache.org/jira/browse/IGNITE-9731
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 19:45, Dmitriy Pavlov
> <
> > > > > > > > > > > >
> > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > I need Vhyacheslav's opinion to be
> absolutely
> > > >
> > > > sure
> > > > > > what
> > > > > > > > > > status
> > > > > > > > > > > is
> > > > > > > > > > > > > > now.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > We never committed to dates of release, as
> > well.
> > > >
> > > > I
> > > > > > > don't
> > > > > > > > > > quite
> > > > > > > > > > > > > > understand
> > > > > > > > > > > > > > > > > what can mean 'the community committed to
> > > > > > >
> > > > > > > doing/releasing
> > > > > > > > > > > > > something'.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > About SG, I also concerned why such a big
> > feature
> > > > >
> > > > > has
> > > > > > > > > quite a
> > > > > > > > > > > few
> > > > > > > > > > > > > > > > > discussions on the list. But it is another
> > story.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 19:33, Vladimir
> > Ozerov <
> > > > > > > > > > > > >
> > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Folks,
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Please stop looking for enemies
> everywhere.
> > > >
> > > > Just
> > > > > > went
> > > > > > > > > > through
> > > > > > > > > > > > > this
> > > > > > > > > > > > > > > > thread
> > > > > > > > > > > > > > > > > > and search for "service" word.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 7:30 PM Denis
> > Magda <
> > > > > > > > > > >
> > > > > > > > > > > dmagda@apache.org
> > > > > > > > > > > > >
> > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > Denis, as PMC Chair, could you please
> > > >
> > > > control,
> > > > > > > that
> > > > > > > > > > > Service
> > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > > > > > inclusion/exclusion is discussed
> > properly
> > > > > > >
> > > > > > > according
> > > > > > > > to
> > > > > > > > > > the
> > > > > > > > > > > > > > Apache
> > > > > > > > > > > > > > > > Way.
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > It's fine when committers/contributors
> > have
> > > > > >
> > > > > > private
> > > > > > > > > > > > discussions
> > > > > > > > > > > > > > > > related
> > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > > a feature they've been working on. Not
> > > > >
> > > > > everything
> > > > > > > > should
> > > > > > > > > > go
> > > > > > > > > > > > > > through
> > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > dev
> > > > > > > > > > > > > > > > > > > list. Otherwise, it will be inundated.
> > > >
> > > > However,
> > > > > > > > agree,
> > > > > > > > > > that
> > > > > > > > > > > > > > > > > architectural
> > > > > > > > > > > > > > > > > > > and release decisions need to be done
> > > >
> > > > publicly.
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > Speaking about Service Grid, there was
> a
> > > > > >
> > > > > > discussion
> > > > > > > > > where
> > > > > > > > > > I
> > > > > > > > > > > > saw
> > > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > was
> > > > > > > > > > > > > > > > > > > questionable whether it gets added to
> the
> > > > >
> > > > > release
> > > > > > or
> > > > > > > > > not.
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > *Vladislav*, could you please shed some
> > light
> > > >
> > > > on
> > > > > > the
> > > > > > > > > > current
> > > > > > > > > > > > > > status of
> > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > service grid?
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 9:12 AM Dmitriy
> > > >
> > > > Pavlov <
> > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > Ok, let's wait for feedback from SG
> > > > > > > > > >
> > > > > > > > > > Author(s)/Reviewer(s)
> > > > > > > > > > > > > > first. If
> > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > > > > > not ready, ok. But I thought it is
> > almost
> > > > >
> > > > > done.
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > I apologize if I missed some
> > discussion (it
> > > > >
> > > > > can
> > > > > > > > > happen),
> > > > > > > > > > > but
> > > > > > > > > > > > > > > > > > > > According to the statement "our
> current
> > > > > >
> > > > > > agreement"
> > > > > > > > > > > > > > > > > > > > I can suspect some members are making
> > some
> > > > >
> > > > > sort
> > > > > > of
> > > > > > > > > > private
> > > > > > > > > > > > > > > > agreements,
> > > > > > > > > > > > > > > > > > > and
> > > > > > > > > > > > > > > > > > > > do not to discuss it on the list.
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > Let's build consensus here first, and
> > then
> > > > >
> > > > > name
> > > > > > an
> > > > > > > > > > > > agreement.
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > Denis, as PMC Chair, could you please
> > > >
> > > > control,
> > > > > > > that
> > > > > > > > > > > Service
> > > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > > > > > inclusion/exclusion is discussed
> > properly
> > > > > > >
> > > > > > > according
> > > > > > > > to
> > > > > > > > > > the
> > > > > > > > > > > > > > Apache
> > > > > > > > > > > > > > > > Way.
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 18:55,
> Vladimir
> > > >
> > > > Ozerov
> > > > > <
> > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > This is an outcome of current state
> > of
> > > > >
> > > > > Service
> > > > > > > > Grid -
> > > > > > > > > > it
> > > > > > > > > > > is
> > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > > ready.
> > > > > > > > > > > > > > > > > > > We
> > > > > > > > > > > > > > > > > > > > > never committed to have it to 2.7.
> > Our goal
> > > > >
> > > > > was
> > > > > > > to
> > > > > > > > > try
> > > > > > > > > > to
> > > > > > > > > > > > > > include
> > > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > into
> > > > > > > > > > > > > > > > > > > > > 2.7.
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 6:48 PM
> > Dmitriy
> > > > >
> > > > > Pavlov
> > > > > > <
> > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > Could you please provide a
> > reference to
> > > > >
> > > > > some
> > > > > > > > > thread?
> > > > > > > > > > > > > > Probably I
> > > > > > > > > > > > > > > > > > > missed
> > > > > > > > > > > > > > > > > > > > > it.
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 18:46,
> > Vladimir
> > > > > >
> > > > > > Ozerov <
> > > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > Our current agreement is that
> > Service
> > > > >
> > > > > Grid
> > > > > > is
> > > > > > > > out
> > > > > > > > > > of
> > > > > > > > > > > > > scope.
> > > > > > > > > > > > > > > > This
> > > > > > > > > > > > > > > > > > > is a
> > > > > > > > > > > > > > > > > > > > > > huge
> > > > > > > > > > > > > > > > > > > > > > > feature, which hasn't entered
> > review
> > > > >
> > > > > stage
> > > > > > so
> > > > > > > > > far,
> > > > > > > > > > We
> > > > > > > > > > > > > will
> > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > > > > able to
> > > > > > > > > > > > > > > > > > > > > > > review/fix/test it properly.
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 6:32 PM
> > Dmitriy
> > > > > > >
> > > > > > > Pavlov
> > > > > > > > <
> > > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > I agree, and I prefer four
> > weeks for
> > > > > > > > > >
> > > > > > > > > > stabilization*
> > > > > > > > > > > > (1
> > > > > > > > > > > > > > Oct -
> > > > > > > > > > > > > > > > 29
> > > > > > > > > > > > > > > > > > > Oct)
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > Do I understand it correctly:
> > Service
> > > > > >
> > > > > > Grid
> > > > > > > is
> > > > > > > > > > still
> > > > > > > > > > > > in
> > > > > > > > > > > > > > scope,
> > > > > > > > > > > > > > > > > > > isn't
> > > > > > > > > > > > > > > > > > > > > > it? I
> > > > > > > > > > > > > > > > > > > > > > > > find it very important.
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 18:28,
> > Nikolay
> > > > > > > >
> > > > > > > > Izhikov <
> > > > > > > > > > > > > > > > > > > nizhikov@apache.org
> > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > Hello, Vova.
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > Thank you for clear release
> > status.
> > > > > > > > > > > > > > > > > > > > > > > > > I'm +1 for your proposal.
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г., 18:25
> > Alexey
> > > > > > > >
> > > > > > > > Kuznetsov
> > > > > > > > > <
> > > > > > > > > > > > > > > > > > > > > akuznetsov@apache.org
> > > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > Vova,
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > Huge +1 to do a
> > stabilization.
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > > > > > > > > > > > Alexey Kuznetsov
> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > Best regards,
> > > > > > > > > > > > > > > > Andrey Kuznetsov.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > --
> > > > > > > > > > > > > > Best Regards, Vyacheslav D.
> > > > > > > > > > > > > >
> >
>
Re: Apache Ignite 2.7 release
Posted by Denis Magda <dm...@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 <ni...@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 <ds...@apache.org>:
> >
> > > Dmitriy,
> > >
> > > We agreed in the beginning of this thread that Service Grid changes
> are not
> > > going to make the release because the community still did not approve
> the
> > > design. Nothing has changed since. I have not seen any design
> discussions.
> > > At this point, I have no confidence that the Service Grid changes will
> make
> > > it into the 2.8 release. The 2.7 release seems out of question
> altogether.
> > >
> > > Also, Nikolay is a release manager. We should let him drive the
> release. To
> > > my knowledge, he is doing a great job and the release is going
> according to
> > > the schedule he proposed.
> > >
> > > D.
> > >
> > > On Fri, Sep 28, 2018 at 4:31 AM Dmitriy Pavlov <dp...@gmail.com>
> > > wrote:
> > >
> > > > Hi Dmitriy, Vladimir,
> > > >
> > > > I suggest we stop this nonsense with release dates-pushing because of
> > >
> > > some
> > > > open question.
> > > >
> > > > Just because you disagreed with any include/exclude something into
> scope,
> > > > does not mean that whole community disagreed.
> > > >
> > > > If folks will start a separate discussion with results of the
> review, I
> > >
> > > see
> > > > no reasons to reject their contribution, even if we need to revisit
> our
> > > > agreements and wait for a couple of days more.
> > > >
> > > > Am I missing some reason why dates are so fundamentally important to
> you?
> > > >
> > > > Sincerely,
> > > > Dmitriy Pavlov
> > > >
> > > > пт, 28 сент. 2018 г. в 12:20, Dmitriy Setrakyan <
> dsetrakyan@apache.org>:
> > > >
> > > > > If services is not ready, which it is not, then we should include
> them
> > > >
> > > > into
> > > > > the next release. There is no need to force them into 2.7. I
> suggest we
> > > > > move according to the schedule we all agreed on.
> > > > >
> > > > > D.
> > > > >
> > > > > On Fri, Sep 28, 2018 at 1:22 AM Dmitriy Pavlov <
> dpavlov.spb@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Yes, so correct statement is "community did not make any
> decisions
> > > >
> > > > about
> > > > > > services not go to 2.7/ services are out of scope".
> > > > > >
> > > > > > If so, please forgive me my confusion.
> > > > > >
> > > > > > пт, 28 сент. 2018 г. в 11:19, Vladimir Ozerov <
> vozerov@gridgain.com
> > > >
> > > > :
> > > > > >
> > > > > > > Exactly. So correct statement is “it is up to *community* to
> decide
> > > > > >
> > > > > > whether
> > > > > > > something goes to 2.7”.
> > > > > > >
> > > > > > > пт, 28 сент. 2018 г. в 11:11, Dmitriy Pavlov <
> > >
> > > dpavlov.spb@gmail.com
> > > > > :
> > > > > > >
> > > > > > > > No, it is up to the community to discuss after their review
> > > >
> > > > results.
> > > > > > > >
> > > > > > > > пт, 28 сент. 2018 г. в 11:09, Vladimir Ozerov <
> > > >
> > > > vozerov@gridgain.com
> > > > > > :
> > > > > > > >
> > > > > > > > > Dmitriy,
> > > > > > > > >
> > > > > > > > > Did I read your words correctly that it is up to
> implementor
> > >
> > > of a
> > > > > > > single
> > > > > > > > > feature to decide whether release of all other features and
> > >
> > > fixes
> > > > > to
> > > > > > be
> > > > > > > > > delayed?
> > > > > > > > >
> > > > > > > > > пт, 28 сент. 2018 г. в 11:00, Dmitriy Pavlov <
> > > > >
> > > > > dpavlov.spb@gmail.com
> > > > > > > :
> > > > > > > > >
> > > > > > > > > > My point we can wait a bit for services because
> > > > > > > > > > 1 we are open-minded and we don't have outside pressure
> to
> > >
> > > do
> > > > > > > release
> > > > > > > > in
> > > > > > > > > > October
> > > > > > > > > > 2 and services it is not some new feature, which
> suddenly
> > > > >
> > > > > appeared
> > > > > > > in
> > > > > > > > > > autumn, it is a well known and important feature.
> > > > > > > > > >
> > > > > > > > > > So it is up to Vyacheslav, Anton and Nikolay to decide.
> > > > > > > > > >
> > > > > > > > > > Decisions can be services are not ready/ready to merge
> only
> > >
> > > to
> > > > > > > > > master/ready
> > > > > > > > > > to merge to master and to 2.7.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > пт, 28 сент. 2018 г. в 10:46, Vladimir Ozerov <
> > > > > >
> > > > > > vozerov@gridgain.com
> > > > > > > > :
> > > > > > > > > >
> > > > > > > > > > > Dmitry,
> > > > > > > > > > >
> > > > > > > > > > > Community agreement was to perform the release in
> October.
> > >
> > > Of
> > > > > > > course
> > > > > > > > we
> > > > > > > > > > can
> > > > > > > > > > > wait a bit for services. Then we wait a bit for other
> cool
> > > > > >
> > > > > > features
> > > > > > > > > ready
> > > > > > > > > > > by that time, then again and again, and release will
> never
> > > > > >
> > > > > > happen.
> > > > > > > > And
> > > > > > > > > > > while we are waiting for new features to come, already
> > > > >
> > > > > completerd
> > > > > > > > > > features
> > > > > > > > > > > cannot be used by anyone.
> > > > > > > > > > >
> > > > > > > > > > > This is why we have an agreement that if feature is not
> > > >
> > > > ready,
> > > > > it
> > > > > > > > > should
> > > > > > > > > > be
> > > > > > > > > > > moved to future release, instead of shifting release.
> The
> > > >
> > > > sole
> > > > > > > reason
> > > > > > > > > to
> > > > > > > > > > > have strict dates when decisions are made is to let
> release
> > > > > >
> > > > > > happen.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > On Fri, Sep 28, 2018 at 2:22 AM Dmitriy Pavlov <
> > > > > > > >
> > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > > Vladimir, I'm not searching for enemy, and not
> fighting
> > > >
> > > > with
> > > > > > > you.
> > > > > > > > > I'm
> > > > > > > > > > > not
> > > > > > > > > > > > happy about cases when we are hurrying.
> > > > > > > > > > > >
> > > > > > > > > > > > We can't fix test, fill ticket details, can't wait
> for
> > > > > > > >
> > > > > > > > contributions
> > > > > > > > > to
> > > > > > > > > > > > finish their tasks. It is not best idea to use
> > >
> > > experience
> > > > > from
> > > > > > > > > > > commercial
> > > > > > > > > > > > companies in open source. Are there any pressure
> outside
> > > > > > >
> > > > > > > community?
> > > > > > > > > Did
> > > > > > > > > > > > someone promised rest of features to be released at
> 30
> > > > > >
> > > > > > September?
> > > > > > > > > > > >
> > > > > > > > > > > > Let's remember principle do-orcracy, power of those
> who
> > >
> > > do.
> > > > > If
> > > > > > > > > > contribor
> > > > > > > > > > > > does change and reviewer does review, let's give
> right of
> > > > > >
> > > > > > making
> > > > > > > > > > decision
> > > > > > > > > > > > to them, but not to some closed club of people who
> > > >
> > > > privately
> > > > > > > > discuss
> > > > > > > > > > > > something.
> > > > > > > > > > > >
> > > > > > > > > > > > Sincerely
> > > > > > > > > > > > Dmitriy Pavlov
> > > > > > > > > > > >
> > > > > > > > > > > > чт, 27 сент. 2018 г., 23:42 Vyacheslav Daradur <
> > > > > > > >
> > > > > > > > daradurvs@gmail.com
> > > > > > > > > > :
> > > > > > > > > > > >
> > > > > > > > > > > > > Hi Igniters!
> > > > > > > > > > > > >
> > > > > > > > > > > > > As I have written about Service Grid before [1] I'm
> > > > > >
> > > > > > finalizing
> > > > > > > > the
> > > > > > > > > > > > > solution to be sure that implementation is
> reliable.
> > > > > > > > > > > > >
> > > > > > > > > > > > > About including it in 2.7, if we talk that code
> freeze
> > > > > >
> > > > > > tomorrow
> > > > > > > > > then
> > > > > > > > > > > > > the solution is not ready to merge yet.
> > > > > > > > > > > > > I hope that prereviewers Anton Vinogradov and
> Nikolay
> > > > >
> > > > > Izhikov
> > > > > > > > will
> > > > > > > > > be
> > > > > > > > > > > > > able to answer if solution out of scope or not in a
> > > >
> > > > couple
> > > > > of
> > > > > > > > days.
> > > > > > > > > > > > >
> > > > > > > > > > > > > [1]
> > > > > > > > > > > > >
> > >
> > >
> http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-release-td34076.html#a34485
> > > > > > > > > > > > > On Thu, Sep 27, 2018 at 11:14 PM Dmitriy Pavlov <
> > > > > > > > > >
> > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > >
> > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Yes, I agree, NPE during WAL flush is definitely
> a
> > > > >
> > > > > blocker.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > It is strange why the current test set did not
> fail
> > > >
> > > > after
> > > > > > > > commit.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 21:45, Andrey Kuznetsov <
> > > > > > > > >
> > > > > > > > > stkuzma@gmail.com
> > > > > > > > > > > :
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Igniters,
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > I've bumped into a new bug in WAL manager
> recently,
> > > >
> > > > see
> > > > > > > [1].
> > > > > > > > It
> > > > > > > > > > > looks
> > > > > > > > > > > > > > > critical enough, and can be a good candidate
> for
> > > >
> > > > fixing
> > > > > > > > before
> > > > > > > > > > 2.7
> > > > > > > > > > > > > release.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Do you agree?
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > [1]
> > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-9731
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 19:45, Dmitriy Pavlov <
> > > > > > > > > > >
> > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > :
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > I need Vhyacheslav's opinion to be absolutely
> > >
> > > sure
> > > > > what
> > > > > > > > > status
> > > > > > > > > > is
> > > > > > > > > > > > > now.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > We never committed to dates of release, as
> well.
> > >
> > > I
> > > > > > don't
> > > > > > > > > quite
> > > > > > > > > > > > > understand
> > > > > > > > > > > > > > > > what can mean 'the community committed to
> > > > > >
> > > > > > doing/releasing
> > > > > > > > > > > > something'.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > About SG, I also concerned why such a big
> feature
> > > >
> > > > has
> > > > > > > > quite a
> > > > > > > > > > few
> > > > > > > > > > > > > > > > discussions on the list. But it is another
> story.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 19:33, Vladimir
> Ozerov <
> > > > > > > > > > > >
> > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Folks,
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Please stop looking for enemies everywhere.
> > >
> > > Just
> > > > > went
> > > > > > > > > through
> > > > > > > > > > > > this
> > > > > > > > > > > > > > > thread
> > > > > > > > > > > > > > > > > and search for "service" word.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 7:30 PM Denis
> Magda <
> > > > > > > > > >
> > > > > > > > > > dmagda@apache.org
> > > > > > > > > > > >
> > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > Denis, as PMC Chair, could you please
> > >
> > > control,
> > > > > > that
> > > > > > > > > > Service
> > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > > > > inclusion/exclusion is discussed
> properly
> > > > > >
> > > > > > according
> > > > > > > to
> > > > > > > > > the
> > > > > > > > > > > > > Apache
> > > > > > > > > > > > > > > Way.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > It's fine when committers/contributors
> have
> > > > >
> > > > > private
> > > > > > > > > > > discussions
> > > > > > > > > > > > > > > related
> > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > a feature they've been working on. Not
> > > >
> > > > everything
> > > > > > > should
> > > > > > > > > go
> > > > > > > > > > > > > through
> > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > dev
> > > > > > > > > > > > > > > > > > list. Otherwise, it will be inundated.
> > >
> > > However,
> > > > > > > agree,
> > > > > > > > > that
> > > > > > > > > > > > > > > > architectural
> > > > > > > > > > > > > > > > > > and release decisions need to be done
> > >
> > > publicly.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Speaking about Service Grid, there was a
> > > > >
> > > > > discussion
> > > > > > > > where
> > > > > > > > > I
> > > > > > > > > > > saw
> > > > > > > > > > > > > that
> > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > was
> > > > > > > > > > > > > > > > > > questionable whether it gets added to the
> > > >
> > > > release
> > > > > or
> > > > > > > > not.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > *Vladislav*, could you please shed some
> light
> > >
> > > on
> > > > > the
> > > > > > > > > current
> > > > > > > > > > > > > status of
> > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > service grid?
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 9:12 AM Dmitriy
> > >
> > > Pavlov <
> > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > Ok, let's wait for feedback from SG
> > > > > > > > >
> > > > > > > > > Author(s)/Reviewer(s)
> > > > > > > > > > > > > first. If
> > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > > > > not ready, ok. But I thought it is
> almost
> > > >
> > > > done.
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > I apologize if I missed some
> discussion (it
> > > >
> > > > can
> > > > > > > > happen),
> > > > > > > > > > but
> > > > > > > > > > > > > > > > > > > According to the statement "our current
> > > > >
> > > > > agreement"
> > > > > > > > > > > > > > > > > > > I can suspect some members are making
> some
> > > >
> > > > sort
> > > > > of
> > > > > > > > > private
> > > > > > > > > > > > > > > agreements,
> > > > > > > > > > > > > > > > > > and
> > > > > > > > > > > > > > > > > > > do not to discuss it on the list.
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > Let's build consensus here first, and
> then
> > > >
> > > > name
> > > > > an
> > > > > > > > > > > agreement.
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > Denis, as PMC Chair, could you please
> > >
> > > control,
> > > > > > that
> > > > > > > > > > Service
> > > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > > > > inclusion/exclusion is discussed
> properly
> > > > > >
> > > > > > according
> > > > > > > to
> > > > > > > > > the
> > > > > > > > > > > > > Apache
> > > > > > > > > > > > > > > Way.
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 18:55, Vladimir
> > >
> > > Ozerov
> > > > <
> > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > This is an outcome of current state
> of
> > > >
> > > > Service
> > > > > > > Grid -
> > > > > > > > > it
> > > > > > > > > > is
> > > > > > > > > > > > not
> > > > > > > > > > > > > > > > ready.
> > > > > > > > > > > > > > > > > > We
> > > > > > > > > > > > > > > > > > > > never committed to have it to 2.7.
> Our goal
> > > >
> > > > was
> > > > > > to
> > > > > > > > try
> > > > > > > > > to
> > > > > > > > > > > > > include
> > > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > into
> > > > > > > > > > > > > > > > > > > > 2.7.
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 6:48 PM
> Dmitriy
> > > >
> > > > Pavlov
> > > > > <
> > > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > Could you please provide a
> reference to
> > > >
> > > > some
> > > > > > > > thread?
> > > > > > > > > > > > > Probably I
> > > > > > > > > > > > > > > > > > missed
> > > > > > > > > > > > > > > > > > > > it.
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 18:46,
> Vladimir
> > > > >
> > > > > Ozerov <
> > > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > Our current agreement is that
> Service
> > > >
> > > > Grid
> > > > > is
> > > > > > > out
> > > > > > > > > of
> > > > > > > > > > > > scope.
> > > > > > > > > > > > > > > This
> > > > > > > > > > > > > > > > > > is a
> > > > > > > > > > > > > > > > > > > > > huge
> > > > > > > > > > > > > > > > > > > > > > feature, which hasn't entered
> review
> > > >
> > > > stage
> > > > > so
> > > > > > > > far,
> > > > > > > > > We
> > > > > > > > > > > > will
> > > > > > > > > > > > > not
> > > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > > > able to
> > > > > > > > > > > > > > > > > > > > > > review/fix/test it properly.
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 6:32 PM
> Dmitriy
> > > > > >
> > > > > > Pavlov
> > > > > > > <
> > > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > I agree, and I prefer four
> weeks for
> > > > > > > > >
> > > > > > > > > stabilization*
> > > > > > > > > > > (1
> > > > > > > > > > > > > Oct -
> > > > > > > > > > > > > > > 29
> > > > > > > > > > > > > > > > > > Oct)
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > Do I understand it correctly:
> Service
> > > > >
> > > > > Grid
> > > > > > is
> > > > > > > > > still
> > > > > > > > > > > in
> > > > > > > > > > > > > scope,
> > > > > > > > > > > > > > > > > > isn't
> > > > > > > > > > > > > > > > > > > > > it? I
> > > > > > > > > > > > > > > > > > > > > > > find it very important.
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 18:28,
> Nikolay
> > > > > > >
> > > > > > > Izhikov <
> > > > > > > > > > > > > > > > > > nizhikov@apache.org
> > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > Hello, Vova.
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > Thank you for clear release
> status.
> > > > > > > > > > > > > > > > > > > > > > > > I'm +1 for your proposal.
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г., 18:25
> Alexey
> > > > > > >
> > > > > > > Kuznetsov
> > > > > > > > <
> > > > > > > > > > > > > > > > > > > > akuznetsov@apache.org
> > > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > Vova,
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > Huge +1 to do a
> stabilization.
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > > > > > > > > > > Alexey Kuznetsov
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > Best regards,
> > > > > > > > > > > > > > > Andrey Kuznetsov.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > --
> > > > > > > > > > > > > Best Regards, Vyacheslav D.
> > > > > > > > > > > > >
>
Re: Apache Ignite 2.7 release
Posted by Nikolay Izhikov <ni...@apache.org>.
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 <ds...@apache.org>:
>
> > Dmitriy,
> >
> > We agreed in the beginning of this thread that Service Grid changes are not
> > going to make the release because the community still did not approve the
> > design. Nothing has changed since. I have not seen any design discussions.
> > At this point, I have no confidence that the Service Grid changes will make
> > it into the 2.8 release. The 2.7 release seems out of question altogether.
> >
> > Also, Nikolay is a release manager. We should let him drive the release. To
> > my knowledge, he is doing a great job and the release is going according to
> > the schedule he proposed.
> >
> > D.
> >
> > On Fri, Sep 28, 2018 at 4:31 AM Dmitriy Pavlov <dp...@gmail.com>
> > wrote:
> >
> > > Hi Dmitriy, Vladimir,
> > >
> > > I suggest we stop this nonsense with release dates-pushing because of
> >
> > some
> > > open question.
> > >
> > > Just because you disagreed with any include/exclude something into scope,
> > > does not mean that whole community disagreed.
> > >
> > > If folks will start a separate discussion with results of the review, I
> >
> > see
> > > no reasons to reject their contribution, even if we need to revisit our
> > > agreements and wait for a couple of days more.
> > >
> > > Am I missing some reason why dates are so fundamentally important to you?
> > >
> > > Sincerely,
> > > Dmitriy Pavlov
> > >
> > > пт, 28 сент. 2018 г. в 12:20, Dmitriy Setrakyan <ds...@apache.org>:
> > >
> > > > If services is not ready, which it is not, then we should include them
> > >
> > > into
> > > > the next release. There is no need to force them into 2.7. I suggest we
> > > > move according to the schedule we all agreed on.
> > > >
> > > > D.
> > > >
> > > > On Fri, Sep 28, 2018 at 1:22 AM Dmitriy Pavlov <dp...@gmail.com>
> > > > wrote:
> > > >
> > > > > Yes, so correct statement is "community did not make any decisions
> > >
> > > about
> > > > > services not go to 2.7/ services are out of scope".
> > > > >
> > > > > If so, please forgive me my confusion.
> > > > >
> > > > > пт, 28 сент. 2018 г. в 11:19, Vladimir Ozerov <vozerov@gridgain.com
> > >
> > > :
> > > > >
> > > > > > Exactly. So correct statement is “it is up to *community* to decide
> > > > >
> > > > > whether
> > > > > > something goes to 2.7”.
> > > > > >
> > > > > > пт, 28 сент. 2018 г. в 11:11, Dmitriy Pavlov <
> >
> > dpavlov.spb@gmail.com
> > > > :
> > > > > >
> > > > > > > No, it is up to the community to discuss after their review
> > >
> > > results.
> > > > > > >
> > > > > > > пт, 28 сент. 2018 г. в 11:09, Vladimir Ozerov <
> > >
> > > vozerov@gridgain.com
> > > > > :
> > > > > > >
> > > > > > > > Dmitriy,
> > > > > > > >
> > > > > > > > Did I read your words correctly that it is up to implementor
> >
> > of a
> > > > > > single
> > > > > > > > feature to decide whether release of all other features and
> >
> > fixes
> > > > to
> > > > > be
> > > > > > > > delayed?
> > > > > > > >
> > > > > > > > пт, 28 сент. 2018 г. в 11:00, Dmitriy Pavlov <
> > > >
> > > > dpavlov.spb@gmail.com
> > > > > > :
> > > > > > > >
> > > > > > > > > My point we can wait a bit for services because
> > > > > > > > > 1 we are open-minded and we don't have outside pressure to
> >
> > do
> > > > > > release
> > > > > > > in
> > > > > > > > > October
> > > > > > > > > 2 and services it is not some new feature, which suddenly
> > > >
> > > > appeared
> > > > > > in
> > > > > > > > > autumn, it is a well known and important feature.
> > > > > > > > >
> > > > > > > > > So it is up to Vyacheslav, Anton and Nikolay to decide.
> > > > > > > > >
> > > > > > > > > Decisions can be services are not ready/ready to merge only
> >
> > to
> > > > > > > > master/ready
> > > > > > > > > to merge to master and to 2.7.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > пт, 28 сент. 2018 г. в 10:46, Vladimir Ozerov <
> > > > >
> > > > > vozerov@gridgain.com
> > > > > > > :
> > > > > > > > >
> > > > > > > > > > Dmitry,
> > > > > > > > > >
> > > > > > > > > > Community agreement was to perform the release in October.
> >
> > Of
> > > > > > course
> > > > > > > we
> > > > > > > > > can
> > > > > > > > > > wait a bit for services. Then we wait a bit for other cool
> > > > >
> > > > > features
> > > > > > > > ready
> > > > > > > > > > by that time, then again and again, and release will never
> > > > >
> > > > > happen.
> > > > > > > And
> > > > > > > > > > while we are waiting for new features to come, already
> > > >
> > > > completerd
> > > > > > > > > features
> > > > > > > > > > cannot be used by anyone.
> > > > > > > > > >
> > > > > > > > > > This is why we have an agreement that if feature is not
> > >
> > > ready,
> > > > it
> > > > > > > > should
> > > > > > > > > be
> > > > > > > > > > moved to future release, instead of shifting release. The
> > >
> > > sole
> > > > > > reason
> > > > > > > > to
> > > > > > > > > > have strict dates when decisions are made is to let release
> > > > >
> > > > > happen.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Fri, Sep 28, 2018 at 2:22 AM Dmitriy Pavlov <
> > > > > > >
> > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Vladimir, I'm not searching for enemy, and not fighting
> > >
> > > with
> > > > > > you.
> > > > > > > > I'm
> > > > > > > > > > not
> > > > > > > > > > > happy about cases when we are hurrying.
> > > > > > > > > > >
> > > > > > > > > > > We can't fix test, fill ticket details, can't wait for
> > > > > > >
> > > > > > > contributions
> > > > > > > > to
> > > > > > > > > > > finish their tasks. It is not best idea to use
> >
> > experience
> > > > from
> > > > > > > > > > commercial
> > > > > > > > > > > companies in open source. Are there any pressure outside
> > > > > >
> > > > > > community?
> > > > > > > > Did
> > > > > > > > > > > someone promised rest of features to be released at 30
> > > > >
> > > > > September?
> > > > > > > > > > >
> > > > > > > > > > > Let's remember principle do-orcracy, power of those who
> >
> > do.
> > > > If
> > > > > > > > > contribor
> > > > > > > > > > > does change and reviewer does review, let's give right of
> > > > >
> > > > > making
> > > > > > > > > decision
> > > > > > > > > > > to them, but not to some closed club of people who
> > >
> > > privately
> > > > > > > discuss
> > > > > > > > > > > something.
> > > > > > > > > > >
> > > > > > > > > > > Sincerely
> > > > > > > > > > > Dmitriy Pavlov
> > > > > > > > > > >
> > > > > > > > > > > чт, 27 сент. 2018 г., 23:42 Vyacheslav Daradur <
> > > > > > >
> > > > > > > daradurvs@gmail.com
> > > > > > > > > :
> > > > > > > > > > >
> > > > > > > > > > > > Hi Igniters!
> > > > > > > > > > > >
> > > > > > > > > > > > As I have written about Service Grid before [1] I'm
> > > > >
> > > > > finalizing
> > > > > > > the
> > > > > > > > > > > > solution to be sure that implementation is reliable.
> > > > > > > > > > > >
> > > > > > > > > > > > About including it in 2.7, if we talk that code freeze
> > > > >
> > > > > tomorrow
> > > > > > > > then
> > > > > > > > > > > > the solution is not ready to merge yet.
> > > > > > > > > > > > I hope that prereviewers Anton Vinogradov and Nikolay
> > > >
> > > > Izhikov
> > > > > > > will
> > > > > > > > be
> > > > > > > > > > > > able to answer if solution out of scope or not in a
> > >
> > > couple
> > > > of
> > > > > > > days.
> > > > > > > > > > > >
> > > > > > > > > > > > [1]
> > > > > > > > > > > >
> >
> > http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-release-td34076.html#a34485
> > > > > > > > > > > > On Thu, Sep 27, 2018 at 11:14 PM Dmitriy Pavlov <
> > > > > > > > >
> > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > >
> > > > > > > > > > > > wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > > Yes, I agree, NPE during WAL flush is definitely a
> > > >
> > > > blocker.
> > > > > > > > > > > > >
> > > > > > > > > > > > > It is strange why the current test set did not fail
> > >
> > > after
> > > > > > > commit.
> > > > > > > > > > > > >
> > > > > > > > > > > > > чт, 27 сент. 2018 г. в 21:45, Andrey Kuznetsov <
> > > > > > > >
> > > > > > > > stkuzma@gmail.com
> > > > > > > > > > :
> > > > > > > > > > > > >
> > > > > > > > > > > > > > Igniters,
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > I've bumped into a new bug in WAL manager recently,
> > >
> > > see
> > > > > > [1].
> > > > > > > It
> > > > > > > > > > looks
> > > > > > > > > > > > > > critical enough, and can be a good candidate for
> > >
> > > fixing
> > > > > > > before
> > > > > > > > > 2.7
> > > > > > > > > > > > release.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Do you agree?
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > [1]
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-9731
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 19:45, Dmitriy Pavlov <
> > > > > > > > > >
> > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > :
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > > I need Vhyacheslav's opinion to be absolutely
> >
> > sure
> > > > what
> > > > > > > > status
> > > > > > > > > is
> > > > > > > > > > > > now.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > We never committed to dates of release, as well.
> >
> > I
> > > > > don't
> > > > > > > > quite
> > > > > > > > > > > > understand
> > > > > > > > > > > > > > > what can mean 'the community committed to
> > > > >
> > > > > doing/releasing
> > > > > > > > > > > something'.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > About SG, I also concerned why such a big feature
> > >
> > > has
> > > > > > > quite a
> > > > > > > > > few
> > > > > > > > > > > > > > > discussions on the list. But it is another story.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 19:33, Vladimir Ozerov <
> > > > > > > > > > >
> > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > :
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Folks,
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Please stop looking for enemies everywhere.
> >
> > Just
> > > > went
> > > > > > > > through
> > > > > > > > > > > this
> > > > > > > > > > > > > > thread
> > > > > > > > > > > > > > > > and search for "service" word.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 7:30 PM Denis Magda <
> > > > > > > > >
> > > > > > > > > dmagda@apache.org
> > > > > > > > > > >
> > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Denis, as PMC Chair, could you please
> >
> > control,
> > > > > that
> > > > > > > > > Service
> > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > > > inclusion/exclusion is discussed properly
> > > > >
> > > > > according
> > > > > > to
> > > > > > > > the
> > > > > > > > > > > > Apache
> > > > > > > > > > > > > > Way.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > It's fine when committers/contributors have
> > > >
> > > > private
> > > > > > > > > > discussions
> > > > > > > > > > > > > > related
> > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > a feature they've been working on. Not
> > >
> > > everything
> > > > > > should
> > > > > > > > go
> > > > > > > > > > > > through
> > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > dev
> > > > > > > > > > > > > > > > > list. Otherwise, it will be inundated.
> >
> > However,
> > > > > > agree,
> > > > > > > > that
> > > > > > > > > > > > > > > architectural
> > > > > > > > > > > > > > > > > and release decisions need to be done
> >
> > publicly.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Speaking about Service Grid, there was a
> > > >
> > > > discussion
> > > > > > > where
> > > > > > > > I
> > > > > > > > > > saw
> > > > > > > > > > > > that
> > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > was
> > > > > > > > > > > > > > > > > questionable whether it gets added to the
> > >
> > > release
> > > > or
> > > > > > > not.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > *Vladislav*, could you please shed some light
> >
> > on
> > > > the
> > > > > > > > current
> > > > > > > > > > > > status of
> > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > service grid?
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 9:12 AM Dmitriy
> >
> > Pavlov <
> > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Ok, let's wait for feedback from SG
> > > > > > > >
> > > > > > > > Author(s)/Reviewer(s)
> > > > > > > > > > > > first. If
> > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > is
> > > > > > > > > > > > > > > > > > not ready, ok. But I thought it is almost
> > >
> > > done.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > I apologize if I missed some discussion (it
> > >
> > > can
> > > > > > > happen),
> > > > > > > > > but
> > > > > > > > > > > > > > > > > > According to the statement "our current
> > > >
> > > > agreement"
> > > > > > > > > > > > > > > > > > I can suspect some members are making some
> > >
> > > sort
> > > > of
> > > > > > > > private
> > > > > > > > > > > > > > agreements,
> > > > > > > > > > > > > > > > > and
> > > > > > > > > > > > > > > > > > do not to discuss it on the list.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Let's build consensus here first, and then
> > >
> > > name
> > > > an
> > > > > > > > > > agreement.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Denis, as PMC Chair, could you please
> >
> > control,
> > > > > that
> > > > > > > > > Service
> > > > > > > > > > > Grid
> > > > > > > > > > > > > > > > > > inclusion/exclusion is discussed properly
> > > > >
> > > > > according
> > > > > > to
> > > > > > > > the
> > > > > > > > > > > > Apache
> > > > > > > > > > > > > > Way.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 18:55, Vladimir
> >
> > Ozerov
> > > <
> > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > This is an outcome of current state of
> > >
> > > Service
> > > > > > Grid -
> > > > > > > > it
> > > > > > > > > is
> > > > > > > > > > > not
> > > > > > > > > > > > > > > ready.
> > > > > > > > > > > > > > > > > We
> > > > > > > > > > > > > > > > > > > never committed to have it to 2.7. Our goal
> > >
> > > was
> > > > > to
> > > > > > > try
> > > > > > > > to
> > > > > > > > > > > > include
> > > > > > > > > > > > > > it
> > > > > > > > > > > > > > > > > into
> > > > > > > > > > > > > > > > > > > 2.7.
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 6:48 PM Dmitriy
> > >
> > > Pavlov
> > > > <
> > > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > Could you please provide a reference to
> > >
> > > some
> > > > > > > thread?
> > > > > > > > > > > > Probably I
> > > > > > > > > > > > > > > > > missed
> > > > > > > > > > > > > > > > > > > it.
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 18:46, Vladimir
> > > >
> > > > Ozerov <
> > > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > Our current agreement is that Service
> > >
> > > Grid
> > > > is
> > > > > > out
> > > > > > > > of
> > > > > > > > > > > scope.
> > > > > > > > > > > > > > This
> > > > > > > > > > > > > > > > > is a
> > > > > > > > > > > > > > > > > > > > huge
> > > > > > > > > > > > > > > > > > > > > feature, which hasn't entered review
> > >
> > > stage
> > > > so
> > > > > > > far,
> > > > > > > > We
> > > > > > > > > > > will
> > > > > > > > > > > > not
> > > > > > > > > > > > > > be
> > > > > > > > > > > > > > > > > > > able to
> > > > > > > > > > > > > > > > > > > > > review/fix/test it properly.
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 6:32 PM Dmitriy
> > > > >
> > > > > Pavlov
> > > > > > <
> > > > > > > > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > I agree, and I prefer four weeks for
> > > > > > > >
> > > > > > > > stabilization*
> > > > > > > > > > (1
> > > > > > > > > > > > Oct -
> > > > > > > > > > > > > > 29
> > > > > > > > > > > > > > > > > Oct)
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > Do I understand it correctly: Service
> > > >
> > > > Grid
> > > > > is
> > > > > > > > still
> > > > > > > > > > in
> > > > > > > > > > > > scope,
> > > > > > > > > > > > > > > > > isn't
> > > > > > > > > > > > > > > > > > > > it? I
> > > > > > > > > > > > > > > > > > > > > > find it very important.
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 18:28, Nikolay
> > > > > >
> > > > > > Izhikov <
> > > > > > > > > > > > > > > > > nizhikov@apache.org
> > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > Hello, Vova.
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > Thank you for clear release status.
> > > > > > > > > > > > > > > > > > > > > > > I'm +1 for your proposal.
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > чт, 27 сент. 2018 г., 18:25 Alexey
> > > > > >
> > > > > > Kuznetsov
> > > > > > > <
> > > > > > > > > > > > > > > > > > > akuznetsov@apache.org
> > > > > > > > > > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > Vova,
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > Huge +1 to do a stabilization.
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > > > > > > > > > Alexey Kuznetsov
> > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > --
> > > > > > > > > > > > > > Best regards,
> > > > > > > > > > > > > > Andrey Kuznetsov.
> > > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > --
> > > > > > > > > > > > Best Regards, Vyacheslav D.
> > > > > > > > > > > >
Re: Apache Ignite 2.7 release
Posted by Dmitriy Pavlov <dp...@gmail.com>.
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 <ds...@apache.org>:
> Dmitriy,
>
> We agreed in the beginning of this thread that Service Grid changes are not
> going to make the release because the community still did not approve the
> design. Nothing has changed since. I have not seen any design discussions.
> At this point, I have no confidence that the Service Grid changes will make
> it into the 2.8 release. The 2.7 release seems out of question altogether.
>
> Also, Nikolay is a release manager. We should let him drive the release. To
> my knowledge, he is doing a great job and the release is going according to
> the schedule he proposed.
>
> D.
>
> On Fri, Sep 28, 2018 at 4:31 AM Dmitriy Pavlov <dp...@gmail.com>
> wrote:
>
> > Hi Dmitriy, Vladimir,
> >
> > I suggest we stop this nonsense with release dates-pushing because of
> some
> > open question.
> >
> > Just because you disagreed with any include/exclude something into scope,
> > does not mean that whole community disagreed.
> >
> > If folks will start a separate discussion with results of the review, I
> see
> > no reasons to reject their contribution, even if we need to revisit our
> > agreements and wait for a couple of days more.
> >
> > Am I missing some reason why dates are so fundamentally important to you?
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > пт, 28 сент. 2018 г. в 12:20, Dmitriy Setrakyan <ds...@apache.org>:
> >
> > > If services is not ready, which it is not, then we should include them
> > into
> > > the next release. There is no need to force them into 2.7. I suggest we
> > > move according to the schedule we all agreed on.
> > >
> > > D.
> > >
> > > On Fri, Sep 28, 2018 at 1:22 AM Dmitriy Pavlov <dp...@gmail.com>
> > > wrote:
> > >
> > > > Yes, so correct statement is "community did not make any decisions
> > about
> > > > services not go to 2.7/ services are out of scope".
> > > >
> > > > If so, please forgive me my confusion.
> > > >
> > > > пт, 28 сент. 2018 г. в 11:19, Vladimir Ozerov <vozerov@gridgain.com
> >:
> > > >
> > > > > Exactly. So correct statement is “it is up to *community* to decide
> > > > whether
> > > > > something goes to 2.7”.
> > > > >
> > > > > пт, 28 сент. 2018 г. в 11:11, Dmitriy Pavlov <
> dpavlov.spb@gmail.com
> > >:
> > > > >
> > > > > > No, it is up to the community to discuss after their review
> > results.
> > > > > >
> > > > > > пт, 28 сент. 2018 г. в 11:09, Vladimir Ozerov <
> > vozerov@gridgain.com
> > > >:
> > > > > >
> > > > > > > Dmitriy,
> > > > > > >
> > > > > > > Did I read your words correctly that it is up to implementor
> of a
> > > > > single
> > > > > > > feature to decide whether release of all other features and
> fixes
> > > to
> > > > be
> > > > > > > delayed?
> > > > > > >
> > > > > > > пт, 28 сент. 2018 г. в 11:00, Dmitriy Pavlov <
> > > dpavlov.spb@gmail.com
> > > > >:
> > > > > > >
> > > > > > > > My point we can wait a bit for services because
> > > > > > > > 1 we are open-minded and we don't have outside pressure to
> do
> > > > > release
> > > > > > in
> > > > > > > > October
> > > > > > > > 2 and services it is not some new feature, which suddenly
> > > appeared
> > > > > in
> > > > > > > > autumn, it is a well known and important feature.
> > > > > > > >
> > > > > > > > So it is up to Vyacheslav, Anton and Nikolay to decide.
> > > > > > > >
> > > > > > > > Decisions can be services are not ready/ready to merge only
> to
> > > > > > > master/ready
> > > > > > > > to merge to master and to 2.7.
> > > > > > > >
> > > > > > > >
> > > > > > > > пт, 28 сент. 2018 г. в 10:46, Vladimir Ozerov <
> > > > vozerov@gridgain.com
> > > > > >:
> > > > > > > >
> > > > > > > > > Dmitry,
> > > > > > > > >
> > > > > > > > > Community agreement was to perform the release in October.
> Of
> > > > > course
> > > > > > we
> > > > > > > > can
> > > > > > > > > wait a bit for services. Then we wait a bit for other cool
> > > > features
> > > > > > > ready
> > > > > > > > > by that time, then again and again, and release will never
> > > > happen.
> > > > > > And
> > > > > > > > > while we are waiting for new features to come, already
> > > completerd
> > > > > > > > features
> > > > > > > > > cannot be used by anyone.
> > > > > > > > >
> > > > > > > > > This is why we have an agreement that if feature is not
> > ready,
> > > it
> > > > > > > should
> > > > > > > > be
> > > > > > > > > moved to future release, instead of shifting release. The
> > sole
> > > > > reason
> > > > > > > to
> > > > > > > > > have strict dates when decisions are made is to let release
> > > > happen.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Fri, Sep 28, 2018 at 2:22 AM Dmitriy Pavlov <
> > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Vladimir, I'm not searching for enemy, and not fighting
> > with
> > > > > you.
> > > > > > > I'm
> > > > > > > > > not
> > > > > > > > > > happy about cases when we are hurrying.
> > > > > > > > > >
> > > > > > > > > > We can't fix test, fill ticket details, can't wait for
> > > > > > contributions
> > > > > > > to
> > > > > > > > > > finish their tasks. It is not best idea to use
> experience
> > > from
> > > > > > > > > commercial
> > > > > > > > > > companies in open source. Are there any pressure outside
> > > > > community?
> > > > > > > Did
> > > > > > > > > > someone promised rest of features to be released at 30
> > > > September?
> > > > > > > > > >
> > > > > > > > > > Let's remember principle do-orcracy, power of those who
> do.
> > > If
> > > > > > > > contribor
> > > > > > > > > > does change and reviewer does review, let's give right of
> > > > making
> > > > > > > > decision
> > > > > > > > > > to them, but not to some closed club of people who
> > privately
> > > > > > discuss
> > > > > > > > > > something.
> > > > > > > > > >
> > > > > > > > > > Sincerely
> > > > > > > > > > Dmitriy Pavlov
> > > > > > > > > >
> > > > > > > > > > чт, 27 сент. 2018 г., 23:42 Vyacheslav Daradur <
> > > > > > daradurvs@gmail.com
> > > > > > > >:
> > > > > > > > > >
> > > > > > > > > > > Hi Igniters!
> > > > > > > > > > >
> > > > > > > > > > > As I have written about Service Grid before [1] I'm
> > > > finalizing
> > > > > > the
> > > > > > > > > > > solution to be sure that implementation is reliable.
> > > > > > > > > > >
> > > > > > > > > > > About including it in 2.7, if we talk that code freeze
> > > > tomorrow
> > > > > > > then
> > > > > > > > > > > the solution is not ready to merge yet.
> > > > > > > > > > > I hope that prereviewers Anton Vinogradov and Nikolay
> > > Izhikov
> > > > > > will
> > > > > > > be
> > > > > > > > > > > able to answer if solution out of scope or not in a
> > couple
> > > of
> > > > > > days.
> > > > > > > > > > >
> > > > > > > > > > > [1]
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-release-td34076.html#a34485
> > > > > > > > > > > On Thu, Sep 27, 2018 at 11:14 PM Dmitriy Pavlov <
> > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > >
> > > > > > > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > Yes, I agree, NPE during WAL flush is definitely a
> > > blocker.
> > > > > > > > > > > >
> > > > > > > > > > > > It is strange why the current test set did not fail
> > after
> > > > > > commit.
> > > > > > > > > > > >
> > > > > > > > > > > > чт, 27 сент. 2018 г. в 21:45, Andrey Kuznetsov <
> > > > > > > stkuzma@gmail.com
> > > > > > > > >:
> > > > > > > > > > > >
> > > > > > > > > > > > > Igniters,
> > > > > > > > > > > > >
> > > > > > > > > > > > > I've bumped into a new bug in WAL manager recently,
> > see
> > > > > [1].
> > > > > > It
> > > > > > > > > looks
> > > > > > > > > > > > > critical enough, and can be a good candidate for
> > fixing
> > > > > > before
> > > > > > > > 2.7
> > > > > > > > > > > release.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Do you agree?
> > > > > > > > > > > > >
> > > > > > > > > > > > > [1]
> > https://issues.apache.org/jira/browse/IGNITE-9731
> > > > > > > > > > > > >
> > > > > > > > > > > > > чт, 27 сент. 2018 г. в 19:45, Dmitriy Pavlov <
> > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > >:
> > > > > > > > > > > > >
> > > > > > > > > > > > > > I need Vhyacheslav's opinion to be absolutely
> sure
> > > what
> > > > > > > status
> > > > > > > > is
> > > > > > > > > > > now.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > We never committed to dates of release, as well.
> I
> > > > don't
> > > > > > > quite
> > > > > > > > > > > understand
> > > > > > > > > > > > > > what can mean 'the community committed to
> > > > doing/releasing
> > > > > > > > > > something'.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > About SG, I also concerned why such a big feature
> > has
> > > > > > quite a
> > > > > > > > few
> > > > > > > > > > > > > > discussions on the list. But it is another story.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 19:33, Vladimir Ozerov <
> > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > >:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Folks,
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Please stop looking for enemies everywhere.
> Just
> > > went
> > > > > > > through
> > > > > > > > > > this
> > > > > > > > > > > > > thread
> > > > > > > > > > > > > > > and search for "service" word.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 7:30 PM Denis Magda <
> > > > > > > > dmagda@apache.org
> > > > > > > > > >
> > > > > > > > > > > wrote:
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >> >
> > > > > > > > > > > > > > >> > Denis, as PMC Chair, could you please
> control,
> > > > that
> > > > > > > > Service
> > > > > > > > > > Grid
> > > > > > > > > > > > > > >> > inclusion/exclusion is discussed properly
> > > > according
> > > > > to
> > > > > > > the
> > > > > > > > > > > Apache
> > > > > > > > > > > > > Way.
> > > > > > > > > > > > > > >>
> > > > > > > > > > > > > > >>
> > > > > > > > > > > > > > >> It's fine when committers/contributors have
> > > private
> > > > > > > > > discussions
> > > > > > > > > > > > > related
> > > > > > > > > > > > > > to
> > > > > > > > > > > > > > >> a feature they've been working on. Not
> > everything
> > > > > should
> > > > > > > go
> > > > > > > > > > > through
> > > > > > > > > > > > > the
> > > > > > > > > > > > > > >> dev
> > > > > > > > > > > > > > >> list. Otherwise, it will be inundated.
> However,
> > > > > agree,
> > > > > > > that
> > > > > > > > > > > > > > architectural
> > > > > > > > > > > > > > >> and release decisions need to be done
> publicly.
> > > > > > > > > > > > > > >>
> > > > > > > > > > > > > > >> Speaking about Service Grid, there was a
> > > discussion
> > > > > > where
> > > > > > > I
> > > > > > > > > saw
> > > > > > > > > > > that
> > > > > > > > > > > > > it
> > > > > > > > > > > > > > >> was
> > > > > > > > > > > > > > >> questionable whether it gets added to the
> > release
> > > or
> > > > > > not.
> > > > > > > > > > > > > > >>
> > > > > > > > > > > > > > >> *Vladislav*, could you please shed some light
> on
> > > the
> > > > > > > current
> > > > > > > > > > > status of
> > > > > > > > > > > > > > the
> > > > > > > > > > > > > > >> service grid?
> > > > > > > > > > > > > > >>
> > > > > > > > > > > > > > >> On Thu, Sep 27, 2018 at 9:12 AM Dmitriy
> Pavlov <
> > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > >> wrote:
> > > > > > > > > > > > > > >>
> > > > > > > > > > > > > > >> > Ok, let's wait for feedback from SG
> > > > > > > Author(s)/Reviewer(s)
> > > > > > > > > > > first. If
> > > > > > > > > > > > > it
> > > > > > > > > > > > > > >> is
> > > > > > > > > > > > > > >> > not ready, ok. But I thought it is almost
> > done.
> > > > > > > > > > > > > > >> >
> > > > > > > > > > > > > > >> > I apologize if I missed some discussion (it
> > can
> > > > > > happen),
> > > > > > > > but
> > > > > > > > > > > > > > >> > According to the statement "our current
> > > agreement"
> > > > > > > > > > > > > > >> > I can suspect some members are making some
> > sort
> > > of
> > > > > > > private
> > > > > > > > > > > > > agreements,
> > > > > > > > > > > > > > >> and
> > > > > > > > > > > > > > >> > do not to discuss it on the list.
> > > > > > > > > > > > > > >> >
> > > > > > > > > > > > > > >> > Let's build consensus here first, and then
> > name
> > > an
> > > > > > > > > agreement.
> > > > > > > > > > > > > > >> >
> > > > > > > > > > > > > > >> > Denis, as PMC Chair, could you please
> control,
> > > > that
> > > > > > > > Service
> > > > > > > > > > Grid
> > > > > > > > > > > > > > >> > inclusion/exclusion is discussed properly
> > > > according
> > > > > to
> > > > > > > the
> > > > > > > > > > > Apache
> > > > > > > > > > > > > Way.
> > > > > > > > > > > > > > >> >
> > > > > > > > > > > > > > >> > чт, 27 сент. 2018 г. в 18:55, Vladimir
> Ozerov
> > <
> > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > >:
> > > > > > > > > > > > > > >> >
> > > > > > > > > > > > > > >> >> Dmitriy,
> > > > > > > > > > > > > > >> >>
> > > > > > > > > > > > > > >> >> This is an outcome of current state of
> > Service
> > > > > Grid -
> > > > > > > it
> > > > > > > > is
> > > > > > > > > > not
> > > > > > > > > > > > > > ready.
> > > > > > > > > > > > > > >> We
> > > > > > > > > > > > > > >> >> never committed to have it to 2.7. Our goal
> > was
> > > > to
> > > > > > try
> > > > > > > to
> > > > > > > > > > > include
> > > > > > > > > > > > > it
> > > > > > > > > > > > > > >> into
> > > > > > > > > > > > > > >> >> 2.7.
> > > > > > > > > > > > > > >> >>
> > > > > > > > > > > > > > >> >> On Thu, Sep 27, 2018 at 6:48 PM Dmitriy
> > Pavlov
> > > <
> > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > >> >> wrote:
> > > > > > > > > > > > > > >> >>
> > > > > > > > > > > > > > >> >> > Could you please provide a reference to
> > some
> > > > > > thread?
> > > > > > > > > > > Probably I
> > > > > > > > > > > > > > >> missed
> > > > > > > > > > > > > > >> >> it.
> > > > > > > > > > > > > > >> >> >
> > > > > > > > > > > > > > >> >> > чт, 27 сент. 2018 г. в 18:46, Vladimir
> > > Ozerov <
> > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > >> >:
> > > > > > > > > > > > > > >> >> >
> > > > > > > > > > > > > > >> >> > > Our current agreement is that Service
> > Grid
> > > is
> > > > > out
> > > > > > > of
> > > > > > > > > > scope.
> > > > > > > > > > > > > This
> > > > > > > > > > > > > > >> is a
> > > > > > > > > > > > > > >> >> > huge
> > > > > > > > > > > > > > >> >> > > feature, which hasn't entered review
> > stage
> > > so
> > > > > > far,
> > > > > > > We
> > > > > > > > > > will
> > > > > > > > > > > not
> > > > > > > > > > > > > be
> > > > > > > > > > > > > > >> >> able to
> > > > > > > > > > > > > > >> >> > > review/fix/test it properly.
> > > > > > > > > > > > > > >> >> > >
> > > > > > > > > > > > > > >> >> > > On Thu, Sep 27, 2018 at 6:32 PM Dmitriy
> > > > Pavlov
> > > > > <
> > > > > > > > > > > > > > >> dpavlov.spb@gmail.com
> > > > > > > > > > > > > > >> >> >
> > > > > > > > > > > > > > >> >> > > wrote:
> > > > > > > > > > > > > > >> >> > >
> > > > > > > > > > > > > > >> >> > > > I agree, and I prefer four weeks for
> > > > > > > stabilization*
> > > > > > > > > (1
> > > > > > > > > > > Oct -
> > > > > > > > > > > > > 29
> > > > > > > > > > > > > > >> Oct)
> > > > > > > > > > > > > > >> >> > > >
> > > > > > > > > > > > > > >> >> > > > Do I understand it correctly: Service
> > > Grid
> > > > is
> > > > > > > still
> > > > > > > > > in
> > > > > > > > > > > scope,
> > > > > > > > > > > > > > >> isn't
> > > > > > > > > > > > > > >> >> > it? I
> > > > > > > > > > > > > > >> >> > > > find it very important.
> > > > > > > > > > > > > > >> >> > > >
> > > > > > > > > > > > > > >> >> > > > чт, 27 сент. 2018 г. в 18:28, Nikolay
> > > > > Izhikov <
> > > > > > > > > > > > > > >> nizhikov@apache.org
> > > > > > > > > > > > > > >> >> >:
> > > > > > > > > > > > > > >> >> > > >
> > > > > > > > > > > > > > >> >> > > > > Hello, Vova.
> > > > > > > > > > > > > > >> >> > > > >
> > > > > > > > > > > > > > >> >> > > > > Thank you for clear release status.
> > > > > > > > > > > > > > >> >> > > > > I'm +1 for your proposal.
> > > > > > > > > > > > > > >> >> > > > >
> > > > > > > > > > > > > > >> >> > > > > чт, 27 сент. 2018 г., 18:25 Alexey
> > > > > Kuznetsov
> > > > > > <
> > > > > > > > > > > > > > >> >> akuznetsov@apache.org
> > > > > > > > > > > > > > >> >> > >:
> > > > > > > > > > > > > > >> >> > > > >
> > > > > > > > > > > > > > >> >> > > > > > Vova,
> > > > > > > > > > > > > > >> >> > > > > >
> > > > > > > > > > > > > > >> >> > > > > > Huge +1 to do a stabilization.
> > > > > > > > > > > > > > >> >> > > > > >
> > > > > > > > > > > > > > >> >> > > > > >
> > > > > > > > > > > > > > >> >> > > > > > --
> > > > > > > > > > > > > > >> >> > > > > > Alexey Kuznetsov
> > > > > > > > > > > > > > >> >> > > > > >
> > > > > > > > > > > > > > >> >> > > > >
> > > > > > > > > > > > > > >> >> > > >
> > > > > > > > > > > > > > >> >> > >
> > > > > > > > > > > > > > >> >> >
> > > > > > > > > > > > > > >> >>
> > > > > > > > > > > > > > >> >
> > > > > > > > > > > > > > >>
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > --
> > > > > > > > > > > > > Best regards,
> > > > > > > > > > > > > Andrey Kuznetsov.
> > > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > --
> > > > > > > > > > > Best Regards, Vyacheslav D.
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: Apache Ignite 2.7 release
Posted by Dmitriy Setrakyan <ds...@apache.org>.
Dmitriy,
We agreed in the beginning of this thread that Service Grid changes are not
going to make the release because the community still did not approve the
design. Nothing has changed since. I have not seen any design discussions.
At this point, I have no confidence that the Service Grid changes will make
it into the 2.8 release. The 2.7 release seems out of question altogether.
Also, Nikolay is a release manager. We should let him drive the release. To
my knowledge, he is doing a great job and the release is going according to
the schedule he proposed.
D.
On Fri, Sep 28, 2018 at 4:31 AM Dmitriy Pavlov <dp...@gmail.com>
wrote:
> Hi Dmitriy, Vladimir,
>
> I suggest we stop this nonsense with release dates-pushing because of some
> open question.
>
> Just because you disagreed with any include/exclude something into scope,
> does not mean that whole community disagreed.
>
> If folks will start a separate discussion with results of the review, I see
> no reasons to reject their contribution, even if we need to revisit our
> agreements and wait for a couple of days more.
>
> Am I missing some reason why dates are so fundamentally important to you?
>
> Sincerely,
> Dmitriy Pavlov
>
> пт, 28 сент. 2018 г. в 12:20, Dmitriy Setrakyan <ds...@apache.org>:
>
> > If services is not ready, which it is not, then we should include them
> into
> > the next release. There is no need to force them into 2.7. I suggest we
> > move according to the schedule we all agreed on.
> >
> > D.
> >
> > On Fri, Sep 28, 2018 at 1:22 AM Dmitriy Pavlov <dp...@gmail.com>
> > wrote:
> >
> > > Yes, so correct statement is "community did not make any decisions
> about
> > > services not go to 2.7/ services are out of scope".
> > >
> > > If so, please forgive me my confusion.
> > >
> > > пт, 28 сент. 2018 г. в 11:19, Vladimir Ozerov <vo...@gridgain.com>:
> > >
> > > > Exactly. So correct statement is “it is up to *community* to decide
> > > whether
> > > > something goes to 2.7”.
> > > >
> > > > пт, 28 сент. 2018 г. в 11:11, Dmitriy Pavlov <dpavlov.spb@gmail.com
> >:
> > > >
> > > > > No, it is up to the community to discuss after their review
> results.
> > > > >
> > > > > пт, 28 сент. 2018 г. в 11:09, Vladimir Ozerov <
> vozerov@gridgain.com
> > >:
> > > > >
> > > > > > Dmitriy,
> > > > > >
> > > > > > Did I read your words correctly that it is up to implementor of a
> > > > single
> > > > > > feature to decide whether release of all other features and fixes
> > to
> > > be
> > > > > > delayed?
> > > > > >
> > > > > > пт, 28 сент. 2018 г. в 11:00, Dmitriy Pavlov <
> > dpavlov.spb@gmail.com
> > > >:
> > > > > >
> > > > > > > My point we can wait a bit for services because
> > > > > > > 1 we are open-minded and we don't have outside pressure to do
> > > > release
> > > > > in
> > > > > > > October
> > > > > > > 2 and services it is not some new feature, which suddenly
> > appeared
> > > > in
> > > > > > > autumn, it is a well known and important feature.
> > > > > > >
> > > > > > > So it is up to Vyacheslav, Anton and Nikolay to decide.
> > > > > > >
> > > > > > > Decisions can be services are not ready/ready to merge only to
> > > > > > master/ready
> > > > > > > to merge to master and to 2.7.
> > > > > > >
> > > > > > >
> > > > > > > пт, 28 сент. 2018 г. в 10:46, Vladimir Ozerov <
> > > vozerov@gridgain.com
> > > > >:
> > > > > > >
> > > > > > > > Dmitry,
> > > > > > > >
> > > > > > > > Community agreement was to perform the release in October. Of
> > > > course
> > > > > we
> > > > > > > can
> > > > > > > > wait a bit for services. Then we wait a bit for other cool
> > > features
> > > > > > ready
> > > > > > > > by that time, then again and again, and release will never
> > > happen.
> > > > > And
> > > > > > > > while we are waiting for new features to come, already
> > completerd
> > > > > > > features
> > > > > > > > cannot be used by anyone.
> > > > > > > >
> > > > > > > > This is why we have an agreement that if feature is not
> ready,
> > it
> > > > > > should
> > > > > > > be
> > > > > > > > moved to future release, instead of shifting release. The
> sole
> > > > reason
> > > > > > to
> > > > > > > > have strict dates when decisions are made is to let release
> > > happen.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On Fri, Sep 28, 2018 at 2:22 AM Dmitriy Pavlov <
> > > > > dpavlov.spb@gmail.com>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Vladimir, I'm not searching for enemy, and not fighting
> with
> > > > you.
> > > > > > I'm
> > > > > > > > not
> > > > > > > > > happy about cases when we are hurrying.
> > > > > > > > >
> > > > > > > > > We can't fix test, fill ticket details, can't wait for
> > > > > contributions
> > > > > > to
> > > > > > > > > finish their tasks. It is not best idea to use experience
> > from
> > > > > > > > commercial
> > > > > > > > > companies in open source. Are there any pressure outside
> > > > community?
> > > > > > Did
> > > > > > > > > someone promised rest of features to be released at 30
> > > September?
> > > > > > > > >
> > > > > > > > > Let's remember principle do-orcracy, power of those who do.
> > If
> > > > > > > contribor
> > > > > > > > > does change and reviewer does review, let's give right of
> > > making
> > > > > > > decision
> > > > > > > > > to them, but not to some closed club of people who
> privately
> > > > > discuss
> > > > > > > > > something.
> > > > > > > > >
> > > > > > > > > Sincerely
> > > > > > > > > Dmitriy Pavlov
> > > > > > > > >
> > > > > > > > > чт, 27 сент. 2018 г., 23:42 Vyacheslav Daradur <
> > > > > daradurvs@gmail.com
> > > > > > >:
> > > > > > > > >
> > > > > > > > > > Hi Igniters!
> > > > > > > > > >
> > > > > > > > > > As I have written about Service Grid before [1] I'm
> > > finalizing
> > > > > the
> > > > > > > > > > solution to be sure that implementation is reliable.
> > > > > > > > > >
> > > > > > > > > > About including it in 2.7, if we talk that code freeze
> > > tomorrow
> > > > > > then
> > > > > > > > > > the solution is not ready to merge yet.
> > > > > > > > > > I hope that prereviewers Anton Vinogradov and Nikolay
> > Izhikov
> > > > > will
> > > > > > be
> > > > > > > > > > able to answer if solution out of scope or not in a
> couple
> > of
> > > > > days.
> > > > > > > > > >
> > > > > > > > > > [1]
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-release-td34076.html#a34485
> > > > > > > > > > On Thu, Sep 27, 2018 at 11:14 PM Dmitriy Pavlov <
> > > > > > > dpavlov.spb@gmail.com
> > > > > > > > >
> > > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > Yes, I agree, NPE during WAL flush is definitely a
> > blocker.
> > > > > > > > > > >
> > > > > > > > > > > It is strange why the current test set did not fail
> after
> > > > > commit.
> > > > > > > > > > >
> > > > > > > > > > > чт, 27 сент. 2018 г. в 21:45, Andrey Kuznetsov <
> > > > > > stkuzma@gmail.com
> > > > > > > >:
> > > > > > > > > > >
> > > > > > > > > > > > Igniters,
> > > > > > > > > > > >
> > > > > > > > > > > > I've bumped into a new bug in WAL manager recently,
> see
> > > > [1].
> > > > > It
> > > > > > > > looks
> > > > > > > > > > > > critical enough, and can be a good candidate for
> fixing
> > > > > before
> > > > > > > 2.7
> > > > > > > > > > release.
> > > > > > > > > > > >
> > > > > > > > > > > > Do you agree?
> > > > > > > > > > > >
> > > > > > > > > > > > [1]
> https://issues.apache.org/jira/browse/IGNITE-9731
> > > > > > > > > > > >
> > > > > > > > > > > > чт, 27 сент. 2018 г. в 19:45, Dmitriy Pavlov <
> > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > >:
> > > > > > > > > > > >
> > > > > > > > > > > > > I need Vhyacheslav's opinion to be absolutely sure
> > what
> > > > > > status
> > > > > > > is
> > > > > > > > > > now.
> > > > > > > > > > > > >
> > > > > > > > > > > > > We never committed to dates of release, as well. I
> > > don't
> > > > > > quite
> > > > > > > > > > understand
> > > > > > > > > > > > > what can mean 'the community committed to
> > > doing/releasing
> > > > > > > > > something'.
> > > > > > > > > > > > >
> > > > > > > > > > > > > About SG, I also concerned why such a big feature
> has
> > > > > quite a
> > > > > > > few
> > > > > > > > > > > > > discussions on the list. But it is another story.
> > > > > > > > > > > > >
> > > > > > > > > > > > > чт, 27 сент. 2018 г. в 19:33, Vladimir Ozerov <
> > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > >:
> > > > > > > > > > > > >
> > > > > > > > > > > > > > Folks,
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Please stop looking for enemies everywhere. Just
> > went
> > > > > > through
> > > > > > > > > this
> > > > > > > > > > > > thread
> > > > > > > > > > > > > > and search for "service" word.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 7:30 PM Denis Magda <
> > > > > > > dmagda@apache.org
> > > > > > > > >
> > > > > > > > > > wrote:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >> >
> > > > > > > > > > > > > >> > Denis, as PMC Chair, could you please control,
> > > that
> > > > > > > Service
> > > > > > > > > Grid
> > > > > > > > > > > > > >> > inclusion/exclusion is discussed properly
> > > according
> > > > to
> > > > > > the
> > > > > > > > > > Apache
> > > > > > > > > > > > Way.
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> It's fine when committers/contributors have
> > private
> > > > > > > > discussions
> > > > > > > > > > > > related
> > > > > > > > > > > > > to
> > > > > > > > > > > > > >> a feature they've been working on. Not
> everything
> > > > should
> > > > > > go
> > > > > > > > > > through
> > > > > > > > > > > > the
> > > > > > > > > > > > > >> dev
> > > > > > > > > > > > > >> list. Otherwise, it will be inundated. However,
> > > > agree,
> > > > > > that
> > > > > > > > > > > > > architectural
> > > > > > > > > > > > > >> and release decisions need to be done publicly.
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> Speaking about Service Grid, there was a
> > discussion
> > > > > where
> > > > > > I
> > > > > > > > saw
> > > > > > > > > > that
> > > > > > > > > > > > it
> > > > > > > > > > > > > >> was
> > > > > > > > > > > > > >> questionable whether it gets added to the
> release
> > or
> > > > > not.
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> *Vladislav*, could you please shed some light on
> > the
> > > > > > current
> > > > > > > > > > status of
> > > > > > > > > > > > > the
> > > > > > > > > > > > > >> service grid?
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> On Thu, Sep 27, 2018 at 9:12 AM Dmitriy Pavlov <
> > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > >
> > > > > > > > > > > > > >> wrote:
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> > Ok, let's wait for feedback from SG
> > > > > > Author(s)/Reviewer(s)
> > > > > > > > > > first. If
> > > > > > > > > > > > it
> > > > > > > > > > > > > >> is
> > > > > > > > > > > > > >> > not ready, ok. But I thought it is almost
> done.
> > > > > > > > > > > > > >> >
> > > > > > > > > > > > > >> > I apologize if I missed some discussion (it
> can
> > > > > happen),
> > > > > > > but
> > > > > > > > > > > > > >> > According to the statement "our current
> > agreement"
> > > > > > > > > > > > > >> > I can suspect some members are making some
> sort
> > of
> > > > > > private
> > > > > > > > > > > > agreements,
> > > > > > > > > > > > > >> and
> > > > > > > > > > > > > >> > do not to discuss it on the list.
> > > > > > > > > > > > > >> >
> > > > > > > > > > > > > >> > Let's build consensus here first, and then
> name
> > an
> > > > > > > > agreement.
> > > > > > > > > > > > > >> >
> > > > > > > > > > > > > >> > Denis, as PMC Chair, could you please control,
> > > that
> > > > > > > Service
> > > > > > > > > Grid
> > > > > > > > > > > > > >> > inclusion/exclusion is discussed properly
> > > according
> > > > to
> > > > > > the
> > > > > > > > > > Apache
> > > > > > > > > > > > Way.
> > > > > > > > > > > > > >> >
> > > > > > > > > > > > > >> > чт, 27 сент. 2018 г. в 18:55, Vladimir Ozerov
> <
> > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > >:
> > > > > > > > > > > > > >> >
> > > > > > > > > > > > > >> >> Dmitriy,
> > > > > > > > > > > > > >> >>
> > > > > > > > > > > > > >> >> This is an outcome of current state of
> Service
> > > > Grid -
> > > > > > it
> > > > > > > is
> > > > > > > > > not
> > > > > > > > > > > > > ready.
> > > > > > > > > > > > > >> We
> > > > > > > > > > > > > >> >> never committed to have it to 2.7. Our goal
> was
> > > to
> > > > > try
> > > > > > to
> > > > > > > > > > include
> > > > > > > > > > > > it
> > > > > > > > > > > > > >> into
> > > > > > > > > > > > > >> >> 2.7.
> > > > > > > > > > > > > >> >>
> > > > > > > > > > > > > >> >> On Thu, Sep 27, 2018 at 6:48 PM Dmitriy
> Pavlov
> > <
> > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > >> >> wrote:
> > > > > > > > > > > > > >> >>
> > > > > > > > > > > > > >> >> > Could you please provide a reference to
> some
> > > > > thread?
> > > > > > > > > > Probably I
> > > > > > > > > > > > > >> missed
> > > > > > > > > > > > > >> >> it.
> > > > > > > > > > > > > >> >> >
> > > > > > > > > > > > > >> >> > чт, 27 сент. 2018 г. в 18:46, Vladimir
> > Ozerov <
> > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > >> >:
> > > > > > > > > > > > > >> >> >
> > > > > > > > > > > > > >> >> > > Our current agreement is that Service
> Grid
> > is
> > > > out
> > > > > > of
> > > > > > > > > scope.
> > > > > > > > > > > > This
> > > > > > > > > > > > > >> is a
> > > > > > > > > > > > > >> >> > huge
> > > > > > > > > > > > > >> >> > > feature, which hasn't entered review
> stage
> > so
> > > > > far,
> > > > > > We
> > > > > > > > > will
> > > > > > > > > > not
> > > > > > > > > > > > be
> > > > > > > > > > > > > >> >> able to
> > > > > > > > > > > > > >> >> > > review/fix/test it properly.
> > > > > > > > > > > > > >> >> > >
> > > > > > > > > > > > > >> >> > > On Thu, Sep 27, 2018 at 6:32 PM Dmitriy
> > > Pavlov
> > > > <
> > > > > > > > > > > > > >> dpavlov.spb@gmail.com
> > > > > > > > > > > > > >> >> >
> > > > > > > > > > > > > >> >> > > wrote:
> > > > > > > > > > > > > >> >> > >
> > > > > > > > > > > > > >> >> > > > I agree, and I prefer four weeks for
> > > > > > stabilization*
> > > > > > > > (1
> > > > > > > > > > Oct -
> > > > > > > > > > > > 29
> > > > > > > > > > > > > >> Oct)
> > > > > > > > > > > > > >> >> > > >
> > > > > > > > > > > > > >> >> > > > Do I understand it correctly: Service
> > Grid
> > > is
> > > > > > still
> > > > > > > > in
> > > > > > > > > > scope,
> > > > > > > > > > > > > >> isn't
> > > > > > > > > > > > > >> >> > it? I
> > > > > > > > > > > > > >> >> > > > find it very important.
> > > > > > > > > > > > > >> >> > > >
> > > > > > > > > > > > > >> >> > > > чт, 27 сент. 2018 г. в 18:28, Nikolay
> > > > Izhikov <
> > > > > > > > > > > > > >> nizhikov@apache.org
> > > > > > > > > > > > > >> >> >:
> > > > > > > > > > > > > >> >> > > >
> > > > > > > > > > > > > >> >> > > > > Hello, Vova.
> > > > > > > > > > > > > >> >> > > > >
> > > > > > > > > > > > > >> >> > > > > Thank you for clear release status.
> > > > > > > > > > > > > >> >> > > > > I'm +1 for your proposal.
> > > > > > > > > > > > > >> >> > > > >
> > > > > > > > > > > > > >> >> > > > > чт, 27 сент. 2018 г., 18:25 Alexey
> > > > Kuznetsov
> > > > > <
> > > > > > > > > > > > > >> >> akuznetsov@apache.org
> > > > > > > > > > > > > >> >> > >:
> > > > > > > > > > > > > >> >> > > > >
> > > > > > > > > > > > > >> >> > > > > > Vova,
> > > > > > > > > > > > > >> >> > > > > >
> > > > > > > > > > > > > >> >> > > > > > Huge +1 to do a stabilization.
> > > > > > > > > > > > > >> >> > > > > >
> > > > > > > > > > > > > >> >> > > > > >
> > > > > > > > > > > > > >> >> > > > > > --
> > > > > > > > > > > > > >> >> > > > > > Alexey Kuznetsov
> > > > > > > > > > > > > >> >> > > > > >
> > > > > > > > > > > > > >> >> > > > >
> > > > > > > > > > > > > >> >> > > >
> > > > > > > > > > > > > >> >> > >
> > > > > > > > > > > > > >> >> >
> > > > > > > > > > > > > >> >>
> > > > > > > > > > > > > >> >
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > --
> > > > > > > > > > > > Best regards,
> > > > > > > > > > > > Andrey Kuznetsov.
> > > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > --
> > > > > > > > > > Best Regards, Vyacheslav D.
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: Apache Ignite 2.7 release
Posted by Denis Magda <dm...@apache.org>.
Even though I was not involved in the Service Grid 2.0 architectural or
development discussions, my guts feel that we need to allocate enough time
to test them through. It won't be just a fix or minor improvement,
Vyacheslav has been working on a tremendous task that seems to re-engineer
many aspects of the component. Plus, keep in mind that the current service
grid engine is battle-tested and used in production, so every architectural
change has to be well tested.
Let's wait what the reviewers say (Anton and Nikolay). We need to allocate
enough time to test it thoroughly and that time can go beyond the timeframe
of 2.7.
--
Denis
On Fri, Sep 28, 2018 at 4:58 AM Vladimir Ozerov <vo...@gridgain.com>
wrote:
> Importance come from the fact that we agreed on these dates. Neither
> community, nor implementors of the feature were against it. And community
> already work hard to met that dates: a lot of people already aligned their
> plans, a lot very important tickets were moved out of scope to met the
> dates.
>
> Nonsense - is to come at the end of coding phase and suggest to replay the
> plans all of a sudden. If you find it important - please start a separate
> discussion where it will be your responsibility to prove community that we
> have to realign our plans and delay release of all other features due to
> Service Grid being ahead of schedule. And solution to that problem will be
> very simple - to plan another release once Service Grid is coded, tested,
> reviewed and benchmarked.
>
> On Fri, Sep 28, 2018 at 2:31 PM Dmitriy Pavlov <dp...@gmail.com>
> wrote:
>
> > Hi Dmitriy, Vladimir,
> >
> > I suggest we stop this nonsense with release dates-pushing because of
> some
> > open question.
> >
> > Just because you disagreed with any include/exclude something into scope,
> > does not mean that whole community disagreed.
> >
> > If folks will start a separate discussion with results of the review, I
> see
> > no reasons to reject their contribution, even if we need to revisit our
> > agreements and wait for a couple of days more.
> >
> > Am I missing some reason why dates are so fundamentally important to you?
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > пт, 28 сент. 2018 г. в 12:20, Dmitriy Setrakyan <ds...@apache.org>:
> >
> > > If services is not ready, which it is not, then we should include them
> > into
> > > the next release. There is no need to force them into 2.7. I suggest we
> > > move according to the schedule we all agreed on.
> > >
> > > D.
> > >
> > > On Fri, Sep 28, 2018 at 1:22 AM Dmitriy Pavlov <dp...@gmail.com>
> > > wrote:
> > >
> > > > Yes, so correct statement is "community did not make any decisions
> > about
> > > > services not go to 2.7/ services are out of scope".
> > > >
> > > > If so, please forgive me my confusion.
> > > >
> > > > пт, 28 сент. 2018 г. в 11:19, Vladimir Ozerov <vozerov@gridgain.com
> >:
> > > >
> > > > > Exactly. So correct statement is “it is up to *community* to decide
> > > > whether
> > > > > something goes to 2.7”.
> > > > >
> > > > > пт, 28 сент. 2018 г. в 11:11, Dmitriy Pavlov <
> dpavlov.spb@gmail.com
> > >:
> > > > >
> > > > > > No, it is up to the community to discuss after their review
> > results.
> > > > > >
> > > > > > пт, 28 сент. 2018 г. в 11:09, Vladimir Ozerov <
> > vozerov@gridgain.com
> > > >:
> > > > > >
> > > > > > > Dmitriy,
> > > > > > >
> > > > > > > Did I read your words correctly that it is up to implementor
> of a
> > > > > single
> > > > > > > feature to decide whether release of all other features and
> fixes
> > > to
> > > > be
> > > > > > > delayed?
> > > > > > >
> > > > > > > пт, 28 сент. 2018 г. в 11:00, Dmitriy Pavlov <
> > > dpavlov.spb@gmail.com
> > > > >:
> > > > > > >
> > > > > > > > My point we can wait a bit for services because
> > > > > > > > 1 we are open-minded and we don't have outside pressure to
> do
> > > > > release
> > > > > > in
> > > > > > > > October
> > > > > > > > 2 and services it is not some new feature, which suddenly
> > > appeared
> > > > > in
> > > > > > > > autumn, it is a well known and important feature.
> > > > > > > >
> > > > > > > > So it is up to Vyacheslav, Anton and Nikolay to decide.
> > > > > > > >
> > > > > > > > Decisions can be services are not ready/ready to merge only
> to
> > > > > > > master/ready
> > > > > > > > to merge to master and to 2.7.
> > > > > > > >
> > > > > > > >
> > > > > > > > пт, 28 сент. 2018 г. в 10:46, Vladimir Ozerov <
> > > > vozerov@gridgain.com
> > > > > >:
> > > > > > > >
> > > > > > > > > Dmitry,
> > > > > > > > >
> > > > > > > > > Community agreement was to perform the release in October.
> Of
> > > > > course
> > > > > > we
> > > > > > > > can
> > > > > > > > > wait a bit for services. Then we wait a bit for other cool
> > > > features
> > > > > > > ready
> > > > > > > > > by that time, then again and again, and release will never
> > > > happen.
> > > > > > And
> > > > > > > > > while we are waiting for new features to come, already
> > > completerd
> > > > > > > > features
> > > > > > > > > cannot be used by anyone.
> > > > > > > > >
> > > > > > > > > This is why we have an agreement that if feature is not
> > ready,
> > > it
> > > > > > > should
> > > > > > > > be
> > > > > > > > > moved to future release, instead of shifting release. The
> > sole
> > > > > reason
> > > > > > > to
> > > > > > > > > have strict dates when decisions are made is to let release
> > > > happen.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Fri, Sep 28, 2018 at 2:22 AM Dmitriy Pavlov <
> > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Vladimir, I'm not searching for enemy, and not fighting
> > with
> > > > > you.
> > > > > > > I'm
> > > > > > > > > not
> > > > > > > > > > happy about cases when we are hurrying.
> > > > > > > > > >
> > > > > > > > > > We can't fix test, fill ticket details, can't wait for
> > > > > > contributions
> > > > > > > to
> > > > > > > > > > finish their tasks. It is not best idea to use
> experience
> > > from
> > > > > > > > > commercial
> > > > > > > > > > companies in open source. Are there any pressure outside
> > > > > community?
> > > > > > > Did
> > > > > > > > > > someone promised rest of features to be released at 30
> > > > September?
> > > > > > > > > >
> > > > > > > > > > Let's remember principle do-orcracy, power of those who
> do.
> > > If
> > > > > > > > contribor
> > > > > > > > > > does change and reviewer does review, let's give right of
> > > > making
> > > > > > > > decision
> > > > > > > > > > to them, but not to some closed club of people who
> > privately
> > > > > > discuss
> > > > > > > > > > something.
> > > > > > > > > >
> > > > > > > > > > Sincerely
> > > > > > > > > > Dmitriy Pavlov
> > > > > > > > > >
> > > > > > > > > > чт, 27 сент. 2018 г., 23:42 Vyacheslav Daradur <
> > > > > > daradurvs@gmail.com
> > > > > > > >:
> > > > > > > > > >
> > > > > > > > > > > Hi Igniters!
> > > > > > > > > > >
> > > > > > > > > > > As I have written about Service Grid before [1] I'm
> > > > finalizing
> > > > > > the
> > > > > > > > > > > solution to be sure that implementation is reliable.
> > > > > > > > > > >
> > > > > > > > > > > About including it in 2.7, if we talk that code freeze
> > > > tomorrow
> > > > > > > then
> > > > > > > > > > > the solution is not ready to merge yet.
> > > > > > > > > > > I hope that prereviewers Anton Vinogradov and Nikolay
> > > Izhikov
> > > > > > will
> > > > > > > be
> > > > > > > > > > > able to answer if solution out of scope or not in a
> > couple
> > > of
> > > > > > days.
> > > > > > > > > > >
> > > > > > > > > > > [1]
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-release-td34076.html#a34485
> > > > > > > > > > > On Thu, Sep 27, 2018 at 11:14 PM Dmitriy Pavlov <
> > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > >
> > > > > > > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > Yes, I agree, NPE during WAL flush is definitely a
> > > blocker.
> > > > > > > > > > > >
> > > > > > > > > > > > It is strange why the current test set did not fail
> > after
> > > > > > commit.
> > > > > > > > > > > >
> > > > > > > > > > > > чт, 27 сент. 2018 г. в 21:45, Andrey Kuznetsov <
> > > > > > > stkuzma@gmail.com
> > > > > > > > >:
> > > > > > > > > > > >
> > > > > > > > > > > > > Igniters,
> > > > > > > > > > > > >
> > > > > > > > > > > > > I've bumped into a new bug in WAL manager recently,
> > see
> > > > > [1].
> > > > > > It
> > > > > > > > > looks
> > > > > > > > > > > > > critical enough, and can be a good candidate for
> > fixing
> > > > > > before
> > > > > > > > 2.7
> > > > > > > > > > > release.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Do you agree?
> > > > > > > > > > > > >
> > > > > > > > > > > > > [1]
> > https://issues.apache.org/jira/browse/IGNITE-9731
> > > > > > > > > > > > >
> > > > > > > > > > > > > чт, 27 сент. 2018 г. в 19:45, Dmitriy Pavlov <
> > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > >:
> > > > > > > > > > > > >
> > > > > > > > > > > > > > I need Vhyacheslav's opinion to be absolutely
> sure
> > > what
> > > > > > > status
> > > > > > > > is
> > > > > > > > > > > now.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > We never committed to dates of release, as well.
> I
> > > > don't
> > > > > > > quite
> > > > > > > > > > > understand
> > > > > > > > > > > > > > what can mean 'the community committed to
> > > > doing/releasing
> > > > > > > > > > something'.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > About SG, I also concerned why such a big feature
> > has
> > > > > > quite a
> > > > > > > > few
> > > > > > > > > > > > > > discussions on the list. But it is another story.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > чт, 27 сент. 2018 г. в 19:33, Vladimir Ozerov <
> > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > >:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Folks,
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Please stop looking for enemies everywhere.
> Just
> > > went
> > > > > > > through
> > > > > > > > > > this
> > > > > > > > > > > > > thread
> > > > > > > > > > > > > > > and search for "service" word.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 7:30 PM Denis Magda <
> > > > > > > > dmagda@apache.org
> > > > > > > > > >
> > > > > > > > > > > wrote:
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >> >
> > > > > > > > > > > > > > >> > Denis, as PMC Chair, could you please
> control,
> > > > that
> > > > > > > > Service
> > > > > > > > > > Grid
> > > > > > > > > > > > > > >> > inclusion/exclusion is discussed properly
> > > > according
> > > > > to
> > > > > > > the
> > > > > > > > > > > Apache
> > > > > > > > > > > > > Way.
> > > > > > > > > > > > > > >>
> > > > > > > > > > > > > > >>
> > > > > > > > > > > > > > >> It's fine when committers/contributors have
> > > private
> > > > > > > > > discussions
> > > > > > > > > > > > > related
> > > > > > > > > > > > > > to
> > > > > > > > > > > > > > >> a feature they've been working on. Not
> > everything
> > > > > should
> > > > > > > go
> > > > > > > > > > > through
> > > > > > > > > > > > > the
> > > > > > > > > > > > > > >> dev
> > > > > > > > > > > > > > >> list. Otherwise, it will be inundated.
> However,
> > > > > agree,
> > > > > > > that
> > > > > > > > > > > > > > architectural
> > > > > > > > > > > > > > >> and release decisions need to be done
> publicly.
> > > > > > > > > > > > > > >>
> > > > > > > > > > > > > > >> Speaking about Service Grid, there was a
> > > discussion
> > > > > > where
> > > > > > > I
> > > > > > > > > saw
> > > > > > > > > > > that
> > > > > > > > > > > > > it
> > > > > > > > > > > > > > >> was
> > > > > > > > > > > > > > >> questionable whether it gets added to the
> > release
> > > or
> > > > > > not.
> > > > > > > > > > > > > > >>
> > > > > > > > > > > > > > >> *Vladislav*, could you please shed some light
> on
> > > the
> > > > > > > current
> > > > > > > > > > > status of
> > > > > > > > > > > > > > the
> > > > > > > > > > > > > > >> service grid?
> > > > > > > > > > > > > > >>
> > > > > > > > > > > > > > >> On Thu, Sep 27, 2018 at 9:12 AM Dmitriy
> Pavlov <
> > > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > >> wrote:
> > > > > > > > > > > > > > >>
> > > > > > > > > > > > > > >> > Ok, let's wait for feedback from SG
> > > > > > > Author(s)/Reviewer(s)
> > > > > > > > > > > first. If
> > > > > > > > > > > > > it
> > > > > > > > > > > > > > >> is
> > > > > > > > > > > > > > >> > not ready, ok. But I thought it is almost
> > done.
> > > > > > > > > > > > > > >> >
> > > > > > > > > > > > > > >> > I apologize if I missed some discussion (it
> > can
> > > > > > happen),
> > > > > > > > but
> > > > > > > > > > > > > > >> > According to the statement "our current
> > > agreement"
> > > > > > > > > > > > > > >> > I can suspect some members are making some
> > sort
> > > of
> > > > > > > private
> > > > > > > > > > > > > agreements,
> > > > > > > > > > > > > > >> and
> > > > > > > > > > > > > > >> > do not to discuss it on the list.
> > > > > > > > > > > > > > >> >
> > > > > > > > > > > > > > >> > Let's build consensus here first, and then
> > name
> > > an
> > > > > > > > > agreement.
> > > > > > > > > > > > > > >> >
> > > > > > > > > > > > > > >> > Denis, as PMC Chair, could you please
> control,
> > > > that
> > > > > > > > Service
> > > > > > > > > > Grid
> > > > > > > > > > > > > > >> > inclusion/exclusion is discussed properly
> > > > according
> > > > > to
> > > > > > > the
> > > > > > > > > > > Apache
> > > > > > > > > > > > > Way.
> > > > > > > > > > > > > > >> >
> > > > > > > > > > > > > > >> > чт, 27 сент. 2018 г. в 18:55, Vladimir
> Ozerov
> > <
> > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > >:
> > > > > > > > > > > > > > >> >
> > > > > > > > > > > > > > >> >> Dmitriy,
> > > > > > > > > > > > > > >> >>
> > > > > > > > > > > > > > >> >> This is an outcome of current state of
> > Service
> > > > > Grid -
> > > > > > > it
> > > > > > > > is
> > > > > > > > > > not
> > > > > > > > > > > > > > ready.
> > > > > > > > > > > > > > >> We
> > > > > > > > > > > > > > >> >> never committed to have it to 2.7. Our goal
> > was
> > > > to
> > > > > > try
> > > > > > > to
> > > > > > > > > > > include
> > > > > > > > > > > > > it
> > > > > > > > > > > > > > >> into
> > > > > > > > > > > > > > >> >> 2.7.
> > > > > > > > > > > > > > >> >>
> > > > > > > > > > > > > > >> >> On Thu, Sep 27, 2018 at 6:48 PM Dmitriy
> > Pavlov
> > > <
> > > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > > >> >> wrote:
> > > > > > > > > > > > > > >> >>
> > > > > > > > > > > > > > >> >> > Could you please provide a reference to
> > some
> > > > > > thread?
> > > > > > > > > > > Probably I
> > > > > > > > > > > > > > >> missed
> > > > > > > > > > > > > > >> >> it.
> > > > > > > > > > > > > > >> >> >
> > > > > > > > > > > > > > >> >> > чт, 27 сент. 2018 г. в 18:46, Vladimir
> > > Ozerov <
> > > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > > >> >:
> > > > > > > > > > > > > > >> >> >
> > > > > > > > > > > > > > >> >> > > Our current agreement is that Service
> > Grid
> > > is
> > > > > out
> > > > > > > of
> > > > > > > > > > scope.
> > > > > > > > > > > > > This
> > > > > > > > > > > > > > >> is a
> > > > > > > > > > > > > > >> >> > huge
> > > > > > > > > > > > > > >> >> > > feature, which hasn't entered review
> > stage
> > > so
> > > > > > far,
> > > > > > > We
> > > > > > > > > > will
> > > > > > > > > > > not
> > > > > > > > > > > > > be
> > > > > > > > > > > > > > >> >> able to
> > > > > > > > > > > > > > >> >> > > review/fix/test it properly.
> > > > > > > > > > > > > > >> >> > >
> > > > > > > > > > > > > > >> >> > > On Thu, Sep 27, 2018 at 6:32 PM Dmitriy
> > > > Pavlov
> > > > > <
> > > > > > > > > > > > > > >> dpavlov.spb@gmail.com
> > > > > > > > > > > > > > >> >> >
> > > > > > > > > > > > > > >> >> > > wrote:
> > > > > > > > > > > > > > >> >> > >
> > > > > > > > > > > > > > >> >> > > > I agree, and I prefer four weeks for
> > > > > > > stabilization*
> > > > > > > > > (1
> > > > > > > > > > > Oct -
> > > > > > > > > > > > > 29
> > > > > > > > > > > > > > >> Oct)
> > > > > > > > > > > > > > >> >> > > >
> > > > > > > > > > > > > > >> >> > > > Do I understand it correctly: Service
> > > Grid
> > > > is
> > > > > > > still
> > > > > > > > > in
> > > > > > > > > > > scope,
> > > > > > > > > > > > > > >> isn't
> > > > > > > > > > > > > > >> >> > it? I
> > > > > > > > > > > > > > >> >> > > > find it very important.
> > > > > > > > > > > > > > >> >> > > >
> > > > > > > > > > > > > > >> >> > > > чт, 27 сент. 2018 г. в 18:28, Nikolay
> > > > > Izhikov <
> > > > > > > > > > > > > > >> nizhikov@apache.org
> > > > > > > > > > > > > > >> >> >:
> > > > > > > > > > > > > > >> >> > > >
> > > > > > > > > > > > > > >> >> > > > > Hello, Vova.
> > > > > > > > > > > > > > >> >> > > > >
> > > > > > > > > > > > > > >> >> > > > > Thank you for clear release status.
> > > > > > > > > > > > > > >> >> > > > > I'm +1 for your proposal.
> > > > > > > > > > > > > > >> >> > > > >
> > > > > > > > > > > > > > >> >> > > > > чт, 27 сент. 2018 г., 18:25 Alexey
> > > > > Kuznetsov
> > > > > > <
> > > > > > > > > > > > > > >> >> akuznetsov@apache.org
> > > > > > > > > > > > > > >> >> > >:
> > > > > > > > > > > > > > >> >> > > > >
> > > > > > > > > > > > > > >> >> > > > > > Vova,
> > > > > > > > > > > > > > >> >> > > > > >
> > > > > > > > > > > > > > >> >> > > > > > Huge +1 to do a stabilization.
> > > > > > > > > > > > > > >> >> > > > > >
> > > > > > > > > > > > > > >> >> > > > > >
> > > > > > > > > > > > > > >> >> > > > > > --
> > > > > > > > > > > > > > >> >> > > > > > Alexey Kuznetsov
> > > > > > > > > > > > > > >> >> > > > > >
> > > > > > > > > > > > > > >> >> > > > >
> > > > > > > > > > > > > > >> >> > > >
> > > > > > > > > > > > > > >> >> > >
> > > > > > > > > > > > > > >> >> >
> > > > > > > > > > > > > > >> >>
> > > > > > > > > > > > > > >> >
> > > > > > > > > > > > > > >>
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > --
> > > > > > > > > > > > > Best regards,
> > > > > > > > > > > > > Andrey Kuznetsov.
> > > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > --
> > > > > > > > > > > Best Regards, Vyacheslav D.
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: Apache Ignite 2.7 release
Posted by Vladimir Ozerov <vo...@gridgain.com>.
Importance come from the fact that we agreed on these dates. Neither
community, nor implementors of the feature were against it. And community
already work hard to met that dates: a lot of people already aligned their
plans, a lot very important tickets were moved out of scope to met the
dates.
Nonsense - is to come at the end of coding phase and suggest to replay the
plans all of a sudden. If you find it important - please start a separate
discussion where it will be your responsibility to prove community that we
have to realign our plans and delay release of all other features due to
Service Grid being ahead of schedule. And solution to that problem will be
very simple - to plan another release once Service Grid is coded, tested,
reviewed and benchmarked.
On Fri, Sep 28, 2018 at 2:31 PM Dmitriy Pavlov <dp...@gmail.com>
wrote:
> Hi Dmitriy, Vladimir,
>
> I suggest we stop this nonsense with release dates-pushing because of some
> open question.
>
> Just because you disagreed with any include/exclude something into scope,
> does not mean that whole community disagreed.
>
> If folks will start a separate discussion with results of the review, I see
> no reasons to reject their contribution, even if we need to revisit our
> agreements and wait for a couple of days more.
>
> Am I missing some reason why dates are so fundamentally important to you?
>
> Sincerely,
> Dmitriy Pavlov
>
> пт, 28 сент. 2018 г. в 12:20, Dmitriy Setrakyan <ds...@apache.org>:
>
> > If services is not ready, which it is not, then we should include them
> into
> > the next release. There is no need to force them into 2.7. I suggest we
> > move according to the schedule we all agreed on.
> >
> > D.
> >
> > On Fri, Sep 28, 2018 at 1:22 AM Dmitriy Pavlov <dp...@gmail.com>
> > wrote:
> >
> > > Yes, so correct statement is "community did not make any decisions
> about
> > > services not go to 2.7/ services are out of scope".
> > >
> > > If so, please forgive me my confusion.
> > >
> > > пт, 28 сент. 2018 г. в 11:19, Vladimir Ozerov <vo...@gridgain.com>:
> > >
> > > > Exactly. So correct statement is “it is up to *community* to decide
> > > whether
> > > > something goes to 2.7”.
> > > >
> > > > пт, 28 сент. 2018 г. в 11:11, Dmitriy Pavlov <dpavlov.spb@gmail.com
> >:
> > > >
> > > > > No, it is up to the community to discuss after their review
> results.
> > > > >
> > > > > пт, 28 сент. 2018 г. в 11:09, Vladimir Ozerov <
> vozerov@gridgain.com
> > >:
> > > > >
> > > > > > Dmitriy,
> > > > > >
> > > > > > Did I read your words correctly that it is up to implementor of a
> > > > single
> > > > > > feature to decide whether release of all other features and fixes
> > to
> > > be
> > > > > > delayed?
> > > > > >
> > > > > > пт, 28 сент. 2018 г. в 11:00, Dmitriy Pavlov <
> > dpavlov.spb@gmail.com
> > > >:
> > > > > >
> > > > > > > My point we can wait a bit for services because
> > > > > > > 1 we are open-minded and we don't have outside pressure to do
> > > > release
> > > > > in
> > > > > > > October
> > > > > > > 2 and services it is not some new feature, which suddenly
> > appeared
> > > > in
> > > > > > > autumn, it is a well known and important feature.
> > > > > > >
> > > > > > > So it is up to Vyacheslav, Anton and Nikolay to decide.
> > > > > > >
> > > > > > > Decisions can be services are not ready/ready to merge only to
> > > > > > master/ready
> > > > > > > to merge to master and to 2.7.
> > > > > > >
> > > > > > >
> > > > > > > пт, 28 сент. 2018 г. в 10:46, Vladimir Ozerov <
> > > vozerov@gridgain.com
> > > > >:
> > > > > > >
> > > > > > > > Dmitry,
> > > > > > > >
> > > > > > > > Community agreement was to perform the release in October. Of
> > > > course
> > > > > we
> > > > > > > can
> > > > > > > > wait a bit for services. Then we wait a bit for other cool
> > > features
> > > > > > ready
> > > > > > > > by that time, then again and again, and release will never
> > > happen.
> > > > > And
> > > > > > > > while we are waiting for new features to come, already
> > completerd
> > > > > > > features
> > > > > > > > cannot be used by anyone.
> > > > > > > >
> > > > > > > > This is why we have an agreement that if feature is not
> ready,
> > it
> > > > > > should
> > > > > > > be
> > > > > > > > moved to future release, instead of shifting release. The
> sole
> > > > reason
> > > > > > to
> > > > > > > > have strict dates when decisions are made is to let release
> > > happen.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On Fri, Sep 28, 2018 at 2:22 AM Dmitriy Pavlov <
> > > > > dpavlov.spb@gmail.com>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Vladimir, I'm not searching for enemy, and not fighting
> with
> > > > you.
> > > > > > I'm
> > > > > > > > not
> > > > > > > > > happy about cases when we are hurrying.
> > > > > > > > >
> > > > > > > > > We can't fix test, fill ticket details, can't wait for
> > > > > contributions
> > > > > > to
> > > > > > > > > finish their tasks. It is not best idea to use experience
> > from
> > > > > > > > commercial
> > > > > > > > > companies in open source. Are there any pressure outside
> > > > community?
> > > > > > Did
> > > > > > > > > someone promised rest of features to be released at 30
> > > September?
> > > > > > > > >
> > > > > > > > > Let's remember principle do-orcracy, power of those who do.
> > If
> > > > > > > contribor
> > > > > > > > > does change and reviewer does review, let's give right of
> > > making
> > > > > > > decision
> > > > > > > > > to them, but not to some closed club of people who
> privately
> > > > > discuss
> > > > > > > > > something.
> > > > > > > > >
> > > > > > > > > Sincerely
> > > > > > > > > Dmitriy Pavlov
> > > > > > > > >
> > > > > > > > > чт, 27 сент. 2018 г., 23:42 Vyacheslav Daradur <
> > > > > daradurvs@gmail.com
> > > > > > >:
> > > > > > > > >
> > > > > > > > > > Hi Igniters!
> > > > > > > > > >
> > > > > > > > > > As I have written about Service Grid before [1] I'm
> > > finalizing
> > > > > the
> > > > > > > > > > solution to be sure that implementation is reliable.
> > > > > > > > > >
> > > > > > > > > > About including it in 2.7, if we talk that code freeze
> > > tomorrow
> > > > > > then
> > > > > > > > > > the solution is not ready to merge yet.
> > > > > > > > > > I hope that prereviewers Anton Vinogradov and Nikolay
> > Izhikov
> > > > > will
> > > > > > be
> > > > > > > > > > able to answer if solution out of scope or not in a
> couple
> > of
> > > > > days.
> > > > > > > > > >
> > > > > > > > > > [1]
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-release-td34076.html#a34485
> > > > > > > > > > On Thu, Sep 27, 2018 at 11:14 PM Dmitriy Pavlov <
> > > > > > > dpavlov.spb@gmail.com
> > > > > > > > >
> > > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > Yes, I agree, NPE during WAL flush is definitely a
> > blocker.
> > > > > > > > > > >
> > > > > > > > > > > It is strange why the current test set did not fail
> after
> > > > > commit.
> > > > > > > > > > >
> > > > > > > > > > > чт, 27 сент. 2018 г. в 21:45, Andrey Kuznetsov <
> > > > > > stkuzma@gmail.com
> > > > > > > >:
> > > > > > > > > > >
> > > > > > > > > > > > Igniters,
> > > > > > > > > > > >
> > > > > > > > > > > > I've bumped into a new bug in WAL manager recently,
> see
> > > > [1].
> > > > > It
> > > > > > > > looks
> > > > > > > > > > > > critical enough, and can be a good candidate for
> fixing
> > > > > before
> > > > > > > 2.7
> > > > > > > > > > release.
> > > > > > > > > > > >
> > > > > > > > > > > > Do you agree?
> > > > > > > > > > > >
> > > > > > > > > > > > [1]
> https://issues.apache.org/jira/browse/IGNITE-9731
> > > > > > > > > > > >
> > > > > > > > > > > > чт, 27 сент. 2018 г. в 19:45, Dmitriy Pavlov <
> > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > >:
> > > > > > > > > > > >
> > > > > > > > > > > > > I need Vhyacheslav's opinion to be absolutely sure
> > what
> > > > > > status
> > > > > > > is
> > > > > > > > > > now.
> > > > > > > > > > > > >
> > > > > > > > > > > > > We never committed to dates of release, as well. I
> > > don't
> > > > > > quite
> > > > > > > > > > understand
> > > > > > > > > > > > > what can mean 'the community committed to
> > > doing/releasing
> > > > > > > > > something'.
> > > > > > > > > > > > >
> > > > > > > > > > > > > About SG, I also concerned why such a big feature
> has
> > > > > quite a
> > > > > > > few
> > > > > > > > > > > > > discussions on the list. But it is another story.
> > > > > > > > > > > > >
> > > > > > > > > > > > > чт, 27 сент. 2018 г. в 19:33, Vladimir Ozerov <
> > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > >:
> > > > > > > > > > > > >
> > > > > > > > > > > > > > Folks,
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Please stop looking for enemies everywhere. Just
> > went
> > > > > > through
> > > > > > > > > this
> > > > > > > > > > > > thread
> > > > > > > > > > > > > > and search for "service" word.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > On Thu, Sep 27, 2018 at 7:30 PM Denis Magda <
> > > > > > > dmagda@apache.org
> > > > > > > > >
> > > > > > > > > > wrote:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >> >
> > > > > > > > > > > > > >> > Denis, as PMC Chair, could you please control,
> > > that
> > > > > > > Service
> > > > > > > > > Grid
> > > > > > > > > > > > > >> > inclusion/exclusion is discussed properly
> > > according
> > > > to
> > > > > > the
> > > > > > > > > > Apache
> > > > > > > > > > > > Way.
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> It's fine when committers/contributors have
> > private
> > > > > > > > discussions
> > > > > > > > > > > > related
> > > > > > > > > > > > > to
> > > > > > > > > > > > > >> a feature they've been working on. Not
> everything
> > > > should
> > > > > > go
> > > > > > > > > > through
> > > > > > > > > > > > the
> > > > > > > > > > > > > >> dev
> > > > > > > > > > > > > >> list. Otherwise, it will be inundated. However,
> > > > agree,
> > > > > > that
> > > > > > > > > > > > > architectural
> > > > > > > > > > > > > >> and release decisions need to be done publicly.
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> Speaking about Service Grid, there was a
> > discussion
> > > > > where
> > > > > > I
> > > > > > > > saw
> > > > > > > > > > that
> > > > > > > > > > > > it
> > > > > > > > > > > > > >> was
> > > > > > > > > > > > > >> questionable whether it gets added to the
> release
> > or
> > > > > not.
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> *Vladislav*, could you please shed some light on
> > the
> > > > > > current
> > > > > > > > > > status of
> > > > > > > > > > > > > the
> > > > > > > > > > > > > >> service grid?
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> On Thu, Sep 27, 2018 at 9:12 AM Dmitriy Pavlov <
> > > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > > >
> > > > > > > > > > > > > >> wrote:
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> > Ok, let's wait for feedback from SG
> > > > > > Author(s)/Reviewer(s)
> > > > > > > > > > first. If
> > > > > > > > > > > > it
> > > > > > > > > > > > > >> is
> > > > > > > > > > > > > >> > not ready, ok. But I thought it is almost
> done.
> > > > > > > > > > > > > >> >
> > > > > > > > > > > > > >> > I apologize if I missed some discussion (it
> can
> > > > > happen),
> > > > > > > but
> > > > > > > > > > > > > >> > According to the statement "our current
> > agreement"
> > > > > > > > > > > > > >> > I can suspect some members are making some
> sort
> > of
> > > > > > private
> > > > > > > > > > > > agreements,
> > > > > > > > > > > > > >> and
> > > > > > > > > > > > > >> > do not to discuss it on the list.
> > > > > > > > > > > > > >> >
> > > > > > > > > > > > > >> > Let's build consensus here first, and then
> name
> > an
> > > > > > > > agreement.
> > > > > > > > > > > > > >> >
> > > > > > > > > > > > > >> > Denis, as PMC Chair, could you please control,
> > > that
> > > > > > > Service
> > > > > > > > > Grid
> > > > > > > > > > > > > >> > inclusion/exclusion is discussed properly
> > > according
> > > > to
> > > > > > the
> > > > > > > > > > Apache
> > > > > > > > > > > > Way.
> > > > > > > > > > > > > >> >
> > > > > > > > > > > > > >> > чт, 27 сент. 2018 г. в 18:55, Vladimir Ozerov
> <
> > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > >:
> > > > > > > > > > > > > >> >
> > > > > > > > > > > > > >> >> Dmitriy,
> > > > > > > > > > > > > >> >>
> > > > > > > > > > > > > >> >> This is an outcome of current state of
> Service
> > > > Grid -
> > > > > > it
> > > > > > > is
> > > > > > > > > not
> > > > > > > > > > > > > ready.
> > > > > > > > > > > > > >> We
> > > > > > > > > > > > > >> >> never committed to have it to 2.7. Our goal
> was
> > > to
> > > > > try
> > > > > > to
> > > > > > > > > > include
> > > > > > > > > > > > it
> > > > > > > > > > > > > >> into
> > > > > > > > > > > > > >> >> 2.7.
> > > > > > > > > > > > > >> >>
> > > > > > > > > > > > > >> >> On Thu, Sep 27, 2018 at 6:48 PM Dmitriy
> Pavlov
> > <
> > > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > > >> >> wrote:
> > > > > > > > > > > > > >> >>
> > > > > > > > > > > > > >> >> > Could you please provide a reference to
> some
> > > > > thread?
> > > > > > > > > > Probably I
> > > > > > > > > > > > > >> missed
> > > > > > > > > > > > > >> >> it.
> > > > > > > > > > > > > >> >> >
> > > > > > > > > > > > > >> >> > чт, 27 сент. 2018 г. в 18:46, Vladimir
> > Ozerov <
> > > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > > >> >:
> > > > > > > > > > > > > >> >> >
> > > > > > > > > > > > > >> >> > > Our current agreement is that Service
> Grid
> > is
> > > > out
> > > > > > of
> > > > > > > > > scope.
> > > > > > > > > > > > This
> > > > > > > > > > > > > >> is a
> > > > > > > > > > > > > >> >> > huge
> > > > > > > > > > > > > >> >> > > feature, which hasn't entered review
> stage
> > so
> > > > > far,
> > > > > > We
> > > > > > > > > will
> > > > > > > > > > not
> > > > > > > > > > > > be
> > > > > > > > > > > > > >> >> able to
> > > > > > > > > > > > > >> >> > > review/fix/test it properly.
> > > > > > > > > > > > > >> >> > >
> > > > > > > > > > > > > >> >> > > On Thu, Sep 27, 2018 at 6:32 PM Dmitriy
> > > Pavlov
> > > > <
> > > > > > > > > > > > > >> dpavlov.spb@gmail.com
> > > > > > > > > > > > > >> >> >
> > > > > > > > > > > > > >> >> > > wrote:
> > > > > > > > > > > > > >> >> > >
> > > > > > > > > > > > > >> >> > > > I agree, and I prefer four weeks for
> > > > > > stabilization*
> > > > > > > > (1
> > > > > > > > > > Oct -
> > > > > > > > > > > > 29
> > > > > > > > > > > > > >> Oct)
> > > > > > > > > > > > > >> >> > > >
> > > > > > > > > > > > > >> >> > > > Do I understand it correctly: Service
> > Grid
> > > is
> > > > > > still
> > > > > > > > in
> > > > > > > > > > scope,
> > > > > > > > > > > > > >> isn't
> > > > > > > > > > > > > >> >> > it? I
> > > > > > > > > > > > > >> >> > > > find it very important.
> > > > > > > > > > > > > >> >> > > >
> > > > > > > > > > > > > >> >> > > > чт, 27 сент. 2018 г. в 18:28, Nikolay
> > > > Izhikov <
> > > > > > > > > > > > > >> nizhikov@apache.org
> > > > > > > > > > > > > >> >> >:
> > > > > > > > > > > > > >> >> > > >
> > > > > > > > > > > > > >> >> > > > > Hello, Vova.
> > > > > > > > > > > > > >> >> > > > >
> > > > > > > > > > > > > >> >> > > > > Thank you for clear release status.
> > > > > > > > > > > > > >> >> > > > > I'm +1 for your proposal.
> > > > > > > > > > > > > >> >> > > > >
> > > > > > > > > > > > > >> >> > > > > чт, 27 сент. 2018 г., 18:25 Alexey
> > > > Kuznetsov
> > > > > <
> > > > > > > > > > > > > >> >> akuznetsov@apache.org
> > > > > > > > > > > > > >> >> > >:
> > > > > > > > > > > > > >> >> > > > >
> > > > > > > > > > > > > >> >> > > > > > Vova,
> > > > > > > > > > > > > >> >> > > > > >
> > > > > > > > > > > > > >> >> > > > > > Huge +1 to do a stabilization.
> > > > > > > > > > > > > >> >> > > > > >
> > > > > > > > > > > > > >> >> > > > > >
> > > > > > > > > > > > > >> >> > > > > > --
> > > > > > > > > > > > > >> >> > > > > > Alexey Kuznetsov
> > > > > > > > > > > > > >> >> > > > > >
> > > > > > > > > > > > > >> >> > > > >
> > > > > > > > > > > > > >> >> > > >
> > > > > > > > > > > > > >> >> > >
> > > > > > > > > > > > > >> >> >
> > > > > > > > > > > > > >> >>
> > > > > > > > > > > > > >> >
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > --
> > > > > > > > > > > > Best regards,
> > > > > > > > > > > > Andrey Kuznetsov.
> > > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > --
> > > > > > > > > > Best Regards, Vyacheslav D.
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: Apache Ignite 2.7 release
Posted by Dmitriy Pavlov <dp...@gmail.com>.
Hi Dmitriy, Vladimir,
I suggest we stop this nonsense with release dates-pushing because of some
open question.
Just because you disagreed with any include/exclude something into scope,
does not mean that whole community disagreed.
If folks will start a separate discussion with results of the review, I see
no reasons to reject their contribution, even if we need to revisit our
agreements and wait for a couple of days more.
Am I missing some reason why dates are so fundamentally important to you?
Sincerely,
Dmitriy Pavlov
пт, 28 сент. 2018 г. в 12:20, Dmitriy Setrakyan <ds...@apache.org>:
> If services is not ready, which it is not, then we should include them into
> the next release. There is no need to force them into 2.7. I suggest we
> move according to the schedule we all agreed on.
>
> D.
>
> On Fri, Sep 28, 2018 at 1:22 AM Dmitriy Pavlov <dp...@gmail.com>
> wrote:
>
> > Yes, so correct statement is "community did not make any decisions about
> > services not go to 2.7/ services are out of scope".
> >
> > If so, please forgive me my confusion.
> >
> > пт, 28 сент. 2018 г. в 11:19, Vladimir Ozerov <vo...@gridgain.com>:
> >
> > > Exactly. So correct statement is “it is up to *community* to decide
> > whether
> > > something goes to 2.7”.
> > >
> > > пт, 28 сент. 2018 г. в 11:11, Dmitriy Pavlov <dp...@gmail.com>:
> > >
> > > > No, it is up to the community to discuss after their review results.
> > > >
> > > > пт, 28 сент. 2018 г. в 11:09, Vladimir Ozerov <vozerov@gridgain.com
> >:
> > > >
> > > > > Dmitriy,
> > > > >
> > > > > Did I read your words correctly that it is up to implementor of a
> > > single
> > > > > feature to decide whether release of all other features and fixes
> to
> > be
> > > > > delayed?
> > > > >
> > > > > пт, 28 сент. 2018 г. в 11:00, Dmitriy Pavlov <
> dpavlov.spb@gmail.com
> > >:
> > > > >
> > > > > > My point we can wait a bit for services because
> > > > > > 1 we are open-minded and we don't have outside pressure to do
> > > release
> > > > in
> > > > > > October
> > > > > > 2 and services it is not some new feature, which suddenly
> appeared
> > > in
> > > > > > autumn, it is a well known and important feature.
> > > > > >
> > > > > > So it is up to Vyacheslav, Anton and Nikolay to decide.
> > > > > >
> > > > > > Decisions can be services are not ready/ready to merge only to
> > > > > master/ready
> > > > > > to merge to master and to 2.7.
> > > > > >
> > > > > >
> > > > > > пт, 28 сент. 2018 г. в 10:46, Vladimir Ozerov <
> > vozerov@gridgain.com
> > > >:
> > > > > >
> > > > > > > Dmitry,
> > > > > > >
> > > > > > > Community agreement was to perform the release in October. Of
> > > course
> > > > we
> > > > > > can
> > > > > > > wait a bit for services. Then we wait a bit for other cool
> > features
> > > > > ready
> > > > > > > by that time, then again and again, and release will never
> > happen.
> > > > And
> > > > > > > while we are waiting for new features to come, already
> completerd
> > > > > > features
> > > > > > > cannot be used by anyone.
> > > > > > >
> > > > > > > This is why we have an agreement that if feature is not ready,
> it
> > > > > should
> > > > > > be
> > > > > > > moved to future release, instead of shifting release. The sole
> > > reason
> > > > > to
> > > > > > > have strict dates when decisions are made is to let release
> > happen.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On Fri, Sep 28, 2018 at 2:22 AM Dmitriy Pavlov <
> > > > dpavlov.spb@gmail.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Vladimir, I'm not searching for enemy, and not fighting with
> > > you.
> > > > > I'm
> > > > > > > not
> > > > > > > > happy about cases when we are hurrying.
> > > > > > > >
> > > > > > > > We can't fix test, fill ticket details, can't wait for
> > > > contributions
> > > > > to
> > > > > > > > finish their tasks. It is not best idea to use experience
> from
> > > > > > > commercial
> > > > > > > > companies in open source. Are there any pressure outside
> > > community?
> > > > > Did
> > > > > > > > someone promised rest of features to be released at 30
> > September?
> > > > > > > >
> > > > > > > > Let's remember principle do-orcracy, power of those who do.
> If
> > > > > > contribor
> > > > > > > > does change and reviewer does review, let's give right of
> > making
> > > > > > decision
> > > > > > > > to them, but not to some closed club of people who privately
> > > > discuss
> > > > > > > > something.
> > > > > > > >
> > > > > > > > Sincerely
> > > > > > > > Dmitriy Pavlov
> > > > > > > >
> > > > > > > > чт, 27 сент. 2018 г., 23:42 Vyacheslav Daradur <
> > > > daradurvs@gmail.com
> > > > > >:
> > > > > > > >
> > > > > > > > > Hi Igniters!
> > > > > > > > >
> > > > > > > > > As I have written about Service Grid before [1] I'm
> > finalizing
> > > > the
> > > > > > > > > solution to be sure that implementation is reliable.
> > > > > > > > >
> > > > > > > > > About including it in 2.7, if we talk that code freeze
> > tomorrow
> > > > > then
> > > > > > > > > the solution is not ready to merge yet.
> > > > > > > > > I hope that prereviewers Anton Vinogradov and Nikolay
> Izhikov
> > > > will
> > > > > be
> > > > > > > > > able to answer if solution out of scope or not in a couple
> of
> > > > days.
> > > > > > > > >
> > > > > > > > > [1]
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-release-td34076.html#a34485
> > > > > > > > > On Thu, Sep 27, 2018 at 11:14 PM Dmitriy Pavlov <
> > > > > > dpavlov.spb@gmail.com
> > > > > > > >
> > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > Yes, I agree, NPE during WAL flush is definitely a
> blocker.
> > > > > > > > > >
> > > > > > > > > > It is strange why the current test set did not fail after
> > > > commit.
> > > > > > > > > >
> > > > > > > > > > чт, 27 сент. 2018 г. в 21:45, Andrey Kuznetsov <
> > > > > stkuzma@gmail.com
> > > > > > >:
> > > > > > > > > >
> > > > > > > > > > > Igniters,
> > > > > > > > > > >
> > > > > > > > > > > I've bumped into a new bug in WAL manager recently, see
> > > [1].
> > > > It
> > > > > > > looks
> > > > > > > > > > > critical enough, and can be a good candidate for fixing
> > > > before
> > > > > > 2.7
> > > > > > > > > release.
> > > > > > > > > > >
> > > > > > > > > > > Do you agree?
> > > > > > > > > > >
> > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-9731
> > > > > > > > > > >
> > > > > > > > > > > чт, 27 сент. 2018 г. в 19:45, Dmitriy Pavlov <
> > > > > > > dpavlov.spb@gmail.com
> > > > > > > > >:
> > > > > > > > > > >
> > > > > > > > > > > > I need Vhyacheslav's opinion to be absolutely sure
> what
> > > > > status
> > > > > > is
> > > > > > > > > now.
> > > > > > > > > > > >
> > > > > > > > > > > > We never committed to dates of release, as well. I
> > don't
> > > > > quite
> > > > > > > > > understand
> > > > > > > > > > > > what can mean 'the community committed to
> > doing/releasing
> > > > > > > > something'.
> > > > > > > > > > > >
> > > > > > > > > > > > About SG, I also concerned why such a big feature has
> > > > quite a
> > > > > > few
> > > > > > > > > > > > discussions on the list. But it is another story.
> > > > > > > > > > > >
> > > > > > > > > > > > чт, 27 сент. 2018 г. в 19:33, Vladimir Ozerov <
> > > > > > > > vozerov@gridgain.com
> > > > > > > > > >:
> > > > > > > > > > > >
> > > > > > > > > > > > > Folks,
> > > > > > > > > > > > >
> > > > > > > > > > > > > Please stop looking for enemies everywhere. Just
> went
> > > > > through
> > > > > > > > this
> > > > > > > > > > > thread
> > > > > > > > > > > > > and search for "service" word.
> > > > > > > > > > > > >
> > > > > > > > > > > > > On Thu, Sep 27, 2018 at 7:30 PM Denis Magda <
> > > > > > dmagda@apache.org
> > > > > > > >
> > > > > > > > > wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > >> >
> > > > > > > > > > > > >> > Denis, as PMC Chair, could you please control,
> > that
> > > > > > Service
> > > > > > > > Grid
> > > > > > > > > > > > >> > inclusion/exclusion is discussed properly
> > according
> > > to
> > > > > the
> > > > > > > > > Apache
> > > > > > > > > > > Way.
> > > > > > > > > > > > >>
> > > > > > > > > > > > >>
> > > > > > > > > > > > >> It's fine when committers/contributors have
> private
> > > > > > > discussions
> > > > > > > > > > > related
> > > > > > > > > > > > to
> > > > > > > > > > > > >> a feature they've been working on. Not everything
> > > should
> > > > > go
> > > > > > > > > through
> > > > > > > > > > > the
> > > > > > > > > > > > >> dev
> > > > > > > > > > > > >> list. Otherwise, it will be inundated. However,
> > > agree,
> > > > > that
> > > > > > > > > > > > architectural
> > > > > > > > > > > > >> and release decisions need to be done publicly.
> > > > > > > > > > > > >>
> > > > > > > > > > > > >> Speaking about Service Grid, there was a
> discussion
> > > > where
> > > > > I
> > > > > > > saw
> > > > > > > > > that
> > > > > > > > > > > it
> > > > > > > > > > > > >> was
> > > > > > > > > > > > >> questionable whether it gets added to the release
> or
> > > > not.
> > > > > > > > > > > > >>
> > > > > > > > > > > > >> *Vladislav*, could you please shed some light on
> the
> > > > > current
> > > > > > > > > status of
> > > > > > > > > > > > the
> > > > > > > > > > > > >> service grid?
> > > > > > > > > > > > >>
> > > > > > > > > > > > >> On Thu, Sep 27, 2018 at 9:12 AM Dmitriy Pavlov <
> > > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > > >
> > > > > > > > > > > > >> wrote:
> > > > > > > > > > > > >>
> > > > > > > > > > > > >> > Ok, let's wait for feedback from SG
> > > > > Author(s)/Reviewer(s)
> > > > > > > > > first. If
> > > > > > > > > > > it
> > > > > > > > > > > > >> is
> > > > > > > > > > > > >> > not ready, ok. But I thought it is almost done.
> > > > > > > > > > > > >> >
> > > > > > > > > > > > >> > I apologize if I missed some discussion (it can
> > > > happen),
> > > > > > but
> > > > > > > > > > > > >> > According to the statement "our current
> agreement"
> > > > > > > > > > > > >> > I can suspect some members are making some sort
> of
> > > > > private
> > > > > > > > > > > agreements,
> > > > > > > > > > > > >> and
> > > > > > > > > > > > >> > do not to discuss it on the list.
> > > > > > > > > > > > >> >
> > > > > > > > > > > > >> > Let's build consensus here first, and then name
> an
> > > > > > > agreement.
> > > > > > > > > > > > >> >
> > > > > > > > > > > > >> > Denis, as PMC Chair, could you please control,
> > that
> > > > > > Service
> > > > > > > > Grid
> > > > > > > > > > > > >> > inclusion/exclusion is discussed properly
> > according
> > > to
> > > > > the
> > > > > > > > > Apache
> > > > > > > > > > > Way.
> > > > > > > > > > > > >> >
> > > > > > > > > > > > >> > чт, 27 сент. 2018 г. в 18:55, Vladimir Ozerov <
> > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > >:
> > > > > > > > > > > > >> >
> > > > > > > > > > > > >> >> Dmitriy,
> > > > > > > > > > > > >> >>
> > > > > > > > > > > > >> >> This is an outcome of current state of Service
> > > Grid -
> > > > > it
> > > > > > is
> > > > > > > > not
> > > > > > > > > > > > ready.
> > > > > > > > > > > > >> We
> > > > > > > > > > > > >> >> never committed to have it to 2.7. Our goal was
> > to
> > > > try
> > > > > to
> > > > > > > > > include
> > > > > > > > > > > it
> > > > > > > > > > > > >> into
> > > > > > > > > > > > >> >> 2.7.
> > > > > > > > > > > > >> >>
> > > > > > > > > > > > >> >> On Thu, Sep 27, 2018 at 6:48 PM Dmitriy Pavlov
> <
> > > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > > >> >> wrote:
> > > > > > > > > > > > >> >>
> > > > > > > > > > > > >> >> > Could you please provide a reference to some
> > > > thread?
> > > > > > > > > Probably I
> > > > > > > > > > > > >> missed
> > > > > > > > > > > > >> >> it.
> > > > > > > > > > > > >> >> >
> > > > > > > > > > > > >> >> > чт, 27 сент. 2018 г. в 18:46, Vladimir
> Ozerov <
> > > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > > >> >:
> > > > > > > > > > > > >> >> >
> > > > > > > > > > > > >> >> > > Our current agreement is that Service Grid
> is
> > > out
> > > > > of
> > > > > > > > scope.
> > > > > > > > > > > This
> > > > > > > > > > > > >> is a
> > > > > > > > > > > > >> >> > huge
> > > > > > > > > > > > >> >> > > feature, which hasn't entered review stage
> so
> > > > far,
> > > > > We
> > > > > > > > will
> > > > > > > > > not
> > > > > > > > > > > be
> > > > > > > > > > > > >> >> able to
> > > > > > > > > > > > >> >> > > review/fix/test it properly.
> > > > > > > > > > > > >> >> > >
> > > > > > > > > > > > >> >> > > On Thu, Sep 27, 2018 at 6:32 PM Dmitriy
> > Pavlov
> > > <
> > > > > > > > > > > > >> dpavlov.spb@gmail.com
> > > > > > > > > > > > >> >> >
> > > > > > > > > > > > >> >> > > wrote:
> > > > > > > > > > > > >> >> > >
> > > > > > > > > > > > >> >> > > > I agree, and I prefer four weeks for
> > > > > stabilization*
> > > > > > > (1
> > > > > > > > > Oct -
> > > > > > > > > > > 29
> > > > > > > > > > > > >> Oct)
> > > > > > > > > > > > >> >> > > >
> > > > > > > > > > > > >> >> > > > Do I understand it correctly: Service
> Grid
> > is
> > > > > still
> > > > > > > in
> > > > > > > > > scope,
> > > > > > > > > > > > >> isn't
> > > > > > > > > > > > >> >> > it? I
> > > > > > > > > > > > >> >> > > > find it very important.
> > > > > > > > > > > > >> >> > > >
> > > > > > > > > > > > >> >> > > > чт, 27 сент. 2018 г. в 18:28, Nikolay
> > > Izhikov <
> > > > > > > > > > > > >> nizhikov@apache.org
> > > > > > > > > > > > >> >> >:
> > > > > > > > > > > > >> >> > > >
> > > > > > > > > > > > >> >> > > > > Hello, Vova.
> > > > > > > > > > > > >> >> > > > >
> > > > > > > > > > > > >> >> > > > > Thank you for clear release status.
> > > > > > > > > > > > >> >> > > > > I'm +1 for your proposal.
> > > > > > > > > > > > >> >> > > > >
> > > > > > > > > > > > >> >> > > > > чт, 27 сент. 2018 г., 18:25 Alexey
> > > Kuznetsov
> > > > <
> > > > > > > > > > > > >> >> akuznetsov@apache.org
> > > > > > > > > > > > >> >> > >:
> > > > > > > > > > > > >> >> > > > >
> > > > > > > > > > > > >> >> > > > > > Vova,
> > > > > > > > > > > > >> >> > > > > >
> > > > > > > > > > > > >> >> > > > > > Huge +1 to do a stabilization.
> > > > > > > > > > > > >> >> > > > > >
> > > > > > > > > > > > >> >> > > > > >
> > > > > > > > > > > > >> >> > > > > > --
> > > > > > > > > > > > >> >> > > > > > Alexey Kuznetsov
> > > > > > > > > > > > >> >> > > > > >
> > > > > > > > > > > > >> >> > > > >
> > > > > > > > > > > > >> >> > > >
> > > > > > > > > > > > >> >> > >
> > > > > > > > > > > > >> >> >
> > > > > > > > > > > > >> >>
> > > > > > > > > > > > >> >
> > > > > > > > > > > > >>
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > --
> > > > > > > > > > > Best regards,
> > > > > > > > > > > Andrey Kuznetsov.
> > > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > Best Regards, Vyacheslav D.
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: Apache Ignite 2.7 release
Posted by Dmitriy Setrakyan <ds...@apache.org>.
If services is not ready, which it is not, then we should include them into
the next release. There is no need to force them into 2.7. I suggest we
move according to the schedule we all agreed on.
D.
On Fri, Sep 28, 2018 at 1:22 AM Dmitriy Pavlov <dp...@gmail.com>
wrote:
> Yes, so correct statement is "community did not make any decisions about
> services not go to 2.7/ services are out of scope".
>
> If so, please forgive me my confusion.
>
> пт, 28 сент. 2018 г. в 11:19, Vladimir Ozerov <vo...@gridgain.com>:
>
> > Exactly. So correct statement is “it is up to *community* to decide
> whether
> > something goes to 2.7”.
> >
> > пт, 28 сент. 2018 г. в 11:11, Dmitriy Pavlov <dp...@gmail.com>:
> >
> > > No, it is up to the community to discuss after their review results.
> > >
> > > пт, 28 сент. 2018 г. в 11:09, Vladimir Ozerov <vo...@gridgain.com>:
> > >
> > > > Dmitriy,
> > > >
> > > > Did I read your words correctly that it is up to implementor of a
> > single
> > > > feature to decide whether release of all other features and fixes to
> be
> > > > delayed?
> > > >
> > > > пт, 28 сент. 2018 г. в 11:00, Dmitriy Pavlov <dpavlov.spb@gmail.com
> >:
> > > >
> > > > > My point we can wait a bit for services because
> > > > > 1 we are open-minded and we don't have outside pressure to do
> > release
> > > in
> > > > > October
> > > > > 2 and services it is not some new feature, which suddenly appeared
> > in
> > > > > autumn, it is a well known and important feature.
> > > > >
> > > > > So it is up to Vyacheslav, Anton and Nikolay to decide.
> > > > >
> > > > > Decisions can be services are not ready/ready to merge only to
> > > > master/ready
> > > > > to merge to master and to 2.7.
> > > > >
> > > > >
> > > > > пт, 28 сент. 2018 г. в 10:46, Vladimir Ozerov <
> vozerov@gridgain.com
> > >:
> > > > >
> > > > > > Dmitry,
> > > > > >
> > > > > > Community agreement was to perform the release in October. Of
> > course
> > > we
> > > > > can
> > > > > > wait a bit for services. Then we wait a bit for other cool
> features
> > > > ready
> > > > > > by that time, then again and again, and release will never
> happen.
> > > And
> > > > > > while we are waiting for new features to come, already completerd
> > > > > features
> > > > > > cannot be used by anyone.
> > > > > >
> > > > > > This is why we have an agreement that if feature is not ready, it
> > > > should
> > > > > be
> > > > > > moved to future release, instead of shifting release. The sole
> > reason
> > > > to
> > > > > > have strict dates when decisions are made is to let release
> happen.
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Fri, Sep 28, 2018 at 2:22 AM Dmitriy Pavlov <
> > > dpavlov.spb@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Vladimir, I'm not searching for enemy, and not fighting with
> > you.
> > > > I'm
> > > > > > not
> > > > > > > happy about cases when we are hurrying.
> > > > > > >
> > > > > > > We can't fix test, fill ticket details, can't wait for
> > > contributions
> > > > to
> > > > > > > finish their tasks. It is not best idea to use experience from
> > > > > > commercial
> > > > > > > companies in open source. Are there any pressure outside
> > community?
> > > > Did
> > > > > > > someone promised rest of features to be released at 30
> September?
> > > > > > >
> > > > > > > Let's remember principle do-orcracy, power of those who do. If
> > > > > contribor
> > > > > > > does change and reviewer does review, let's give right of
> making
> > > > > decision
> > > > > > > to them, but not to some closed club of people who privately
> > > discuss
> > > > > > > something.
> > > > > > >
> > > > > > > Sincerely
> > > > > > > Dmitriy Pavlov
> > > > > > >
> > > > > > > чт, 27 сент. 2018 г., 23:42 Vyacheslav Daradur <
> > > daradurvs@gmail.com
> > > > >:
> > > > > > >
> > > > > > > > Hi Igniters!
> > > > > > > >
> > > > > > > > As I have written about Service Grid before [1] I'm
> finalizing
> > > the
> > > > > > > > solution to be sure that implementation is reliable.
> > > > > > > >
> > > > > > > > About including it in 2.7, if we talk that code freeze
> tomorrow
> > > > then
> > > > > > > > the solution is not ready to merge yet.
> > > > > > > > I hope that prereviewers Anton Vinogradov and Nikolay Izhikov
> > > will
> > > > be
> > > > > > > > able to answer if solution out of scope or not in a couple of
> > > days.
> > > > > > > >
> > > > > > > > [1]
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-release-td34076.html#a34485
> > > > > > > > On Thu, Sep 27, 2018 at 11:14 PM Dmitriy Pavlov <
> > > > > dpavlov.spb@gmail.com
> > > > > > >
> > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > Yes, I agree, NPE during WAL flush is definitely a blocker.
> > > > > > > > >
> > > > > > > > > It is strange why the current test set did not fail after
> > > commit.
> > > > > > > > >
> > > > > > > > > чт, 27 сент. 2018 г. в 21:45, Andrey Kuznetsov <
> > > > stkuzma@gmail.com
> > > > > >:
> > > > > > > > >
> > > > > > > > > > Igniters,
> > > > > > > > > >
> > > > > > > > > > I've bumped into a new bug in WAL manager recently, see
> > [1].
> > > It
> > > > > > looks
> > > > > > > > > > critical enough, and can be a good candidate for fixing
> > > before
> > > > > 2.7
> > > > > > > > release.
> > > > > > > > > >
> > > > > > > > > > Do you agree?
> > > > > > > > > >
> > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-9731
> > > > > > > > > >
> > > > > > > > > > чт, 27 сент. 2018 г. в 19:45, Dmitriy Pavlov <
> > > > > > dpavlov.spb@gmail.com
> > > > > > > >:
> > > > > > > > > >
> > > > > > > > > > > I need Vhyacheslav's opinion to be absolutely sure what
> > > > status
> > > > > is
> > > > > > > > now.
> > > > > > > > > > >
> > > > > > > > > > > We never committed to dates of release, as well. I
> don't
> > > > quite
> > > > > > > > understand
> > > > > > > > > > > what can mean 'the community committed to
> doing/releasing
> > > > > > > something'.
> > > > > > > > > > >
> > > > > > > > > > > About SG, I also concerned why such a big feature has
> > > quite a
> > > > > few
> > > > > > > > > > > discussions on the list. But it is another story.
> > > > > > > > > > >
> > > > > > > > > > > чт, 27 сент. 2018 г. в 19:33, Vladimir Ozerov <
> > > > > > > vozerov@gridgain.com
> > > > > > > > >:
> > > > > > > > > > >
> > > > > > > > > > > > Folks,
> > > > > > > > > > > >
> > > > > > > > > > > > Please stop looking for enemies everywhere. Just went
> > > > through
> > > > > > > this
> > > > > > > > > > thread
> > > > > > > > > > > > and search for "service" word.
> > > > > > > > > > > >
> > > > > > > > > > > > On Thu, Sep 27, 2018 at 7:30 PM Denis Magda <
> > > > > dmagda@apache.org
> > > > > > >
> > > > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > >> >
> > > > > > > > > > > >> > Denis, as PMC Chair, could you please control,
> that
> > > > > Service
> > > > > > > Grid
> > > > > > > > > > > >> > inclusion/exclusion is discussed properly
> according
> > to
> > > > the
> > > > > > > > Apache
> > > > > > > > > > Way.
> > > > > > > > > > > >>
> > > > > > > > > > > >>
> > > > > > > > > > > >> It's fine when committers/contributors have private
> > > > > > discussions
> > > > > > > > > > related
> > > > > > > > > > > to
> > > > > > > > > > > >> a feature they've been working on. Not everything
> > should
> > > > go
> > > > > > > > through
> > > > > > > > > > the
> > > > > > > > > > > >> dev
> > > > > > > > > > > >> list. Otherwise, it will be inundated. However,
> > agree,
> > > > that
> > > > > > > > > > > architectural
> > > > > > > > > > > >> and release decisions need to be done publicly.
> > > > > > > > > > > >>
> > > > > > > > > > > >> Speaking about Service Grid, there was a discussion
> > > where
> > > > I
> > > > > > saw
> > > > > > > > that
> > > > > > > > > > it
> > > > > > > > > > > >> was
> > > > > > > > > > > >> questionable whether it gets added to the release or
> > > not.
> > > > > > > > > > > >>
> > > > > > > > > > > >> *Vladislav*, could you please shed some light on the
> > > > current
> > > > > > > > status of
> > > > > > > > > > > the
> > > > > > > > > > > >> service grid?
> > > > > > > > > > > >>
> > > > > > > > > > > >> On Thu, Sep 27, 2018 at 9:12 AM Dmitriy Pavlov <
> > > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > > >
> > > > > > > > > > > >> wrote:
> > > > > > > > > > > >>
> > > > > > > > > > > >> > Ok, let's wait for feedback from SG
> > > > Author(s)/Reviewer(s)
> > > > > > > > first. If
> > > > > > > > > > it
> > > > > > > > > > > >> is
> > > > > > > > > > > >> > not ready, ok. But I thought it is almost done.
> > > > > > > > > > > >> >
> > > > > > > > > > > >> > I apologize if I missed some discussion (it can
> > > happen),
> > > > > but
> > > > > > > > > > > >> > According to the statement "our current agreement"
> > > > > > > > > > > >> > I can suspect some members are making some sort of
> > > > private
> > > > > > > > > > agreements,
> > > > > > > > > > > >> and
> > > > > > > > > > > >> > do not to discuss it on the list.
> > > > > > > > > > > >> >
> > > > > > > > > > > >> > Let's build consensus here first, and then name an
> > > > > > agreement.
> > > > > > > > > > > >> >
> > > > > > > > > > > >> > Denis, as PMC Chair, could you please control,
> that
> > > > > Service
> > > > > > > Grid
> > > > > > > > > > > >> > inclusion/exclusion is discussed properly
> according
> > to
> > > > the
> > > > > > > > Apache
> > > > > > > > > > Way.
> > > > > > > > > > > >> >
> > > > > > > > > > > >> > чт, 27 сент. 2018 г. в 18:55, Vladimir Ozerov <
> > > > > > > > vozerov@gridgain.com
> > > > > > > > > > >:
> > > > > > > > > > > >> >
> > > > > > > > > > > >> >> Dmitriy,
> > > > > > > > > > > >> >>
> > > > > > > > > > > >> >> This is an outcome of current state of Service
> > Grid -
> > > > it
> > > > > is
> > > > > > > not
> > > > > > > > > > > ready.
> > > > > > > > > > > >> We
> > > > > > > > > > > >> >> never committed to have it to 2.7. Our goal was
> to
> > > try
> > > > to
> > > > > > > > include
> > > > > > > > > > it
> > > > > > > > > > > >> into
> > > > > > > > > > > >> >> 2.7.
> > > > > > > > > > > >> >>
> > > > > > > > > > > >> >> On Thu, Sep 27, 2018 at 6:48 PM Dmitriy Pavlov <
> > > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > > >> >> wrote:
> > > > > > > > > > > >> >>
> > > > > > > > > > > >> >> > Could you please provide a reference to some
> > > thread?
> > > > > > > > Probably I
> > > > > > > > > > > >> missed
> > > > > > > > > > > >> >> it.
> > > > > > > > > > > >> >> >
> > > > > > > > > > > >> >> > чт, 27 сент. 2018 г. в 18:46, Vladimir Ozerov <
> > > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > > >> >:
> > > > > > > > > > > >> >> >
> > > > > > > > > > > >> >> > > Our current agreement is that Service Grid is
> > out
> > > > of
> > > > > > > scope.
> > > > > > > > > > This
> > > > > > > > > > > >> is a
> > > > > > > > > > > >> >> > huge
> > > > > > > > > > > >> >> > > feature, which hasn't entered review stage so
> > > far,
> > > > We
> > > > > > > will
> > > > > > > > not
> > > > > > > > > > be
> > > > > > > > > > > >> >> able to
> > > > > > > > > > > >> >> > > review/fix/test it properly.
> > > > > > > > > > > >> >> > >
> > > > > > > > > > > >> >> > > On Thu, Sep 27, 2018 at 6:32 PM Dmitriy
> Pavlov
> > <
> > > > > > > > > > > >> dpavlov.spb@gmail.com
> > > > > > > > > > > >> >> >
> > > > > > > > > > > >> >> > > wrote:
> > > > > > > > > > > >> >> > >
> > > > > > > > > > > >> >> > > > I agree, and I prefer four weeks for
> > > > stabilization*
> > > > > > (1
> > > > > > > > Oct -
> > > > > > > > > > 29
> > > > > > > > > > > >> Oct)
> > > > > > > > > > > >> >> > > >
> > > > > > > > > > > >> >> > > > Do I understand it correctly: Service Grid
> is
> > > > still
> > > > > > in
> > > > > > > > scope,
> > > > > > > > > > > >> isn't
> > > > > > > > > > > >> >> > it? I
> > > > > > > > > > > >> >> > > > find it very important.
> > > > > > > > > > > >> >> > > >
> > > > > > > > > > > >> >> > > > чт, 27 сент. 2018 г. в 18:28, Nikolay
> > Izhikov <
> > > > > > > > > > > >> nizhikov@apache.org
> > > > > > > > > > > >> >> >:
> > > > > > > > > > > >> >> > > >
> > > > > > > > > > > >> >> > > > > Hello, Vova.
> > > > > > > > > > > >> >> > > > >
> > > > > > > > > > > >> >> > > > > Thank you for clear release status.
> > > > > > > > > > > >> >> > > > > I'm +1 for your proposal.
> > > > > > > > > > > >> >> > > > >
> > > > > > > > > > > >> >> > > > > чт, 27 сент. 2018 г., 18:25 Alexey
> > Kuznetsov
> > > <
> > > > > > > > > > > >> >> akuznetsov@apache.org
> > > > > > > > > > > >> >> > >:
> > > > > > > > > > > >> >> > > > >
> > > > > > > > > > > >> >> > > > > > Vova,
> > > > > > > > > > > >> >> > > > > >
> > > > > > > > > > > >> >> > > > > > Huge +1 to do a stabilization.
> > > > > > > > > > > >> >> > > > > >
> > > > > > > > > > > >> >> > > > > >
> > > > > > > > > > > >> >> > > > > > --
> > > > > > > > > > > >> >> > > > > > Alexey Kuznetsov
> > > > > > > > > > > >> >> > > > > >
> > > > > > > > > > > >> >> > > > >
> > > > > > > > > > > >> >> > > >
> > > > > > > > > > > >> >> > >
> > > > > > > > > > > >> >> >
> > > > > > > > > > > >> >>
> > > > > > > > > > > >> >
> > > > > > > > > > > >>
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > --
> > > > > > > > > > Best regards,
> > > > > > > > > > Andrey Kuznetsov.
> > > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > Best Regards, Vyacheslav D.
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: Apache Ignite 2.7 release
Posted by Dmitriy Pavlov <dp...@gmail.com>.
Yes, so correct statement is "community did not make any decisions about
services not go to 2.7/ services are out of scope".
If so, please forgive me my confusion.
пт, 28 сент. 2018 г. в 11:19, Vladimir Ozerov <vo...@gridgain.com>:
> Exactly. So correct statement is “it is up to *community* to decide whether
> something goes to 2.7”.
>
> пт, 28 сент. 2018 г. в 11:11, Dmitriy Pavlov <dp...@gmail.com>:
>
> > No, it is up to the community to discuss after their review results.
> >
> > пт, 28 сент. 2018 г. в 11:09, Vladimir Ozerov <vo...@gridgain.com>:
> >
> > > Dmitriy,
> > >
> > > Did I read your words correctly that it is up to implementor of a
> single
> > > feature to decide whether release of all other features and fixes to be
> > > delayed?
> > >
> > > пт, 28 сент. 2018 г. в 11:00, Dmitriy Pavlov <dp...@gmail.com>:
> > >
> > > > My point we can wait a bit for services because
> > > > 1 we are open-minded and we don't have outside pressure to do
> release
> > in
> > > > October
> > > > 2 and services it is not some new feature, which suddenly appeared
> in
> > > > autumn, it is a well known and important feature.
> > > >
> > > > So it is up to Vyacheslav, Anton and Nikolay to decide.
> > > >
> > > > Decisions can be services are not ready/ready to merge only to
> > > master/ready
> > > > to merge to master and to 2.7.
> > > >
> > > >
> > > > пт, 28 сент. 2018 г. в 10:46, Vladimir Ozerov <vozerov@gridgain.com
> >:
> > > >
> > > > > Dmitry,
> > > > >
> > > > > Community agreement was to perform the release in October. Of
> course
> > we
> > > > can
> > > > > wait a bit for services. Then we wait a bit for other cool features
> > > ready
> > > > > by that time, then again and again, and release will never happen.
> > And
> > > > > while we are waiting for new features to come, already completerd
> > > > features
> > > > > cannot be used by anyone.
> > > > >
> > > > > This is why we have an agreement that if feature is not ready, it
> > > should
> > > > be
> > > > > moved to future release, instead of shifting release. The sole
> reason
> > > to
> > > > > have strict dates when decisions are made is to let release happen.
> > > > >
> > > > >
> > > > >
> > > > > On Fri, Sep 28, 2018 at 2:22 AM Dmitriy Pavlov <
> > dpavlov.spb@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Vladimir, I'm not searching for enemy, and not fighting with
> you.
> > > I'm
> > > > > not
> > > > > > happy about cases when we are hurrying.
> > > > > >
> > > > > > We can't fix test, fill ticket details, can't wait for
> > contributions
> > > to
> > > > > > finish their tasks. It is not best idea to use experience from
> > > > > commercial
> > > > > > companies in open source. Are there any pressure outside
> community?
> > > Did
> > > > > > someone promised rest of features to be released at 30 September?
> > > > > >
> > > > > > Let's remember principle do-orcracy, power of those who do. If
> > > > contribor
> > > > > > does change and reviewer does review, let's give right of making
> > > > decision
> > > > > > to them, but not to some closed club of people who privately
> > discuss
> > > > > > something.
> > > > > >
> > > > > > Sincerely
> > > > > > Dmitriy Pavlov
> > > > > >
> > > > > > чт, 27 сент. 2018 г., 23:42 Vyacheslav Daradur <
> > daradurvs@gmail.com
> > > >:
> > > > > >
> > > > > > > Hi Igniters!
> > > > > > >
> > > > > > > As I have written about Service Grid before [1] I'm finalizing
> > the
> > > > > > > solution to be sure that implementation is reliable.
> > > > > > >
> > > > > > > About including it in 2.7, if we talk that code freeze tomorrow
> > > then
> > > > > > > the solution is not ready to merge yet.
> > > > > > > I hope that prereviewers Anton Vinogradov and Nikolay Izhikov
> > will
> > > be
> > > > > > > able to answer if solution out of scope or not in a couple of
> > days.
> > > > > > >
> > > > > > > [1]
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-release-td34076.html#a34485
> > > > > > > On Thu, Sep 27, 2018 at 11:14 PM Dmitriy Pavlov <
> > > > dpavlov.spb@gmail.com
> > > > > >
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > Yes, I agree, NPE during WAL flush is definitely a blocker.
> > > > > > > >
> > > > > > > > It is strange why the current test set did not fail after
> > commit.
> > > > > > > >
> > > > > > > > чт, 27 сент. 2018 г. в 21:45, Andrey Kuznetsov <
> > > stkuzma@gmail.com
> > > > >:
> > > > > > > >
> > > > > > > > > Igniters,
> > > > > > > > >
> > > > > > > > > I've bumped into a new bug in WAL manager recently, see
> [1].
> > It
> > > > > looks
> > > > > > > > > critical enough, and can be a good candidate for fixing
> > before
> > > > 2.7
> > > > > > > release.
> > > > > > > > >
> > > > > > > > > Do you agree?
> > > > > > > > >
> > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-9731
> > > > > > > > >
> > > > > > > > > чт, 27 сент. 2018 г. в 19:45, Dmitriy Pavlov <
> > > > > dpavlov.spb@gmail.com
> > > > > > >:
> > > > > > > > >
> > > > > > > > > > I need Vhyacheslav's opinion to be absolutely sure what
> > > status
> > > > is
> > > > > > > now.
> > > > > > > > > >
> > > > > > > > > > We never committed to dates of release, as well. I don't
> > > quite
> > > > > > > understand
> > > > > > > > > > what can mean 'the community committed to doing/releasing
> > > > > > something'.
> > > > > > > > > >
> > > > > > > > > > About SG, I also concerned why such a big feature has
> > quite a
> > > > few
> > > > > > > > > > discussions on the list. But it is another story.
> > > > > > > > > >
> > > > > > > > > > чт, 27 сент. 2018 г. в 19:33, Vladimir Ozerov <
> > > > > > vozerov@gridgain.com
> > > > > > > >:
> > > > > > > > > >
> > > > > > > > > > > Folks,
> > > > > > > > > > >
> > > > > > > > > > > Please stop looking for enemies everywhere. Just went
> > > through
> > > > > > this
> > > > > > > > > thread
> > > > > > > > > > > and search for "service" word.
> > > > > > > > > > >
> > > > > > > > > > > On Thu, Sep 27, 2018 at 7:30 PM Denis Magda <
> > > > dmagda@apache.org
> > > > > >
> > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > >> >
> > > > > > > > > > >> > Denis, as PMC Chair, could you please control, that
> > > > Service
> > > > > > Grid
> > > > > > > > > > >> > inclusion/exclusion is discussed properly according
> to
> > > the
> > > > > > > Apache
> > > > > > > > > Way.
> > > > > > > > > > >>
> > > > > > > > > > >>
> > > > > > > > > > >> It's fine when committers/contributors have private
> > > > > discussions
> > > > > > > > > related
> > > > > > > > > > to
> > > > > > > > > > >> a feature they've been working on. Not everything
> should
> > > go
> > > > > > > through
> > > > > > > > > the
> > > > > > > > > > >> dev
> > > > > > > > > > >> list. Otherwise, it will be inundated. However,
> agree,
> > > that
> > > > > > > > > > architectural
> > > > > > > > > > >> and release decisions need to be done publicly.
> > > > > > > > > > >>
> > > > > > > > > > >> Speaking about Service Grid, there was a discussion
> > where
> > > I
> > > > > saw
> > > > > > > that
> > > > > > > > > it
> > > > > > > > > > >> was
> > > > > > > > > > >> questionable whether it gets added to the release or
> > not.
> > > > > > > > > > >>
> > > > > > > > > > >> *Vladislav*, could you please shed some light on the
> > > current
> > > > > > > status of
> > > > > > > > > > the
> > > > > > > > > > >> service grid?
> > > > > > > > > > >>
> > > > > > > > > > >> On Thu, Sep 27, 2018 at 9:12 AM Dmitriy Pavlov <
> > > > > > > dpavlov.spb@gmail.com
> > > > > > > > > >
> > > > > > > > > > >> wrote:
> > > > > > > > > > >>
> > > > > > > > > > >> > Ok, let's wait for feedback from SG
> > > Author(s)/Reviewer(s)
> > > > > > > first. If
> > > > > > > > > it
> > > > > > > > > > >> is
> > > > > > > > > > >> > not ready, ok. But I thought it is almost done.
> > > > > > > > > > >> >
> > > > > > > > > > >> > I apologize if I missed some discussion (it can
> > happen),
> > > > but
> > > > > > > > > > >> > According to the statement "our current agreement"
> > > > > > > > > > >> > I can suspect some members are making some sort of
> > > private
> > > > > > > > > agreements,
> > > > > > > > > > >> and
> > > > > > > > > > >> > do not to discuss it on the list.
> > > > > > > > > > >> >
> > > > > > > > > > >> > Let's build consensus here first, and then name an
> > > > > agreement.
> > > > > > > > > > >> >
> > > > > > > > > > >> > Denis, as PMC Chair, could you please control, that
> > > > Service
> > > > > > Grid
> > > > > > > > > > >> > inclusion/exclusion is discussed properly according
> to
> > > the
> > > > > > > Apache
> > > > > > > > > Way.
> > > > > > > > > > >> >
> > > > > > > > > > >> > чт, 27 сент. 2018 г. в 18:55, Vladimir Ozerov <
> > > > > > > vozerov@gridgain.com
> > > > > > > > > >:
> > > > > > > > > > >> >
> > > > > > > > > > >> >> Dmitriy,
> > > > > > > > > > >> >>
> > > > > > > > > > >> >> This is an outcome of current state of Service
> Grid -
> > > it
> > > > is
> > > > > > not
> > > > > > > > > > ready.
> > > > > > > > > > >> We
> > > > > > > > > > >> >> never committed to have it to 2.7. Our goal was to
> > try
> > > to
> > > > > > > include
> > > > > > > > > it
> > > > > > > > > > >> into
> > > > > > > > > > >> >> 2.7.
> > > > > > > > > > >> >>
> > > > > > > > > > >> >> On Thu, Sep 27, 2018 at 6:48 PM Dmitriy Pavlov <
> > > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > > >> >> wrote:
> > > > > > > > > > >> >>
> > > > > > > > > > >> >> > Could you please provide a reference to some
> > thread?
> > > > > > > Probably I
> > > > > > > > > > >> missed
> > > > > > > > > > >> >> it.
> > > > > > > > > > >> >> >
> > > > > > > > > > >> >> > чт, 27 сент. 2018 г. в 18:46, Vladimir Ozerov <
> > > > > > > > > > vozerov@gridgain.com
> > > > > > > > > > >> >:
> > > > > > > > > > >> >> >
> > > > > > > > > > >> >> > > Our current agreement is that Service Grid is
> out
> > > of
> > > > > > scope.
> > > > > > > > > This
> > > > > > > > > > >> is a
> > > > > > > > > > >> >> > huge
> > > > > > > > > > >> >> > > feature, which hasn't entered review stage so
> > far,
> > > We
> > > > > > will
> > > > > > > not
> > > > > > > > > be
> > > > > > > > > > >> >> able to
> > > > > > > > > > >> >> > > review/fix/test it properly.
> > > > > > > > > > >> >> > >
> > > > > > > > > > >> >> > > On Thu, Sep 27, 2018 at 6:32 PM Dmitriy Pavlov
> <
> > > > > > > > > > >> dpavlov.spb@gmail.com
> > > > > > > > > > >> >> >
> > > > > > > > > > >> >> > > wrote:
> > > > > > > > > > >> >> > >
> > > > > > > > > > >> >> > > > I agree, and I prefer four weeks for
> > > stabilization*
> > > > > (1
> > > > > > > Oct -
> > > > > > > > > 29
> > > > > > > > > > >> Oct)
> > > > > > > > > > >> >> > > >
> > > > > > > > > > >> >> > > > Do I understand it correctly: Service Grid is
> > > still
> > > > > in
> > > > > > > scope,
> > > > > > > > > > >> isn't
> > > > > > > > > > >> >> > it? I
> > > > > > > > > > >> >> > > > find it very important.
> > > > > > > > > > >> >> > > >
> > > > > > > > > > >> >> > > > чт, 27 сент. 2018 г. в 18:28, Nikolay
> Izhikov <
> > > > > > > > > > >> nizhikov@apache.org
> > > > > > > > > > >> >> >:
> > > > > > > > > > >> >> > > >
> > > > > > > > > > >> >> > > > > Hello, Vova.
> > > > > > > > > > >> >> > > > >
> > > > > > > > > > >> >> > > > > Thank you for clear release status.
> > > > > > > > > > >> >> > > > > I'm +1 for your proposal.
> > > > > > > > > > >> >> > > > >
> > > > > > > > > > >> >> > > > > чт, 27 сент. 2018 г., 18:25 Alexey
> Kuznetsov
> > <
> > > > > > > > > > >> >> akuznetsov@apache.org
> > > > > > > > > > >> >> > >:
> > > > > > > > > > >> >> > > > >
> > > > > > > > > > >> >> > > > > > Vova,
> > > > > > > > > > >> >> > > > > >
> > > > > > > > > > >> >> > > > > > Huge +1 to do a stabilization.
> > > > > > > > > > >> >> > > > > >
> > > > > > > > > > >> >> > > > > >
> > > > > > > > > > >> >> > > > > > --
> > > > > > > > > > >> >> > > > > > Alexey Kuznetsov
> > > > > > > > > > >> >> > > > > >
> > > > > > > > > > >> >> > > > >
> > > > > > > > > > >> >> > > >
> > > > > > > > > > >> >> > >
> > > > > > > > > > >> >> >
> > > > > > > > > > >> >>
> > > > > > > > > > >> >
> > > > > > > > > > >>
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > Best regards,
> > > > > > > > > Andrey Kuznetsov.
> > > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Best Regards, Vyacheslav D.
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: Apache Ignite 2.7 release
Posted by Vladimir Ozerov <vo...@gridgain.com>.
Exactly. So correct statement is “it is up to *community* to decide whether
something goes to 2.7”.
пт, 28 сент. 2018 г. в 11:11, Dmitriy Pavlov <dp...@gmail.com>:
> No, it is up to the community to discuss after their review results.
>
> пт, 28 сент. 2018 г. в 11:09, Vladimir Ozerov <vo...@gridgain.com>:
>
> > Dmitriy,
> >
> > Did I read your words correctly that it is up to implementor of a single
> > feature to decide whether release of all other features and fixes to be
> > delayed?
> >
> > пт, 28 сент. 2018 г. в 11:00, Dmitriy Pavlov <dp...@gmail.com>:
> >
> > > My point we can wait a bit for services because
> > > 1 we are open-minded and we don't have outside pressure to do release
> in
> > > October
> > > 2 and services it is not some new feature, which suddenly appeared in
> > > autumn, it is a well known and important feature.
> > >
> > > So it is up to Vyacheslav, Anton and Nikolay to decide.
> > >
> > > Decisions can be services are not ready/ready to merge only to
> > master/ready
> > > to merge to master and to 2.7.
> > >
> > >
> > > пт, 28 сент. 2018 г. в 10:46, Vladimir Ozerov <vo...@gridgain.com>:
> > >
> > > > Dmitry,
> > > >
> > > > Community agreement was to perform the release in October. Of course
> we
> > > can
> > > > wait a bit for services. Then we wait a bit for other cool features
> > ready
> > > > by that time, then again and again, and release will never happen.
> And
> > > > while we are waiting for new features to come, already completerd
> > > features
> > > > cannot be used by anyone.
> > > >
> > > > This is why we have an agreement that if feature is not ready, it
> > should
> > > be
> > > > moved to future release, instead of shifting release. The sole reason
> > to
> > > > have strict dates when decisions are made is to let release happen.
> > > >
> > > >
> > > >
> > > > On Fri, Sep 28, 2018 at 2:22 AM Dmitriy Pavlov <
> dpavlov.spb@gmail.com>
> > > > wrote:
> > > >
> > > > > Vladimir, I'm not searching for enemy, and not fighting with you.
> > I'm
> > > > not
> > > > > happy about cases when we are hurrying.
> > > > >
> > > > > We can't fix test, fill ticket details, can't wait for
> contributions
> > to
> > > > > finish their tasks. It is not best idea to use experience from
> > > > commercial
> > > > > companies in open source. Are there any pressure outside community?
> > Did
> > > > > someone promised rest of features to be released at 30 September?
> > > > >
> > > > > Let's remember principle do-orcracy, power of those who do. If
> > > contribor
> > > > > does change and reviewer does review, let's give right of making
> > > decision
> > > > > to them, but not to some closed club of people who privately
> discuss
> > > > > something.
> > > > >
> > > > > Sincerely
> > > > > Dmitriy Pavlov
> > > > >
> > > > > чт, 27 сент. 2018 г., 23:42 Vyacheslav Daradur <
> daradurvs@gmail.com
> > >:
> > > > >
> > > > > > Hi Igniters!
> > > > > >
> > > > > > As I have written about Service Grid before [1] I'm finalizing
> the
> > > > > > solution to be sure that implementation is reliable.
> > > > > >
> > > > > > About including it in 2.7, if we talk that code freeze tomorrow
> > then
> > > > > > the solution is not ready to merge yet.
> > > > > > I hope that prereviewers Anton Vinogradov and Nikolay Izhikov
> will
> > be
> > > > > > able to answer if solution out of scope or not in a couple of
> days.
> > > > > >
> > > > > > [1]
> > > > > >
> > > > >
> > > >
> > >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-release-td34076.html#a34485
> > > > > > On Thu, Sep 27, 2018 at 11:14 PM Dmitriy Pavlov <
> > > dpavlov.spb@gmail.com
> > > > >
> > > > > > wrote:
> > > > > > >
> > > > > > > Yes, I agree, NPE during WAL flush is definitely a blocker.
> > > > > > >
> > > > > > > It is strange why the current test set did not fail after
> commit.
> > > > > > >
> > > > > > > чт, 27 сент. 2018 г. в 21:45, Andrey Kuznetsov <
> > stkuzma@gmail.com
> > > >:
> > > > > > >
> > > > > > > > Igniters,
> > > > > > > >
> > > > > > > > I've bumped into a new bug in WAL manager recently, see [1].
> It
> > > > looks
> > > > > > > > critical enough, and can be a good candidate for fixing
> before
> > > 2.7
> > > > > > release.
> > > > > > > >
> > > > > > > > Do you agree?
> > > > > > > >
> > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-9731
> > > > > > > >
> > > > > > > > чт, 27 сент. 2018 г. в 19:45, Dmitriy Pavlov <
> > > > dpavlov.spb@gmail.com
> > > > > >:
> > > > > > > >
> > > > > > > > > I need Vhyacheslav's opinion to be absolutely sure what
> > status
> > > is
> > > > > > now.
> > > > > > > > >
> > > > > > > > > We never committed to dates of release, as well. I don't
> > quite
> > > > > > understand
> > > > > > > > > what can mean 'the community committed to doing/releasing
> > > > > something'.
> > > > > > > > >
> > > > > > > > > About SG, I also concerned why such a big feature has
> quite a
> > > few
> > > > > > > > > discussions on the list. But it is another story.
> > > > > > > > >
> > > > > > > > > чт, 27 сент. 2018 г. в 19:33, Vladimir Ozerov <
> > > > > vozerov@gridgain.com
> > > > > > >:
> > > > > > > > >
> > > > > > > > > > Folks,
> > > > > > > > > >
> > > > > > > > > > Please stop looking for enemies everywhere. Just went
> > through
> > > > > this
> > > > > > > > thread
> > > > > > > > > > and search for "service" word.
> > > > > > > > > >
> > > > > > > > > > On Thu, Sep 27, 2018 at 7:30 PM Denis Magda <
> > > dmagda@apache.org
> > > > >
> > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > >> >
> > > > > > > > > >> > Denis, as PMC Chair, could you please control, that
> > > Service
> > > > > Grid
> > > > > > > > > >> > inclusion/exclusion is discussed properly according to
> > the
> > > > > > Apache
> > > > > > > > Way.
> > > > > > > > > >>
> > > > > > > > > >>
> > > > > > > > > >> It's fine when committers/contributors have private
> > > > discussions
> > > > > > > > related
> > > > > > > > > to
> > > > > > > > > >> a feature they've been working on. Not everything should
> > go
> > > > > > through
> > > > > > > > the
> > > > > > > > > >> dev
> > > > > > > > > >> list. Otherwise, it will be inundated. However, agree,
> > that
> > > > > > > > > architectural
> > > > > > > > > >> and release decisions need to be done publicly.
> > > > > > > > > >>
> > > > > > > > > >> Speaking about Service Grid, there was a discussion
> where
> > I
> > > > saw
> > > > > > that
> > > > > > > > it
> > > > > > > > > >> was
> > > > > > > > > >> questionable whether it gets added to the release or
> not.
> > > > > > > > > >>
> > > > > > > > > >> *Vladislav*, could you please shed some light on the
> > current
> > > > > > status of
> > > > > > > > > the
> > > > > > > > > >> service grid?
> > > > > > > > > >>
> > > > > > > > > >> On Thu, Sep 27, 2018 at 9:12 AM Dmitriy Pavlov <
> > > > > > dpavlov.spb@gmail.com
> > > > > > > > >
> > > > > > > > > >> wrote:
> > > > > > > > > >>
> > > > > > > > > >> > Ok, let's wait for feedback from SG
> > Author(s)/Reviewer(s)
> > > > > > first. If
> > > > > > > > it
> > > > > > > > > >> is
> > > > > > > > > >> > not ready, ok. But I thought it is almost done.
> > > > > > > > > >> >
> > > > > > > > > >> > I apologize if I missed some discussion (it can
> happen),
> > > but
> > > > > > > > > >> > According to the statement "our current agreement"
> > > > > > > > > >> > I can suspect some members are making some sort of
> > private
> > > > > > > > agreements,
> > > > > > > > > >> and
> > > > > > > > > >> > do not to discuss it on the list.
> > > > > > > > > >> >
> > > > > > > > > >> > Let's build consensus here first, and then name an
> > > > agreement.
> > > > > > > > > >> >
> > > > > > > > > >> > Denis, as PMC Chair, could you please control, that
> > > Service
> > > > > Grid
> > > > > > > > > >> > inclusion/exclusion is discussed properly according to
> > the
> > > > > > Apache
> > > > > > > > Way.
> > > > > > > > > >> >
> > > > > > > > > >> > чт, 27 сент. 2018 г. в 18:55, Vladimir Ozerov <
> > > > > > vozerov@gridgain.com
> > > > > > > > >:
> > > > > > > > > >> >
> > > > > > > > > >> >> Dmitriy,
> > > > > > > > > >> >>
> > > > > > > > > >> >> This is an outcome of current state of Service Grid -
> > it
> > > is
> > > > > not
> > > > > > > > > ready.
> > > > > > > > > >> We
> > > > > > > > > >> >> never committed to have it to 2.7. Our goal was to
> try
> > to
> > > > > > include
> > > > > > > > it
> > > > > > > > > >> into
> > > > > > > > > >> >> 2.7.
> > > > > > > > > >> >>
> > > > > > > > > >> >> On Thu, Sep 27, 2018 at 6:48 PM Dmitriy Pavlov <
> > > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > > >> >> wrote:
> > > > > > > > > >> >>
> > > > > > > > > >> >> > Could you please provide a reference to some
> thread?
> > > > > > Probably I
> > > > > > > > > >> missed
> > > > > > > > > >> >> it.
> > > > > > > > > >> >> >
> > > > > > > > > >> >> > чт, 27 сент. 2018 г. в 18:46, Vladimir Ozerov <
> > > > > > > > > vozerov@gridgain.com
> > > > > > > > > >> >:
> > > > > > > > > >> >> >
> > > > > > > > > >> >> > > Our current agreement is that Service Grid is out
> > of
> > > > > scope.
> > > > > > > > This
> > > > > > > > > >> is a
> > > > > > > > > >> >> > huge
> > > > > > > > > >> >> > > feature, which hasn't entered review stage so
> far,
> > We
> > > > > will
> > > > > > not
> > > > > > > > be
> > > > > > > > > >> >> able to
> > > > > > > > > >> >> > > review/fix/test it properly.
> > > > > > > > > >> >> > >
> > > > > > > > > >> >> > > On Thu, Sep 27, 2018 at 6:32 PM Dmitriy Pavlov <
> > > > > > > > > >> dpavlov.spb@gmail.com
> > > > > > > > > >> >> >
> > > > > > > > > >> >> > > wrote:
> > > > > > > > > >> >> > >
> > > > > > > > > >> >> > > > I agree, and I prefer four weeks for
> > stabilization*
> > > > (1
> > > > > > Oct -
> > > > > > > > 29
> > > > > > > > > >> Oct)
> > > > > > > > > >> >> > > >
> > > > > > > > > >> >> > > > Do I understand it correctly: Service Grid is
> > still
> > > > in
> > > > > > scope,
> > > > > > > > > >> isn't
> > > > > > > > > >> >> > it? I
> > > > > > > > > >> >> > > > find it very important.
> > > > > > > > > >> >> > > >
> > > > > > > > > >> >> > > > чт, 27 сент. 2018 г. в 18:28, Nikolay Izhikov <
> > > > > > > > > >> nizhikov@apache.org
> > > > > > > > > >> >> >:
> > > > > > > > > >> >> > > >
> > > > > > > > > >> >> > > > > Hello, Vova.
> > > > > > > > > >> >> > > > >
> > > > > > > > > >> >> > > > > Thank you for clear release status.
> > > > > > > > > >> >> > > > > I'm +1 for your proposal.
> > > > > > > > > >> >> > > > >
> > > > > > > > > >> >> > > > > чт, 27 сент. 2018 г., 18:25 Alexey Kuznetsov
> <
> > > > > > > > > >> >> akuznetsov@apache.org
> > > > > > > > > >> >> > >:
> > > > > > > > > >> >> > > > >
> > > > > > > > > >> >> > > > > > Vova,
> > > > > > > > > >> >> > > > > >
> > > > > > > > > >> >> > > > > > Huge +1 to do a stabilization.
> > > > > > > > > >> >> > > > > >
> > > > > > > > > >> >> > > > > >
> > > > > > > > > >> >> > > > > > --
> > > > > > > > > >> >> > > > > > Alexey Kuznetsov
> > > > > > > > > >> >> > > > > >
> > > > > > > > > >> >> > > > >
> > > > > > > > > >> >> > > >
> > > > > > > > > >> >> > >
> > > > > > > > > >> >> >
> > > > > > > > > >> >>
> > > > > > > > > >> >
> > > > > > > > > >>
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > Best regards,
> > > > > > > > Andrey Kuznetsov.
> > > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Best Regards, Vyacheslav D.
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: Apache Ignite 2.7 release
Posted by Dmitriy Pavlov <dp...@gmail.com>.
No, it is up to the community to discuss after their review results.
пт, 28 сент. 2018 г. в 11:09, Vladimir Ozerov <vo...@gridgain.com>:
> Dmitriy,
>
> Did I read your words correctly that it is up to implementor of a single
> feature to decide whether release of all other features and fixes to be
> delayed?
>
> пт, 28 сент. 2018 г. в 11:00, Dmitriy Pavlov <dp...@gmail.com>:
>
> > My point we can wait a bit for services because
> > 1 we are open-minded and we don't have outside pressure to do release in
> > October
> > 2 and services it is not some new feature, which suddenly appeared in
> > autumn, it is a well known and important feature.
> >
> > So it is up to Vyacheslav, Anton and Nikolay to decide.
> >
> > Decisions can be services are not ready/ready to merge only to
> master/ready
> > to merge to master and to 2.7.
> >
> >
> > пт, 28 сент. 2018 г. в 10:46, Vladimir Ozerov <vo...@gridgain.com>:
> >
> > > Dmitry,
> > >
> > > Community agreement was to perform the release in October. Of course we
> > can
> > > wait a bit for services. Then we wait a bit for other cool features
> ready
> > > by that time, then again and again, and release will never happen. And
> > > while we are waiting for new features to come, already completerd
> > features
> > > cannot be used by anyone.
> > >
> > > This is why we have an agreement that if feature is not ready, it
> should
> > be
> > > moved to future release, instead of shifting release. The sole reason
> to
> > > have strict dates when decisions are made is to let release happen.
> > >
> > >
> > >
> > > On Fri, Sep 28, 2018 at 2:22 AM Dmitriy Pavlov <dp...@gmail.com>
> > > wrote:
> > >
> > > > Vladimir, I'm not searching for enemy, and not fighting with you.
> I'm
> > > not
> > > > happy about cases when we are hurrying.
> > > >
> > > > We can't fix test, fill ticket details, can't wait for contributions
> to
> > > > finish their tasks. It is not best idea to use experience from
> > > commercial
> > > > companies in open source. Are there any pressure outside community?
> Did
> > > > someone promised rest of features to be released at 30 September?
> > > >
> > > > Let's remember principle do-orcracy, power of those who do. If
> > contribor
> > > > does change and reviewer does review, let's give right of making
> > decision
> > > > to them, but not to some closed club of people who privately discuss
> > > > something.
> > > >
> > > > Sincerely
> > > > Dmitriy Pavlov
> > > >
> > > > чт, 27 сент. 2018 г., 23:42 Vyacheslav Daradur <daradurvs@gmail.com
> >:
> > > >
> > > > > Hi Igniters!
> > > > >
> > > > > As I have written about Service Grid before [1] I'm finalizing the
> > > > > solution to be sure that implementation is reliable.
> > > > >
> > > > > About including it in 2.7, if we talk that code freeze tomorrow
> then
> > > > > the solution is not ready to merge yet.
> > > > > I hope that prereviewers Anton Vinogradov and Nikolay Izhikov will
> be
> > > > > able to answer if solution out of scope or not in a couple of days.
> > > > >
> > > > > [1]
> > > > >
> > > >
> > >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-release-td34076.html#a34485
> > > > > On Thu, Sep 27, 2018 at 11:14 PM Dmitriy Pavlov <
> > dpavlov.spb@gmail.com
> > > >
> > > > > wrote:
> > > > > >
> > > > > > Yes, I agree, NPE during WAL flush is definitely a blocker.
> > > > > >
> > > > > > It is strange why the current test set did not fail after commit.
> > > > > >
> > > > > > чт, 27 сент. 2018 г. в 21:45, Andrey Kuznetsov <
> stkuzma@gmail.com
> > >:
> > > > > >
> > > > > > > Igniters,
> > > > > > >
> > > > > > > I've bumped into a new bug in WAL manager recently, see [1]. It
> > > looks
> > > > > > > critical enough, and can be a good candidate for fixing before
> > 2.7
> > > > > release.
> > > > > > >
> > > > > > > Do you agree?
> > > > > > >
> > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-9731
> > > > > > >
> > > > > > > чт, 27 сент. 2018 г. в 19:45, Dmitriy Pavlov <
> > > dpavlov.spb@gmail.com
> > > > >:
> > > > > > >
> > > > > > > > I need Vhyacheslav's opinion to be absolutely sure what
> status
> > is
> > > > > now.
> > > > > > > >
> > > > > > > > We never committed to dates of release, as well. I don't
> quite
> > > > > understand
> > > > > > > > what can mean 'the community committed to doing/releasing
> > > > something'.
> > > > > > > >
> > > > > > > > About SG, I also concerned why such a big feature has quite a
> > few
> > > > > > > > discussions on the list. But it is another story.
> > > > > > > >
> > > > > > > > чт, 27 сент. 2018 г. в 19:33, Vladimir Ozerov <
> > > > vozerov@gridgain.com
> > > > > >:
> > > > > > > >
> > > > > > > > > Folks,
> > > > > > > > >
> > > > > > > > > Please stop looking for enemies everywhere. Just went
> through
> > > > this
> > > > > > > thread
> > > > > > > > > and search for "service" word.
> > > > > > > > >
> > > > > > > > > On Thu, Sep 27, 2018 at 7:30 PM Denis Magda <
> > dmagda@apache.org
> > > >
> > > > > wrote:
> > > > > > > > >
> > > > > > > > >> >
> > > > > > > > >> > Denis, as PMC Chair, could you please control, that
> > Service
> > > > Grid
> > > > > > > > >> > inclusion/exclusion is discussed properly according to
> the
> > > > > Apache
> > > > > > > Way.
> > > > > > > > >>
> > > > > > > > >>
> > > > > > > > >> It's fine when committers/contributors have private
> > > discussions
> > > > > > > related
> > > > > > > > to
> > > > > > > > >> a feature they've been working on. Not everything should
> go
> > > > > through
> > > > > > > the
> > > > > > > > >> dev
> > > > > > > > >> list. Otherwise, it will be inundated. However, agree,
> that
> > > > > > > > architectural
> > > > > > > > >> and release decisions need to be done publicly.
> > > > > > > > >>
> > > > > > > > >> Speaking about Service Grid, there was a discussion where
> I
> > > saw
> > > > > that
> > > > > > > it
> > > > > > > > >> was
> > > > > > > > >> questionable whether it gets added to the release or not.
> > > > > > > > >>
> > > > > > > > >> *Vladislav*, could you please shed some light on the
> current
> > > > > status of
> > > > > > > > the
> > > > > > > > >> service grid?
> > > > > > > > >>
> > > > > > > > >> On Thu, Sep 27, 2018 at 9:12 AM Dmitriy Pavlov <
> > > > > dpavlov.spb@gmail.com
> > > > > > > >
> > > > > > > > >> wrote:
> > > > > > > > >>
> > > > > > > > >> > Ok, let's wait for feedback from SG
> Author(s)/Reviewer(s)
> > > > > first. If
> > > > > > > it
> > > > > > > > >> is
> > > > > > > > >> > not ready, ok. But I thought it is almost done.
> > > > > > > > >> >
> > > > > > > > >> > I apologize if I missed some discussion (it can happen),
> > but
> > > > > > > > >> > According to the statement "our current agreement"
> > > > > > > > >> > I can suspect some members are making some sort of
> private
> > > > > > > agreements,
> > > > > > > > >> and
> > > > > > > > >> > do not to discuss it on the list.
> > > > > > > > >> >
> > > > > > > > >> > Let's build consensus here first, and then name an
> > > agreement.
> > > > > > > > >> >
> > > > > > > > >> > Denis, as PMC Chair, could you please control, that
> > Service
> > > > Grid
> > > > > > > > >> > inclusion/exclusion is discussed properly according to
> the
> > > > > Apache
> > > > > > > Way.
> > > > > > > > >> >
> > > > > > > > >> > чт, 27 сент. 2018 г. в 18:55, Vladimir Ozerov <
> > > > > vozerov@gridgain.com
> > > > > > > >:
> > > > > > > > >> >
> > > > > > > > >> >> Dmitriy,
> > > > > > > > >> >>
> > > > > > > > >> >> This is an outcome of current state of Service Grid -
> it
> > is
> > > > not
> > > > > > > > ready.
> > > > > > > > >> We
> > > > > > > > >> >> never committed to have it to 2.7. Our goal was to try
> to
> > > > > include
> > > > > > > it
> > > > > > > > >> into
> > > > > > > > >> >> 2.7.
> > > > > > > > >> >>
> > > > > > > > >> >> On Thu, Sep 27, 2018 at 6:48 PM Dmitriy Pavlov <
> > > > > > > > dpavlov.spb@gmail.com>
> > > > > > > > >> >> wrote:
> > > > > > > > >> >>
> > > > > > > > >> >> > Could you please provide a reference to some thread?
> > > > > Probably I
> > > > > > > > >> missed
> > > > > > > > >> >> it.
> > > > > > > > >> >> >
> > > > > > > > >> >> > чт, 27 сент. 2018 г. в 18:46, Vladimir Ozerov <
> > > > > > > > vozerov@gridgain.com
> > > > > > > > >> >:
> > > > > > > > >> >> >
> > > > > > > > >> >> > > Our current agreement is that Service Grid is out
> of
> > > > scope.
> > > > > > > This
> > > > > > > > >> is a
> > > > > > > > >> >> > huge
> > > > > > > > >> >> > > feature, which hasn't entered review stage so far,
> We
> > > > will
> > > > > not
> > > > > > > be
> > > > > > > > >> >> able to
> > > > > > > > >> >> > > review/fix/test it properly.
> > > > > > > > >> >> > >
> > > > > > > > >> >> > > On Thu, Sep 27, 2018 at 6:32 PM Dmitriy Pavlov <
> > > > > > > > >> dpavlov.spb@gmail.com
> > > > > > > > >> >> >
> > > > > > > > >> >> > > wrote:
> > > > > > > > >> >> > >
> > > > > > > > >> >> > > > I agree, and I prefer four weeks for
> stabilization*
> > > (1
> > > > > Oct -
> > > > > > > 29
> > > > > > > > >> Oct)
> > > > > > > > >> >> > > >
> > > > > > > > >> >> > > > Do I understand it correctly: Service Grid is
> still
> > > in
> > > > > scope,
> > > > > > > > >> isn't
> > > > > > > > >> >> > it? I
> > > > > > > > >> >> > > > find it very important.
> > > > > > > > >> >> > > >
> > > > > > > > >> >> > > > чт, 27 сент. 2018 г. в 18:28, Nikolay Izhikov <
> > > > > > > > >> nizhikov@apache.org
> > > > > > > > >> >> >:
> > > > > > > > >> >> > > >
> > > > > > > > >> >> > > > > Hello, Vova.
> > > > > > > > >> >> > > > >
> > > > > > > > >> >> > > > > Thank you for clear release status.
> > > > > > > > >> >> > > > > I'm +1 for your proposal.
> > > > > > > > >> >> > > > >
> > > > > > > > >> >> > > > > чт, 27 сент. 2018 г., 18:25 Alexey Kuznetsov <
> > > > > > > > >> >> akuznetsov@apache.org
> > > > > > > > >> >> > >:
> > > > > > > > >> >> > > > >
> > > > > > > > >> >> > > > > > Vova,
> > > > > > > > >> >> > > > > >
> > > > > > > > >> >> > > > > > Huge +1 to do a stabilization.
> > > > > > > > >> >> > > > > >
> > > > > > > > >> >> > > > > >
> > > > > > > > >> >> > > > > > --
> > > > > > > > >> >> > > > > > Alexey Kuznetsov
> > > > > > > > >> >> > > > > >
> > > > > > > > >> >> > > > >
> > > > > > > > >> >> > > >
> > > > > > > > >> >> > >
> > > > > > > > >> >> >
> > > > > > > > >> >>
> > > > > > > > >> >
> > > > > > > > >>
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Best regards,
> > > > > > > Andrey Kuznetsov.
> > > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Best Regards, Vyacheslav D.
> > > > >
> > > >
> > >
> >
>
Re: Apache Ignite 2.7 release
Posted by Vladimir Ozerov <vo...@gridgain.com>.
Dmitriy,
Did I read your words correctly that it is up to implementor of a single
feature to decide whether release of all other features and fixes to be
delayed?
пт, 28 сент. 2018 г. в 11:00, Dmitriy Pavlov <dp...@gmail.com>:
> My point we can wait a bit for services because
> 1 we are open-minded and we don't have outside pressure to do release in
> October
> 2 and services it is not some new feature, which suddenly appeared in
> autumn, it is a well known and important feature.
>
> So it is up to Vyacheslav, Anton and Nikolay to decide.
>
> Decisions can be services are not ready/ready to merge only to master/ready
> to merge to master and to 2.7.
>
>
> пт, 28 сент. 2018 г. в 10:46, Vladimir Ozerov <vo...@gridgain.com>:
>
> > Dmitry,
> >
> > Community agreement was to perform the release in October. Of course we
> can
> > wait a bit for services. Then we wait a bit for other cool features ready
> > by that time, then again and again, and release will never happen. And
> > while we are waiting for new features to come, already completerd
> features
> > cannot be used by anyone.
> >
> > This is why we have an agreement that if feature is not ready, it should
> be
> > moved to future release, instead of shifting release. The sole reason to
> > have strict dates when decisions are made is to let release happen.
> >
> >
> >
> > On Fri, Sep 28, 2018 at 2:22 AM Dmitriy Pavlov <dp...@gmail.com>
> > wrote:
> >
> > > Vladimir, I'm not searching for enemy, and not fighting with you. I'm
> > not
> > > happy about cases when we are hurrying.
> > >
> > > We can't fix test, fill ticket details, can't wait for contributions to
> > > finish their tasks. It is not best idea to use experience from
> > commercial
> > > companies in open source. Are there any pressure outside community? Did
> > > someone promised rest of features to be released at 30 September?
> > >
> > > Let's remember principle do-orcracy, power of those who do. If
> contribor
> > > does change and reviewer does review, let's give right of making
> decision
> > > to them, but not to some closed club of people who privately discuss
> > > something.
> > >
> > > Sincerely
> > > Dmitriy Pavlov
> > >
> > > чт, 27 сент. 2018 г., 23:42 Vyacheslav Daradur <da...@gmail.com>:
> > >
> > > > Hi Igniters!
> > > >
> > > > As I have written about Service Grid before [1] I'm finalizing the
> > > > solution to be sure that implementation is reliable.
> > > >
> > > > About including it in 2.7, if we talk that code freeze tomorrow then
> > > > the solution is not ready to merge yet.
> > > > I hope that prereviewers Anton Vinogradov and Nikolay Izhikov will be
> > > > able to answer if solution out of scope or not in a couple of days.
> > > >
> > > > [1]
> > > >
> > >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-release-td34076.html#a34485
> > > > On Thu, Sep 27, 2018 at 11:14 PM Dmitriy Pavlov <
> dpavlov.spb@gmail.com
> > >
> > > > wrote:
> > > > >
> > > > > Yes, I agree, NPE during WAL flush is definitely a blocker.
> > > > >
> > > > > It is strange why the current test set did not fail after commit.
> > > > >
> > > > > чт, 27 сент. 2018 г. в 21:45, Andrey Kuznetsov <stkuzma@gmail.com
> >:
> > > > >
> > > > > > Igniters,
> > > > > >
> > > > > > I've bumped into a new bug in WAL manager recently, see [1]. It
> > looks
> > > > > > critical enough, and can be a good candidate for fixing before
> 2.7
> > > > release.
> > > > > >
> > > > > > Do you agree?
> > > > > >
> > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-9731
> > > > > >
> > > > > > чт, 27 сент. 2018 г. в 19:45, Dmitriy Pavlov <
> > dpavlov.spb@gmail.com
> > > >:
> > > > > >
> > > > > > > I need Vhyacheslav's opinion to be absolutely sure what status
> is
> > > > now.
> > > > > > >
> > > > > > > We never committed to dates of release, as well. I don't quite
> > > > understand
> > > > > > > what can mean 'the community committed to doing/releasing
> > > something'.
> > > > > > >
> > > > > > > About SG, I also concerned why such a big feature has quite a
> few
> > > > > > > discussions on the list. But it is another story.
> > > > > > >
> > > > > > > чт, 27 сент. 2018 г. в 19:33, Vladimir Ozerov <
> > > vozerov@gridgain.com
> > > > >:
> > > > > > >
> > > > > > > > Folks,
> > > > > > > >
> > > > > > > > Please stop looking for enemies everywhere. Just went through
> > > this
> > > > > > thread
> > > > > > > > and search for "service" word.
> > > > > > > >
> > > > > > > > On Thu, Sep 27, 2018 at 7:30 PM Denis Magda <
> dmagda@apache.org
> > >
> > > > wrote:
> > > > > > > >
> > > > > > > >> >
> > > > > > > >> > Denis, as PMC Chair, could you please control, that
> Service
> > > Grid
> > > > > > > >> > inclusion/exclusion is discussed properly according to the
> > > > Apache
> > > > > > Way.
> > > > > > > >>
> > > > > > > >>
> > > > > > > >> It's fine when committers/contributors have private
> > discussions
> > > > > > related
> > > > > > > to
> > > > > > > >> a feature they've been working on. Not everything should go
> > > > through
> > > > > > the
> > > > > > > >> dev
> > > > > > > >> list. Otherwise, it will be inundated. However, agree, that
> > > > > > > architectural
> > > > > > > >> and release decisions need to be done publicly.
> > > > > > > >>
> > > > > > > >> Speaking about Service Grid, there was a discussion where I
> > saw
> > > > that
> > > > > > it
> > > > > > > >> was
> > > > > > > >> questionable whether it gets added to the release or not.
> > > > > > > >>
> > > > > > > >> *Vladislav*, could you please shed some light on the current
> > > > status of
> > > > > > > the
> > > > > > > >> service grid?
> > > > > > > >>
> > > > > > > >> On Thu, Sep 27, 2018 at 9:12 AM Dmitriy Pavlov <
> > > > dpavlov.spb@gmail.com
> > > > > > >
> > > > > > > >> wrote:
> > > > > > > >>
> > > > > > > >> > Ok, let's wait for feedback from SG Author(s)/Reviewer(s)
> > > > first. If
> > > > > > it
> > > > > > > >> is
> > > > > > > >> > not ready, ok. But I thought it is almost done.
> > > > > > > >> >
> > > > > > > >> > I apologize if I missed some discussion (it can happen),
> but
> > > > > > > >> > According to the statement "our current agreement"
> > > > > > > >> > I can suspect some members are making some sort of private
> > > > > > agreements,
> > > > > > > >> and
> > > > > > > >> > do not to discuss it on the list.
> > > > > > > >> >
> > > > > > > >> > Let's build consensus here first, and then name an
> > agreement.
> > > > > > > >> >
> > > > > > > >> > Denis, as PMC Chair, could you please control, that
> Service
> > > Grid
> > > > > > > >> > inclusion/exclusion is discussed properly according to the
> > > > Apache
> > > > > > Way.
> > > > > > > >> >
> > > > > > > >> > чт, 27 сент. 2018 г. в 18:55, Vladimir Ozerov <
> > > > vozerov@gridgain.com
> > > > > > >:
> > > > > > > >> >
> > > > > > > >> >> Dmitriy,
> > > > > > > >> >>
> > > > > > > >> >> This is an outcome of current state of Service Grid - it
> is
> > > not
> > > > > > > ready.
> > > > > > > >> We
> > > > > > > >> >> never committed to have it to 2.7. Our goal was to try to
> > > > include
> > > > > > it
> > > > > > > >> into
> > > > > > > >> >> 2.7.
> > > > > > > >> >>
> > > > > > > >> >> On Thu, Sep 27, 2018 at 6:48 PM Dmitriy Pavlov <
> > > > > > > dpavlov.spb@gmail.com>
> > > > > > > >> >> wrote:
> > > > > > > >> >>
> > > > > > > >> >> > Could you please provide a reference to some thread?
> > > > Probably I
> > > > > > > >> missed
> > > > > > > >> >> it.
> > > > > > > >> >> >
> > > > > > > >> >> > чт, 27 сент. 2018 г. в 18:46, Vladimir Ozerov <
> > > > > > > vozerov@gridgain.com
> > > > > > > >> >:
> > > > > > > >> >> >
> > > > > > > >> >> > > Our current agreement is that Service Grid is out of
> > > scope.
> > > > > > This
> > > > > > > >> is a
> > > > > > > >> >> > huge
> > > > > > > >> >> > > feature, which hasn't entered review stage so far, We
> > > will
> > > > not
> > > > > > be
> > > > > > > >> >> able to
> > > > > > > >> >> > > review/fix/test it properly.
> > > > > > > >> >> > >
> > > > > > > >> >> > > On Thu, Sep 27, 2018 at 6:32 PM Dmitriy Pavlov <
> > > > > > > >> dpavlov.spb@gmail.com
> > > > > > > >> >> >
> > > > > > > >> >> > > wrote:
> > > > > > > >> >> > >
> > > > > > > >> >> > > > I agree, and I prefer four weeks for stabilization*
> > (1
> > > > Oct -
> > > > > > 29
> > > > > > > >> Oct)
> > > > > > > >> >> > > >
> > > > > > > >> >> > > > Do I understand it correctly: Service Grid is still
> > in
> > > > scope,
> > > > > > > >> isn't
> > > > > > > >> >> > it? I
> > > > > > > >> >> > > > find it very important.
> > > > > > > >> >> > > >
> > > > > > > >> >> > > > чт, 27 сент. 2018 г. в 18:28, Nikolay Izhikov <
> > > > > > > >> nizhikov@apache.org
> > > > > > > >> >> >:
> > > > > > > >> >> > > >
> > > > > > > >> >> > > > > Hello, Vova.
> > > > > > > >> >> > > > >
> > > > > > > >> >> > > > > Thank you for clear release status.
> > > > > > > >> >> > > > > I'm +1 for your proposal.
> > > > > > > >> >> > > > >
> > > > > > > >> >> > > > > чт, 27 сент. 2018 г., 18:25 Alexey Kuznetsov <
> > > > > > > >> >> akuznetsov@apache.org
> > > > > > > >> >> > >:
> > > > > > > >> >> > > > >
> > > > > > > >> >> > > > > > Vova,
> > > > > > > >> >> > > > > >
> > > > > > > >> >> > > > > > Huge +1 to do a stabilization.
> > > > > > > >> >> > > > > >
> > > > > > > >> >> > > > > >
> > > > > > > >> >> > > > > > --
> > > > > > > >> >> > > > > > Alexey Kuznetsov
> > > > > > > >> >> > > > > >
> > > > > > > >> >> > > > >
> > > > > > > >> >> > > >
> > > > > > > >> >> > >
> > > > > > > >> >> >
> > > > > > > >> >>
> > > > > > > >> >
> > > > > > > >>
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Best regards,
> > > > > > Andrey Kuznetsov.
> > > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Best Regards, Vyacheslav D.
> > > >
> > >
> >
>
Re: Apache Ignite 2.7 release
Posted by Dmitriy Pavlov <dp...@gmail.com>.
My point we can wait a bit for services because
1 we are open-minded and we don't have outside pressure to do release in
October
2 and services it is not some new feature, which suddenly appeared in
autumn, it is a well known and important feature.
So it is up to Vyacheslav, Anton and Nikolay to decide.
Decisions can be services are not ready/ready to merge only to master/ready
to merge to master and to 2.7.
пт, 28 сент. 2018 г. в 10:46, Vladimir Ozerov <vo...@gridgain.com>:
> Dmitry,
>
> Community agreement was to perform the release in October. Of course we can
> wait a bit for services. Then we wait a bit for other cool features ready
> by that time, then again and again, and release will never happen. And
> while we are waiting for new features to come, already completerd features
> cannot be used by anyone.
>
> This is why we have an agreement that if feature is not ready, it should be
> moved to future release, instead of shifting release. The sole reason to
> have strict dates when decisions are made is to let release happen.
>
>
>
> On Fri, Sep 28, 2018 at 2:22 AM Dmitriy Pavlov <dp...@gmail.com>
> wrote:
>
> > Vladimir, I'm not searching for enemy, and not fighting with you. I'm
> not
> > happy about cases when we are hurrying.
> >
> > We can't fix test, fill ticket details, can't wait for contributions to
> > finish their tasks. It is not best idea to use experience from
> commercial
> > companies in open source. Are there any pressure outside community? Did
> > someone promised rest of features to be released at 30 September?
> >
> > Let's remember principle do-orcracy, power of those who do. If contribor
> > does change and reviewer does review, let's give right of making decision
> > to them, but not to some closed club of people who privately discuss
> > something.
> >
> > Sincerely
> > Dmitriy Pavlov
> >
> > чт, 27 сент. 2018 г., 23:42 Vyacheslav Daradur <da...@gmail.com>:
> >
> > > Hi Igniters!
> > >
> > > As I have written about Service Grid before [1] I'm finalizing the
> > > solution to be sure that implementation is reliable.
> > >
> > > About including it in 2.7, if we talk that code freeze tomorrow then
> > > the solution is not ready to merge yet.
> > > I hope that prereviewers Anton Vinogradov and Nikolay Izhikov will be
> > > able to answer if solution out of scope or not in a couple of days.
> > >
> > > [1]
> > >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-release-td34076.html#a34485
> > > On Thu, Sep 27, 2018 at 11:14 PM Dmitriy Pavlov <dpavlov.spb@gmail.com
> >
> > > wrote:
> > > >
> > > > Yes, I agree, NPE during WAL flush is definitely a blocker.
> > > >
> > > > It is strange why the current test set did not fail after commit.
> > > >
> > > > чт, 27 сент. 2018 г. в 21:45, Andrey Kuznetsov <st...@gmail.com>:
> > > >
> > > > > Igniters,
> > > > >
> > > > > I've bumped into a new bug in WAL manager recently, see [1]. It
> looks
> > > > > critical enough, and can be a good candidate for fixing before 2.7
> > > release.
> > > > >
> > > > > Do you agree?
> > > > >
> > > > > [1] https://issues.apache.org/jira/browse/IGNITE-9731
> > > > >
> > > > > чт, 27 сент. 2018 г. в 19:45, Dmitriy Pavlov <
> dpavlov.spb@gmail.com
> > >:
> > > > >
> > > > > > I need Vhyacheslav's opinion to be absolutely sure what status is
> > > now.
> > > > > >
> > > > > > We never committed to dates of release, as well. I don't quite
> > > understand
> > > > > > what can mean 'the community committed to doing/releasing
> > something'.
> > > > > >
> > > > > > About SG, I also concerned why such a big feature has quite a few
> > > > > > discussions on the list. But it is another story.
> > > > > >
> > > > > > чт, 27 сент. 2018 г. в 19:33, Vladimir Ozerov <
> > vozerov@gridgain.com
> > > >:
> > > > > >
> > > > > > > Folks,
> > > > > > >
> > > > > > > Please stop looking for enemies everywhere. Just went through
> > this
> > > > > thread
> > > > > > > and search for "service" word.
> > > > > > >
> > > > > > > On Thu, Sep 27, 2018 at 7:30 PM Denis Magda <dmagda@apache.org
> >
> > > wrote:
> > > > > > >
> > > > > > >> >
> > > > > > >> > Denis, as PMC Chair, could you please control, that Service
> > Grid
> > > > > > >> > inclusion/exclusion is discussed properly according to the
> > > Apache
> > > > > Way.
> > > > > > >>
> > > > > > >>
> > > > > > >> It's fine when committers/contributors have private
> discussions
> > > > > related
> > > > > > to
> > > > > > >> a feature they've been working on. Not everything should go
> > > through
> > > > > the
> > > > > > >> dev
> > > > > > >> list. Otherwise, it will be inundated. However, agree, that
> > > > > > architectural
> > > > > > >> and release decisions need to be done publicly.
> > > > > > >>
> > > > > > >> Speaking about Service Grid, there was a discussion where I
> saw
> > > that
> > > > > it
> > > > > > >> was
> > > > > > >> questionable whether it gets added to the release or not.
> > > > > > >>
> > > > > > >> *Vladislav*, could you please shed some light on the current
> > > status of
> > > > > > the
> > > > > > >> service grid?
> > > > > > >>
> > > > > > >> On Thu, Sep 27, 2018 at 9:12 AM Dmitriy Pavlov <
> > > dpavlov.spb@gmail.com
> > > > > >
> > > > > > >> wrote:
> > > > > > >>
> > > > > > >> > Ok, let's wait for feedback from SG Author(s)/Reviewer(s)
> > > first. If
> > > > > it
> > > > > > >> is
> > > > > > >> > not ready, ok. But I thought it is almost done.
> > > > > > >> >
> > > > > > >> > I apologize if I missed some discussion (it can happen), but
> > > > > > >> > According to the statement "our current agreement"
> > > > > > >> > I can suspect some members are making some sort of private
> > > > > agreements,
> > > > > > >> and
> > > > > > >> > do not to discuss it on the list.
> > > > > > >> >
> > > > > > >> > Let's build consensus here first, and then name an
> agreement.
> > > > > > >> >
> > > > > > >> > Denis, as PMC Chair, could you please control, that Service
> > Grid
> > > > > > >> > inclusion/exclusion is discussed properly according to the
> > > Apache
> > > > > Way.
> > > > > > >> >
> > > > > > >> > чт, 27 сент. 2018 г. в 18:55, Vladimir Ozerov <
> > > vozerov@gridgain.com
> > > > > >:
> > > > > > >> >
> > > > > > >> >> Dmitriy,
> > > > > > >> >>
> > > > > > >> >> This is an outcome of current state of Service Grid - it is
> > not
> > > > > > ready.
> > > > > > >> We
> > > > > > >> >> never committed to have it to 2.7. Our goal was to try to
> > > include
> > > > > it
> > > > > > >> into
> > > > > > >> >> 2.7.
> > > > > > >> >>
> > > > > > >> >> On Thu, Sep 27, 2018 at 6:48 PM Dmitriy Pavlov <
> > > > > > dpavlov.spb@gmail.com>
> > > > > > >> >> wrote:
> > > > > > >> >>
> > > > > > >> >> > Could you please provide a reference to some thread?
> > > Probably I
> > > > > > >> missed
> > > > > > >> >> it.
> > > > > > >> >> >
> > > > > > >> >> > чт, 27 сент. 2018 г. в 18:46, Vladimir Ozerov <
> > > > > > vozerov@gridgain.com
> > > > > > >> >:
> > > > > > >> >> >
> > > > > > >> >> > > Our current agreement is that Service Grid is out of
> > scope.
> > > > > This
> > > > > > >> is a
> > > > > > >> >> > huge
> > > > > > >> >> > > feature, which hasn't entered review stage so far, We
> > will
> > > not
> > > > > be
> > > > > > >> >> able to
> > > > > > >> >> > > review/fix/test it properly.
> > > > > > >> >> > >
> > > > > > >> >> > > On Thu, Sep 27, 2018 at 6:32 PM Dmitriy Pavlov <
> > > > > > >> dpavlov.spb@gmail.com
> > > > > > >> >> >
> > > > > > >> >> > > wrote:
> > > > > > >> >> > >
> > > > > > >> >> > > > I agree, and I prefer four weeks for stabilization*
> (1
> > > Oct -
> > > > > 29
> > > > > > >> Oct)
> > > > > > >> >> > > >
> > > > > > >> >> > > > Do I understand it correctly: Service Grid is still
> in
> > > scope,
> > > > > > >> isn't
> > > > > > >> >> > it? I
> > > > > > >> >> > > > find it very important.
> > > > > > >> >> > > >
> > > > > > >> >> > > > чт, 27 сент. 2018 г. в 18:28, Nikolay Izhikov <
> > > > > > >> nizhikov@apache.org
> > > > > > >> >> >:
> > > > > > >> >> > > >
> > > > > > >> >> > > > > Hello, Vova.
> > > > > > >> >> > > > >
> > > > > > >> >> > > > > Thank you for clear release status.
> > > > > > >> >> > > > > I'm +1 for your proposal.
> > > > > > >> >> > > > >
> > > > > > >> >> > > > > чт, 27 сент. 2018 г., 18:25 Alexey Kuznetsov <
> > > > > > >> >> akuznetsov@apache.org
> > > > > > >> >> > >:
> > > > > > >> >> > > > >
> > > > > > >> >> > > > > > Vova,
> > > > > > >> >> > > > > >
> > > > > > >> >> > > > > > Huge +1 to do a stabilization.
> > > > > > >> >> > > > > >
> > > > > > >> >> > > > > >
> > > > > > >> >> > > > > > --
> > > > > > >> >> > > > > > Alexey Kuznetsov
> > > > > > >> >> > > > > >
> > > > > > >> >> > > > >
> > > > > > >> >> > > >
> > > > > > >> >> > >
> > > > > > >> >> >
> > > > > > >> >>
> > > > > > >> >
> > > > > > >>
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Best regards,
> > > > > Andrey Kuznetsov.
> > > > >
> > >
> > >
> > >
> > > --
> > > Best Regards, Vyacheslav D.
> > >
> >
>
Re: Apache Ignite 2.7 release
Posted by Vladimir Ozerov <vo...@gridgain.com>.
Dmitry,
Community agreement was to perform the release in October. Of course we can
wait a bit for services. Then we wait a bit for other cool features ready
by that time, then again and again, and release will never happen. And
while we are waiting for new features to come, already completerd features
cannot be used by anyone.
This is why we have an agreement that if feature is not ready, it should be
moved to future release, instead of shifting release. The sole reason to
have strict dates when decisions are made is to let release happen.
On Fri, Sep 28, 2018 at 2:22 AM Dmitriy Pavlov <dp...@gmail.com>
wrote:
> Vladimir, I'm not searching for enemy, and not fighting with you. I'm not
> happy about cases when we are hurrying.
>
> We can't fix test, fill ticket details, can't wait for contributions to
> finish their tasks. It is not best idea to use experience from commercial
> companies in open source. Are there any pressure outside community? Did
> someone promised rest of features to be released at 30 September?
>
> Let's remember principle do-orcracy, power of those who do. If contribor
> does change and reviewer does review, let's give right of making decision
> to them, but not to some closed club of people who privately discuss
> something.
>
> Sincerely
> Dmitriy Pavlov
>
> чт, 27 сент. 2018 г., 23:42 Vyacheslav Daradur <da...@gmail.com>:
>
> > Hi Igniters!
> >
> > As I have written about Service Grid before [1] I'm finalizing the
> > solution to be sure that implementation is reliable.
> >
> > About including it in 2.7, if we talk that code freeze tomorrow then
> > the solution is not ready to merge yet.
> > I hope that prereviewers Anton Vinogradov and Nikolay Izhikov will be
> > able to answer if solution out of scope or not in a couple of days.
> >
> > [1]
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-release-td34076.html#a34485
> > On Thu, Sep 27, 2018 at 11:14 PM Dmitriy Pavlov <dp...@gmail.com>
> > wrote:
> > >
> > > Yes, I agree, NPE during WAL flush is definitely a blocker.
> > >
> > > It is strange why the current test set did not fail after commit.
> > >
> > > чт, 27 сент. 2018 г. в 21:45, Andrey Kuznetsov <st...@gmail.com>:
> > >
> > > > Igniters,
> > > >
> > > > I've bumped into a new bug in WAL manager recently, see [1]. It looks
> > > > critical enough, and can be a good candidate for fixing before 2.7
> > release.
> > > >
> > > > Do you agree?
> > > >
> > > > [1] https://issues.apache.org/jira/browse/IGNITE-9731
> > > >
> > > > чт, 27 сент. 2018 г. в 19:45, Dmitriy Pavlov <dpavlov.spb@gmail.com
> >:
> > > >
> > > > > I need Vhyacheslav's opinion to be absolutely sure what status is
> > now.
> > > > >
> > > > > We never committed to dates of release, as well. I don't quite
> > understand
> > > > > what can mean 'the community committed to doing/releasing
> something'.
> > > > >
> > > > > About SG, I also concerned why such a big feature has quite a few
> > > > > discussions on the list. But it is another story.
> > > > >
> > > > > чт, 27 сент. 2018 г. в 19:33, Vladimir Ozerov <
> vozerov@gridgain.com
> > >:
> > > > >
> > > > > > Folks,
> > > > > >
> > > > > > Please stop looking for enemies everywhere. Just went through
> this
> > > > thread
> > > > > > and search for "service" word.
> > > > > >
> > > > > > On Thu, Sep 27, 2018 at 7:30 PM Denis Magda <dm...@apache.org>
> > wrote:
> > > > > >
> > > > > >> >
> > > > > >> > Denis, as PMC Chair, could you please control, that Service
> Grid
> > > > > >> > inclusion/exclusion is discussed properly according to the
> > Apache
> > > > Way.
> > > > > >>
> > > > > >>
> > > > > >> It's fine when committers/contributors have private discussions
> > > > related
> > > > > to
> > > > > >> a feature they've been working on. Not everything should go
> > through
> > > > the
> > > > > >> dev
> > > > > >> list. Otherwise, it will be inundated. However, agree, that
> > > > > architectural
> > > > > >> and release decisions need to be done publicly.
> > > > > >>
> > > > > >> Speaking about Service Grid, there was a discussion where I saw
> > that
> > > > it
> > > > > >> was
> > > > > >> questionable whether it gets added to the release or not.
> > > > > >>
> > > > > >> *Vladislav*, could you please shed some light on the current
> > status of
> > > > > the
> > > > > >> service grid?
> > > > > >>
> > > > > >> On Thu, Sep 27, 2018 at 9:12 AM Dmitriy Pavlov <
> > dpavlov.spb@gmail.com
> > > > >
> > > > > >> wrote:
> > > > > >>
> > > > > >> > Ok, let's wait for feedback from SG Author(s)/Reviewer(s)
> > first. If
> > > > it
> > > > > >> is
> > > > > >> > not ready, ok. But I thought it is almost done.
> > > > > >> >
> > > > > >> > I apologize if I missed some discussion (it can happen), but
> > > > > >> > According to the statement "our current agreement"
> > > > > >> > I can suspect some members are making some sort of private
> > > > agreements,
> > > > > >> and
> > > > > >> > do not to discuss it on the list.
> > > > > >> >
> > > > > >> > Let's build consensus here first, and then name an agreement.
> > > > > >> >
> > > > > >> > Denis, as PMC Chair, could you please control, that Service
> Grid
> > > > > >> > inclusion/exclusion is discussed properly according to the
> > Apache
> > > > Way.
> > > > > >> >
> > > > > >> > чт, 27 сент. 2018 г. в 18:55, Vladimir Ozerov <
> > vozerov@gridgain.com
> > > > >:
> > > > > >> >
> > > > > >> >> Dmitriy,
> > > > > >> >>
> > > > > >> >> This is an outcome of current state of Service Grid - it is
> not
> > > > > ready.
> > > > > >> We
> > > > > >> >> never committed to have it to 2.7. Our goal was to try to
> > include
> > > > it
> > > > > >> into
> > > > > >> >> 2.7.
> > > > > >> >>
> > > > > >> >> On Thu, Sep 27, 2018 at 6:48 PM Dmitriy Pavlov <
> > > > > dpavlov.spb@gmail.com>
> > > > > >> >> wrote:
> > > > > >> >>
> > > > > >> >> > Could you please provide a reference to some thread?
> > Probably I
> > > > > >> missed
> > > > > >> >> it.
> > > > > >> >> >
> > > > > >> >> > чт, 27 сент. 2018 г. в 18:46, Vladimir Ozerov <
> > > > > vozerov@gridgain.com
> > > > > >> >:
> > > > > >> >> >
> > > > > >> >> > > Our current agreement is that Service Grid is out of
> scope.
> > > > This
> > > > > >> is a
> > > > > >> >> > huge
> > > > > >> >> > > feature, which hasn't entered review stage so far, We
> will
> > not
> > > > be
> > > > > >> >> able to
> > > > > >> >> > > review/fix/test it properly.
> > > > > >> >> > >
> > > > > >> >> > > On Thu, Sep 27, 2018 at 6:32 PM Dmitriy Pavlov <
> > > > > >> dpavlov.spb@gmail.com
> > > > > >> >> >
> > > > > >> >> > > wrote:
> > > > > >> >> > >
> > > > > >> >> > > > I agree, and I prefer four weeks for stabilization* (1
> > Oct -
> > > > 29
> > > > > >> Oct)
> > > > > >> >> > > >
> > > > > >> >> > > > Do I understand it correctly: Service Grid is still in
> > scope,
> > > > > >> isn't
> > > > > >> >> > it? I
> > > > > >> >> > > > find it very important.
> > > > > >> >> > > >
> > > > > >> >> > > > чт, 27 сент. 2018 г. в 18:28, Nikolay Izhikov <
> > > > > >> nizhikov@apache.org
> > > > > >> >> >:
> > > > > >> >> > > >
> > > > > >> >> > > > > Hello, Vova.
> > > > > >> >> > > > >
> > > > > >> >> > > > > Thank you for clear release status.
> > > > > >> >> > > > > I'm +1 for your proposal.
> > > > > >> >> > > > >
> > > > > >> >> > > > > чт, 27 сент. 2018 г., 18:25 Alexey Kuznetsov <
> > > > > >> >> akuznetsov@apache.org
> > > > > >> >> > >:
> > > > > >> >> > > > >
> > > > > >> >> > > > > > Vova,
> > > > > >> >> > > > > >
> > > > > >> >> > > > > > Huge +1 to do a stabilization.
> > > > > >> >> > > > > >
> > > > > >> >> > > > > >
> > > > > >> >> > > > > > --
> > > > > >> >> > > > > > Alexey Kuznetsov
> > > > > >> >> > > > > >
> > > > > >> >> > > > >
> > > > > >> >> > > >
> > > > > >> >> > >
> > > > > >> >> >
> > > > > >> >>
> > > > > >> >
> > > > > >>
> > > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Best regards,
> > > > Andrey Kuznetsov.
> > > >
> >
> >
> >
> > --
> > Best Regards, Vyacheslav D.
> >
>
Re: Apache Ignite 2.7 release
Posted by Dmitriy Pavlov <dp...@gmail.com>.
Vladimir, I'm not searching for enemy, and not fighting with you. I'm not
happy about cases when we are hurrying.
We can't fix test, fill ticket details, can't wait for contributions to
finish their tasks. It is not best idea to use experience from commercial
companies in open source. Are there any pressure outside community? Did
someone promised rest of features to be released at 30 September?
Let's remember principle do-orcracy, power of those who do. If contribor
does change and reviewer does review, let's give right of making decision
to them, but not to some closed club of people who privately discuss
something.
Sincerely
Dmitriy Pavlov
чт, 27 сент. 2018 г., 23:42 Vyacheslav Daradur <da...@gmail.com>:
> Hi Igniters!
>
> As I have written about Service Grid before [1] I'm finalizing the
> solution to be sure that implementation is reliable.
>
> About including it in 2.7, if we talk that code freeze tomorrow then
> the solution is not ready to merge yet.
> I hope that prereviewers Anton Vinogradov and Nikolay Izhikov will be
> able to answer if solution out of scope or not in a couple of days.
>
> [1]
> http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-release-td34076.html#a34485
> On Thu, Sep 27, 2018 at 11:14 PM Dmitriy Pavlov <dp...@gmail.com>
> wrote:
> >
> > Yes, I agree, NPE during WAL flush is definitely a blocker.
> >
> > It is strange why the current test set did not fail after commit.
> >
> > чт, 27 сент. 2018 г. в 21:45, Andrey Kuznetsov <st...@gmail.com>:
> >
> > > Igniters,
> > >
> > > I've bumped into a new bug in WAL manager recently, see [1]. It looks
> > > critical enough, and can be a good candidate for fixing before 2.7
> release.
> > >
> > > Do you agree?
> > >
> > > [1] https://issues.apache.org/jira/browse/IGNITE-9731
> > >
> > > чт, 27 сент. 2018 г. в 19:45, Dmitriy Pavlov <dp...@gmail.com>:
> > >
> > > > I need Vhyacheslav's opinion to be absolutely sure what status is
> now.
> > > >
> > > > We never committed to dates of release, as well. I don't quite
> understand
> > > > what can mean 'the community committed to doing/releasing something'.
> > > >
> > > > About SG, I also concerned why such a big feature has quite a few
> > > > discussions on the list. But it is another story.
> > > >
> > > > чт, 27 сент. 2018 г. в 19:33, Vladimir Ozerov <vozerov@gridgain.com
> >:
> > > >
> > > > > Folks,
> > > > >
> > > > > Please stop looking for enemies everywhere. Just went through this
> > > thread
> > > > > and search for "service" word.
> > > > >
> > > > > On Thu, Sep 27, 2018 at 7:30 PM Denis Magda <dm...@apache.org>
> wrote:
> > > > >
> > > > >> >
> > > > >> > Denis, as PMC Chair, could you please control, that Service Grid
> > > > >> > inclusion/exclusion is discussed properly according to the
> Apache
> > > Way.
> > > > >>
> > > > >>
> > > > >> It's fine when committers/contributors have private discussions
> > > related
> > > > to
> > > > >> a feature they've been working on. Not everything should go
> through
> > > the
> > > > >> dev
> > > > >> list. Otherwise, it will be inundated. However, agree, that
> > > > architectural
> > > > >> and release decisions need to be done publicly.
> > > > >>
> > > > >> Speaking about Service Grid, there was a discussion where I saw
> that
> > > it
> > > > >> was
> > > > >> questionable whether it gets added to the release or not.
> > > > >>
> > > > >> *Vladislav*, could you please shed some light on the current
> status of
> > > > the
> > > > >> service grid?
> > > > >>
> > > > >> On Thu, Sep 27, 2018 at 9:12 AM Dmitriy Pavlov <
> dpavlov.spb@gmail.com
> > > >
> > > > >> wrote:
> > > > >>
> > > > >> > Ok, let's wait for feedback from SG Author(s)/Reviewer(s)
> first. If
> > > it
> > > > >> is
> > > > >> > not ready, ok. But I thought it is almost done.
> > > > >> >
> > > > >> > I apologize if I missed some discussion (it can happen), but
> > > > >> > According to the statement "our current agreement"
> > > > >> > I can suspect some members are making some sort of private
> > > agreements,
> > > > >> and
> > > > >> > do not to discuss it on the list.
> > > > >> >
> > > > >> > Let's build consensus here first, and then name an agreement.
> > > > >> >
> > > > >> > Denis, as PMC Chair, could you please control, that Service Grid
> > > > >> > inclusion/exclusion is discussed properly according to the
> Apache
> > > Way.
> > > > >> >
> > > > >> > чт, 27 сент. 2018 г. в 18:55, Vladimir Ozerov <
> vozerov@gridgain.com
> > > >:
> > > > >> >
> > > > >> >> Dmitriy,
> > > > >> >>
> > > > >> >> This is an outcome of current state of Service Grid - it is not
> > > > ready.
> > > > >> We
> > > > >> >> never committed to have it to 2.7. Our goal was to try to
> include
> > > it
> > > > >> into
> > > > >> >> 2.7.
> > > > >> >>
> > > > >> >> On Thu, Sep 27, 2018 at 6:48 PM Dmitriy Pavlov <
> > > > dpavlov.spb@gmail.com>
> > > > >> >> wrote:
> > > > >> >>
> > > > >> >> > Could you please provide a reference to some thread?
> Probably I
> > > > >> missed
> > > > >> >> it.
> > > > >> >> >
> > > > >> >> > чт, 27 сент. 2018 г. в 18:46, Vladimir Ozerov <
> > > > vozerov@gridgain.com
> > > > >> >:
> > > > >> >> >
> > > > >> >> > > Our current agreement is that Service Grid is out of scope.
> > > This
> > > > >> is a
> > > > >> >> > huge
> > > > >> >> > > feature, which hasn't entered review stage so far, We will
> not
> > > be
> > > > >> >> able to
> > > > >> >> > > review/fix/test it properly.
> > > > >> >> > >
> > > > >> >> > > On Thu, Sep 27, 2018 at 6:32 PM Dmitriy Pavlov <
> > > > >> dpavlov.spb@gmail.com
> > > > >> >> >
> > > > >> >> > > wrote:
> > > > >> >> > >
> > > > >> >> > > > I agree, and I prefer four weeks for stabilization* (1
> Oct -
> > > 29
> > > > >> Oct)
> > > > >> >> > > >
> > > > >> >> > > > Do I understand it correctly: Service Grid is still in
> scope,
> > > > >> isn't
> > > > >> >> > it? I
> > > > >> >> > > > find it very important.
> > > > >> >> > > >
> > > > >> >> > > > чт, 27 сент. 2018 г. в 18:28, Nikolay Izhikov <
> > > > >> nizhikov@apache.org
> > > > >> >> >:
> > > > >> >> > > >
> > > > >> >> > > > > Hello, Vova.
> > > > >> >> > > > >
> > > > >> >> > > > > Thank you for clear release status.
> > > > >> >> > > > > I'm +1 for your proposal.
> > > > >> >> > > > >
> > > > >> >> > > > > чт, 27 сент. 2018 г., 18:25 Alexey Kuznetsov <
> > > > >> >> akuznetsov@apache.org
> > > > >> >> > >:
> > > > >> >> > > > >
> > > > >> >> > > > > > Vova,
> > > > >> >> > > > > >
> > > > >> >> > > > > > Huge +1 to do a stabilization.
> > > > >> >> > > > > >
> > > > >> >> > > > > >
> > > > >> >> > > > > > --
> > > > >> >> > > > > > Alexey Kuznetsov
> > > > >> >> > > > > >
> > > > >> >> > > > >
> > > > >> >> > > >
> > > > >> >> > >
> > > > >> >> >
> > > > >> >>
> > > > >> >
> > > > >>
> > > > >
> > > >
> > >
> > >
> > > --
> > > Best regards,
> > > Andrey Kuznetsov.
> > >
>
>
>
> --
> Best Regards, Vyacheslav D.
>
Re: Apache Ignite 2.7 release
Posted by Vyacheslav Daradur <da...@gmail.com>.
Hi Igniters!
As I have written about Service Grid before [1] I'm finalizing the
solution to be sure that implementation is reliable.
About including it in 2.7, if we talk that code freeze tomorrow then
the solution is not ready to merge yet.
I hope that prereviewers Anton Vinogradov and Nikolay Izhikov will be
able to answer if solution out of scope or not in a couple of days.
[1] http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-release-td34076.html#a34485
On Thu, Sep 27, 2018 at 11:14 PM Dmitriy Pavlov <dp...@gmail.com> wrote:
>
> Yes, I agree, NPE during WAL flush is definitely a blocker.
>
> It is strange why the current test set did not fail after commit.
>
> чт, 27 сент. 2018 г. в 21:45, Andrey Kuznetsov <st...@gmail.com>:
>
> > Igniters,
> >
> > I've bumped into a new bug in WAL manager recently, see [1]. It looks
> > critical enough, and can be a good candidate for fixing before 2.7 release.
> >
> > Do you agree?
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-9731
> >
> > чт, 27 сент. 2018 г. в 19:45, Dmitriy Pavlov <dp...@gmail.com>:
> >
> > > I need Vhyacheslav's opinion to be absolutely sure what status is now.
> > >
> > > We never committed to dates of release, as well. I don't quite understand
> > > what can mean 'the community committed to doing/releasing something'.
> > >
> > > About SG, I also concerned why such a big feature has quite a few
> > > discussions on the list. But it is another story.
> > >
> > > чт, 27 сент. 2018 г. в 19:33, Vladimir Ozerov <vo...@gridgain.com>:
> > >
> > > > Folks,
> > > >
> > > > Please stop looking for enemies everywhere. Just went through this
> > thread
> > > > and search for "service" word.
> > > >
> > > > On Thu, Sep 27, 2018 at 7:30 PM Denis Magda <dm...@apache.org> wrote:
> > > >
> > > >> >
> > > >> > Denis, as PMC Chair, could you please control, that Service Grid
> > > >> > inclusion/exclusion is discussed properly according to the Apache
> > Way.
> > > >>
> > > >>
> > > >> It's fine when committers/contributors have private discussions
> > related
> > > to
> > > >> a feature they've been working on. Not everything should go through
> > the
> > > >> dev
> > > >> list. Otherwise, it will be inundated. However, agree, that
> > > architectural
> > > >> and release decisions need to be done publicly.
> > > >>
> > > >> Speaking about Service Grid, there was a discussion where I saw that
> > it
> > > >> was
> > > >> questionable whether it gets added to the release or not.
> > > >>
> > > >> *Vladislav*, could you please shed some light on the current status of
> > > the
> > > >> service grid?
> > > >>
> > > >> On Thu, Sep 27, 2018 at 9:12 AM Dmitriy Pavlov <dpavlov.spb@gmail.com
> > >
> > > >> wrote:
> > > >>
> > > >> > Ok, let's wait for feedback from SG Author(s)/Reviewer(s) first. If
> > it
> > > >> is
> > > >> > not ready, ok. But I thought it is almost done.
> > > >> >
> > > >> > I apologize if I missed some discussion (it can happen), but
> > > >> > According to the statement "our current agreement"
> > > >> > I can suspect some members are making some sort of private
> > agreements,
> > > >> and
> > > >> > do not to discuss it on the list.
> > > >> >
> > > >> > Let's build consensus here first, and then name an agreement.
> > > >> >
> > > >> > Denis, as PMC Chair, could you please control, that Service Grid
> > > >> > inclusion/exclusion is discussed properly according to the Apache
> > Way.
> > > >> >
> > > >> > чт, 27 сент. 2018 г. в 18:55, Vladimir Ozerov <vozerov@gridgain.com
> > >:
> > > >> >
> > > >> >> Dmitriy,
> > > >> >>
> > > >> >> This is an outcome of current state of Service Grid - it is not
> > > ready.
> > > >> We
> > > >> >> never committed to have it to 2.7. Our goal was to try to include
> > it
> > > >> into
> > > >> >> 2.7.
> > > >> >>
> > > >> >> On Thu, Sep 27, 2018 at 6:48 PM Dmitriy Pavlov <
> > > dpavlov.spb@gmail.com>
> > > >> >> wrote:
> > > >> >>
> > > >> >> > Could you please provide a reference to some thread? Probably I
> > > >> missed
> > > >> >> it.
> > > >> >> >
> > > >> >> > чт, 27 сент. 2018 г. в 18:46, Vladimir Ozerov <
> > > vozerov@gridgain.com
> > > >> >:
> > > >> >> >
> > > >> >> > > Our current agreement is that Service Grid is out of scope.
> > This
> > > >> is a
> > > >> >> > huge
> > > >> >> > > feature, which hasn't entered review stage so far, We will not
> > be
> > > >> >> able to
> > > >> >> > > review/fix/test it properly.
> > > >> >> > >
> > > >> >> > > On Thu, Sep 27, 2018 at 6:32 PM Dmitriy Pavlov <
> > > >> dpavlov.spb@gmail.com
> > > >> >> >
> > > >> >> > > wrote:
> > > >> >> > >
> > > >> >> > > > I agree, and I prefer four weeks for stabilization* (1 Oct -
> > 29
> > > >> Oct)
> > > >> >> > > >
> > > >> >> > > > Do I understand it correctly: Service Grid is still in scope,
> > > >> isn't
> > > >> >> > it? I
> > > >> >> > > > find it very important.
> > > >> >> > > >
> > > >> >> > > > чт, 27 сент. 2018 г. в 18:28, Nikolay Izhikov <
> > > >> nizhikov@apache.org
> > > >> >> >:
> > > >> >> > > >
> > > >> >> > > > > Hello, Vova.
> > > >> >> > > > >
> > > >> >> > > > > Thank you for clear release status.
> > > >> >> > > > > I'm +1 for your proposal.
> > > >> >> > > > >
> > > >> >> > > > > чт, 27 сент. 2018 г., 18:25 Alexey Kuznetsov <
> > > >> >> akuznetsov@apache.org
> > > >> >> > >:
> > > >> >> > > > >
> > > >> >> > > > > > Vova,
> > > >> >> > > > > >
> > > >> >> > > > > > Huge +1 to do a stabilization.
> > > >> >> > > > > >
> > > >> >> > > > > >
> > > >> >> > > > > > --
> > > >> >> > > > > > Alexey Kuznetsov
> > > >> >> > > > > >
> > > >> >> > > > >
> > > >> >> > > >
> > > >> >> > >
> > > >> >> >
> > > >> >>
> > > >> >
> > > >>
> > > >
> > >
> >
> >
> > --
> > Best regards,
> > Andrey Kuznetsov.
> >
--
Best Regards, Vyacheslav D.
Re: Apache Ignite 2.7 release
Posted by Dmitriy Pavlov <dp...@gmail.com>.
Yes, I agree, NPE during WAL flush is definitely a blocker.
It is strange why the current test set did not fail after commit.
чт, 27 сент. 2018 г. в 21:45, Andrey Kuznetsov <st...@gmail.com>:
> Igniters,
>
> I've bumped into a new bug in WAL manager recently, see [1]. It looks
> critical enough, and can be a good candidate for fixing before 2.7 release.
>
> Do you agree?
>
> [1] https://issues.apache.org/jira/browse/IGNITE-9731
>
> чт, 27 сент. 2018 г. в 19:45, Dmitriy Pavlov <dp...@gmail.com>:
>
> > I need Vhyacheslav's opinion to be absolutely sure what status is now.
> >
> > We never committed to dates of release, as well. I don't quite understand
> > what can mean 'the community committed to doing/releasing something'.
> >
> > About SG, I also concerned why such a big feature has quite a few
> > discussions on the list. But it is another story.
> >
> > чт, 27 сент. 2018 г. в 19:33, Vladimir Ozerov <vo...@gridgain.com>:
> >
> > > Folks,
> > >
> > > Please stop looking for enemies everywhere. Just went through this
> thread
> > > and search for "service" word.
> > >
> > > On Thu, Sep 27, 2018 at 7:30 PM Denis Magda <dm...@apache.org> wrote:
> > >
> > >> >
> > >> > Denis, as PMC Chair, could you please control, that Service Grid
> > >> > inclusion/exclusion is discussed properly according to the Apache
> Way.
> > >>
> > >>
> > >> It's fine when committers/contributors have private discussions
> related
> > to
> > >> a feature they've been working on. Not everything should go through
> the
> > >> dev
> > >> list. Otherwise, it will be inundated. However, agree, that
> > architectural
> > >> and release decisions need to be done publicly.
> > >>
> > >> Speaking about Service Grid, there was a discussion where I saw that
> it
> > >> was
> > >> questionable whether it gets added to the release or not.
> > >>
> > >> *Vladislav*, could you please shed some light on the current status of
> > the
> > >> service grid?
> > >>
> > >> On Thu, Sep 27, 2018 at 9:12 AM Dmitriy Pavlov <dpavlov.spb@gmail.com
> >
> > >> wrote:
> > >>
> > >> > Ok, let's wait for feedback from SG Author(s)/Reviewer(s) first. If
> it
> > >> is
> > >> > not ready, ok. But I thought it is almost done.
> > >> >
> > >> > I apologize if I missed some discussion (it can happen), but
> > >> > According to the statement "our current agreement"
> > >> > I can suspect some members are making some sort of private
> agreements,
> > >> and
> > >> > do not to discuss it on the list.
> > >> >
> > >> > Let's build consensus here first, and then name an agreement.
> > >> >
> > >> > Denis, as PMC Chair, could you please control, that Service Grid
> > >> > inclusion/exclusion is discussed properly according to the Apache
> Way.
> > >> >
> > >> > чт, 27 сент. 2018 г. в 18:55, Vladimir Ozerov <vozerov@gridgain.com
> >:
> > >> >
> > >> >> Dmitriy,
> > >> >>
> > >> >> This is an outcome of current state of Service Grid - it is not
> > ready.
> > >> We
> > >> >> never committed to have it to 2.7. Our goal was to try to include
> it
> > >> into
> > >> >> 2.7.
> > >> >>
> > >> >> On Thu, Sep 27, 2018 at 6:48 PM Dmitriy Pavlov <
> > dpavlov.spb@gmail.com>
> > >> >> wrote:
> > >> >>
> > >> >> > Could you please provide a reference to some thread? Probably I
> > >> missed
> > >> >> it.
> > >> >> >
> > >> >> > чт, 27 сент. 2018 г. в 18:46, Vladimir Ozerov <
> > vozerov@gridgain.com
> > >> >:
> > >> >> >
> > >> >> > > Our current agreement is that Service Grid is out of scope.
> This
> > >> is a
> > >> >> > huge
> > >> >> > > feature, which hasn't entered review stage so far, We will not
> be
> > >> >> able to
> > >> >> > > review/fix/test it properly.
> > >> >> > >
> > >> >> > > On Thu, Sep 27, 2018 at 6:32 PM Dmitriy Pavlov <
> > >> dpavlov.spb@gmail.com
> > >> >> >
> > >> >> > > wrote:
> > >> >> > >
> > >> >> > > > I agree, and I prefer four weeks for stabilization* (1 Oct -
> 29
> > >> Oct)
> > >> >> > > >
> > >> >> > > > Do I understand it correctly: Service Grid is still in scope,
> > >> isn't
> > >> >> > it? I
> > >> >> > > > find it very important.
> > >> >> > > >
> > >> >> > > > чт, 27 сент. 2018 г. в 18:28, Nikolay Izhikov <
> > >> nizhikov@apache.org
> > >> >> >:
> > >> >> > > >
> > >> >> > > > > Hello, Vova.
> > >> >> > > > >
> > >> >> > > > > Thank you for clear release status.
> > >> >> > > > > I'm +1 for your proposal.
> > >> >> > > > >
> > >> >> > > > > чт, 27 сент. 2018 г., 18:25 Alexey Kuznetsov <
> > >> >> akuznetsov@apache.org
> > >> >> > >:
> > >> >> > > > >
> > >> >> > > > > > Vova,
> > >> >> > > > > >
> > >> >> > > > > > Huge +1 to do a stabilization.
> > >> >> > > > > >
> > >> >> > > > > >
> > >> >> > > > > > --
> > >> >> > > > > > Alexey Kuznetsov
> > >> >> > > > > >
> > >> >> > > > >
> > >> >> > > >
> > >> >> > >
> > >> >> >
> > >> >>
> > >> >
> > >>
> > >
> >
>
>
> --
> Best regards,
> Andrey Kuznetsov.
>
Re: Apache Ignite 2.7 release
Posted by Andrey Kuznetsov <st...@gmail.com>.
Igniters,
I've bumped into a new bug in WAL manager recently, see [1]. It looks
critical enough, and can be a good candidate for fixing before 2.7 release.
Do you agree?
[1] https://issues.apache.org/jira/browse/IGNITE-9731
чт, 27 сент. 2018 г. в 19:45, Dmitriy Pavlov <dp...@gmail.com>:
> I need Vhyacheslav's opinion to be absolutely sure what status is now.
>
> We never committed to dates of release, as well. I don't quite understand
> what can mean 'the community committed to doing/releasing something'.
>
> About SG, I also concerned why such a big feature has quite a few
> discussions on the list. But it is another story.
>
> чт, 27 сент. 2018 г. в 19:33, Vladimir Ozerov <vo...@gridgain.com>:
>
> > Folks,
> >
> > Please stop looking for enemies everywhere. Just went through this thread
> > and search for "service" word.
> >
> > On Thu, Sep 27, 2018 at 7:30 PM Denis Magda <dm...@apache.org> wrote:
> >
> >> >
> >> > Denis, as PMC Chair, could you please control, that Service Grid
> >> > inclusion/exclusion is discussed properly according to the Apache Way.
> >>
> >>
> >> It's fine when committers/contributors have private discussions related
> to
> >> a feature they've been working on. Not everything should go through the
> >> dev
> >> list. Otherwise, it will be inundated. However, agree, that
> architectural
> >> and release decisions need to be done publicly.
> >>
> >> Speaking about Service Grid, there was a discussion where I saw that it
> >> was
> >> questionable whether it gets added to the release or not.
> >>
> >> *Vladislav*, could you please shed some light on the current status of
> the
> >> service grid?
> >>
> >> On Thu, Sep 27, 2018 at 9:12 AM Dmitriy Pavlov <dp...@gmail.com>
> >> wrote:
> >>
> >> > Ok, let's wait for feedback from SG Author(s)/Reviewer(s) first. If it
> >> is
> >> > not ready, ok. But I thought it is almost done.
> >> >
> >> > I apologize if I missed some discussion (it can happen), but
> >> > According to the statement "our current agreement"
> >> > I can suspect some members are making some sort of private agreements,
> >> and
> >> > do not to discuss it on the list.
> >> >
> >> > Let's build consensus here first, and then name an agreement.
> >> >
> >> > Denis, as PMC Chair, could you please control, that Service Grid
> >> > inclusion/exclusion is discussed properly according to the Apache Way.
> >> >
> >> > чт, 27 сент. 2018 г. в 18:55, Vladimir Ozerov <vo...@gridgain.com>:
> >> >
> >> >> Dmitriy,
> >> >>
> >> >> This is an outcome of current state of Service Grid - it is not
> ready.
> >> We
> >> >> never committed to have it to 2.7. Our goal was to try to include it
> >> into
> >> >> 2.7.
> >> >>
> >> >> On Thu, Sep 27, 2018 at 6:48 PM Dmitriy Pavlov <
> dpavlov.spb@gmail.com>
> >> >> wrote:
> >> >>
> >> >> > Could you please provide a reference to some thread? Probably I
> >> missed
> >> >> it.
> >> >> >
> >> >> > чт, 27 сент. 2018 г. в 18:46, Vladimir Ozerov <
> vozerov@gridgain.com
> >> >:
> >> >> >
> >> >> > > Our current agreement is that Service Grid is out of scope. This
> >> is a
> >> >> > huge
> >> >> > > feature, which hasn't entered review stage so far, We will not be
> >> >> able to
> >> >> > > review/fix/test it properly.
> >> >> > >
> >> >> > > On Thu, Sep 27, 2018 at 6:32 PM Dmitriy Pavlov <
> >> dpavlov.spb@gmail.com
> >> >> >
> >> >> > > wrote:
> >> >> > >
> >> >> > > > I agree, and I prefer four weeks for stabilization* (1 Oct - 29
> >> Oct)
> >> >> > > >
> >> >> > > > Do I understand it correctly: Service Grid is still in scope,
> >> isn't
> >> >> > it? I
> >> >> > > > find it very important.
> >> >> > > >
> >> >> > > > чт, 27 сент. 2018 г. в 18:28, Nikolay Izhikov <
> >> nizhikov@apache.org
> >> >> >:
> >> >> > > >
> >> >> > > > > Hello, Vova.
> >> >> > > > >
> >> >> > > > > Thank you for clear release status.
> >> >> > > > > I'm +1 for your proposal.
> >> >> > > > >
> >> >> > > > > чт, 27 сент. 2018 г., 18:25 Alexey Kuznetsov <
> >> >> akuznetsov@apache.org
> >> >> > >:
> >> >> > > > >
> >> >> > > > > > Vova,
> >> >> > > > > >
> >> >> > > > > > Huge +1 to do a stabilization.
> >> >> > > > > >
> >> >> > > > > >
> >> >> > > > > > --
> >> >> > > > > > Alexey Kuznetsov
> >> >> > > > > >
> >> >> > > > >
> >> >> > > >
> >> >> > >
> >> >> >
> >> >>
> >> >
> >>
> >
>
--
Best regards,
Andrey Kuznetsov.
Re: Apache Ignite 2.7 release
Posted by Dmitriy Pavlov <dp...@gmail.com>.
I need Vhyacheslav's opinion to be absolutely sure what status is now.
We never committed to dates of release, as well. I don't quite understand
what can mean 'the community committed to doing/releasing something'.
About SG, I also concerned why such a big feature has quite a few
discussions on the list. But it is another story.
чт, 27 сент. 2018 г. в 19:33, Vladimir Ozerov <vo...@gridgain.com>:
> Folks,
>
> Please stop looking for enemies everywhere. Just went through this thread
> and search for "service" word.
>
> On Thu, Sep 27, 2018 at 7:30 PM Denis Magda <dm...@apache.org> wrote:
>
>> >
>> > Denis, as PMC Chair, could you please control, that Service Grid
>> > inclusion/exclusion is discussed properly according to the Apache Way.
>>
>>
>> It's fine when committers/contributors have private discussions related to
>> a feature they've been working on. Not everything should go through the
>> dev
>> list. Otherwise, it will be inundated. However, agree, that architectural
>> and release decisions need to be done publicly.
>>
>> Speaking about Service Grid, there was a discussion where I saw that it
>> was
>> questionable whether it gets added to the release or not.
>>
>> *Vladislav*, could you please shed some light on the current status of the
>> service grid?
>>
>> On Thu, Sep 27, 2018 at 9:12 AM Dmitriy Pavlov <dp...@gmail.com>
>> wrote:
>>
>> > Ok, let's wait for feedback from SG Author(s)/Reviewer(s) first. If it
>> is
>> > not ready, ok. But I thought it is almost done.
>> >
>> > I apologize if I missed some discussion (it can happen), but
>> > According to the statement "our current agreement"
>> > I can suspect some members are making some sort of private agreements,
>> and
>> > do not to discuss it on the list.
>> >
>> > Let's build consensus here first, and then name an agreement.
>> >
>> > Denis, as PMC Chair, could you please control, that Service Grid
>> > inclusion/exclusion is discussed properly according to the Apache Way.
>> >
>> > чт, 27 сент. 2018 г. в 18:55, Vladimir Ozerov <vo...@gridgain.com>:
>> >
>> >> Dmitriy,
>> >>
>> >> This is an outcome of current state of Service Grid - it is not ready.
>> We
>> >> never committed to have it to 2.7. Our goal was to try to include it
>> into
>> >> 2.7.
>> >>
>> >> On Thu, Sep 27, 2018 at 6:48 PM Dmitriy Pavlov <dp...@gmail.com>
>> >> wrote:
>> >>
>> >> > Could you please provide a reference to some thread? Probably I
>> missed
>> >> it.
>> >> >
>> >> > чт, 27 сент. 2018 г. в 18:46, Vladimir Ozerov <vozerov@gridgain.com
>> >:
>> >> >
>> >> > > Our current agreement is that Service Grid is out of scope. This
>> is a
>> >> > huge
>> >> > > feature, which hasn't entered review stage so far, We will not be
>> >> able to
>> >> > > review/fix/test it properly.
>> >> > >
>> >> > > On Thu, Sep 27, 2018 at 6:32 PM Dmitriy Pavlov <
>> dpavlov.spb@gmail.com
>> >> >
>> >> > > wrote:
>> >> > >
>> >> > > > I agree, and I prefer four weeks for stabilization* (1 Oct - 29
>> Oct)
>> >> > > >
>> >> > > > Do I understand it correctly: Service Grid is still in scope,
>> isn't
>> >> > it? I
>> >> > > > find it very important.
>> >> > > >
>> >> > > > чт, 27 сент. 2018 г. в 18:28, Nikolay Izhikov <
>> nizhikov@apache.org
>> >> >:
>> >> > > >
>> >> > > > > Hello, Vova.
>> >> > > > >
>> >> > > > > Thank you for clear release status.
>> >> > > > > I'm +1 for your proposal.
>> >> > > > >
>> >> > > > > чт, 27 сент. 2018 г., 18:25 Alexey Kuznetsov <
>> >> akuznetsov@apache.org
>> >> > >:
>> >> > > > >
>> >> > > > > > Vova,
>> >> > > > > >
>> >> > > > > > Huge +1 to do a stabilization.
>> >> > > > > >
>> >> > > > > >
>> >> > > > > > --
>> >> > > > > > Alexey Kuznetsov
>> >> > > > > >
>> >> > > > >
>> >> > > >
>> >> > >
>> >> >
>> >>
>> >
>>
>
Re: Apache Ignite 2.7 release
Posted by Vladimir Ozerov <vo...@gridgain.com>.
Folks,
Please stop looking for enemies everywhere. Just went through this thread
and search for "service" word.
On Thu, Sep 27, 2018 at 7:30 PM Denis Magda <dm...@apache.org> wrote:
> >
> > Denis, as PMC Chair, could you please control, that Service Grid
> > inclusion/exclusion is discussed properly according to the Apache Way.
>
>
> It's fine when committers/contributors have private discussions related to
> a feature they've been working on. Not everything should go through the dev
> list. Otherwise, it will be inundated. However, agree, that architectural
> and release decisions need to be done publicly.
>
> Speaking about Service Grid, there was a discussion where I saw that it was
> questionable whether it gets added to the release or not.
>
> *Vladislav*, could you please shed some light on the current status of the
> service grid?
>
> On Thu, Sep 27, 2018 at 9:12 AM Dmitriy Pavlov <dp...@gmail.com>
> wrote:
>
> > Ok, let's wait for feedback from SG Author(s)/Reviewer(s) first. If it is
> > not ready, ok. But I thought it is almost done.
> >
> > I apologize if I missed some discussion (it can happen), but
> > According to the statement "our current agreement"
> > I can suspect some members are making some sort of private agreements,
> and
> > do not to discuss it on the list.
> >
> > Let's build consensus here first, and then name an agreement.
> >
> > Denis, as PMC Chair, could you please control, that Service Grid
> > inclusion/exclusion is discussed properly according to the Apache Way.
> >
> > чт, 27 сент. 2018 г. в 18:55, Vladimir Ozerov <vo...@gridgain.com>:
> >
> >> Dmitriy,
> >>
> >> This is an outcome of current state of Service Grid - it is not ready.
> We
> >> never committed to have it to 2.7. Our goal was to try to include it
> into
> >> 2.7.
> >>
> >> On Thu, Sep 27, 2018 at 6:48 PM Dmitriy Pavlov <dp...@gmail.com>
> >> wrote:
> >>
> >> > Could you please provide a reference to some thread? Probably I missed
> >> it.
> >> >
> >> > чт, 27 сент. 2018 г. в 18:46, Vladimir Ozerov <vo...@gridgain.com>:
> >> >
> >> > > Our current agreement is that Service Grid is out of scope. This is
> a
> >> > huge
> >> > > feature, which hasn't entered review stage so far, We will not be
> >> able to
> >> > > review/fix/test it properly.
> >> > >
> >> > > On Thu, Sep 27, 2018 at 6:32 PM Dmitriy Pavlov <
> dpavlov.spb@gmail.com
> >> >
> >> > > wrote:
> >> > >
> >> > > > I agree, and I prefer four weeks for stabilization* (1 Oct - 29
> Oct)
> >> > > >
> >> > > > Do I understand it correctly: Service Grid is still in scope,
> isn't
> >> > it? I
> >> > > > find it very important.
> >> > > >
> >> > > > чт, 27 сент. 2018 г. в 18:28, Nikolay Izhikov <
> nizhikov@apache.org
> >> >:
> >> > > >
> >> > > > > Hello, Vova.
> >> > > > >
> >> > > > > Thank you for clear release status.
> >> > > > > I'm +1 for your proposal.
> >> > > > >
> >> > > > > чт, 27 сент. 2018 г., 18:25 Alexey Kuznetsov <
> >> akuznetsov@apache.org
> >> > >:
> >> > > > >
> >> > > > > > Vova,
> >> > > > > >
> >> > > > > > Huge +1 to do a stabilization.
> >> > > > > >
> >> > > > > >
> >> > > > > > --
> >> > > > > > Alexey Kuznetsov
> >> > > > > >
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> >
>
Re: Apache Ignite 2.7 release
Posted by Denis Magda <dm...@apache.org>.
>
> Denis, as PMC Chair, could you please control, that Service Grid
> inclusion/exclusion is discussed properly according to the Apache Way.
It's fine when committers/contributors have private discussions related to
a feature they've been working on. Not everything should go through the dev
list. Otherwise, it will be inundated. However, agree, that architectural
and release decisions need to be done publicly.
Speaking about Service Grid, there was a discussion where I saw that it was
questionable whether it gets added to the release or not.
*Vladislav*, could you please shed some light on the current status of the
service grid?
On Thu, Sep 27, 2018 at 9:12 AM Dmitriy Pavlov <dp...@gmail.com>
wrote:
> Ok, let's wait for feedback from SG Author(s)/Reviewer(s) first. If it is
> not ready, ok. But I thought it is almost done.
>
> I apologize if I missed some discussion (it can happen), but
> According to the statement "our current agreement"
> I can suspect some members are making some sort of private agreements, and
> do not to discuss it on the list.
>
> Let's build consensus here first, and then name an agreement.
>
> Denis, as PMC Chair, could you please control, that Service Grid
> inclusion/exclusion is discussed properly according to the Apache Way.
>
> чт, 27 сент. 2018 г. в 18:55, Vladimir Ozerov <vo...@gridgain.com>:
>
>> Dmitriy,
>>
>> This is an outcome of current state of Service Grid - it is not ready. We
>> never committed to have it to 2.7. Our goal was to try to include it into
>> 2.7.
>>
>> On Thu, Sep 27, 2018 at 6:48 PM Dmitriy Pavlov <dp...@gmail.com>
>> wrote:
>>
>> > Could you please provide a reference to some thread? Probably I missed
>> it.
>> >
>> > чт, 27 сент. 2018 г. в 18:46, Vladimir Ozerov <vo...@gridgain.com>:
>> >
>> > > Our current agreement is that Service Grid is out of scope. This is a
>> > huge
>> > > feature, which hasn't entered review stage so far, We will not be
>> able to
>> > > review/fix/test it properly.
>> > >
>> > > On Thu, Sep 27, 2018 at 6:32 PM Dmitriy Pavlov <dpavlov.spb@gmail.com
>> >
>> > > wrote:
>> > >
>> > > > I agree, and I prefer four weeks for stabilization* (1 Oct - 29 Oct)
>> > > >
>> > > > Do I understand it correctly: Service Grid is still in scope, isn't
>> > it? I
>> > > > find it very important.
>> > > >
>> > > > чт, 27 сент. 2018 г. в 18:28, Nikolay Izhikov <nizhikov@apache.org
>> >:
>> > > >
>> > > > > Hello, Vova.
>> > > > >
>> > > > > Thank you for clear release status.
>> > > > > I'm +1 for your proposal.
>> > > > >
>> > > > > чт, 27 сент. 2018 г., 18:25 Alexey Kuznetsov <
>> akuznetsov@apache.org
>> > >:
>> > > > >
>> > > > > > Vova,
>> > > > > >
>> > > > > > Huge +1 to do a stabilization.
>> > > > > >
>> > > > > >
>> > > > > > --
>> > > > > > Alexey Kuznetsov
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>>
>
Re: Apache Ignite 2.7 release
Posted by Dmitriy Pavlov <dp...@gmail.com>.
Ok, let's wait for feedback from SG Author(s)/Reviewer(s) first. If it is
not ready, ok. But I thought it is almost done.
I apologize if I missed some discussion (it can happen), but
According to the statement "our current agreement"
I can suspect some members are making some sort of private agreements, and
do not to discuss it on the list.
Let's build consensus here first, and then name an agreement.
Denis, as PMC Chair, could you please control, that Service Grid
inclusion/exclusion is discussed properly according to the Apache Way.
чт, 27 сент. 2018 г. в 18:55, Vladimir Ozerov <vo...@gridgain.com>:
> Dmitriy,
>
> This is an outcome of current state of Service Grid - it is not ready. We
> never committed to have it to 2.7. Our goal was to try to include it into
> 2.7.
>
> On Thu, Sep 27, 2018 at 6:48 PM Dmitriy Pavlov <dp...@gmail.com>
> wrote:
>
> > Could you please provide a reference to some thread? Probably I missed
> it.
> >
> > чт, 27 сент. 2018 г. в 18:46, Vladimir Ozerov <vo...@gridgain.com>:
> >
> > > Our current agreement is that Service Grid is out of scope. This is a
> > huge
> > > feature, which hasn't entered review stage so far, We will not be able
> to
> > > review/fix/test it properly.
> > >
> > > On Thu, Sep 27, 2018 at 6:32 PM Dmitriy Pavlov <dp...@gmail.com>
> > > wrote:
> > >
> > > > I agree, and I prefer four weeks for stabilization* (1 Oct - 29 Oct)
> > > >
> > > > Do I understand it correctly: Service Grid is still in scope, isn't
> > it? I
> > > > find it very important.
> > > >
> > > > чт, 27 сент. 2018 г. в 18:28, Nikolay Izhikov <ni...@apache.org>:
> > > >
> > > > > Hello, Vova.
> > > > >
> > > > > Thank you for clear release status.
> > > > > I'm +1 for your proposal.
> > > > >
> > > > > чт, 27 сент. 2018 г., 18:25 Alexey Kuznetsov <
> akuznetsov@apache.org
> > >:
> > > > >
> > > > > > Vova,
> > > > > >
> > > > > > Huge +1 to do a stabilization.
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Alexey Kuznetsov
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: Apache Ignite 2.7 release
Posted by Vladimir Ozerov <vo...@gridgain.com>.
Dmitriy,
This is an outcome of current state of Service Grid - it is not ready. We
never committed to have it to 2.7. Our goal was to try to include it into
2.7.
On Thu, Sep 27, 2018 at 6:48 PM Dmitriy Pavlov <dp...@gmail.com>
wrote:
> Could you please provide a reference to some thread? Probably I missed it.
>
> чт, 27 сент. 2018 г. в 18:46, Vladimir Ozerov <vo...@gridgain.com>:
>
> > Our current agreement is that Service Grid is out of scope. This is a
> huge
> > feature, which hasn't entered review stage so far, We will not be able to
> > review/fix/test it properly.
> >
> > On Thu, Sep 27, 2018 at 6:32 PM Dmitriy Pavlov <dp...@gmail.com>
> > wrote:
> >
> > > I agree, and I prefer four weeks for stabilization* (1 Oct - 29 Oct)
> > >
> > > Do I understand it correctly: Service Grid is still in scope, isn't
> it? I
> > > find it very important.
> > >
> > > чт, 27 сент. 2018 г. в 18:28, Nikolay Izhikov <ni...@apache.org>:
> > >
> > > > Hello, Vova.
> > > >
> > > > Thank you for clear release status.
> > > > I'm +1 for your proposal.
> > > >
> > > > чт, 27 сент. 2018 г., 18:25 Alexey Kuznetsov <akuznetsov@apache.org
> >:
> > > >
> > > > > Vova,
> > > > >
> > > > > Huge +1 to do a stabilization.
> > > > >
> > > > >
> > > > > --
> > > > > Alexey Kuznetsov
> > > > >
> > > >
> > >
> >
>
Re: Apache Ignite 2.7 release
Posted by Dmitriy Pavlov <dp...@gmail.com>.
Could you please provide a reference to some thread? Probably I missed it.
чт, 27 сент. 2018 г. в 18:46, Vladimir Ozerov <vo...@gridgain.com>:
> Our current agreement is that Service Grid is out of scope. This is a huge
> feature, which hasn't entered review stage so far, We will not be able to
> review/fix/test it properly.
>
> On Thu, Sep 27, 2018 at 6:32 PM Dmitriy Pavlov <dp...@gmail.com>
> wrote:
>
> > I agree, and I prefer four weeks for stabilization* (1 Oct - 29 Oct)
> >
> > Do I understand it correctly: Service Grid is still in scope, isn't it? I
> > find it very important.
> >
> > чт, 27 сент. 2018 г. в 18:28, Nikolay Izhikov <ni...@apache.org>:
> >
> > > Hello, Vova.
> > >
> > > Thank you for clear release status.
> > > I'm +1 for your proposal.
> > >
> > > чт, 27 сент. 2018 г., 18:25 Alexey Kuznetsov <ak...@apache.org>:
> > >
> > > > Vova,
> > > >
> > > > Huge +1 to do a stabilization.
> > > >
> > > >
> > > > --
> > > > Alexey Kuznetsov
> > > >
> > >
> >
>
Re: Apache Ignite 2.7 release
Posted by Vladimir Ozerov <vo...@gridgain.com>.
Our current agreement is that Service Grid is out of scope. This is a huge
feature, which hasn't entered review stage so far, We will not be able to
review/fix/test it properly.
On Thu, Sep 27, 2018 at 6:32 PM Dmitriy Pavlov <dp...@gmail.com>
wrote:
> I agree, and I prefer four weeks for stabilization* (1 Oct - 29 Oct)
>
> Do I understand it correctly: Service Grid is still in scope, isn't it? I
> find it very important.
>
> чт, 27 сент. 2018 г. в 18:28, Nikolay Izhikov <ni...@apache.org>:
>
> > Hello, Vova.
> >
> > Thank you for clear release status.
> > I'm +1 for your proposal.
> >
> > чт, 27 сент. 2018 г., 18:25 Alexey Kuznetsov <ak...@apache.org>:
> >
> > > Vova,
> > >
> > > Huge +1 to do a stabilization.
> > >
> > >
> > > --
> > > Alexey Kuznetsov
> > >
> >
>
Re: Apache Ignite 2.7 release
Posted by Dmitriy Pavlov <dp...@gmail.com>.
I agree, and I prefer four weeks for stabilization* (1 Oct - 29 Oct)
Do I understand it correctly: Service Grid is still in scope, isn't it? I
find it very important.
чт, 27 сент. 2018 г. в 18:28, Nikolay Izhikov <ni...@apache.org>:
> Hello, Vova.
>
> Thank you for clear release status.
> I'm +1 for your proposal.
>
> чт, 27 сент. 2018 г., 18:25 Alexey Kuznetsov <ak...@apache.org>:
>
> > Vova,
> >
> > Huge +1 to do a stabilization.
> >
> >
> > --
> > Alexey Kuznetsov
> >
>
Re: Apache Ignite 2.7 release
Posted by Nikolay Izhikov <ni...@apache.org>.
Hello, Vova.
Thank you for clear release status.
I'm +1 for your proposal.
чт, 27 сент. 2018 г., 18:25 Alexey Kuznetsov <ak...@apache.org>:
> Vova,
>
> Huge +1 to do a stabilization.
>
>
> --
> Alexey Kuznetsov
>
Re: Apache Ignite 2.7 release
Posted by Alexey Kuznetsov <ak...@apache.org>.
Vova,
Huge +1 to do a stabilization.
--
Alexey Kuznetsov
Re: Apache Ignite 2.7 release
Posted by Vladimir Ozerov <vo...@gridgain.com>.
Igniters,
Code Freeze date is tomorrow. Bad news is that we still have a number of
important features not-yet-merged (of most important - some MVCC stuff,
TDE, PHP/Python clients). Good news is that we made a good progress with
scope decrease. I propose the following release plan then:
1) By 30 Sept, only tickets critical for AI 2.7 release should have 2.7 fix
version. I expect that there should be about ~30 tickets, and most of them
are critical bugs (either existing or in new features). This is what we
call Code Freeze. From this time it is not allowed to add any tickets
to 2.7 unless
you are able to prove that it is a blocker for the release. This means
absolute ban for any new features.
2) Then we take *3 weeks for stabilization*: 1 Oct - 22 Oct. During this
time we fix all known bugs in new features, and finalize those new features
which are slightly behind a schedule. I would even suggest to take *4 weeks
for stabilization* (1 Oct - 29 Oct)
3) Once stabilization is over, we start vote.
This big stabilization window is essential for us, as current release will
contain a lot of huge features, which should be tested thoroughly before
going public. But the very critical ingredient here - *no new tickets on
AI 2.7* during this phase except of critical bug fixes found during
stabilization phase.
In the end we will have nice and well tested AI 2.7 at the end of October.
What do you think about it?
On Fri, Sep 21, 2018 at 4:17 PM Nikolay Izhikov <ni...@apache.org> wrote:
> Hello, Igniters.
>
> I ping assigners in all tickets hase been planned for 2.7 and work is
> started.
> I plan to move all tickets in 'Open' state to 2.8 on Moday, 24 September.
>
> Please, respond, if you have any objections.
>
>
> В Ср, 19/09/2018 в 16:02 +0300, Andrey Gura пишет:
> > Nikolay,
> >
> > since we talk about scope freeze all you need now just create
> > ignite-2.7 branch. We still can have tickets targeted to 2.7 release
> > in progress. So you shouldn't move tickets to 2.8 because they can be
> > targeted to 2.7 intentionally and will be merged to master and
> > ignite-2.7 branches.
> > On Wed, Sep 19, 2018 at 12:18 PM Nikolay Izhikov <ni...@apache.org>
> wrote:
> > >
> > > Hello, Igniters.
> > >
> > > Vova, thank you for pointing this out.
> > >
> > > I ask all community members to iterate over assigned tickets.
> > > Please, move your tickets to 2.8 release if work is still in progress.
> > > At the end of the day, I will do it by myself and tomorrow we should
> have
> > > release scope prepared.
> > >
> > >
> > > ср, 19 сент. 2018 г. в 12:08, Vladimir Ozerov <vo...@gridgain.com>:
> > >
> > > > My point was not about code freeze, but about scope freeze, what
> means that
> > > > starting from this point AI 2.7 release should not receive any
> commits
> > > > which doesn't relate to it.
> > > >
> > > > On Wed, Sep 19, 2018 at 11:55 AM Anton Vinogradov <av...@apache.org>
> wrote:
> > > >
> > > > > Vova,
> > > > >
> > > > > AFAIK, codefreeze was not announced yet.
> > > > > Correct me in case I missed this.
> > > > >
> > > > > Now, Nikolay finishing checks that he's able to perform release
> > > >
> > > > (everything
> > > > > installed and properly configured).
> > > > > So, I recommend him to mention this check here to solve any
> > > > > misunderstanding in case some branches or tags related to 2.7 will
> be
> > > >
> > > > found
> > > > > before we announced codefreeze.
> > > > >
> > > > > ср, 19 сент. 2018 г. в 11:45, Vladimir Ozerov <
> vozerov@gridgain.com>:
> > > > >
> > > > > > Anton,
> > > > > >
> > > > > > What do you mean under "preparation to real 2.7". It is already
> real,
> > > >
> > > > we
> > > > > > reached formal code freeze phase we agreed on. At this point we
> need to
> > > > > > exclude non-2.7 commits, otherwise we will not be able to come to
> > > >
> > > > stable
> > > > > > branch in two weeks.
> > > > > > For this reason creating a branch for 2.7 at the moment is
> perfectly
> > > > >
> > > > > valid
> > > > > > thing. This is how we made releases previously.
> > > > > >
> > > > > > On Tue, Sep 18, 2018 at 7:59 PM Dmitriy Pavlov <
> dpavlov.spb@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Hi Paul.
> > > > > > >
> > > > > > > There are 2 PRs linked to that ticket. Who is reviewing your
> changes?
> > > > > > >
> > > > > > > Branch for 2.7 is still master, so if your changes are
> reviewed and
> > > > > > > accepted soon it will be in 2.7.
> > > > > > >
> > > > > > > Sincerely,
> > > > > > > Dmitriy Pavlov
> > > > > > >
> > > > > > > вт, 18 сент. 2018 г. в 16:22, Paul Anderson <
> deviljelly@gmail.com>:
> > > > > > >
> > > > > > > > Hi, may I ask for IGNITE-9298 to be included in 2.7 pls
> > > > > > > >
> > > > > > > > On Tue, Sep 18, 2018 at 1:03 PM Nikolay Izhikov <
> > > >
> > > > nizhikov@apache.org
> > > > > >
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Hello, folks.
> > > > > > > > >
> > > > > > > > > Thanks for the comments.
> > > > > > > > >
> > > > > > > > > I will follow them.
> > > > > > > > >
> > > > > > > > > В Вт, 18/09/2018 в 13:31 +0300, Anton Vinogradov пишет:
> > > > > > > > > > Nikolay,
> > > > > > > > > >
> > > > > > > > > > 1) *Do not* create ignite-2.7 branch until we're not
> started
> > > > > > > >
> > > > > > > > preparation
> > > > > > > > > to
> > > > > > > > > > real 2.7.
> > > > > > > > > > Use some temporary branch for this check instead, eg.
> > > > > > > > > > ignite-2.7-release-test
> > > > > > > > > >
> > > > > > > > > > 2) Please make sure you'll not cause real release actions
> > > >
> > > > (maven
> > > > > > > > release
> > > > > > > > > > and so on).
> > > > > > > > > > Perform only vote_* steps.
> > > > > > > > > >
> > > > > > > > > > 3) Make sure you'll remove all tags, branches, and other
> RC
> > > > > >
> > > > > > artifacts
> > > > > > > > > after
> > > > > > > > > > check.
> > > > > > > > > >
> > > > > > > > > > 4) Mark this release as RC0 to make sure it will be
> clear to
> > > > > > >
> > > > > > > everybody
> > > > > > > > > that
> > > > > > > > > > it's a check.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > вт, 18 сент. 2018 г. в 13:24, Dmitriy Setrakyan <
> > > > > > >
> > > > > > > dsetrakyan@apache.org
> > > > > > > > > :
> > > > > > > > > >
> > > > > > > > > > > If it is an Ignite release, then it has to pass
> through the
> > > > >
> > > > > vote.
> > > > > > > If
> > > > > > > > > not,
> > > > > > > > > > > then you can do the test without publishing or
> uploading the
> > > > > > >
> > > > > > > release.
> > > > > > > > > > >
> > > > > > > > > > > D.
> > > > > > > > > > >
> > > > > > > > > > > On Tue, Sep 18, 2018 at 1:18 PM Petr Ivanov <
> > > > >
> > > > > mr.weider@gmail.com
> > > > > > >
> > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > > Ok.
> > > > > > > > > > > >
> > > > > > > > > > > > In case of TC questions — ask me.
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > > On 18 Sep 2018, at 13:16, Nikolay Izhikov <
> > > > > >
> > > > > > nizhikov@apache.org
> > > > > > > >
> > > > > > > > > wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > > Hello, Petr.
> > > > > > > > > > > > >
> > > > > > > > > > > > > I want to make ignite-2.7 branch today.
> > > > > > > > > > > > > And execute release procedure based on this branch.
> > > > > > > > > > > > >
> > > > > > > > > > > > > However, ignite-2.7 branch will be copy of master
> until
> > > > >
> > > > > code
> > > > > > > > freeze
> > > > > > > > > > >
> > > > > > > > > > > date.
> > > > > > > > > > > > >
> > > > > > > > > > > > > В Вт, 18/09/2018 в 13:13 +0300, Petr Ivanov пишет:
> > > > > > > > > > > > > > Will it be just a test or there is already
> ignite-2.7
> > > > > >
> > > > > > branch?
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Fabric removal related TC modifications are not
> ready
> > > > >
> > > > > yet,
> > > > > > > and
> > > > > > > > > code is
> > > > > > > > > > > >
> > > > > > > > > > > > not in master.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > > On 18 Sep 2018, at 13:07, Nikolay Izhikov <
> > > > > > > >
> > > > > > > > nizhikov@apache.org
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > wrote:
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Hello, Igniters.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > I want to start and release procedures and
> make an
> > > >
> > > > RC1
> > > > > > > build.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > It has a 2 intention:
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > 1. I want to walk through all release steps to
> make
> > > > >
> > > > > sure
> > > > > > > they
> > > > > > > > > all
> > > > > > > > > > > >
> > > > > > > > > > > > works for me.
> > > > > > > > > > > > > > > So I will be fully ready on release date.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > 2. We have updated some dependencies in 2.7
> and we
> > > >
> > > > need
> > > > > > to
> > > > > > > > > make sure
> > > > > > > > > > > >
> > > > > > > > > > > > binary build is still workable.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Any objections?
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > В Пт, 14/09/2018 в 18:52 +0300, Alexey
> Goncharuk
> > > >
> > > > пишет:
> > > > > > > > > > > > > > > > We already have all the mechanics in place
> to work
> > > > >
> > > > > with
> > > > > > > > > properties -
> > > > > > > > > > > >
> > > > > > > > > > > > we use
> > > > > > > > > > > > > > > > ignite.build and ignite.revision from
> > > > >
> > > > > ignite.properties
> > > > > > > > > which are
> > > > > > > > > > > >
> > > > > > > > > > > > adjusted
> > > > > > > > > > > > > > > > during the build in the binary package.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Should I create the ticket if there are no
> > > > >
> > > > > objections?
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > пт, 14 сент. 2018 г. в 13:22, Ilya
> Kasnacheev <
> > > > > > > > > > > >
> > > > > > > > > > > > ilya.kasnacheev@gmail.com>:
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Hello!
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > So now there's an issue that this script
> makes
> > > > >
> > > > > source
> > > > > > > > > change after
> > > > > > > > > > > >
> > > > > > > > > > > > every
> > > > > > > > > > > > > > > > > build, show up in git status.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > What we could do to it:
> > > > > > > > > > > > > > > > > - Commit the changes after the build,
> once. In
> > > > >
> > > > > hopes
> > > > > > > that
> > > > > > > > > it won't
> > > > > > > > > > > >
> > > > > > > > > > > > change
> > > > > > > > > > > > > > > > > very often. With benefit that we could do
> that
> > > > >
> > > > > right
> > > > > > > now,
> > > > > > > > > before
> > > > > > > > > > >
> > > > > > > > > > > the
> > > > > > > > > > > > code
> > > > > > > > > > > > > > > > > freeze.
> > > > > > > > > > > > > > > > > - Move these values to a properties file
> from
> > > >
> > > > both
> > > > > > > > pom.xml
> > > > > > > > > and
> > > > > > > > > > > > > > > > > IgniteProvider.java. Any problems with this
> > > > >
> > > > > approach?
> > > > > > > > > We'll just
> > > > > > > > > > > >
> > > > > > > > > > > > read them
> > > > > > > > > > > > > > > > > from classpath properties file.
> > > > > > > > > > > > > > > > > - Update the links in the file once and
> remove
> > > >
> > > > them
> > > > > > > from
> > > > > > > > > build
> > > > > > > > > > > >
> > > > > > > > > > > > process. Why
> > > > > > > > > > > > > > > > > were they added to build process in the
> first
> > > > >
> > > > > place -
> > > > > > > to
> > > > > > > > > make them
> > > > > > > > > > > > > > > > > configurable during build?
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Regards,
> > > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > вт, 11 сент. 2018 г. в 5:53, Roman Shtykh <
> > > > > > > > >
> > > > > > > > > rshtykh@yahoo.com>:
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Ilya,
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > The "latest" version is the default, and
> > > >
> > > > resolved
> > > > > > by
> > > > > > > > > > > > > > > > > > https://ignite.apache.org/latest which
> is used
> > > > >
> > > > > by
> > > > > > > our
> > > > > > > > > web site
> > > > > > > > > > > >
> > > > > > > > > > > > when a
> > > > > > > > > > > > > > > > > > user download the latest Ignite version.
> And I
> > > > > >
> > > > > > think
> > > > > > > > > this is the
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > authority
> > > > > > > > > > > > > > > > > > to judge of the latest official release
> > > >
> > > > (pom.xml
> > > > > > you
> > > > > > > > > suggest can
> > > > > > > > > > > >
> > > > > > > > > > > > have
> > > > > > > > > > > > > > > > > > SNAPSHOTs etc.).
> > > > > > > > > > > > > > > > > > Also, as I explained during our review
> > > >
> > > > sessions,
> > > > > > > > > > >
> > > > > > > > > > > ignite-mesos-2.6.0
> > > > > > > > > > > > is a
> > > > > > > > > > > > > > > > > > driver and doesn't mean you need to have
> Ignite
> > > > > > >
> > > > > > > 2.6.0.
> > > > > > > > > User can
> > > > > > > > > > >
> > > > > > > > > > > run
> > > > > > > > > > > > any
> > > > > > > > > > > > > > > > > > version of Ignite he/she specifies. By
> default,
> > > > > >
> > > > > > it's
> > > > > > > > > "latest" but
> > > > > > > > > > >
> > > > > > > > > > > a
> > > > > > > > > > > > user
> > > > > > > > > > > > > > > > > > can specify any version needed, even
> from a
> > > > > > >
> > > > > > > non-archive
> > > > > > > > > URL.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > In short, what we have now
> > > > > > > > > > > > > > > > > > 1. mesos driver (ignite-mesos-x.x.x)
> will use
> > > > > > >
> > > > > > > "latest"
> > > > > > > > > version by
> > > > > > > > > > > >
> > > > > > > > > > > > default
> > > > > > > > > > > > > > > > > > -> it will try to resolve the latest
> officially
> > > > > > > >
> > > > > > > > releases
> > > > > > > > > version
> > > > > > > > > > >
> > > > > > > > > > > of
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Apache
> > > > > > > > > > > > > > > > > > Ignite, find the closest mirror and
> download
> > > > >
> > > > > Ignite
> > > > > > > in
> > > > > > > > a
> > > > > > > > > minute.
> > > > > > > > > > >
> > > > > > > > > > > If
> > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > version resolution fails, we fall back
> to the
> > > > >
> > > > > slow
> > > > > > > > > apache archive
> > > > > > > > > > > >
> > > > > > > > > > > > (as you
> > > > > > > > > > > > > > > > > > suggest; in my opinion we better
> fail-fast
> > > > >
> > > > > instead
> > > > > > of
> > > > > > > > > waiting for
> > > > > > > > > > > >
> > > > > > > > > > > > hours
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > download, so the user can choose another
> > > >
> > > > download
> > > > > > > > option
> > > > > > > > > (3))
> > > > > > > > > > > > > > > > > > 2. If the user specifies the version
> > > >
> > > > explicitly,
> > > > > it
> > > > > > > > goes
> > > > > > > > > to the
> > > > > > > > > > >
> > > > > > > > > > > slow
> > > > > > > > > > > > > > > > > > apache archive.
> > > > > > > > > > > > > > > > > > 3. The user can put ignite zip file on
> his/her
> > > > >
> > > > > http
> > > > > > > > > server and
> > > > > > > > > > > >
> > > > > > > > > > > > provide
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > URL as a parameter to the driver, if
> options 1
> > > > >
> > > > > and
> > > > > > 2
> > > > > > > > > don't work.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > As you see, there are 3 options. And I
> just fix
> > > > >
> > > > > the
> > > > > > > 1st
> > > > > > > > > one with
> > > > > > > > > > > > > > > > > >
> > > > >
> > > > > https://issues.apache.org/jira/browse/IGNITE-9388
> > > > > > > and
> > > > > > > > > don't
> > > > > > > > > > >
> > > > > > > > > > > change
> > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > original logic (which I find reasonable)
> > > > >
> > > > > documented
> > > > > > > on
> > > > > > > > > our site
> > > > > > > > > > >
> > > > > > > > > > > -- I
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > don't
> > > > > > > > > > > > > > > > > > see how it blocks anything.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Roman Shtykh
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > On Monday, September 10, 2018, 6:16:15
> p.m.
> > > > >
> > > > > GMT+9,
> > > > > > > Ilya
> > > > > > > > > > >
> > > > > > > > > > > Kasnacheev <
> > > > > > > > > > > > > > > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Hello!
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > There's still two issues with the
> submission.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > The first one is that we're downloading
> > > >
> > > > "latest"
> > > > > > > > version
> > > > > > > > > from
> > > > > > > > > > > >
> > > > > > > > > > > > preferred
> > > > > > > > > > > > > > > > > > mirror but a specified version, such as
> "2.6",
> > > > > >
> > > > > > we're
> > > > > > > > > also going to
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > download
> > > > > > > > > > > > > > > > > > from "slow" archive.apache.org/dist.
> > > > > > > > > > > > > > > > > > That's a great limitation for this
> change,
> > > >
> > > > since
> > > > > > most
> > > > > > > > > real
> > > > > > > > > > > >
> > > > > > > > > > > > deployments of
> > > > > > > > > > > > > > > > > > Apache Ignite will have their Ignite
> version
> > > > >
> > > > > pegged
> > > > > > > to
> > > > > > > > a
> > > > > > > > > specific
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > release.
> > > > > > > > > > > > > > > > > > But in this case there's no win in
> download
> > > > >
> > > > > speed.
> > > > > > > > > > > > > > > > > > *In my opinion it is a blocker.*
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > The second one is that we can't download
> > > >
> > > > anything
> > > > > > > when
> > > > > > > > > we failed
> > > > > > > > > > >
> > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > resolve "latest". My idea is that we
> should try
> > > > >
> > > > > and
> > > > > > > > > download last
> > > > > > > > > > > >
> > > > > > > > > > > > known
> > > > > > > > > > > > > > > > > > version in this case, which can be
> pushed to
> > > > >
> > > > > source
> > > > > > > > from
> > > > > > > > > pom.xml,
> > > > > > > > > > > >
> > > > > > > > > > > > as we
> > > > > > > > > > > > > > > > > > already do with URLs. So if you could not
> > > >
> > > > resolve
> > > > > > > > > "latest" you
> > > > > > > > > > >
> > > > > > > > > > > will
> > > > > > > > > > > > > > > > > > download 2.7.0.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Buuut, maybe it's not necessary, maybe we
> > > >
> > > > should
> > > > > > just
> > > > > > > > > *discourage
> > > > > > > > > > > > > > > > > > "latest"*, which is in my opinion almost
> > > >
> > > > always a
> > > > > > bad
> > > > > > > > > idea.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > WDYT?
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Regards,
> > > > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > вс, 9 сент. 2018 г. в 5:47, Roman Shtykh
> <
> > > > > > > > >
> > > > > > > > > rshtykh@yahoo.com>:
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Hi Ilya,
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Sorry, missed that.
> > > > > > > > > > > > > > > > > > Added now.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > > > Roman Shtykh
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > On Thursday, September 6, 2018, 6:16:58
> p.m.
> > > > >
> > > > > GMT+9,
> > > > > > > > Ilya
> > > > > > > > > > >
> > > > > > > > > > > Kasnacheev
> > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Hello!
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > The last of my requests still standing
> is that
> > > >
> > > > we
> > > > > > > > should
> > > > > > > > > fall-back
> > > > > > > > > > > >
> > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > > single URL download in case of error with
> > > > >
> > > > > 'latest'
> > > > > > > > > version.
> > > > > > > > > > > >
> > > > > > > > > > > > Everything
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > else
> > > > > > > > > > > > > > > > > > looks good to me.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Can we do that? I'm really worried that
> Apache
> > > > >
> > > > > API
> > > > > > > will
> > > > > > > > > go sour.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Regards,
> > > > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > чт, 6 сент. 2018 г. в 8:56, Roman Shtykh
> <
> > > > > > > > >
> > > > > > > > > rshtykh@yahoo.com>:
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Hi Ilya,
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Thanks again.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > 1) Done.
> > > > > > > > > > > > > > > > > > 2) Used catch() for latest version.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Please see my comments on github.
> > > > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > > > Roman Shtykh
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > On Wednesday, September 5, 2018,
> 11:30:10 p.m.
> > > > > >
> > > > > > GMT+9,
> > > > > > > > > Ilya
> > > > > > > > > > > >
> > > > > > > > > > > > Kasnacheev <
> > > > > > > > > > > > > > > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Hello!
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > I've left a new wave of replies.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Basically, 1) let's keep
> DOWNLOAD_URL_PATTERN
> > > > > >
> > > > > > string
> > > > > > > > > value inlined
> > > > > > > > > > > >
> > > > > > > > > > > > so
> > > > > > > > > > > > > > > > > > that it will work even if build process
> is
> > > >
> > > > broken
> > > > > > > > (would
> > > > > > > > > be useful
> > > > > > > > > > > >
> > > > > > > > > > > > for
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > e.g.
> > > > > > > > > > > > > > > > > > developing out of IDE)
> > > > > > > > > > > > > > > > > > And also I urge you to catch() around new
> > > >
> > > > fragile
> > > > > > > > Apache
> > > > > > > > > JSON API
> > > > > > > > > > > > > > > > > > resolving, and download the 'current'
> version
> > > > > > >
> > > > > > > instead,
> > > > > > > > > as defined
> > > > > > > > > > >
> > > > > > > > > > > by
> > > > > > > > > > > > > > > > > > ignite-mesos version.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > This is because this module is not under
> > > > > >
> > > > > > continuouos
> > > > > > > > > scrutiny so
> > > > > > > > > > > >
> > > > > > > > > > > > extra
> > > > > > > > > > > > > > > > > > care should be applied.
> > > > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > вт, 4 сент. 2018 г. в 13:42, Roman
> Shtykh <
> > > > > > > > >
> > > > > > > > > rshtykh@yahoo.com>:
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Thanks, Ilya!
> > > > > > > > > > > > > > > > > > I will check your comments, and discuss
> it at
> > > > >
> > > > > JIRA.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > > > Roman Shtykh
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > On Tuesday, September 4, 2018, 7:17:53
> p.m.
> > > > >
> > > > > GMT+9,
> > > > > > > Ilya
> > > > > > > > > > >
> > > > > > > > > > > Kasnacheev <
> > > > > > > > > > > > > > > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Hello!
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > IGNITE-9408 <
> > > > > > > > >
> > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-9408>;
> > > > > > > > > > > >
> > > > > > > > > > > > looks
> > > > > > > > > > > > > > > > > > good to me and may be merged right away.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > IGNITE-9388 <
> > > > > > > > >
> > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-9388>;
> > > > > > > > > > > >
> > > > > > > > > > > > needs
> > > > > > > > > > > > > > > > > > more work in my opinion, I have
> commented the
> > > > >
> > > > > PR. I
> > > > > > > > also
> > > > > > > > > advice
> > > > > > > > > > > >
> > > > > > > > > > > > having
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > test
> > > > > > > > > > > > > > > > > > for this functionality.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Regards,
> > > > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > вт, 4 сент. 2018 г. в 6:52, Roman Shtykh
> > > > > > > > > > >
> > > > > > > > > > > <rshtykh@yahoo.com.invalid
> > > > > > > > > > > > > :
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > 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
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > > daradurvs@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 <
> > > > > > > > > > > >
> > > > > > > > > > > > nizhikov@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.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
Re: Apache Ignite 2.7 release
Posted by Nikolay Izhikov <ni...@apache.org>.
Hello, Igniters.
I ping assigners in all tickets hase been planned for 2.7 and work is started.
I plan to move all tickets in 'Open' state to 2.8 on Moday, 24 September.
Please, respond, if you have any objections.
В Ср, 19/09/2018 в 16:02 +0300, Andrey Gura пишет:
> Nikolay,
>
> since we talk about scope freeze all you need now just create
> ignite-2.7 branch. We still can have tickets targeted to 2.7 release
> in progress. So you shouldn't move tickets to 2.8 because they can be
> targeted to 2.7 intentionally and will be merged to master and
> ignite-2.7 branches.
> On Wed, Sep 19, 2018 at 12:18 PM Nikolay Izhikov <ni...@apache.org> wrote:
> >
> > Hello, Igniters.
> >
> > Vova, thank you for pointing this out.
> >
> > I ask all community members to iterate over assigned tickets.
> > Please, move your tickets to 2.8 release if work is still in progress.
> > At the end of the day, I will do it by myself and tomorrow we should have
> > release scope prepared.
> >
> >
> > ср, 19 сент. 2018 г. в 12:08, Vladimir Ozerov <vo...@gridgain.com>:
> >
> > > My point was not about code freeze, but about scope freeze, what means that
> > > starting from this point AI 2.7 release should not receive any commits
> > > which doesn't relate to it.
> > >
> > > On Wed, Sep 19, 2018 at 11:55 AM Anton Vinogradov <av...@apache.org> wrote:
> > >
> > > > Vova,
> > > >
> > > > AFAIK, codefreeze was not announced yet.
> > > > Correct me in case I missed this.
> > > >
> > > > Now, Nikolay finishing checks that he's able to perform release
> > >
> > > (everything
> > > > installed and properly configured).
> > > > So, I recommend him to mention this check here to solve any
> > > > misunderstanding in case some branches or tags related to 2.7 will be
> > >
> > > found
> > > > before we announced codefreeze.
> > > >
> > > > ср, 19 сент. 2018 г. в 11:45, Vladimir Ozerov <vo...@gridgain.com>:
> > > >
> > > > > Anton,
> > > > >
> > > > > What do you mean under "preparation to real 2.7". It is already real,
> > >
> > > we
> > > > > reached formal code freeze phase we agreed on. At this point we need to
> > > > > exclude non-2.7 commits, otherwise we will not be able to come to
> > >
> > > stable
> > > > > branch in two weeks.
> > > > > For this reason creating a branch for 2.7 at the moment is perfectly
> > > >
> > > > valid
> > > > > thing. This is how we made releases previously.
> > > > >
> > > > > On Tue, Sep 18, 2018 at 7:59 PM Dmitriy Pavlov <dp...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Hi Paul.
> > > > > >
> > > > > > There are 2 PRs linked to that ticket. Who is reviewing your changes?
> > > > > >
> > > > > > Branch for 2.7 is still master, so if your changes are reviewed and
> > > > > > accepted soon it will be in 2.7.
> > > > > >
> > > > > > Sincerely,
> > > > > > Dmitriy Pavlov
> > > > > >
> > > > > > вт, 18 сент. 2018 г. в 16:22, Paul Anderson <de...@gmail.com>:
> > > > > >
> > > > > > > Hi, may I ask for IGNITE-9298 to be included in 2.7 pls
> > > > > > >
> > > > > > > On Tue, Sep 18, 2018 at 1:03 PM Nikolay Izhikov <
> > >
> > > nizhikov@apache.org
> > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Hello, folks.
> > > > > > > >
> > > > > > > > Thanks for the comments.
> > > > > > > >
> > > > > > > > I will follow them.
> > > > > > > >
> > > > > > > > В Вт, 18/09/2018 в 13:31 +0300, Anton Vinogradov пишет:
> > > > > > > > > Nikolay,
> > > > > > > > >
> > > > > > > > > 1) *Do not* create ignite-2.7 branch until we're not started
> > > > > > >
> > > > > > > preparation
> > > > > > > > to
> > > > > > > > > real 2.7.
> > > > > > > > > Use some temporary branch for this check instead, eg.
> > > > > > > > > ignite-2.7-release-test
> > > > > > > > >
> > > > > > > > > 2) Please make sure you'll not cause real release actions
> > >
> > > (maven
> > > > > > > release
> > > > > > > > > and so on).
> > > > > > > > > Perform only vote_* steps.
> > > > > > > > >
> > > > > > > > > 3) Make sure you'll remove all tags, branches, and other RC
> > > > >
> > > > > artifacts
> > > > > > > > after
> > > > > > > > > check.
> > > > > > > > >
> > > > > > > > > 4) Mark this release as RC0 to make sure it will be clear to
> > > > > >
> > > > > > everybody
> > > > > > > > that
> > > > > > > > > it's a check.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > вт, 18 сент. 2018 г. в 13:24, Dmitriy Setrakyan <
> > > > > >
> > > > > > dsetrakyan@apache.org
> > > > > > > > :
> > > > > > > > >
> > > > > > > > > > If it is an Ignite release, then it has to pass through the
> > > >
> > > > vote.
> > > > > > If
> > > > > > > > not,
> > > > > > > > > > then you can do the test without publishing or uploading the
> > > > > >
> > > > > > release.
> > > > > > > > > >
> > > > > > > > > > D.
> > > > > > > > > >
> > > > > > > > > > On Tue, Sep 18, 2018 at 1:18 PM Petr Ivanov <
> > > >
> > > > mr.weider@gmail.com
> > > > > >
> > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Ok.
> > > > > > > > > > >
> > > > > > > > > > > In case of TC questions — ask me.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > > On 18 Sep 2018, at 13:16, Nikolay Izhikov <
> > > > >
> > > > > nizhikov@apache.org
> > > > > > >
> > > > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > Hello, Petr.
> > > > > > > > > > > >
> > > > > > > > > > > > I want to make ignite-2.7 branch today.
> > > > > > > > > > > > And execute release procedure based on this branch.
> > > > > > > > > > > >
> > > > > > > > > > > > However, ignite-2.7 branch will be copy of master until
> > > >
> > > > code
> > > > > > > freeze
> > > > > > > > > >
> > > > > > > > > > date.
> > > > > > > > > > > >
> > > > > > > > > > > > В Вт, 18/09/2018 в 13:13 +0300, Petr Ivanov пишет:
> > > > > > > > > > > > > Will it be just a test or there is already ignite-2.7
> > > > >
> > > > > branch?
> > > > > > > > > > > > >
> > > > > > > > > > > > > Fabric removal related TC modifications are not ready
> > > >
> > > > yet,
> > > > > > and
> > > > > > > > code is
> > > > > > > > > > >
> > > > > > > > > > > not in master.
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > > On 18 Sep 2018, at 13:07, Nikolay Izhikov <
> > > > > > >
> > > > > > > nizhikov@apache.org
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > wrote:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Hello, Igniters.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > I want to start and release procedures and make an
> > >
> > > RC1
> > > > > > build.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > It has a 2 intention:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > 1. I want to walk through all release steps to make
> > > >
> > > > sure
> > > > > > they
> > > > > > > > all
> > > > > > > > > > >
> > > > > > > > > > > works for me.
> > > > > > > > > > > > > > So I will be fully ready on release date.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > 2. We have updated some dependencies in 2.7 and we
> > >
> > > need
> > > > > to
> > > > > > > > make sure
> > > > > > > > > > >
> > > > > > > > > > > binary build is still workable.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Any objections?
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > В Пт, 14/09/2018 в 18:52 +0300, Alexey Goncharuk
> > >
> > > пишет:
> > > > > > > > > > > > > > > We already have all the mechanics in place to work
> > > >
> > > > with
> > > > > > > > properties -
> > > > > > > > > > >
> > > > > > > > > > > we use
> > > > > > > > > > > > > > > ignite.build and ignite.revision from
> > > >
> > > > ignite.properties
> > > > > > > > which are
> > > > > > > > > > >
> > > > > > > > > > > adjusted
> > > > > > > > > > > > > > > during the build in the binary package.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Should I create the ticket if there are no
> > > >
> > > > objections?
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > пт, 14 сент. 2018 г. в 13:22, Ilya Kasnacheev <
> > > > > > > > > > >
> > > > > > > > > > > ilya.kasnacheev@gmail.com>:
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Hello!
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > So now there's an issue that this script makes
> > > >
> > > > source
> > > > > > > > change after
> > > > > > > > > > >
> > > > > > > > > > > every
> > > > > > > > > > > > > > > > build, show up in git status.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > What we could do to it:
> > > > > > > > > > > > > > > > - Commit the changes after the build, once. In
> > > >
> > > > hopes
> > > > > > that
> > > > > > > > it won't
> > > > > > > > > > >
> > > > > > > > > > > change
> > > > > > > > > > > > > > > > very often. With benefit that we could do that
> > > >
> > > > right
> > > > > > now,
> > > > > > > > before
> > > > > > > > > >
> > > > > > > > > > the
> > > > > > > > > > > code
> > > > > > > > > > > > > > > > freeze.
> > > > > > > > > > > > > > > > - Move these values to a properties file from
> > >
> > > both
> > > > > > > pom.xml
> > > > > > > > and
> > > > > > > > > > > > > > > > IgniteProvider.java. Any problems with this
> > > >
> > > > approach?
> > > > > > > > We'll just
> > > > > > > > > > >
> > > > > > > > > > > read them
> > > > > > > > > > > > > > > > from classpath properties file.
> > > > > > > > > > > > > > > > - Update the links in the file once and remove
> > >
> > > them
> > > > > > from
> > > > > > > > build
> > > > > > > > > > >
> > > > > > > > > > > process. Why
> > > > > > > > > > > > > > > > were they added to build process in the first
> > > >
> > > > place -
> > > > > > to
> > > > > > > > make them
> > > > > > > > > > > > > > > > configurable during build?
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Regards,
> > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > вт, 11 сент. 2018 г. в 5:53, Roman Shtykh <
> > > > > > > >
> > > > > > > > rshtykh@yahoo.com>:
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Ilya,
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > The "latest" version is the default, and
> > >
> > > resolved
> > > > > by
> > > > > > > > > > > > > > > > > https://ignite.apache.org/latest which is used
> > > >
> > > > by
> > > > > > our
> > > > > > > > web site
> > > > > > > > > > >
> > > > > > > > > > > when a
> > > > > > > > > > > > > > > > > user download the latest Ignite version. And I
> > > > >
> > > > > think
> > > > > > > > this is the
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > authority
> > > > > > > > > > > > > > > > > to judge of the latest official release
> > >
> > > (pom.xml
> > > > > you
> > > > > > > > suggest can
> > > > > > > > > > >
> > > > > > > > > > > have
> > > > > > > > > > > > > > > > > SNAPSHOTs etc.).
> > > > > > > > > > > > > > > > > Also, as I explained during our review
> > >
> > > sessions,
> > > > > > > > > >
> > > > > > > > > > ignite-mesos-2.6.0
> > > > > > > > > > > is a
> > > > > > > > > > > > > > > > > driver and doesn't mean you need to have Ignite
> > > > > >
> > > > > > 2.6.0.
> > > > > > > > User can
> > > > > > > > > >
> > > > > > > > > > run
> > > > > > > > > > > any
> > > > > > > > > > > > > > > > > version of Ignite he/she specifies. By default,
> > > > >
> > > > > it's
> > > > > > > > "latest" but
> > > > > > > > > >
> > > > > > > > > > a
> > > > > > > > > > > user
> > > > > > > > > > > > > > > > > can specify any version needed, even from a
> > > > > >
> > > > > > non-archive
> > > > > > > > URL.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > In short, what we have now
> > > > > > > > > > > > > > > > > 1. mesos driver (ignite-mesos-x.x.x) will use
> > > > > >
> > > > > > "latest"
> > > > > > > > version by
> > > > > > > > > > >
> > > > > > > > > > > default
> > > > > > > > > > > > > > > > > -> it will try to resolve the latest officially
> > > > > > >
> > > > > > > releases
> > > > > > > > version
> > > > > > > > > >
> > > > > > > > > > of
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Apache
> > > > > > > > > > > > > > > > > Ignite, find the closest mirror and download
> > > >
> > > > Ignite
> > > > > > in
> > > > > > > a
> > > > > > > > minute.
> > > > > > > > > >
> > > > > > > > > > If
> > > > > > > > > > > the
> > > > > > > > > > > > > > > > > version resolution fails, we fall back to the
> > > >
> > > > slow
> > > > > > > > apache archive
> > > > > > > > > > >
> > > > > > > > > > > (as you
> > > > > > > > > > > > > > > > > suggest; in my opinion we better fail-fast
> > > >
> > > > instead
> > > > > of
> > > > > > > > waiting for
> > > > > > > > > > >
> > > > > > > > > > > hours
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > > download, so the user can choose another
> > >
> > > download
> > > > > > > option
> > > > > > > > (3))
> > > > > > > > > > > > > > > > > 2. If the user specifies the version
> > >
> > > explicitly,
> > > > it
> > > > > > > goes
> > > > > > > > to the
> > > > > > > > > >
> > > > > > > > > > slow
> > > > > > > > > > > > > > > > > apache archive.
> > > > > > > > > > > > > > > > > 3. The user can put ignite zip file on his/her
> > > >
> > > > http
> > > > > > > > server and
> > > > > > > > > > >
> > > > > > > > > > > provide
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > URL as a parameter to the driver, if options 1
> > > >
> > > > and
> > > > > 2
> > > > > > > > don't work.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > As you see, there are 3 options. And I just fix
> > > >
> > > > the
> > > > > > 1st
> > > > > > > > one with
> > > > > > > > > > > > > > > > >
> > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-9388
> > > > > > and
> > > > > > > > don't
> > > > > > > > > >
> > > > > > > > > > change
> > > > > > > > > > > the
> > > > > > > > > > > > > > > > > original logic (which I find reasonable)
> > > >
> > > > documented
> > > > > > on
> > > > > > > > our site
> > > > > > > > > >
> > > > > > > > > > -- I
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > don't
> > > > > > > > > > > > > > > > > see how it blocks anything.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Roman Shtykh
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > On Monday, September 10, 2018, 6:16:15 p.m.
> > > >
> > > > GMT+9,
> > > > > > Ilya
> > > > > > > > > >
> > > > > > > > > > Kasnacheev <
> > > > > > > > > > > > > > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Hello!
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > There's still two issues with the submission.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > The first one is that we're downloading
> > >
> > > "latest"
> > > > > > > version
> > > > > > > > from
> > > > > > > > > > >
> > > > > > > > > > > preferred
> > > > > > > > > > > > > > > > > mirror but a specified version, such as "2.6",
> > > > >
> > > > > we're
> > > > > > > > also going to
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > download
> > > > > > > > > > > > > > > > > from "slow" archive.apache.org/dist.
> > > > > > > > > > > > > > > > > That's a great limitation for this change,
> > >
> > > since
> > > > > most
> > > > > > > > real
> > > > > > > > > > >
> > > > > > > > > > > deployments of
> > > > > > > > > > > > > > > > > Apache Ignite will have their Ignite version
> > > >
> > > > pegged
> > > > > > to
> > > > > > > a
> > > > > > > > specific
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > release.
> > > > > > > > > > > > > > > > > But in this case there's no win in download
> > > >
> > > > speed.
> > > > > > > > > > > > > > > > > *In my opinion it is a blocker.*
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > The second one is that we can't download
> > >
> > > anything
> > > > > > when
> > > > > > > > we failed
> > > > > > > > > >
> > > > > > > > > > to
> > > > > > > > > > > > > > > > > resolve "latest". My idea is that we should try
> > > >
> > > > and
> > > > > > > > download last
> > > > > > > > > > >
> > > > > > > > > > > known
> > > > > > > > > > > > > > > > > version in this case, which can be pushed to
> > > >
> > > > source
> > > > > > > from
> > > > > > > > pom.xml,
> > > > > > > > > > >
> > > > > > > > > > > as we
> > > > > > > > > > > > > > > > > already do with URLs. So if you could not
> > >
> > > resolve
> > > > > > > > "latest" you
> > > > > > > > > >
> > > > > > > > > > will
> > > > > > > > > > > > > > > > > download 2.7.0.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Buuut, maybe it's not necessary, maybe we
> > >
> > > should
> > > > > just
> > > > > > > > *discourage
> > > > > > > > > > > > > > > > > "latest"*, which is in my opinion almost
> > >
> > > always a
> > > > > bad
> > > > > > > > idea.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > WDYT?
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Regards,
> > > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > вс, 9 сент. 2018 г. в 5:47, Roman Shtykh <
> > > > > > > >
> > > > > > > > rshtykh@yahoo.com>:
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Hi Ilya,
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Sorry, missed that.
> > > > > > > > > > > > > > > > > Added now.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > > Roman Shtykh
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > On Thursday, September 6, 2018, 6:16:58 p.m.
> > > >
> > > > GMT+9,
> > > > > > > Ilya
> > > > > > > > > >
> > > > > > > > > > Kasnacheev
> > > > > > > > > > > <
> > > > > > > > > > > > > > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Hello!
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > The last of my requests still standing is that
> > >
> > > we
> > > > > > > should
> > > > > > > > fall-back
> > > > > > > > > > >
> > > > > > > > > > > to
> > > > > > > > > > > > > > > > > single URL download in case of error with
> > > >
> > > > 'latest'
> > > > > > > > version.
> > > > > > > > > > >
> > > > > > > > > > > Everything
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > else
> > > > > > > > > > > > > > > > > looks good to me.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Can we do that? I'm really worried that Apache
> > > >
> > > > API
> > > > > > will
> > > > > > > > go sour.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Regards,
> > > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > чт, 6 сент. 2018 г. в 8:56, Roman Shtykh <
> > > > > > > >
> > > > > > > > rshtykh@yahoo.com>:
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Hi Ilya,
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Thanks again.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > 1) Done.
> > > > > > > > > > > > > > > > > 2) Used catch() for latest version.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Please see my comments on github.
> > > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > > Roman Shtykh
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > On Wednesday, September 5, 2018, 11:30:10 p.m.
> > > > >
> > > > > GMT+9,
> > > > > > > > Ilya
> > > > > > > > > > >
> > > > > > > > > > > Kasnacheev <
> > > > > > > > > > > > > > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Hello!
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > I've left a new wave of replies.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Basically, 1) let's keep DOWNLOAD_URL_PATTERN
> > > > >
> > > > > string
> > > > > > > > value inlined
> > > > > > > > > > >
> > > > > > > > > > > so
> > > > > > > > > > > > > > > > > that it will work even if build process is
> > >
> > > broken
> > > > > > > (would
> > > > > > > > be useful
> > > > > > > > > > >
> > > > > > > > > > > for
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > e.g.
> > > > > > > > > > > > > > > > > developing out of IDE)
> > > > > > > > > > > > > > > > > And also I urge you to catch() around new
> > >
> > > fragile
> > > > > > > Apache
> > > > > > > > JSON API
> > > > > > > > > > > > > > > > > resolving, and download the 'current' version
> > > > > >
> > > > > > instead,
> > > > > > > > as defined
> > > > > > > > > >
> > > > > > > > > > by
> > > > > > > > > > > > > > > > > ignite-mesos version.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > This is because this module is not under
> > > > >
> > > > > continuouos
> > > > > > > > scrutiny so
> > > > > > > > > > >
> > > > > > > > > > > extra
> > > > > > > > > > > > > > > > > care should be applied.
> > > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > вт, 4 сент. 2018 г. в 13:42, Roman Shtykh <
> > > > > > > >
> > > > > > > > rshtykh@yahoo.com>:
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Thanks, Ilya!
> > > > > > > > > > > > > > > > > I will check your comments, and discuss it at
> > > >
> > > > JIRA.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > > Roman Shtykh
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > On Tuesday, September 4, 2018, 7:17:53 p.m.
> > > >
> > > > GMT+9,
> > > > > > Ilya
> > > > > > > > > >
> > > > > > > > > > Kasnacheev <
> > > > > > > > > > > > > > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Hello!
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > IGNITE-9408 <
> > > > > > > >
> > > > > > > > https://issues.apache.org/jira/browse/IGNITE-9408>;
> > > > > > > > > > >
> > > > > > > > > > > looks
> > > > > > > > > > > > > > > > > good to me and may be merged right away.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > IGNITE-9388 <
> > > > > > > >
> > > > > > > > https://issues.apache.org/jira/browse/IGNITE-9388>;
> > > > > > > > > > >
> > > > > > > > > > > needs
> > > > > > > > > > > > > > > > > more work in my opinion, I have commented the
> > > >
> > > > PR. I
> > > > > > > also
> > > > > > > > advice
> > > > > > > > > > >
> > > > > > > > > > > having
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > test
> > > > > > > > > > > > > > > > > for this functionality.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Regards,
> > > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > вт, 4 сент. 2018 г. в 6:52, Roman Shtykh
> > > > > > > > > >
> > > > > > > > > > <rshtykh@yahoo.com.invalid
> > > > > > > > > > > > :
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > 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
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > > daradurvs@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 <
> > > > > > > > > > >
> > > > > > > > > > > nizhikov@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.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
Re: Apache Ignite 2.7 release
Posted by Andrey Gura <ag...@apache.org>.
Nikolay,
since we talk about scope freeze all you need now just create
ignite-2.7 branch. We still can have tickets targeted to 2.7 release
in progress. So you shouldn't move tickets to 2.8 because they can be
targeted to 2.7 intentionally and will be merged to master and
ignite-2.7 branches.
On Wed, Sep 19, 2018 at 12:18 PM Nikolay Izhikov <ni...@apache.org> wrote:
>
> Hello, Igniters.
>
> Vova, thank you for pointing this out.
>
> I ask all community members to iterate over assigned tickets.
> Please, move your tickets to 2.8 release if work is still in progress.
> At the end of the day, I will do it by myself and tomorrow we should have
> release scope prepared.
>
>
> ср, 19 сент. 2018 г. в 12:08, Vladimir Ozerov <vo...@gridgain.com>:
>
> > My point was not about code freeze, but about scope freeze, what means that
> > starting from this point AI 2.7 release should not receive any commits
> > which doesn't relate to it.
> >
> > On Wed, Sep 19, 2018 at 11:55 AM Anton Vinogradov <av...@apache.org> wrote:
> >
> > > Vova,
> > >
> > > AFAIK, codefreeze was not announced yet.
> > > Correct me in case I missed this.
> > >
> > > Now, Nikolay finishing checks that he's able to perform release
> > (everything
> > > installed and properly configured).
> > > So, I recommend him to mention this check here to solve any
> > > misunderstanding in case some branches or tags related to 2.7 will be
> > found
> > > before we announced codefreeze.
> > >
> > > ср, 19 сент. 2018 г. в 11:45, Vladimir Ozerov <vo...@gridgain.com>:
> > >
> > > > Anton,
> > > >
> > > > What do you mean under "preparation to real 2.7". It is already real,
> > we
> > > > reached formal code freeze phase we agreed on. At this point we need to
> > > > exclude non-2.7 commits, otherwise we will not be able to come to
> > stable
> > > > branch in two weeks.
> > > > For this reason creating a branch for 2.7 at the moment is perfectly
> > > valid
> > > > thing. This is how we made releases previously.
> > > >
> > > > On Tue, Sep 18, 2018 at 7:59 PM Dmitriy Pavlov <dp...@gmail.com>
> > > > wrote:
> > > >
> > > > > Hi Paul.
> > > > >
> > > > > There are 2 PRs linked to that ticket. Who is reviewing your changes?
> > > > >
> > > > > Branch for 2.7 is still master, so if your changes are reviewed and
> > > > > accepted soon it will be in 2.7.
> > > > >
> > > > > Sincerely,
> > > > > Dmitriy Pavlov
> > > > >
> > > > > вт, 18 сент. 2018 г. в 16:22, Paul Anderson <de...@gmail.com>:
> > > > >
> > > > > > Hi, may I ask for IGNITE-9298 to be included in 2.7 pls
> > > > > >
> > > > > > On Tue, Sep 18, 2018 at 1:03 PM Nikolay Izhikov <
> > nizhikov@apache.org
> > > >
> > > > > > wrote:
> > > > > >
> > > > > > > Hello, folks.
> > > > > > >
> > > > > > > Thanks for the comments.
> > > > > > >
> > > > > > > I will follow them.
> > > > > > >
> > > > > > > В Вт, 18/09/2018 в 13:31 +0300, Anton Vinogradov пишет:
> > > > > > > > Nikolay,
> > > > > > > >
> > > > > > > > 1) *Do not* create ignite-2.7 branch until we're not started
> > > > > > preparation
> > > > > > > to
> > > > > > > > real 2.7.
> > > > > > > > Use some temporary branch for this check instead, eg.
> > > > > > > > ignite-2.7-release-test
> > > > > > > >
> > > > > > > > 2) Please make sure you'll not cause real release actions
> > (maven
> > > > > > release
> > > > > > > > and so on).
> > > > > > > > Perform only vote_* steps.
> > > > > > > >
> > > > > > > > 3) Make sure you'll remove all tags, branches, and other RC
> > > > artifacts
> > > > > > > after
> > > > > > > > check.
> > > > > > > >
> > > > > > > > 4) Mark this release as RC0 to make sure it will be clear to
> > > > > everybody
> > > > > > > that
> > > > > > > > it's a check.
> > > > > > > >
> > > > > > > >
> > > > > > > > вт, 18 сент. 2018 г. в 13:24, Dmitriy Setrakyan <
> > > > > dsetrakyan@apache.org
> > > > > > >:
> > > > > > > >
> > > > > > > > > If it is an Ignite release, then it has to pass through the
> > > vote.
> > > > > If
> > > > > > > not,
> > > > > > > > > then you can do the test without publishing or uploading the
> > > > > release.
> > > > > > > > >
> > > > > > > > > D.
> > > > > > > > >
> > > > > > > > > On Tue, Sep 18, 2018 at 1:18 PM Petr Ivanov <
> > > mr.weider@gmail.com
> > > > >
> > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Ok.
> > > > > > > > > >
> > > > > > > > > > In case of TC questions — ask me.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > > On 18 Sep 2018, at 13:16, Nikolay Izhikov <
> > > > nizhikov@apache.org
> > > > > >
> > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > Hello, Petr.
> > > > > > > > > > >
> > > > > > > > > > > I want to make ignite-2.7 branch today.
> > > > > > > > > > > And execute release procedure based on this branch.
> > > > > > > > > > >
> > > > > > > > > > > However, ignite-2.7 branch will be copy of master until
> > > code
> > > > > > freeze
> > > > > > > > >
> > > > > > > > > date.
> > > > > > > > > > >
> > > > > > > > > > > В Вт, 18/09/2018 в 13:13 +0300, Petr Ivanov пишет:
> > > > > > > > > > > > Will it be just a test or there is already ignite-2.7
> > > > branch?
> > > > > > > > > > > >
> > > > > > > > > > > > Fabric removal related TC modifications are not ready
> > > yet,
> > > > > and
> > > > > > > code is
> > > > > > > > > >
> > > > > > > > > > not in master.
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > > On 18 Sep 2018, at 13:07, Nikolay Izhikov <
> > > > > > nizhikov@apache.org
> > > > > > > >
> > > > > > > > >
> > > > > > > > > wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > > Hello, Igniters.
> > > > > > > > > > > > >
> > > > > > > > > > > > > I want to start and release procedures and make an
> > RC1
> > > > > build.
> > > > > > > > > > > > >
> > > > > > > > > > > > > It has a 2 intention:
> > > > > > > > > > > > >
> > > > > > > > > > > > > 1. I want to walk through all release steps to make
> > > sure
> > > > > they
> > > > > > > all
> > > > > > > > > >
> > > > > > > > > > works for me.
> > > > > > > > > > > > > So I will be fully ready on release date.
> > > > > > > > > > > > >
> > > > > > > > > > > > > 2. We have updated some dependencies in 2.7 and we
> > need
> > > > to
> > > > > > > make sure
> > > > > > > > > >
> > > > > > > > > > binary build is still workable.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Any objections?
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > В Пт, 14/09/2018 в 18:52 +0300, Alexey Goncharuk
> > пишет:
> > > > > > > > > > > > > > We already have all the mechanics in place to work
> > > with
> > > > > > > properties -
> > > > > > > > > >
> > > > > > > > > > we use
> > > > > > > > > > > > > > ignite.build and ignite.revision from
> > > ignite.properties
> > > > > > > which are
> > > > > > > > > >
> > > > > > > > > > adjusted
> > > > > > > > > > > > > > during the build in the binary package.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Should I create the ticket if there are no
> > > objections?
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > пт, 14 сент. 2018 г. в 13:22, Ilya Kasnacheev <
> > > > > > > > > >
> > > > > > > > > > ilya.kasnacheev@gmail.com>:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Hello!
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > So now there's an issue that this script makes
> > > source
> > > > > > > change after
> > > > > > > > > >
> > > > > > > > > > every
> > > > > > > > > > > > > > > build, show up in git status.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > What we could do to it:
> > > > > > > > > > > > > > > - Commit the changes after the build, once. In
> > > hopes
> > > > > that
> > > > > > > it won't
> > > > > > > > > >
> > > > > > > > > > change
> > > > > > > > > > > > > > > very often. With benefit that we could do that
> > > right
> > > > > now,
> > > > > > > before
> > > > > > > > >
> > > > > > > > > the
> > > > > > > > > > code
> > > > > > > > > > > > > > > freeze.
> > > > > > > > > > > > > > > - Move these values to a properties file from
> > both
> > > > > > pom.xml
> > > > > > > and
> > > > > > > > > > > > > > > IgniteProvider.java. Any problems with this
> > > approach?
> > > > > > > We'll just
> > > > > > > > > >
> > > > > > > > > > read them
> > > > > > > > > > > > > > > from classpath properties file.
> > > > > > > > > > > > > > > - Update the links in the file once and remove
> > them
> > > > > from
> > > > > > > build
> > > > > > > > > >
> > > > > > > > > > process. Why
> > > > > > > > > > > > > > > were they added to build process in the first
> > > place -
> > > > > to
> > > > > > > make them
> > > > > > > > > > > > > > > configurable during build?
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Regards,
> > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > вт, 11 сент. 2018 г. в 5:53, Roman Shtykh <
> > > > > > > rshtykh@yahoo.com>:
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Ilya,
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > The "latest" version is the default, and
> > resolved
> > > > by
> > > > > > > > > > > > > > > > https://ignite.apache.org/latest which is used
> > > by
> > > > > our
> > > > > > > web site
> > > > > > > > > >
> > > > > > > > > > when a
> > > > > > > > > > > > > > > > user download the latest Ignite version. And I
> > > > think
> > > > > > > this is the
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > authority
> > > > > > > > > > > > > > > > to judge of the latest official release
> > (pom.xml
> > > > you
> > > > > > > suggest can
> > > > > > > > > >
> > > > > > > > > > have
> > > > > > > > > > > > > > > > SNAPSHOTs etc.).
> > > > > > > > > > > > > > > > Also, as I explained during our review
> > sessions,
> > > > > > > > >
> > > > > > > > > ignite-mesos-2.6.0
> > > > > > > > > > is a
> > > > > > > > > > > > > > > > driver and doesn't mean you need to have Ignite
> > > > > 2.6.0.
> > > > > > > User can
> > > > > > > > >
> > > > > > > > > run
> > > > > > > > > > any
> > > > > > > > > > > > > > > > version of Ignite he/she specifies. By default,
> > > > it's
> > > > > > > "latest" but
> > > > > > > > >
> > > > > > > > > a
> > > > > > > > > > user
> > > > > > > > > > > > > > > > can specify any version needed, even from a
> > > > > non-archive
> > > > > > > URL.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > In short, what we have now
> > > > > > > > > > > > > > > > 1. mesos driver (ignite-mesos-x.x.x) will use
> > > > > "latest"
> > > > > > > version by
> > > > > > > > > >
> > > > > > > > > > default
> > > > > > > > > > > > > > > > -> it will try to resolve the latest officially
> > > > > > releases
> > > > > > > version
> > > > > > > > >
> > > > > > > > > of
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Apache
> > > > > > > > > > > > > > > > Ignite, find the closest mirror and download
> > > Ignite
> > > > > in
> > > > > > a
> > > > > > > minute.
> > > > > > > > >
> > > > > > > > > If
> > > > > > > > > > the
> > > > > > > > > > > > > > > > version resolution fails, we fall back to the
> > > slow
> > > > > > > apache archive
> > > > > > > > > >
> > > > > > > > > > (as you
> > > > > > > > > > > > > > > > suggest; in my opinion we better fail-fast
> > > instead
> > > > of
> > > > > > > waiting for
> > > > > > > > > >
> > > > > > > > > > hours
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > > download, so the user can choose another
> > download
> > > > > > option
> > > > > > > (3))
> > > > > > > > > > > > > > > > 2. If the user specifies the version
> > explicitly,
> > > it
> > > > > > goes
> > > > > > > to the
> > > > > > > > >
> > > > > > > > > slow
> > > > > > > > > > > > > > > > apache archive.
> > > > > > > > > > > > > > > > 3. The user can put ignite zip file on his/her
> > > http
> > > > > > > server and
> > > > > > > > > >
> > > > > > > > > > provide
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > URL as a parameter to the driver, if options 1
> > > and
> > > > 2
> > > > > > > don't work.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > As you see, there are 3 options. And I just fix
> > > the
> > > > > 1st
> > > > > > > one with
> > > > > > > > > > > > > > > >
> > > https://issues.apache.org/jira/browse/IGNITE-9388
> > > > > and
> > > > > > > don't
> > > > > > > > >
> > > > > > > > > change
> > > > > > > > > > the
> > > > > > > > > > > > > > > > original logic (which I find reasonable)
> > > documented
> > > > > on
> > > > > > > our site
> > > > > > > > >
> > > > > > > > > -- I
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > don't
> > > > > > > > > > > > > > > > see how it blocks anything.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Roman Shtykh
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > On Monday, September 10, 2018, 6:16:15 p.m.
> > > GMT+9,
> > > > > Ilya
> > > > > > > > >
> > > > > > > > > Kasnacheev <
> > > > > > > > > > > > > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Hello!
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > There's still two issues with the submission.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > The first one is that we're downloading
> > "latest"
> > > > > > version
> > > > > > > from
> > > > > > > > > >
> > > > > > > > > > preferred
> > > > > > > > > > > > > > > > mirror but a specified version, such as "2.6",
> > > > we're
> > > > > > > also going to
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > download
> > > > > > > > > > > > > > > > from "slow" archive.apache.org/dist.
> > > > > > > > > > > > > > > > That's a great limitation for this change,
> > since
> > > > most
> > > > > > > real
> > > > > > > > > >
> > > > > > > > > > deployments of
> > > > > > > > > > > > > > > > Apache Ignite will have their Ignite version
> > > pegged
> > > > > to
> > > > > > a
> > > > > > > specific
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > release.
> > > > > > > > > > > > > > > > But in this case there's no win in download
> > > speed.
> > > > > > > > > > > > > > > > *In my opinion it is a blocker.*
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > The second one is that we can't download
> > anything
> > > > > when
> > > > > > > we failed
> > > > > > > > >
> > > > > > > > > to
> > > > > > > > > > > > > > > > resolve "latest". My idea is that we should try
> > > and
> > > > > > > download last
> > > > > > > > > >
> > > > > > > > > > known
> > > > > > > > > > > > > > > > version in this case, which can be pushed to
> > > source
> > > > > > from
> > > > > > > pom.xml,
> > > > > > > > > >
> > > > > > > > > > as we
> > > > > > > > > > > > > > > > already do with URLs. So if you could not
> > resolve
> > > > > > > "latest" you
> > > > > > > > >
> > > > > > > > > will
> > > > > > > > > > > > > > > > download 2.7.0.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Buuut, maybe it's not necessary, maybe we
> > should
> > > > just
> > > > > > > *discourage
> > > > > > > > > > > > > > > > "latest"*, which is in my opinion almost
> > always a
> > > > bad
> > > > > > > idea.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > WDYT?
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Regards,
> > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > вс, 9 сент. 2018 г. в 5:47, Roman Shtykh <
> > > > > > > rshtykh@yahoo.com>:
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Hi Ilya,
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Sorry, missed that.
> > > > > > > > > > > > > > > > Added now.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > Roman Shtykh
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > On Thursday, September 6, 2018, 6:16:58 p.m.
> > > GMT+9,
> > > > > > Ilya
> > > > > > > > >
> > > > > > > > > Kasnacheev
> > > > > > > > > > <
> > > > > > > > > > > > > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Hello!
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > The last of my requests still standing is that
> > we
> > > > > > should
> > > > > > > fall-back
> > > > > > > > > >
> > > > > > > > > > to
> > > > > > > > > > > > > > > > single URL download in case of error with
> > > 'latest'
> > > > > > > version.
> > > > > > > > > >
> > > > > > > > > > Everything
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > else
> > > > > > > > > > > > > > > > looks good to me.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Can we do that? I'm really worried that Apache
> > > API
> > > > > will
> > > > > > > go sour.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Regards,
> > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > чт, 6 сент. 2018 г. в 8:56, Roman Shtykh <
> > > > > > > rshtykh@yahoo.com>:
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Hi Ilya,
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Thanks again.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > 1) Done.
> > > > > > > > > > > > > > > > 2) Used catch() for latest version.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Please see my comments on github.
> > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > Roman Shtykh
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > On Wednesday, September 5, 2018, 11:30:10 p.m.
> > > > GMT+9,
> > > > > > > Ilya
> > > > > > > > > >
> > > > > > > > > > Kasnacheev <
> > > > > > > > > > > > > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Hello!
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > I've left a new wave of replies.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Basically, 1) let's keep DOWNLOAD_URL_PATTERN
> > > > string
> > > > > > > value inlined
> > > > > > > > > >
> > > > > > > > > > so
> > > > > > > > > > > > > > > > that it will work even if build process is
> > broken
> > > > > > (would
> > > > > > > be useful
> > > > > > > > > >
> > > > > > > > > > for
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > e.g.
> > > > > > > > > > > > > > > > developing out of IDE)
> > > > > > > > > > > > > > > > And also I urge you to catch() around new
> > fragile
> > > > > > Apache
> > > > > > > JSON API
> > > > > > > > > > > > > > > > resolving, and download the 'current' version
> > > > > instead,
> > > > > > > as defined
> > > > > > > > >
> > > > > > > > > by
> > > > > > > > > > > > > > > > ignite-mesos version.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > This is because this module is not under
> > > > continuouos
> > > > > > > scrutiny so
> > > > > > > > > >
> > > > > > > > > > extra
> > > > > > > > > > > > > > > > care should be applied.
> > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > вт, 4 сент. 2018 г. в 13:42, Roman Shtykh <
> > > > > > > rshtykh@yahoo.com>:
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Thanks, Ilya!
> > > > > > > > > > > > > > > > I will check your comments, and discuss it at
> > > JIRA.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > Roman Shtykh
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > On Tuesday, September 4, 2018, 7:17:53 p.m.
> > > GMT+9,
> > > > > Ilya
> > > > > > > > >
> > > > > > > > > Kasnacheev <
> > > > > > > > > > > > > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Hello!
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > IGNITE-9408 <
> > > > > > > https://issues.apache.org/jira/browse/IGNITE-9408>
> > > > > > > > > >
> > > > > > > > > > looks
> > > > > > > > > > > > > > > > good to me and may be merged right away.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > IGNITE-9388 <
> > > > > > > https://issues.apache.org/jira/browse/IGNITE-9388>
> > > > > > > > > >
> > > > > > > > > > needs
> > > > > > > > > > > > > > > > more work in my opinion, I have commented the
> > > PR. I
> > > > > > also
> > > > > > > advice
> > > > > > > > > >
> > > > > > > > > > having
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > test
> > > > > > > > > > > > > > > > for this functionality.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Regards,
> > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > вт, 4 сент. 2018 г. в 6:52, Roman Shtykh
> > > > > > > > >
> > > > > > > > > <rshtykh@yahoo.com.invalid
> > > > > > > > > > > :
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > 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
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > <
> > > > > > > > > > > > > > > > daradurvs@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 <
> > > > > > > > > >
> > > > > > > > > > nizhikov@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.
> > > > > > > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
Re: Apache Ignite 2.7 release
Posted by Nikolay Izhikov <ni...@apache.org>.
Hello, Igniters.
Vova, thank you for pointing this out.
I ask all community members to iterate over assigned tickets.
Please, move your tickets to 2.8 release if work is still in progress.
At the end of the day, I will do it by myself and tomorrow we should have
release scope prepared.
ср, 19 сент. 2018 г. в 12:08, Vladimir Ozerov <vo...@gridgain.com>:
> My point was not about code freeze, but about scope freeze, what means that
> starting from this point AI 2.7 release should not receive any commits
> which doesn't relate to it.
>
> On Wed, Sep 19, 2018 at 11:55 AM Anton Vinogradov <av...@apache.org> wrote:
>
> > Vova,
> >
> > AFAIK, codefreeze was not announced yet.
> > Correct me in case I missed this.
> >
> > Now, Nikolay finishing checks that he's able to perform release
> (everything
> > installed and properly configured).
> > So, I recommend him to mention this check here to solve any
> > misunderstanding in case some branches or tags related to 2.7 will be
> found
> > before we announced codefreeze.
> >
> > ср, 19 сент. 2018 г. в 11:45, Vladimir Ozerov <vo...@gridgain.com>:
> >
> > > Anton,
> > >
> > > What do you mean under "preparation to real 2.7". It is already real,
> we
> > > reached formal code freeze phase we agreed on. At this point we need to
> > > exclude non-2.7 commits, otherwise we will not be able to come to
> stable
> > > branch in two weeks.
> > > For this reason creating a branch for 2.7 at the moment is perfectly
> > valid
> > > thing. This is how we made releases previously.
> > >
> > > On Tue, Sep 18, 2018 at 7:59 PM Dmitriy Pavlov <dp...@gmail.com>
> > > wrote:
> > >
> > > > Hi Paul.
> > > >
> > > > There are 2 PRs linked to that ticket. Who is reviewing your changes?
> > > >
> > > > Branch for 2.7 is still master, so if your changes are reviewed and
> > > > accepted soon it will be in 2.7.
> > > >
> > > > Sincerely,
> > > > Dmitriy Pavlov
> > > >
> > > > вт, 18 сент. 2018 г. в 16:22, Paul Anderson <de...@gmail.com>:
> > > >
> > > > > Hi, may I ask for IGNITE-9298 to be included in 2.7 pls
> > > > >
> > > > > On Tue, Sep 18, 2018 at 1:03 PM Nikolay Izhikov <
> nizhikov@apache.org
> > >
> > > > > wrote:
> > > > >
> > > > > > Hello, folks.
> > > > > >
> > > > > > Thanks for the comments.
> > > > > >
> > > > > > I will follow them.
> > > > > >
> > > > > > В Вт, 18/09/2018 в 13:31 +0300, Anton Vinogradov пишет:
> > > > > > > Nikolay,
> > > > > > >
> > > > > > > 1) *Do not* create ignite-2.7 branch until we're not started
> > > > > preparation
> > > > > > to
> > > > > > > real 2.7.
> > > > > > > Use some temporary branch for this check instead, eg.
> > > > > > > ignite-2.7-release-test
> > > > > > >
> > > > > > > 2) Please make sure you'll not cause real release actions
> (maven
> > > > > release
> > > > > > > and so on).
> > > > > > > Perform only vote_* steps.
> > > > > > >
> > > > > > > 3) Make sure you'll remove all tags, branches, and other RC
> > > artifacts
> > > > > > after
> > > > > > > check.
> > > > > > >
> > > > > > > 4) Mark this release as RC0 to make sure it will be clear to
> > > > everybody
> > > > > > that
> > > > > > > it's a check.
> > > > > > >
> > > > > > >
> > > > > > > вт, 18 сент. 2018 г. в 13:24, Dmitriy Setrakyan <
> > > > dsetrakyan@apache.org
> > > > > >:
> > > > > > >
> > > > > > > > If it is an Ignite release, then it has to pass through the
> > vote.
> > > > If
> > > > > > not,
> > > > > > > > then you can do the test without publishing or uploading the
> > > > release.
> > > > > > > >
> > > > > > > > D.
> > > > > > > >
> > > > > > > > On Tue, Sep 18, 2018 at 1:18 PM Petr Ivanov <
> > mr.weider@gmail.com
> > > >
> > > > > > wrote:
> > > > > > > >
> > > > > > > > > Ok.
> > > > > > > > >
> > > > > > > > > In case of TC questions — ask me.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > > On 18 Sep 2018, at 13:16, Nikolay Izhikov <
> > > nizhikov@apache.org
> > > > >
> > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > Hello, Petr.
> > > > > > > > > >
> > > > > > > > > > I want to make ignite-2.7 branch today.
> > > > > > > > > > And execute release procedure based on this branch.
> > > > > > > > > >
> > > > > > > > > > However, ignite-2.7 branch will be copy of master until
> > code
> > > > > freeze
> > > > > > > >
> > > > > > > > date.
> > > > > > > > > >
> > > > > > > > > > В Вт, 18/09/2018 в 13:13 +0300, Petr Ivanov пишет:
> > > > > > > > > > > Will it be just a test or there is already ignite-2.7
> > > branch?
> > > > > > > > > > >
> > > > > > > > > > > Fabric removal related TC modifications are not ready
> > yet,
> > > > and
> > > > > > code is
> > > > > > > > >
> > > > > > > > > not in master.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > > On 18 Sep 2018, at 13:07, Nikolay Izhikov <
> > > > > nizhikov@apache.org
> > > > > > >
> > > > > > > >
> > > > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > Hello, Igniters.
> > > > > > > > > > > >
> > > > > > > > > > > > I want to start and release procedures and make an
> RC1
> > > > build.
> > > > > > > > > > > >
> > > > > > > > > > > > It has a 2 intention:
> > > > > > > > > > > >
> > > > > > > > > > > > 1. I want to walk through all release steps to make
> > sure
> > > > they
> > > > > > all
> > > > > > > > >
> > > > > > > > > works for me.
> > > > > > > > > > > > So I will be fully ready on release date.
> > > > > > > > > > > >
> > > > > > > > > > > > 2. We have updated some dependencies in 2.7 and we
> need
> > > to
> > > > > > make sure
> > > > > > > > >
> > > > > > > > > binary build is still workable.
> > > > > > > > > > > >
> > > > > > > > > > > > Any objections?
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > В Пт, 14/09/2018 в 18:52 +0300, Alexey Goncharuk
> пишет:
> > > > > > > > > > > > > We already have all the mechanics in place to work
> > with
> > > > > > properties -
> > > > > > > > >
> > > > > > > > > we use
> > > > > > > > > > > > > ignite.build and ignite.revision from
> > ignite.properties
> > > > > > which are
> > > > > > > > >
> > > > > > > > > adjusted
> > > > > > > > > > > > > during the build in the binary package.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Should I create the ticket if there are no
> > objections?
> > > > > > > > > > > > >
> > > > > > > > > > > > > пт, 14 сент. 2018 г. в 13:22, Ilya Kasnacheev <
> > > > > > > > >
> > > > > > > > > ilya.kasnacheev@gmail.com>:
> > > > > > > > > > > > >
> > > > > > > > > > > > > > Hello!
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > So now there's an issue that this script makes
> > source
> > > > > > change after
> > > > > > > > >
> > > > > > > > > every
> > > > > > > > > > > > > > build, show up in git status.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > What we could do to it:
> > > > > > > > > > > > > > - Commit the changes after the build, once. In
> > hopes
> > > > that
> > > > > > it won't
> > > > > > > > >
> > > > > > > > > change
> > > > > > > > > > > > > > very often. With benefit that we could do that
> > right
> > > > now,
> > > > > > before
> > > > > > > >
> > > > > > > > the
> > > > > > > > > code
> > > > > > > > > > > > > > freeze.
> > > > > > > > > > > > > > - Move these values to a properties file from
> both
> > > > > pom.xml
> > > > > > and
> > > > > > > > > > > > > > IgniteProvider.java. Any problems with this
> > approach?
> > > > > > We'll just
> > > > > > > > >
> > > > > > > > > read them
> > > > > > > > > > > > > > from classpath properties file.
> > > > > > > > > > > > > > - Update the links in the file once and remove
> them
> > > > from
> > > > > > build
> > > > > > > > >
> > > > > > > > > process. Why
> > > > > > > > > > > > > > were they added to build process in the first
> > place -
> > > > to
> > > > > > make them
> > > > > > > > > > > > > > configurable during build?
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Regards,
> > > > > > > > > > > > > > --
> > > > > > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > вт, 11 сент. 2018 г. в 5:53, Roman Shtykh <
> > > > > > rshtykh@yahoo.com>:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Ilya,
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > The "latest" version is the default, and
> resolved
> > > by
> > > > > > > > > > > > > > > https://ignite.apache.org/latest which is used
> > by
> > > > our
> > > > > > web site
> > > > > > > > >
> > > > > > > > > when a
> > > > > > > > > > > > > > > user download the latest Ignite version. And I
> > > think
> > > > > > this is the
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > authority
> > > > > > > > > > > > > > > to judge of the latest official release
> (pom.xml
> > > you
> > > > > > suggest can
> > > > > > > > >
> > > > > > > > > have
> > > > > > > > > > > > > > > SNAPSHOTs etc.).
> > > > > > > > > > > > > > > Also, as I explained during our review
> sessions,
> > > > > > > >
> > > > > > > > ignite-mesos-2.6.0
> > > > > > > > > is a
> > > > > > > > > > > > > > > driver and doesn't mean you need to have Ignite
> > > > 2.6.0.
> > > > > > User can
> > > > > > > >
> > > > > > > > run
> > > > > > > > > any
> > > > > > > > > > > > > > > version of Ignite he/she specifies. By default,
> > > it's
> > > > > > "latest" but
> > > > > > > >
> > > > > > > > a
> > > > > > > > > user
> > > > > > > > > > > > > > > can specify any version needed, even from a
> > > > non-archive
> > > > > > URL.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > In short, what we have now
> > > > > > > > > > > > > > > 1. mesos driver (ignite-mesos-x.x.x) will use
> > > > "latest"
> > > > > > version by
> > > > > > > > >
> > > > > > > > > default
> > > > > > > > > > > > > > > -> it will try to resolve the latest officially
> > > > > releases
> > > > > > version
> > > > > > > >
> > > > > > > > of
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Apache
> > > > > > > > > > > > > > > Ignite, find the closest mirror and download
> > Ignite
> > > > in
> > > > > a
> > > > > > minute.
> > > > > > > >
> > > > > > > > If
> > > > > > > > > the
> > > > > > > > > > > > > > > version resolution fails, we fall back to the
> > slow
> > > > > > apache archive
> > > > > > > > >
> > > > > > > > > (as you
> > > > > > > > > > > > > > > suggest; in my opinion we better fail-fast
> > instead
> > > of
> > > > > > waiting for
> > > > > > > > >
> > > > > > > > > hours
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > to
> > > > > > > > > > > > > > > download, so the user can choose another
> download
> > > > > option
> > > > > > (3))
> > > > > > > > > > > > > > > 2. If the user specifies the version
> explicitly,
> > it
> > > > > goes
> > > > > > to the
> > > > > > > >
> > > > > > > > slow
> > > > > > > > > > > > > > > apache archive.
> > > > > > > > > > > > > > > 3. The user can put ignite zip file on his/her
> > http
> > > > > > server and
> > > > > > > > >
> > > > > > > > > provide
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > URL as a parameter to the driver, if options 1
> > and
> > > 2
> > > > > > don't work.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > As you see, there are 3 options. And I just fix
> > the
> > > > 1st
> > > > > > one with
> > > > > > > > > > > > > > >
> > https://issues.apache.org/jira/browse/IGNITE-9388
> > > > and
> > > > > > don't
> > > > > > > >
> > > > > > > > change
> > > > > > > > > the
> > > > > > > > > > > > > > > original logic (which I find reasonable)
> > documented
> > > > on
> > > > > > our site
> > > > > > > >
> > > > > > > > -- I
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > don't
> > > > > > > > > > > > > > > see how it blocks anything.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Roman Shtykh
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > On Monday, September 10, 2018, 6:16:15 p.m.
> > GMT+9,
> > > > Ilya
> > > > > > > >
> > > > > > > > Kasnacheev <
> > > > > > > > > > > > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Hello!
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > There's still two issues with the submission.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > The first one is that we're downloading
> "latest"
> > > > > version
> > > > > > from
> > > > > > > > >
> > > > > > > > > preferred
> > > > > > > > > > > > > > > mirror but a specified version, such as "2.6",
> > > we're
> > > > > > also going to
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > download
> > > > > > > > > > > > > > > from "slow" archive.apache.org/dist.
> > > > > > > > > > > > > > > That's a great limitation for this change,
> since
> > > most
> > > > > > real
> > > > > > > > >
> > > > > > > > > deployments of
> > > > > > > > > > > > > > > Apache Ignite will have their Ignite version
> > pegged
> > > > to
> > > > > a
> > > > > > specific
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > release.
> > > > > > > > > > > > > > > But in this case there's no win in download
> > speed.
> > > > > > > > > > > > > > > *In my opinion it is a blocker.*
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > The second one is that we can't download
> anything
> > > > when
> > > > > > we failed
> > > > > > > >
> > > > > > > > to
> > > > > > > > > > > > > > > resolve "latest". My idea is that we should try
> > and
> > > > > > download last
> > > > > > > > >
> > > > > > > > > known
> > > > > > > > > > > > > > > version in this case, which can be pushed to
> > source
> > > > > from
> > > > > > pom.xml,
> > > > > > > > >
> > > > > > > > > as we
> > > > > > > > > > > > > > > already do with URLs. So if you could not
> resolve
> > > > > > "latest" you
> > > > > > > >
> > > > > > > > will
> > > > > > > > > > > > > > > download 2.7.0.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Buuut, maybe it's not necessary, maybe we
> should
> > > just
> > > > > > *discourage
> > > > > > > > > > > > > > > "latest"*, which is in my opinion almost
> always a
> > > bad
> > > > > > idea.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > WDYT?
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Regards,
> > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > вс, 9 сент. 2018 г. в 5:47, Roman Shtykh <
> > > > > > rshtykh@yahoo.com>:
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Hi Ilya,
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Sorry, missed that.
> > > > > > > > > > > > > > > Added now.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > Roman Shtykh
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > On Thursday, September 6, 2018, 6:16:58 p.m.
> > GMT+9,
> > > > > Ilya
> > > > > > > >
> > > > > > > > Kasnacheev
> > > > > > > > > <
> > > > > > > > > > > > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Hello!
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > The last of my requests still standing is that
> we
> > > > > should
> > > > > > fall-back
> > > > > > > > >
> > > > > > > > > to
> > > > > > > > > > > > > > > single URL download in case of error with
> > 'latest'
> > > > > > version.
> > > > > > > > >
> > > > > > > > > Everything
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > else
> > > > > > > > > > > > > > > looks good to me.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Can we do that? I'm really worried that Apache
> > API
> > > > will
> > > > > > go sour.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Regards,
> > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > чт, 6 сент. 2018 г. в 8:56, Roman Shtykh <
> > > > > > rshtykh@yahoo.com>:
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Hi Ilya,
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Thanks again.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > 1) Done.
> > > > > > > > > > > > > > > 2) Used catch() for latest version.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Please see my comments on github.
> > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > Roman Shtykh
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > On Wednesday, September 5, 2018, 11:30:10 p.m.
> > > GMT+9,
> > > > > > Ilya
> > > > > > > > >
> > > > > > > > > Kasnacheev <
> > > > > > > > > > > > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Hello!
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > I've left a new wave of replies.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Basically, 1) let's keep DOWNLOAD_URL_PATTERN
> > > string
> > > > > > value inlined
> > > > > > > > >
> > > > > > > > > so
> > > > > > > > > > > > > > > that it will work even if build process is
> broken
> > > > > (would
> > > > > > be useful
> > > > > > > > >
> > > > > > > > > for
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > e.g.
> > > > > > > > > > > > > > > developing out of IDE)
> > > > > > > > > > > > > > > And also I urge you to catch() around new
> fragile
> > > > > Apache
> > > > > > JSON API
> > > > > > > > > > > > > > > resolving, and download the 'current' version
> > > > instead,
> > > > > > as defined
> > > > > > > >
> > > > > > > > by
> > > > > > > > > > > > > > > ignite-mesos version.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > This is because this module is not under
> > > continuouos
> > > > > > scrutiny so
> > > > > > > > >
> > > > > > > > > extra
> > > > > > > > > > > > > > > care should be applied.
> > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > вт, 4 сент. 2018 г. в 13:42, Roman Shtykh <
> > > > > > rshtykh@yahoo.com>:
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Thanks, Ilya!
> > > > > > > > > > > > > > > I will check your comments, and discuss it at
> > JIRA.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > Roman Shtykh
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > On Tuesday, September 4, 2018, 7:17:53 p.m.
> > GMT+9,
> > > > Ilya
> > > > > > > >
> > > > > > > > Kasnacheev <
> > > > > > > > > > > > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Hello!
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > IGNITE-9408 <
> > > > > > https://issues.apache.org/jira/browse/IGNITE-9408>
> > > > > > > > >
> > > > > > > > > looks
> > > > > > > > > > > > > > > good to me and may be merged right away.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > IGNITE-9388 <
> > > > > > https://issues.apache.org/jira/browse/IGNITE-9388>
> > > > > > > > >
> > > > > > > > > needs
> > > > > > > > > > > > > > > more work in my opinion, I have commented the
> > PR. I
> > > > > also
> > > > > > advice
> > > > > > > > >
> > > > > > > > > having
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > test
> > > > > > > > > > > > > > > for this functionality.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Regards,
> > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > вт, 4 сент. 2018 г. в 6:52, Roman Shtykh
> > > > > > > >
> > > > > > > > <rshtykh@yahoo.com.invalid
> > > > > > > > > > :
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > 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
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > <
> > > > > > > > > > > > > > > daradurvs@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 <
> > > > > > > > >
> > > > > > > > > nizhikov@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.
> > > > > > > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > >
> > > >
> > >
> >
>
Re: Apache Ignite 2.7 release
Posted by Vladimir Ozerov <vo...@gridgain.com>.
My point was not about code freeze, but about scope freeze, what means that
starting from this point AI 2.7 release should not receive any commits
which doesn't relate to it.
On Wed, Sep 19, 2018 at 11:55 AM Anton Vinogradov <av...@apache.org> wrote:
> Vova,
>
> AFAIK, codefreeze was not announced yet.
> Correct me in case I missed this.
>
> Now, Nikolay finishing checks that he's able to perform release (everything
> installed and properly configured).
> So, I recommend him to mention this check here to solve any
> misunderstanding in case some branches or tags related to 2.7 will be found
> before we announced codefreeze.
>
> ср, 19 сент. 2018 г. в 11:45, Vladimir Ozerov <vo...@gridgain.com>:
>
> > Anton,
> >
> > What do you mean under "preparation to real 2.7". It is already real, we
> > reached formal code freeze phase we agreed on. At this point we need to
> > exclude non-2.7 commits, otherwise we will not be able to come to stable
> > branch in two weeks.
> > For this reason creating a branch for 2.7 at the moment is perfectly
> valid
> > thing. This is how we made releases previously.
> >
> > On Tue, Sep 18, 2018 at 7:59 PM Dmitriy Pavlov <dp...@gmail.com>
> > wrote:
> >
> > > Hi Paul.
> > >
> > > There are 2 PRs linked to that ticket. Who is reviewing your changes?
> > >
> > > Branch for 2.7 is still master, so if your changes are reviewed and
> > > accepted soon it will be in 2.7.
> > >
> > > Sincerely,
> > > Dmitriy Pavlov
> > >
> > > вт, 18 сент. 2018 г. в 16:22, Paul Anderson <de...@gmail.com>:
> > >
> > > > Hi, may I ask for IGNITE-9298 to be included in 2.7 pls
> > > >
> > > > On Tue, Sep 18, 2018 at 1:03 PM Nikolay Izhikov <nizhikov@apache.org
> >
> > > > wrote:
> > > >
> > > > > Hello, folks.
> > > > >
> > > > > Thanks for the comments.
> > > > >
> > > > > I will follow them.
> > > > >
> > > > > В Вт, 18/09/2018 в 13:31 +0300, Anton Vinogradov пишет:
> > > > > > Nikolay,
> > > > > >
> > > > > > 1) *Do not* create ignite-2.7 branch until we're not started
> > > > preparation
> > > > > to
> > > > > > real 2.7.
> > > > > > Use some temporary branch for this check instead, eg.
> > > > > > ignite-2.7-release-test
> > > > > >
> > > > > > 2) Please make sure you'll not cause real release actions (maven
> > > > release
> > > > > > and so on).
> > > > > > Perform only vote_* steps.
> > > > > >
> > > > > > 3) Make sure you'll remove all tags, branches, and other RC
> > artifacts
> > > > > after
> > > > > > check.
> > > > > >
> > > > > > 4) Mark this release as RC0 to make sure it will be clear to
> > > everybody
> > > > > that
> > > > > > it's a check.
> > > > > >
> > > > > >
> > > > > > вт, 18 сент. 2018 г. в 13:24, Dmitriy Setrakyan <
> > > dsetrakyan@apache.org
> > > > >:
> > > > > >
> > > > > > > If it is an Ignite release, then it has to pass through the
> vote.
> > > If
> > > > > not,
> > > > > > > then you can do the test without publishing or uploading the
> > > release.
> > > > > > >
> > > > > > > D.
> > > > > > >
> > > > > > > On Tue, Sep 18, 2018 at 1:18 PM Petr Ivanov <
> mr.weider@gmail.com
> > >
> > > > > wrote:
> > > > > > >
> > > > > > > > Ok.
> > > > > > > >
> > > > > > > > In case of TC questions — ask me.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > > On 18 Sep 2018, at 13:16, Nikolay Izhikov <
> > nizhikov@apache.org
> > > >
> > > > > wrote:
> > > > > > > > >
> > > > > > > > > Hello, Petr.
> > > > > > > > >
> > > > > > > > > I want to make ignite-2.7 branch today.
> > > > > > > > > And execute release procedure based on this branch.
> > > > > > > > >
> > > > > > > > > However, ignite-2.7 branch will be copy of master until
> code
> > > > freeze
> > > > > > >
> > > > > > > date.
> > > > > > > > >
> > > > > > > > > В Вт, 18/09/2018 в 13:13 +0300, Petr Ivanov пишет:
> > > > > > > > > > Will it be just a test or there is already ignite-2.7
> > branch?
> > > > > > > > > >
> > > > > > > > > > Fabric removal related TC modifications are not ready
> yet,
> > > and
> > > > > code is
> > > > > > > >
> > > > > > > > not in master.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > > On 18 Sep 2018, at 13:07, Nikolay Izhikov <
> > > > nizhikov@apache.org
> > > > > >
> > > > > > >
> > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > Hello, Igniters.
> > > > > > > > > > >
> > > > > > > > > > > I want to start and release procedures and make an RC1
> > > build.
> > > > > > > > > > >
> > > > > > > > > > > It has a 2 intention:
> > > > > > > > > > >
> > > > > > > > > > > 1. I want to walk through all release steps to make
> sure
> > > they
> > > > > all
> > > > > > > >
> > > > > > > > works for me.
> > > > > > > > > > > So I will be fully ready on release date.
> > > > > > > > > > >
> > > > > > > > > > > 2. We have updated some dependencies in 2.7 and we need
> > to
> > > > > make sure
> > > > > > > >
> > > > > > > > binary build is still workable.
> > > > > > > > > > >
> > > > > > > > > > > Any objections?
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > В Пт, 14/09/2018 в 18:52 +0300, Alexey Goncharuk пишет:
> > > > > > > > > > > > We already have all the mechanics in place to work
> with
> > > > > properties -
> > > > > > > >
> > > > > > > > we use
> > > > > > > > > > > > ignite.build and ignite.revision from
> ignite.properties
> > > > > which are
> > > > > > > >
> > > > > > > > adjusted
> > > > > > > > > > > > during the build in the binary package.
> > > > > > > > > > > >
> > > > > > > > > > > > Should I create the ticket if there are no
> objections?
> > > > > > > > > > > >
> > > > > > > > > > > > пт, 14 сент. 2018 г. в 13:22, Ilya Kasnacheev <
> > > > > > > >
> > > > > > > > ilya.kasnacheev@gmail.com>:
> > > > > > > > > > > >
> > > > > > > > > > > > > Hello!
> > > > > > > > > > > > >
> > > > > > > > > > > > > So now there's an issue that this script makes
> source
> > > > > change after
> > > > > > > >
> > > > > > > > every
> > > > > > > > > > > > > build, show up in git status.
> > > > > > > > > > > > >
> > > > > > > > > > > > > What we could do to it:
> > > > > > > > > > > > > - Commit the changes after the build, once. In
> hopes
> > > that
> > > > > it won't
> > > > > > > >
> > > > > > > > change
> > > > > > > > > > > > > very often. With benefit that we could do that
> right
> > > now,
> > > > > before
> > > > > > >
> > > > > > > the
> > > > > > > > code
> > > > > > > > > > > > > freeze.
> > > > > > > > > > > > > - Move these values to a properties file from both
> > > > pom.xml
> > > > > and
> > > > > > > > > > > > > IgniteProvider.java. Any problems with this
> approach?
> > > > > We'll just
> > > > > > > >
> > > > > > > > read them
> > > > > > > > > > > > > from classpath properties file.
> > > > > > > > > > > > > - Update the links in the file once and remove them
> > > from
> > > > > build
> > > > > > > >
> > > > > > > > process. Why
> > > > > > > > > > > > > were they added to build process in the first
> place -
> > > to
> > > > > make them
> > > > > > > > > > > > > configurable during build?
> > > > > > > > > > > > >
> > > > > > > > > > > > > Regards,
> > > > > > > > > > > > > --
> > > > > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > вт, 11 сент. 2018 г. в 5:53, Roman Shtykh <
> > > > > rshtykh@yahoo.com>:
> > > > > > > > > > > > >
> > > > > > > > > > > > > > Ilya,
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > The "latest" version is the default, and resolved
> > by
> > > > > > > > > > > > > > https://ignite.apache.org/latest which is used
> by
> > > our
> > > > > web site
> > > > > > > >
> > > > > > > > when a
> > > > > > > > > > > > > > user download the latest Ignite version. And I
> > think
> > > > > this is the
> > > > > > > > > > > > >
> > > > > > > > > > > > > authority
> > > > > > > > > > > > > > to judge of the latest official release (pom.xml
> > you
> > > > > suggest can
> > > > > > > >
> > > > > > > > have
> > > > > > > > > > > > > > SNAPSHOTs etc.).
> > > > > > > > > > > > > > Also, as I explained during our review sessions,
> > > > > > >
> > > > > > > ignite-mesos-2.6.0
> > > > > > > > is a
> > > > > > > > > > > > > > driver and doesn't mean you need to have Ignite
> > > 2.6.0.
> > > > > User can
> > > > > > >
> > > > > > > run
> > > > > > > > any
> > > > > > > > > > > > > > version of Ignite he/she specifies. By default,
> > it's
> > > > > "latest" but
> > > > > > >
> > > > > > > a
> > > > > > > > user
> > > > > > > > > > > > > > can specify any version needed, even from a
> > > non-archive
> > > > > URL.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > In short, what we have now
> > > > > > > > > > > > > > 1. mesos driver (ignite-mesos-x.x.x) will use
> > > "latest"
> > > > > version by
> > > > > > > >
> > > > > > > > default
> > > > > > > > > > > > > > -> it will try to resolve the latest officially
> > > > releases
> > > > > version
> > > > > > >
> > > > > > > of
> > > > > > > > > > > > >
> > > > > > > > > > > > > Apache
> > > > > > > > > > > > > > Ignite, find the closest mirror and download
> Ignite
> > > in
> > > > a
> > > > > minute.
> > > > > > >
> > > > > > > If
> > > > > > > > the
> > > > > > > > > > > > > > version resolution fails, we fall back to the
> slow
> > > > > apache archive
> > > > > > > >
> > > > > > > > (as you
> > > > > > > > > > > > > > suggest; in my opinion we better fail-fast
> instead
> > of
> > > > > waiting for
> > > > > > > >
> > > > > > > > hours
> > > > > > > > > > > > >
> > > > > > > > > > > > > to
> > > > > > > > > > > > > > download, so the user can choose another download
> > > > option
> > > > > (3))
> > > > > > > > > > > > > > 2. If the user specifies the version explicitly,
> it
> > > > goes
> > > > > to the
> > > > > > >
> > > > > > > slow
> > > > > > > > > > > > > > apache archive.
> > > > > > > > > > > > > > 3. The user can put ignite zip file on his/her
> http
> > > > > server and
> > > > > > > >
> > > > > > > > provide
> > > > > > > > > > > > >
> > > > > > > > > > > > > the
> > > > > > > > > > > > > > URL as a parameter to the driver, if options 1
> and
> > 2
> > > > > don't work.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > As you see, there are 3 options. And I just fix
> the
> > > 1st
> > > > > one with
> > > > > > > > > > > > > >
> https://issues.apache.org/jira/browse/IGNITE-9388
> > > and
> > > > > don't
> > > > > > >
> > > > > > > change
> > > > > > > > the
> > > > > > > > > > > > > > original logic (which I find reasonable)
> documented
> > > on
> > > > > our site
> > > > > > >
> > > > > > > -- I
> > > > > > > > > > > > >
> > > > > > > > > > > > > don't
> > > > > > > > > > > > > > see how it blocks anything.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Roman Shtykh
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > On Monday, September 10, 2018, 6:16:15 p.m.
> GMT+9,
> > > Ilya
> > > > > > >
> > > > > > > Kasnacheev <
> > > > > > > > > > > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Hello!
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > There's still two issues with the submission.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > The first one is that we're downloading "latest"
> > > > version
> > > > > from
> > > > > > > >
> > > > > > > > preferred
> > > > > > > > > > > > > > mirror but a specified version, such as "2.6",
> > we're
> > > > > also going to
> > > > > > > > > > > > >
> > > > > > > > > > > > > download
> > > > > > > > > > > > > > from "slow" archive.apache.org/dist.
> > > > > > > > > > > > > > That's a great limitation for this change, since
> > most
> > > > > real
> > > > > > > >
> > > > > > > > deployments of
> > > > > > > > > > > > > > Apache Ignite will have their Ignite version
> pegged
> > > to
> > > > a
> > > > > specific
> > > > > > > > > > > > >
> > > > > > > > > > > > > release.
> > > > > > > > > > > > > > But in this case there's no win in download
> speed.
> > > > > > > > > > > > > > *In my opinion it is a blocker.*
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > The second one is that we can't download anything
> > > when
> > > > > we failed
> > > > > > >
> > > > > > > to
> > > > > > > > > > > > > > resolve "latest". My idea is that we should try
> and
> > > > > download last
> > > > > > > >
> > > > > > > > known
> > > > > > > > > > > > > > version in this case, which can be pushed to
> source
> > > > from
> > > > > pom.xml,
> > > > > > > >
> > > > > > > > as we
> > > > > > > > > > > > > > already do with URLs. So if you could not resolve
> > > > > "latest" you
> > > > > > >
> > > > > > > will
> > > > > > > > > > > > > > download 2.7.0.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Buuut, maybe it's not necessary, maybe we should
> > just
> > > > > *discourage
> > > > > > > > > > > > > > "latest"*, which is in my opinion almost always a
> > bad
> > > > > idea.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > WDYT?
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Regards,
> > > > > > > > > > > > > > --
> > > > > > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > вс, 9 сент. 2018 г. в 5:47, Roman Shtykh <
> > > > > rshtykh@yahoo.com>:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Hi Ilya,
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Sorry, missed that.
> > > > > > > > > > > > > > Added now.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > --
> > > > > > > > > > > > > > Roman Shtykh
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > On Thursday, September 6, 2018, 6:16:58 p.m.
> GMT+9,
> > > > Ilya
> > > > > > >
> > > > > > > Kasnacheev
> > > > > > > > <
> > > > > > > > > > > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Hello!
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > The last of my requests still standing is that we
> > > > should
> > > > > fall-back
> > > > > > > >
> > > > > > > > to
> > > > > > > > > > > > > > single URL download in case of error with
> 'latest'
> > > > > version.
> > > > > > > >
> > > > > > > > Everything
> > > > > > > > > > > > >
> > > > > > > > > > > > > else
> > > > > > > > > > > > > > looks good to me.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Can we do that? I'm really worried that Apache
> API
> > > will
> > > > > go sour.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Regards,
> > > > > > > > > > > > > > --
> > > > > > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > чт, 6 сент. 2018 г. в 8:56, Roman Shtykh <
> > > > > rshtykh@yahoo.com>:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Hi Ilya,
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Thanks again.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > 1) Done.
> > > > > > > > > > > > > > 2) Used catch() for latest version.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Please see my comments on github.
> > > > > > > > > > > > > > --
> > > > > > > > > > > > > > Roman Shtykh
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > On Wednesday, September 5, 2018, 11:30:10 p.m.
> > GMT+9,
> > > > > Ilya
> > > > > > > >
> > > > > > > > Kasnacheev <
> > > > > > > > > > > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Hello!
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > I've left a new wave of replies.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Basically, 1) let's keep DOWNLOAD_URL_PATTERN
> > string
> > > > > value inlined
> > > > > > > >
> > > > > > > > so
> > > > > > > > > > > > > > that it will work even if build process is broken
> > > > (would
> > > > > be useful
> > > > > > > >
> > > > > > > > for
> > > > > > > > > > > > >
> > > > > > > > > > > > > e.g.
> > > > > > > > > > > > > > developing out of IDE)
> > > > > > > > > > > > > > And also I urge you to catch() around new fragile
> > > > Apache
> > > > > JSON API
> > > > > > > > > > > > > > resolving, and download the 'current' version
> > > instead,
> > > > > as defined
> > > > > > >
> > > > > > > by
> > > > > > > > > > > > > > ignite-mesos version.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > This is because this module is not under
> > continuouos
> > > > > scrutiny so
> > > > > > > >
> > > > > > > > extra
> > > > > > > > > > > > > > care should be applied.
> > > > > > > > > > > > > > --
> > > > > > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > вт, 4 сент. 2018 г. в 13:42, Roman Shtykh <
> > > > > rshtykh@yahoo.com>:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Thanks, Ilya!
> > > > > > > > > > > > > > I will check your comments, and discuss it at
> JIRA.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > --
> > > > > > > > > > > > > > Roman Shtykh
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > On Tuesday, September 4, 2018, 7:17:53 p.m.
> GMT+9,
> > > Ilya
> > > > > > >
> > > > > > > Kasnacheev <
> > > > > > > > > > > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Hello!
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > IGNITE-9408 <
> > > > > https://issues.apache.org/jira/browse/IGNITE-9408>
> > > > > > > >
> > > > > > > > looks
> > > > > > > > > > > > > > good to me and may be merged right away.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > IGNITE-9388 <
> > > > > https://issues.apache.org/jira/browse/IGNITE-9388>
> > > > > > > >
> > > > > > > > needs
> > > > > > > > > > > > > > more work in my opinion, I have commented the
> PR. I
> > > > also
> > > > > advice
> > > > > > > >
> > > > > > > > having
> > > > > > > > > > > > >
> > > > > > > > > > > > > test
> > > > > > > > > > > > > > for this functionality.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Regards,
> > > > > > > > > > > > > > --
> > > > > > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > вт, 4 сент. 2018 г. в 6:52, Roman Shtykh
> > > > > > >
> > > > > > > <rshtykh@yahoo.com.invalid
> > > > > > > > > :
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > 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
> > > > > > > > > > > > >
> > > > > > > > > > > > > <
> > > > > > > > > > > > > > daradurvs@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 <
> > > > > > > >
> > > > > > > > nizhikov@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.
> > > > > > > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > >
> > >
> >
>
Re: Apache Ignite 2.7 release
Posted by Anton Vinogradov <av...@apache.org>.
Vova,
AFAIK, codefreeze was not announced yet.
Correct me in case I missed this.
Now, Nikolay finishing checks that he's able to perform release (everything
installed and properly configured).
So, I recommend him to mention this check here to solve any
misunderstanding in case some branches or tags related to 2.7 will be found
before we announced codefreeze.
ср, 19 сент. 2018 г. в 11:45, Vladimir Ozerov <vo...@gridgain.com>:
> Anton,
>
> What do you mean under "preparation to real 2.7". It is already real, we
> reached formal code freeze phase we agreed on. At this point we need to
> exclude non-2.7 commits, otherwise we will not be able to come to stable
> branch in two weeks.
> For this reason creating a branch for 2.7 at the moment is perfectly valid
> thing. This is how we made releases previously.
>
> On Tue, Sep 18, 2018 at 7:59 PM Dmitriy Pavlov <dp...@gmail.com>
> wrote:
>
> > Hi Paul.
> >
> > There are 2 PRs linked to that ticket. Who is reviewing your changes?
> >
> > Branch for 2.7 is still master, so if your changes are reviewed and
> > accepted soon it will be in 2.7.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > вт, 18 сент. 2018 г. в 16:22, Paul Anderson <de...@gmail.com>:
> >
> > > Hi, may I ask for IGNITE-9298 to be included in 2.7 pls
> > >
> > > On Tue, Sep 18, 2018 at 1:03 PM Nikolay Izhikov <ni...@apache.org>
> > > wrote:
> > >
> > > > Hello, folks.
> > > >
> > > > Thanks for the comments.
> > > >
> > > > I will follow them.
> > > >
> > > > В Вт, 18/09/2018 в 13:31 +0300, Anton Vinogradov пишет:
> > > > > Nikolay,
> > > > >
> > > > > 1) *Do not* create ignite-2.7 branch until we're not started
> > > preparation
> > > > to
> > > > > real 2.7.
> > > > > Use some temporary branch for this check instead, eg.
> > > > > ignite-2.7-release-test
> > > > >
> > > > > 2) Please make sure you'll not cause real release actions (maven
> > > release
> > > > > and so on).
> > > > > Perform only vote_* steps.
> > > > >
> > > > > 3) Make sure you'll remove all tags, branches, and other RC
> artifacts
> > > > after
> > > > > check.
> > > > >
> > > > > 4) Mark this release as RC0 to make sure it will be clear to
> > everybody
> > > > that
> > > > > it's a check.
> > > > >
> > > > >
> > > > > вт, 18 сент. 2018 г. в 13:24, Dmitriy Setrakyan <
> > dsetrakyan@apache.org
> > > >:
> > > > >
> > > > > > If it is an Ignite release, then it has to pass through the vote.
> > If
> > > > not,
> > > > > > then you can do the test without publishing or uploading the
> > release.
> > > > > >
> > > > > > D.
> > > > > >
> > > > > > On Tue, Sep 18, 2018 at 1:18 PM Petr Ivanov <mr.weider@gmail.com
> >
> > > > wrote:
> > > > > >
> > > > > > > Ok.
> > > > > > >
> > > > > > > In case of TC questions — ask me.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > > On 18 Sep 2018, at 13:16, Nikolay Izhikov <
> nizhikov@apache.org
> > >
> > > > wrote:
> > > > > > > >
> > > > > > > > Hello, Petr.
> > > > > > > >
> > > > > > > > I want to make ignite-2.7 branch today.
> > > > > > > > And execute release procedure based on this branch.
> > > > > > > >
> > > > > > > > However, ignite-2.7 branch will be copy of master until code
> > > freeze
> > > > > >
> > > > > > date.
> > > > > > > >
> > > > > > > > В Вт, 18/09/2018 в 13:13 +0300, Petr Ivanov пишет:
> > > > > > > > > Will it be just a test or there is already ignite-2.7
> branch?
> > > > > > > > >
> > > > > > > > > Fabric removal related TC modifications are not ready yet,
> > and
> > > > code is
> > > > > > >
> > > > > > > not in master.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > > On 18 Sep 2018, at 13:07, Nikolay Izhikov <
> > > nizhikov@apache.org
> > > > >
> > > > > >
> > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > Hello, Igniters.
> > > > > > > > > >
> > > > > > > > > > I want to start and release procedures and make an RC1
> > build.
> > > > > > > > > >
> > > > > > > > > > It has a 2 intention:
> > > > > > > > > >
> > > > > > > > > > 1. I want to walk through all release steps to make sure
> > they
> > > > all
> > > > > > >
> > > > > > > works for me.
> > > > > > > > > > So I will be fully ready on release date.
> > > > > > > > > >
> > > > > > > > > > 2. We have updated some dependencies in 2.7 and we need
> to
> > > > make sure
> > > > > > >
> > > > > > > binary build is still workable.
> > > > > > > > > >
> > > > > > > > > > Any objections?
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > В Пт, 14/09/2018 в 18:52 +0300, Alexey Goncharuk пишет:
> > > > > > > > > > > We already have all the mechanics in place to work with
> > > > properties -
> > > > > > >
> > > > > > > we use
> > > > > > > > > > > ignite.build and ignite.revision from ignite.properties
> > > > which are
> > > > > > >
> > > > > > > adjusted
> > > > > > > > > > > during the build in the binary package.
> > > > > > > > > > >
> > > > > > > > > > > Should I create the ticket if there are no objections?
> > > > > > > > > > >
> > > > > > > > > > > пт, 14 сент. 2018 г. в 13:22, Ilya Kasnacheev <
> > > > > > >
> > > > > > > ilya.kasnacheev@gmail.com>:
> > > > > > > > > > >
> > > > > > > > > > > > Hello!
> > > > > > > > > > > >
> > > > > > > > > > > > So now there's an issue that this script makes source
> > > > change after
> > > > > > >
> > > > > > > every
> > > > > > > > > > > > build, show up in git status.
> > > > > > > > > > > >
> > > > > > > > > > > > What we could do to it:
> > > > > > > > > > > > - Commit the changes after the build, once. In hopes
> > that
> > > > it won't
> > > > > > >
> > > > > > > change
> > > > > > > > > > > > very often. With benefit that we could do that right
> > now,
> > > > before
> > > > > >
> > > > > > the
> > > > > > > code
> > > > > > > > > > > > freeze.
> > > > > > > > > > > > - Move these values to a properties file from both
> > > pom.xml
> > > > and
> > > > > > > > > > > > IgniteProvider.java. Any problems with this approach?
> > > > We'll just
> > > > > > >
> > > > > > > read them
> > > > > > > > > > > > from classpath properties file.
> > > > > > > > > > > > - Update the links in the file once and remove them
> > from
> > > > build
> > > > > > >
> > > > > > > process. Why
> > > > > > > > > > > > were they added to build process in the first place -
> > to
> > > > make them
> > > > > > > > > > > > configurable during build?
> > > > > > > > > > > >
> > > > > > > > > > > > Regards,
> > > > > > > > > > > > --
> > > > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > вт, 11 сент. 2018 г. в 5:53, Roman Shtykh <
> > > > rshtykh@yahoo.com>:
> > > > > > > > > > > >
> > > > > > > > > > > > > Ilya,
> > > > > > > > > > > > >
> > > > > > > > > > > > > The "latest" version is the default, and resolved
> by
> > > > > > > > > > > > > https://ignite.apache.org/latest which is used by
> > our
> > > > web site
> > > > > > >
> > > > > > > when a
> > > > > > > > > > > > > user download the latest Ignite version. And I
> think
> > > > this is the
> > > > > > > > > > > >
> > > > > > > > > > > > authority
> > > > > > > > > > > > > to judge of the latest official release (pom.xml
> you
> > > > suggest can
> > > > > > >
> > > > > > > have
> > > > > > > > > > > > > SNAPSHOTs etc.).
> > > > > > > > > > > > > Also, as I explained during our review sessions,
> > > > > >
> > > > > > ignite-mesos-2.6.0
> > > > > > > is a
> > > > > > > > > > > > > driver and doesn't mean you need to have Ignite
> > 2.6.0.
> > > > User can
> > > > > >
> > > > > > run
> > > > > > > any
> > > > > > > > > > > > > version of Ignite he/she specifies. By default,
> it's
> > > > "latest" but
> > > > > >
> > > > > > a
> > > > > > > user
> > > > > > > > > > > > > can specify any version needed, even from a
> > non-archive
> > > > URL.
> > > > > > > > > > > > >
> > > > > > > > > > > > > In short, what we have now
> > > > > > > > > > > > > 1. mesos driver (ignite-mesos-x.x.x) will use
> > "latest"
> > > > version by
> > > > > > >
> > > > > > > default
> > > > > > > > > > > > > -> it will try to resolve the latest officially
> > > releases
> > > > version
> > > > > >
> > > > > > of
> > > > > > > > > > > >
> > > > > > > > > > > > Apache
> > > > > > > > > > > > > Ignite, find the closest mirror and download Ignite
> > in
> > > a
> > > > minute.
> > > > > >
> > > > > > If
> > > > > > > the
> > > > > > > > > > > > > version resolution fails, we fall back to the slow
> > > > apache archive
> > > > > > >
> > > > > > > (as you
> > > > > > > > > > > > > suggest; in my opinion we better fail-fast instead
> of
> > > > waiting for
> > > > > > >
> > > > > > > hours
> > > > > > > > > > > >
> > > > > > > > > > > > to
> > > > > > > > > > > > > download, so the user can choose another download
> > > option
> > > > (3))
> > > > > > > > > > > > > 2. If the user specifies the version explicitly, it
> > > goes
> > > > to the
> > > > > >
> > > > > > slow
> > > > > > > > > > > > > apache archive.
> > > > > > > > > > > > > 3. The user can put ignite zip file on his/her http
> > > > server and
> > > > > > >
> > > > > > > provide
> > > > > > > > > > > >
> > > > > > > > > > > > the
> > > > > > > > > > > > > URL as a parameter to the driver, if options 1 and
> 2
> > > > don't work.
> > > > > > > > > > > > >
> > > > > > > > > > > > > As you see, there are 3 options. And I just fix the
> > 1st
> > > > one with
> > > > > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-9388
> > and
> > > > don't
> > > > > >
> > > > > > change
> > > > > > > the
> > > > > > > > > > > > > original logic (which I find reasonable) documented
> > on
> > > > our site
> > > > > >
> > > > > > -- I
> > > > > > > > > > > >
> > > > > > > > > > > > don't
> > > > > > > > > > > > > see how it blocks anything.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Roman Shtykh
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > On Monday, September 10, 2018, 6:16:15 p.m. GMT+9,
> > Ilya
> > > > > >
> > > > > > Kasnacheev <
> > > > > > > > > > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > Hello!
> > > > > > > > > > > > >
> > > > > > > > > > > > > There's still two issues with the submission.
> > > > > > > > > > > > >
> > > > > > > > > > > > > The first one is that we're downloading "latest"
> > > version
> > > > from
> > > > > > >
> > > > > > > preferred
> > > > > > > > > > > > > mirror but a specified version, such as "2.6",
> we're
> > > > also going to
> > > > > > > > > > > >
> > > > > > > > > > > > download
> > > > > > > > > > > > > from "slow" archive.apache.org/dist.
> > > > > > > > > > > > > That's a great limitation for this change, since
> most
> > > > real
> > > > > > >
> > > > > > > deployments of
> > > > > > > > > > > > > Apache Ignite will have their Ignite version pegged
> > to
> > > a
> > > > specific
> > > > > > > > > > > >
> > > > > > > > > > > > release.
> > > > > > > > > > > > > But in this case there's no win in download speed.
> > > > > > > > > > > > > *In my opinion it is a blocker.*
> > > > > > > > > > > > >
> > > > > > > > > > > > > The second one is that we can't download anything
> > when
> > > > we failed
> > > > > >
> > > > > > to
> > > > > > > > > > > > > resolve "latest". My idea is that we should try and
> > > > download last
> > > > > > >
> > > > > > > known
> > > > > > > > > > > > > version in this case, which can be pushed to source
> > > from
> > > > pom.xml,
> > > > > > >
> > > > > > > as we
> > > > > > > > > > > > > already do with URLs. So if you could not resolve
> > > > "latest" you
> > > > > >
> > > > > > will
> > > > > > > > > > > > > download 2.7.0.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Buuut, maybe it's not necessary, maybe we should
> just
> > > > *discourage
> > > > > > > > > > > > > "latest"*, which is in my opinion almost always a
> bad
> > > > idea.
> > > > > > > > > > > > >
> > > > > > > > > > > > > WDYT?
> > > > > > > > > > > > >
> > > > > > > > > > > > > Regards,
> > > > > > > > > > > > > --
> > > > > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > вс, 9 сент. 2018 г. в 5:47, Roman Shtykh <
> > > > rshtykh@yahoo.com>:
> > > > > > > > > > > > >
> > > > > > > > > > > > > Hi Ilya,
> > > > > > > > > > > > >
> > > > > > > > > > > > > Sorry, missed that.
> > > > > > > > > > > > > Added now.
> > > > > > > > > > > > >
> > > > > > > > > > > > > --
> > > > > > > > > > > > > Roman Shtykh
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > On Thursday, September 6, 2018, 6:16:58 p.m. GMT+9,
> > > Ilya
> > > > > >
> > > > > > Kasnacheev
> > > > > > > <
> > > > > > > > > > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > Hello!
> > > > > > > > > > > > >
> > > > > > > > > > > > > The last of my requests still standing is that we
> > > should
> > > > fall-back
> > > > > > >
> > > > > > > to
> > > > > > > > > > > > > single URL download in case of error with 'latest'
> > > > version.
> > > > > > >
> > > > > > > Everything
> > > > > > > > > > > >
> > > > > > > > > > > > else
> > > > > > > > > > > > > looks good to me.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Can we do that? I'm really worried that Apache API
> > will
> > > > go sour.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Regards,
> > > > > > > > > > > > > --
> > > > > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > чт, 6 сент. 2018 г. в 8:56, Roman Shtykh <
> > > > rshtykh@yahoo.com>:
> > > > > > > > > > > > >
> > > > > > > > > > > > > Hi Ilya,
> > > > > > > > > > > > >
> > > > > > > > > > > > > Thanks again.
> > > > > > > > > > > > >
> > > > > > > > > > > > > 1) Done.
> > > > > > > > > > > > > 2) Used catch() for latest version.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Please see my comments on github.
> > > > > > > > > > > > > --
> > > > > > > > > > > > > Roman Shtykh
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > On Wednesday, September 5, 2018, 11:30:10 p.m.
> GMT+9,
> > > > Ilya
> > > > > > >
> > > > > > > Kasnacheev <
> > > > > > > > > > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > Hello!
> > > > > > > > > > > > >
> > > > > > > > > > > > > I've left a new wave of replies.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Basically, 1) let's keep DOWNLOAD_URL_PATTERN
> string
> > > > value inlined
> > > > > > >
> > > > > > > so
> > > > > > > > > > > > > that it will work even if build process is broken
> > > (would
> > > > be useful
> > > > > > >
> > > > > > > for
> > > > > > > > > > > >
> > > > > > > > > > > > e.g.
> > > > > > > > > > > > > developing out of IDE)
> > > > > > > > > > > > > And also I urge you to catch() around new fragile
> > > Apache
> > > > JSON API
> > > > > > > > > > > > > resolving, and download the 'current' version
> > instead,
> > > > as defined
> > > > > >
> > > > > > by
> > > > > > > > > > > > > ignite-mesos version.
> > > > > > > > > > > > >
> > > > > > > > > > > > > This is because this module is not under
> continuouos
> > > > scrutiny so
> > > > > > >
> > > > > > > extra
> > > > > > > > > > > > > care should be applied.
> > > > > > > > > > > > > --
> > > > > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > вт, 4 сент. 2018 г. в 13:42, Roman Shtykh <
> > > > rshtykh@yahoo.com>:
> > > > > > > > > > > > >
> > > > > > > > > > > > > Thanks, Ilya!
> > > > > > > > > > > > > I will check your comments, and discuss it at JIRA.
> > > > > > > > > > > > >
> > > > > > > > > > > > > --
> > > > > > > > > > > > > Roman Shtykh
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > On Tuesday, September 4, 2018, 7:17:53 p.m. GMT+9,
> > Ilya
> > > > > >
> > > > > > Kasnacheev <
> > > > > > > > > > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > Hello!
> > > > > > > > > > > > >
> > > > > > > > > > > > > IGNITE-9408 <
> > > > https://issues.apache.org/jira/browse/IGNITE-9408>
> > > > > > >
> > > > > > > looks
> > > > > > > > > > > > > good to me and may be merged right away.
> > > > > > > > > > > > >
> > > > > > > > > > > > > IGNITE-9388 <
> > > > https://issues.apache.org/jira/browse/IGNITE-9388>
> > > > > > >
> > > > > > > needs
> > > > > > > > > > > > > more work in my opinion, I have commented the PR. I
> > > also
> > > > advice
> > > > > > >
> > > > > > > having
> > > > > > > > > > > >
> > > > > > > > > > > > test
> > > > > > > > > > > > > for this functionality.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Regards,
> > > > > > > > > > > > > --
> > > > > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > вт, 4 сент. 2018 г. в 6:52, Roman Shtykh
> > > > > >
> > > > > > <rshtykh@yahoo.com.invalid
> > > > > > > > :
> > > > > > > > > > > > >
> > > > > > > > > > > > > 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
> > > > > > > > > > > >
> > > > > > > > > > > > <
> > > > > > > > > > > > > daradurvs@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 <
> > > > > > >
> > > > > > > nizhikov@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.
> > > > > > > > > > > > >
> > > > > > >
> > > > > > >
> > >
> >
>
Re: Apache Ignite 2.7 release
Posted by Vladimir Ozerov <vo...@gridgain.com>.
Anton,
What do you mean under "preparation to real 2.7". It is already real, we
reached formal code freeze phase we agreed on. At this point we need to
exclude non-2.7 commits, otherwise we will not be able to come to stable
branch in two weeks.
For this reason creating a branch for 2.7 at the moment is perfectly valid
thing. This is how we made releases previously.
On Tue, Sep 18, 2018 at 7:59 PM Dmitriy Pavlov <dp...@gmail.com>
wrote:
> Hi Paul.
>
> There are 2 PRs linked to that ticket. Who is reviewing your changes?
>
> Branch for 2.7 is still master, so if your changes are reviewed and
> accepted soon it will be in 2.7.
>
> Sincerely,
> Dmitriy Pavlov
>
> вт, 18 сент. 2018 г. в 16:22, Paul Anderson <de...@gmail.com>:
>
> > Hi, may I ask for IGNITE-9298 to be included in 2.7 pls
> >
> > On Tue, Sep 18, 2018 at 1:03 PM Nikolay Izhikov <ni...@apache.org>
> > wrote:
> >
> > > Hello, folks.
> > >
> > > Thanks for the comments.
> > >
> > > I will follow them.
> > >
> > > В Вт, 18/09/2018 в 13:31 +0300, Anton Vinogradov пишет:
> > > > Nikolay,
> > > >
> > > > 1) *Do not* create ignite-2.7 branch until we're not started
> > preparation
> > > to
> > > > real 2.7.
> > > > Use some temporary branch for this check instead, eg.
> > > > ignite-2.7-release-test
> > > >
> > > > 2) Please make sure you'll not cause real release actions (maven
> > release
> > > > and so on).
> > > > Perform only vote_* steps.
> > > >
> > > > 3) Make sure you'll remove all tags, branches, and other RC artifacts
> > > after
> > > > check.
> > > >
> > > > 4) Mark this release as RC0 to make sure it will be clear to
> everybody
> > > that
> > > > it's a check.
> > > >
> > > >
> > > > вт, 18 сент. 2018 г. в 13:24, Dmitriy Setrakyan <
> dsetrakyan@apache.org
> > >:
> > > >
> > > > > If it is an Ignite release, then it has to pass through the vote.
> If
> > > not,
> > > > > then you can do the test without publishing or uploading the
> release.
> > > > >
> > > > > D.
> > > > >
> > > > > On Tue, Sep 18, 2018 at 1:18 PM Petr Ivanov <mr...@gmail.com>
> > > wrote:
> > > > >
> > > > > > Ok.
> > > > > >
> > > > > > In case of TC questions — ask me.
> > > > > >
> > > > > >
> > > > > >
> > > > > > > On 18 Sep 2018, at 13:16, Nikolay Izhikov <nizhikov@apache.org
> >
> > > wrote:
> > > > > > >
> > > > > > > Hello, Petr.
> > > > > > >
> > > > > > > I want to make ignite-2.7 branch today.
> > > > > > > And execute release procedure based on this branch.
> > > > > > >
> > > > > > > However, ignite-2.7 branch will be copy of master until code
> > freeze
> > > > >
> > > > > date.
> > > > > > >
> > > > > > > В Вт, 18/09/2018 в 13:13 +0300, Petr Ivanov пишет:
> > > > > > > > Will it be just a test or there is already ignite-2.7 branch?
> > > > > > > >
> > > > > > > > Fabric removal related TC modifications are not ready yet,
> and
> > > code is
> > > > > >
> > > > > > not in master.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > > On 18 Sep 2018, at 13:07, Nikolay Izhikov <
> > nizhikov@apache.org
> > > >
> > > > >
> > > > > wrote:
> > > > > > > > >
> > > > > > > > > Hello, Igniters.
> > > > > > > > >
> > > > > > > > > I want to start and release procedures and make an RC1
> build.
> > > > > > > > >
> > > > > > > > > It has a 2 intention:
> > > > > > > > >
> > > > > > > > > 1. I want to walk through all release steps to make sure
> they
> > > all
> > > > > >
> > > > > > works for me.
> > > > > > > > > So I will be fully ready on release date.
> > > > > > > > >
> > > > > > > > > 2. We have updated some dependencies in 2.7 and we need to
> > > make sure
> > > > > >
> > > > > > binary build is still workable.
> > > > > > > > >
> > > > > > > > > Any objections?
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > В Пт, 14/09/2018 в 18:52 +0300, Alexey Goncharuk пишет:
> > > > > > > > > > We already have all the mechanics in place to work with
> > > properties -
> > > > > >
> > > > > > we use
> > > > > > > > > > ignite.build and ignite.revision from ignite.properties
> > > which are
> > > > > >
> > > > > > adjusted
> > > > > > > > > > during the build in the binary package.
> > > > > > > > > >
> > > > > > > > > > Should I create the ticket if there are no objections?
> > > > > > > > > >
> > > > > > > > > > пт, 14 сент. 2018 г. в 13:22, Ilya Kasnacheev <
> > > > > >
> > > > > > ilya.kasnacheev@gmail.com>:
> > > > > > > > > >
> > > > > > > > > > > Hello!
> > > > > > > > > > >
> > > > > > > > > > > So now there's an issue that this script makes source
> > > change after
> > > > > >
> > > > > > every
> > > > > > > > > > > build, show up in git status.
> > > > > > > > > > >
> > > > > > > > > > > What we could do to it:
> > > > > > > > > > > - Commit the changes after the build, once. In hopes
> that
> > > it won't
> > > > > >
> > > > > > change
> > > > > > > > > > > very often. With benefit that we could do that right
> now,
> > > before
> > > > >
> > > > > the
> > > > > > code
> > > > > > > > > > > freeze.
> > > > > > > > > > > - Move these values to a properties file from both
> > pom.xml
> > > and
> > > > > > > > > > > IgniteProvider.java. Any problems with this approach?
> > > We'll just
> > > > > >
> > > > > > read them
> > > > > > > > > > > from classpath properties file.
> > > > > > > > > > > - Update the links in the file once and remove them
> from
> > > build
> > > > > >
> > > > > > process. Why
> > > > > > > > > > > were they added to build process in the first place -
> to
> > > make them
> > > > > > > > > > > configurable during build?
> > > > > > > > > > >
> > > > > > > > > > > Regards,
> > > > > > > > > > > --
> > > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > вт, 11 сент. 2018 г. в 5:53, Roman Shtykh <
> > > rshtykh@yahoo.com>:
> > > > > > > > > > >
> > > > > > > > > > > > Ilya,
> > > > > > > > > > > >
> > > > > > > > > > > > The "latest" version is the default, and resolved by
> > > > > > > > > > > > https://ignite.apache.org/latest which is used by
> our
> > > web site
> > > > > >
> > > > > > when a
> > > > > > > > > > > > user download the latest Ignite version. And I think
> > > this is the
> > > > > > > > > > >
> > > > > > > > > > > authority
> > > > > > > > > > > > to judge of the latest official release (pom.xml you
> > > suggest can
> > > > > >
> > > > > > have
> > > > > > > > > > > > SNAPSHOTs etc.).
> > > > > > > > > > > > Also, as I explained during our review sessions,
> > > > >
> > > > > ignite-mesos-2.6.0
> > > > > > is a
> > > > > > > > > > > > driver and doesn't mean you need to have Ignite
> 2.6.0.
> > > User can
> > > > >
> > > > > run
> > > > > > any
> > > > > > > > > > > > version of Ignite he/she specifies. By default, it's
> > > "latest" but
> > > > >
> > > > > a
> > > > > > user
> > > > > > > > > > > > can specify any version needed, even from a
> non-archive
> > > URL.
> > > > > > > > > > > >
> > > > > > > > > > > > In short, what we have now
> > > > > > > > > > > > 1. mesos driver (ignite-mesos-x.x.x) will use
> "latest"
> > > version by
> > > > > >
> > > > > > default
> > > > > > > > > > > > -> it will try to resolve the latest officially
> > releases
> > > version
> > > > >
> > > > > of
> > > > > > > > > > >
> > > > > > > > > > > Apache
> > > > > > > > > > > > Ignite, find the closest mirror and download Ignite
> in
> > a
> > > minute.
> > > > >
> > > > > If
> > > > > > the
> > > > > > > > > > > > version resolution fails, we fall back to the slow
> > > apache archive
> > > > > >
> > > > > > (as you
> > > > > > > > > > > > suggest; in my opinion we better fail-fast instead of
> > > waiting for
> > > > > >
> > > > > > hours
> > > > > > > > > > >
> > > > > > > > > > > to
> > > > > > > > > > > > download, so the user can choose another download
> > option
> > > (3))
> > > > > > > > > > > > 2. If the user specifies the version explicitly, it
> > goes
> > > to the
> > > > >
> > > > > slow
> > > > > > > > > > > > apache archive.
> > > > > > > > > > > > 3. The user can put ignite zip file on his/her http
> > > server and
> > > > > >
> > > > > > provide
> > > > > > > > > > >
> > > > > > > > > > > the
> > > > > > > > > > > > URL as a parameter to the driver, if options 1 and 2
> > > don't work.
> > > > > > > > > > > >
> > > > > > > > > > > > As you see, there are 3 options. And I just fix the
> 1st
> > > one with
> > > > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-9388
> and
> > > don't
> > > > >
> > > > > change
> > > > > > the
> > > > > > > > > > > > original logic (which I find reasonable) documented
> on
> > > our site
> > > > >
> > > > > -- I
> > > > > > > > > > >
> > > > > > > > > > > don't
> > > > > > > > > > > > see how it blocks anything.
> > > > > > > > > > > >
> > > > > > > > > > > > Roman Shtykh
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > On Monday, September 10, 2018, 6:16:15 p.m. GMT+9,
> Ilya
> > > > >
> > > > > Kasnacheev <
> > > > > > > > > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > Hello!
> > > > > > > > > > > >
> > > > > > > > > > > > There's still two issues with the submission.
> > > > > > > > > > > >
> > > > > > > > > > > > The first one is that we're downloading "latest"
> > version
> > > from
> > > > > >
> > > > > > preferred
> > > > > > > > > > > > mirror but a specified version, such as "2.6", we're
> > > also going to
> > > > > > > > > > >
> > > > > > > > > > > download
> > > > > > > > > > > > from "slow" archive.apache.org/dist.
> > > > > > > > > > > > That's a great limitation for this change, since most
> > > real
> > > > > >
> > > > > > deployments of
> > > > > > > > > > > > Apache Ignite will have their Ignite version pegged
> to
> > a
> > > specific
> > > > > > > > > > >
> > > > > > > > > > > release.
> > > > > > > > > > > > But in this case there's no win in download speed.
> > > > > > > > > > > > *In my opinion it is a blocker.*
> > > > > > > > > > > >
> > > > > > > > > > > > The second one is that we can't download anything
> when
> > > we failed
> > > > >
> > > > > to
> > > > > > > > > > > > resolve "latest". My idea is that we should try and
> > > download last
> > > > > >
> > > > > > known
> > > > > > > > > > > > version in this case, which can be pushed to source
> > from
> > > pom.xml,
> > > > > >
> > > > > > as we
> > > > > > > > > > > > already do with URLs. So if you could not resolve
> > > "latest" you
> > > > >
> > > > > will
> > > > > > > > > > > > download 2.7.0.
> > > > > > > > > > > >
> > > > > > > > > > > > Buuut, maybe it's not necessary, maybe we should just
> > > *discourage
> > > > > > > > > > > > "latest"*, which is in my opinion almost always a bad
> > > idea.
> > > > > > > > > > > >
> > > > > > > > > > > > WDYT?
> > > > > > > > > > > >
> > > > > > > > > > > > Regards,
> > > > > > > > > > > > --
> > > > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > вс, 9 сент. 2018 г. в 5:47, Roman Shtykh <
> > > rshtykh@yahoo.com>:
> > > > > > > > > > > >
> > > > > > > > > > > > Hi Ilya,
> > > > > > > > > > > >
> > > > > > > > > > > > Sorry, missed that.
> > > > > > > > > > > > Added now.
> > > > > > > > > > > >
> > > > > > > > > > > > --
> > > > > > > > > > > > Roman Shtykh
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > On Thursday, September 6, 2018, 6:16:58 p.m. GMT+9,
> > Ilya
> > > > >
> > > > > Kasnacheev
> > > > > > <
> > > > > > > > > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > Hello!
> > > > > > > > > > > >
> > > > > > > > > > > > The last of my requests still standing is that we
> > should
> > > fall-back
> > > > > >
> > > > > > to
> > > > > > > > > > > > single URL download in case of error with 'latest'
> > > version.
> > > > > >
> > > > > > Everything
> > > > > > > > > > >
> > > > > > > > > > > else
> > > > > > > > > > > > looks good to me.
> > > > > > > > > > > >
> > > > > > > > > > > > Can we do that? I'm really worried that Apache API
> will
> > > go sour.
> > > > > > > > > > > >
> > > > > > > > > > > > Regards,
> > > > > > > > > > > > --
> > > > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > чт, 6 сент. 2018 г. в 8:56, Roman Shtykh <
> > > rshtykh@yahoo.com>:
> > > > > > > > > > > >
> > > > > > > > > > > > Hi Ilya,
> > > > > > > > > > > >
> > > > > > > > > > > > Thanks again.
> > > > > > > > > > > >
> > > > > > > > > > > > 1) Done.
> > > > > > > > > > > > 2) Used catch() for latest version.
> > > > > > > > > > > >
> > > > > > > > > > > > Please see my comments on github.
> > > > > > > > > > > > --
> > > > > > > > > > > > Roman Shtykh
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > On Wednesday, September 5, 2018, 11:30:10 p.m. GMT+9,
> > > Ilya
> > > > > >
> > > > > > Kasnacheev <
> > > > > > > > > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > Hello!
> > > > > > > > > > > >
> > > > > > > > > > > > I've left a new wave of replies.
> > > > > > > > > > > >
> > > > > > > > > > > > Basically, 1) let's keep DOWNLOAD_URL_PATTERN string
> > > value inlined
> > > > > >
> > > > > > so
> > > > > > > > > > > > that it will work even if build process is broken
> > (would
> > > be useful
> > > > > >
> > > > > > for
> > > > > > > > > > >
> > > > > > > > > > > e.g.
> > > > > > > > > > > > developing out of IDE)
> > > > > > > > > > > > And also I urge you to catch() around new fragile
> > Apache
> > > JSON API
> > > > > > > > > > > > resolving, and download the 'current' version
> instead,
> > > as defined
> > > > >
> > > > > by
> > > > > > > > > > > > ignite-mesos version.
> > > > > > > > > > > >
> > > > > > > > > > > > This is because this module is not under continuouos
> > > scrutiny so
> > > > > >
> > > > > > extra
> > > > > > > > > > > > care should be applied.
> > > > > > > > > > > > --
> > > > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > вт, 4 сент. 2018 г. в 13:42, Roman Shtykh <
> > > rshtykh@yahoo.com>:
> > > > > > > > > > > >
> > > > > > > > > > > > Thanks, Ilya!
> > > > > > > > > > > > I will check your comments, and discuss it at JIRA.
> > > > > > > > > > > >
> > > > > > > > > > > > --
> > > > > > > > > > > > Roman Shtykh
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > On Tuesday, September 4, 2018, 7:17:53 p.m. GMT+9,
> Ilya
> > > > >
> > > > > Kasnacheev <
> > > > > > > > > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > Hello!
> > > > > > > > > > > >
> > > > > > > > > > > > IGNITE-9408 <
> > > https://issues.apache.org/jira/browse/IGNITE-9408>
> > > > > >
> > > > > > looks
> > > > > > > > > > > > good to me and may be merged right away.
> > > > > > > > > > > >
> > > > > > > > > > > > IGNITE-9388 <
> > > https://issues.apache.org/jira/browse/IGNITE-9388>
> > > > > >
> > > > > > needs
> > > > > > > > > > > > more work in my opinion, I have commented the PR. I
> > also
> > > advice
> > > > > >
> > > > > > having
> > > > > > > > > > >
> > > > > > > > > > > test
> > > > > > > > > > > > for this functionality.
> > > > > > > > > > > >
> > > > > > > > > > > > Regards,
> > > > > > > > > > > > --
> > > > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > вт, 4 сент. 2018 г. в 6:52, Roman Shtykh
> > > > >
> > > > > <rshtykh@yahoo.com.invalid
> > > > > > > :
> > > > > > > > > > > >
> > > > > > > > > > > > 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
> > > > > > > > > > >
> > > > > > > > > > > <
> > > > > > > > > > > > daradurvs@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 <
> > > > > >
> > > > > > nizhikov@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.
> > > > > > > > > > > >
> > > > > >
> > > > > >
> >
>
Re: Apache Ignite 2.7 release
Posted by Dmitriy Pavlov <dp...@gmail.com>.
Hi Paul.
There are 2 PRs linked to that ticket. Who is reviewing your changes?
Branch for 2.7 is still master, so if your changes are reviewed and
accepted soon it will be in 2.7.
Sincerely,
Dmitriy Pavlov
вт, 18 сент. 2018 г. в 16:22, Paul Anderson <de...@gmail.com>:
> Hi, may I ask for IGNITE-9298 to be included in 2.7 pls
>
> On Tue, Sep 18, 2018 at 1:03 PM Nikolay Izhikov <ni...@apache.org>
> wrote:
>
> > Hello, folks.
> >
> > Thanks for the comments.
> >
> > I will follow them.
> >
> > В Вт, 18/09/2018 в 13:31 +0300, Anton Vinogradov пишет:
> > > Nikolay,
> > >
> > > 1) *Do not* create ignite-2.7 branch until we're not started
> preparation
> > to
> > > real 2.7.
> > > Use some temporary branch for this check instead, eg.
> > > ignite-2.7-release-test
> > >
> > > 2) Please make sure you'll not cause real release actions (maven
> release
> > > and so on).
> > > Perform only vote_* steps.
> > >
> > > 3) Make sure you'll remove all tags, branches, and other RC artifacts
> > after
> > > check.
> > >
> > > 4) Mark this release as RC0 to make sure it will be clear to everybody
> > that
> > > it's a check.
> > >
> > >
> > > вт, 18 сент. 2018 г. в 13:24, Dmitriy Setrakyan <dsetrakyan@apache.org
> >:
> > >
> > > > If it is an Ignite release, then it has to pass through the vote. If
> > not,
> > > > then you can do the test without publishing or uploading the release.
> > > >
> > > > D.
> > > >
> > > > On Tue, Sep 18, 2018 at 1:18 PM Petr Ivanov <mr...@gmail.com>
> > wrote:
> > > >
> > > > > Ok.
> > > > >
> > > > > In case of TC questions — ask me.
> > > > >
> > > > >
> > > > >
> > > > > > On 18 Sep 2018, at 13:16, Nikolay Izhikov <ni...@apache.org>
> > wrote:
> > > > > >
> > > > > > Hello, Petr.
> > > > > >
> > > > > > I want to make ignite-2.7 branch today.
> > > > > > And execute release procedure based on this branch.
> > > > > >
> > > > > > However, ignite-2.7 branch will be copy of master until code
> freeze
> > > >
> > > > date.
> > > > > >
> > > > > > В Вт, 18/09/2018 в 13:13 +0300, Petr Ivanov пишет:
> > > > > > > Will it be just a test or there is already ignite-2.7 branch?
> > > > > > >
> > > > > > > Fabric removal related TC modifications are not ready yet, and
> > code is
> > > > >
> > > > > not in master.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > > On 18 Sep 2018, at 13:07, Nikolay Izhikov <
> nizhikov@apache.org
> > >
> > > >
> > > > wrote:
> > > > > > > >
> > > > > > > > Hello, Igniters.
> > > > > > > >
> > > > > > > > I want to start and release procedures and make an RC1 build.
> > > > > > > >
> > > > > > > > It has a 2 intention:
> > > > > > > >
> > > > > > > > 1. I want to walk through all release steps to make sure they
> > all
> > > > >
> > > > > works for me.
> > > > > > > > So I will be fully ready on release date.
> > > > > > > >
> > > > > > > > 2. We have updated some dependencies in 2.7 and we need to
> > make sure
> > > > >
> > > > > binary build is still workable.
> > > > > > > >
> > > > > > > > Any objections?
> > > > > > > >
> > > > > > > >
> > > > > > > > В Пт, 14/09/2018 в 18:52 +0300, Alexey Goncharuk пишет:
> > > > > > > > > We already have all the mechanics in place to work with
> > properties -
> > > > >
> > > > > we use
> > > > > > > > > ignite.build and ignite.revision from ignite.properties
> > which are
> > > > >
> > > > > adjusted
> > > > > > > > > during the build in the binary package.
> > > > > > > > >
> > > > > > > > > Should I create the ticket if there are no objections?
> > > > > > > > >
> > > > > > > > > пт, 14 сент. 2018 г. в 13:22, Ilya Kasnacheev <
> > > > >
> > > > > ilya.kasnacheev@gmail.com>:
> > > > > > > > >
> > > > > > > > > > Hello!
> > > > > > > > > >
> > > > > > > > > > So now there's an issue that this script makes source
> > change after
> > > > >
> > > > > every
> > > > > > > > > > build, show up in git status.
> > > > > > > > > >
> > > > > > > > > > What we could do to it:
> > > > > > > > > > - Commit the changes after the build, once. In hopes that
> > it won't
> > > > >
> > > > > change
> > > > > > > > > > very often. With benefit that we could do that right now,
> > before
> > > >
> > > > the
> > > > > code
> > > > > > > > > > freeze.
> > > > > > > > > > - Move these values to a properties file from both
> pom.xml
> > and
> > > > > > > > > > IgniteProvider.java. Any problems with this approach?
> > We'll just
> > > > >
> > > > > read them
> > > > > > > > > > from classpath properties file.
> > > > > > > > > > - Update the links in the file once and remove them from
> > build
> > > > >
> > > > > process. Why
> > > > > > > > > > were they added to build process in the first place - to
> > make them
> > > > > > > > > > configurable during build?
> > > > > > > > > >
> > > > > > > > > > Regards,
> > > > > > > > > > --
> > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > вт, 11 сент. 2018 г. в 5:53, Roman Shtykh <
> > rshtykh@yahoo.com>:
> > > > > > > > > >
> > > > > > > > > > > Ilya,
> > > > > > > > > > >
> > > > > > > > > > > The "latest" version is the default, and resolved by
> > > > > > > > > > > https://ignite.apache.org/latest which is used by our
> > web site
> > > > >
> > > > > when a
> > > > > > > > > > > user download the latest Ignite version. And I think
> > this is the
> > > > > > > > > >
> > > > > > > > > > authority
> > > > > > > > > > > to judge of the latest official release (pom.xml you
> > suggest can
> > > > >
> > > > > have
> > > > > > > > > > > SNAPSHOTs etc.).
> > > > > > > > > > > Also, as I explained during our review sessions,
> > > >
> > > > ignite-mesos-2.6.0
> > > > > is a
> > > > > > > > > > > driver and doesn't mean you need to have Ignite 2.6.0.
> > User can
> > > >
> > > > run
> > > > > any
> > > > > > > > > > > version of Ignite he/she specifies. By default, it's
> > "latest" but
> > > >
> > > > a
> > > > > user
> > > > > > > > > > > can specify any version needed, even from a non-archive
> > URL.
> > > > > > > > > > >
> > > > > > > > > > > In short, what we have now
> > > > > > > > > > > 1. mesos driver (ignite-mesos-x.x.x) will use "latest"
> > version by
> > > > >
> > > > > default
> > > > > > > > > > > -> it will try to resolve the latest officially
> releases
> > version
> > > >
> > > > of
> > > > > > > > > >
> > > > > > > > > > Apache
> > > > > > > > > > > Ignite, find the closest mirror and download Ignite in
> a
> > minute.
> > > >
> > > > If
> > > > > the
> > > > > > > > > > > version resolution fails, we fall back to the slow
> > apache archive
> > > > >
> > > > > (as you
> > > > > > > > > > > suggest; in my opinion we better fail-fast instead of
> > waiting for
> > > > >
> > > > > hours
> > > > > > > > > >
> > > > > > > > > > to
> > > > > > > > > > > download, so the user can choose another download
> option
> > (3))
> > > > > > > > > > > 2. If the user specifies the version explicitly, it
> goes
> > to the
> > > >
> > > > slow
> > > > > > > > > > > apache archive.
> > > > > > > > > > > 3. The user can put ignite zip file on his/her http
> > server and
> > > > >
> > > > > provide
> > > > > > > > > >
> > > > > > > > > > the
> > > > > > > > > > > URL as a parameter to the driver, if options 1 and 2
> > don't work.
> > > > > > > > > > >
> > > > > > > > > > > As you see, there are 3 options. And I just fix the 1st
> > one with
> > > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-9388 and
> > don't
> > > >
> > > > change
> > > > > the
> > > > > > > > > > > original logic (which I find reasonable) documented on
> > our site
> > > >
> > > > -- I
> > > > > > > > > >
> > > > > > > > > > don't
> > > > > > > > > > > see how it blocks anything.
> > > > > > > > > > >
> > > > > > > > > > > Roman Shtykh
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > On Monday, September 10, 2018, 6:16:15 p.m. GMT+9, Ilya
> > > >
> > > > Kasnacheev <
> > > > > > > > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Hello!
> > > > > > > > > > >
> > > > > > > > > > > There's still two issues with the submission.
> > > > > > > > > > >
> > > > > > > > > > > The first one is that we're downloading "latest"
> version
> > from
> > > > >
> > > > > preferred
> > > > > > > > > > > mirror but a specified version, such as "2.6", we're
> > also going to
> > > > > > > > > >
> > > > > > > > > > download
> > > > > > > > > > > from "slow" archive.apache.org/dist.
> > > > > > > > > > > That's a great limitation for this change, since most
> > real
> > > > >
> > > > > deployments of
> > > > > > > > > > > Apache Ignite will have their Ignite version pegged to
> a
> > specific
> > > > > > > > > >
> > > > > > > > > > release.
> > > > > > > > > > > But in this case there's no win in download speed.
> > > > > > > > > > > *In my opinion it is a blocker.*
> > > > > > > > > > >
> > > > > > > > > > > The second one is that we can't download anything when
> > we failed
> > > >
> > > > to
> > > > > > > > > > > resolve "latest". My idea is that we should try and
> > download last
> > > > >
> > > > > known
> > > > > > > > > > > version in this case, which can be pushed to source
> from
> > pom.xml,
> > > > >
> > > > > as we
> > > > > > > > > > > already do with URLs. So if you could not resolve
> > "latest" you
> > > >
> > > > will
> > > > > > > > > > > download 2.7.0.
> > > > > > > > > > >
> > > > > > > > > > > Buuut, maybe it's not necessary, maybe we should just
> > *discourage
> > > > > > > > > > > "latest"*, which is in my opinion almost always a bad
> > idea.
> > > > > > > > > > >
> > > > > > > > > > > WDYT?
> > > > > > > > > > >
> > > > > > > > > > > Regards,
> > > > > > > > > > > --
> > > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > вс, 9 сент. 2018 г. в 5:47, Roman Shtykh <
> > rshtykh@yahoo.com>:
> > > > > > > > > > >
> > > > > > > > > > > Hi Ilya,
> > > > > > > > > > >
> > > > > > > > > > > Sorry, missed that.
> > > > > > > > > > > Added now.
> > > > > > > > > > >
> > > > > > > > > > > --
> > > > > > > > > > > Roman Shtykh
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > On Thursday, September 6, 2018, 6:16:58 p.m. GMT+9,
> Ilya
> > > >
> > > > Kasnacheev
> > > > > <
> > > > > > > > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Hello!
> > > > > > > > > > >
> > > > > > > > > > > The last of my requests still standing is that we
> should
> > fall-back
> > > > >
> > > > > to
> > > > > > > > > > > single URL download in case of error with 'latest'
> > version.
> > > > >
> > > > > Everything
> > > > > > > > > >
> > > > > > > > > > else
> > > > > > > > > > > looks good to me.
> > > > > > > > > > >
> > > > > > > > > > > Can we do that? I'm really worried that Apache API will
> > go sour.
> > > > > > > > > > >
> > > > > > > > > > > Regards,
> > > > > > > > > > > --
> > > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > чт, 6 сент. 2018 г. в 8:56, Roman Shtykh <
> > rshtykh@yahoo.com>:
> > > > > > > > > > >
> > > > > > > > > > > Hi Ilya,
> > > > > > > > > > >
> > > > > > > > > > > Thanks again.
> > > > > > > > > > >
> > > > > > > > > > > 1) Done.
> > > > > > > > > > > 2) Used catch() for latest version.
> > > > > > > > > > >
> > > > > > > > > > > Please see my comments on github.
> > > > > > > > > > > --
> > > > > > > > > > > Roman Shtykh
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > On Wednesday, September 5, 2018, 11:30:10 p.m. GMT+9,
> > Ilya
> > > > >
> > > > > Kasnacheev <
> > > > > > > > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Hello!
> > > > > > > > > > >
> > > > > > > > > > > I've left a new wave of replies.
> > > > > > > > > > >
> > > > > > > > > > > Basically, 1) let's keep DOWNLOAD_URL_PATTERN string
> > value inlined
> > > > >
> > > > > so
> > > > > > > > > > > that it will work even if build process is broken
> (would
> > be useful
> > > > >
> > > > > for
> > > > > > > > > >
> > > > > > > > > > e.g.
> > > > > > > > > > > developing out of IDE)
> > > > > > > > > > > And also I urge you to catch() around new fragile
> Apache
> > JSON API
> > > > > > > > > > > resolving, and download the 'current' version instead,
> > as defined
> > > >
> > > > by
> > > > > > > > > > > ignite-mesos version.
> > > > > > > > > > >
> > > > > > > > > > > This is because this module is not under continuouos
> > scrutiny so
> > > > >
> > > > > extra
> > > > > > > > > > > care should be applied.
> > > > > > > > > > > --
> > > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > вт, 4 сент. 2018 г. в 13:42, Roman Shtykh <
> > rshtykh@yahoo.com>:
> > > > > > > > > > >
> > > > > > > > > > > Thanks, Ilya!
> > > > > > > > > > > I will check your comments, and discuss it at JIRA.
> > > > > > > > > > >
> > > > > > > > > > > --
> > > > > > > > > > > Roman Shtykh
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > On Tuesday, September 4, 2018, 7:17:53 p.m. GMT+9, Ilya
> > > >
> > > > Kasnacheev <
> > > > > > > > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Hello!
> > > > > > > > > > >
> > > > > > > > > > > IGNITE-9408 <
> > https://issues.apache.org/jira/browse/IGNITE-9408>
> > > > >
> > > > > looks
> > > > > > > > > > > good to me and may be merged right away.
> > > > > > > > > > >
> > > > > > > > > > > IGNITE-9388 <
> > https://issues.apache.org/jira/browse/IGNITE-9388>
> > > > >
> > > > > needs
> > > > > > > > > > > more work in my opinion, I have commented the PR. I
> also
> > advice
> > > > >
> > > > > having
> > > > > > > > > >
> > > > > > > > > > test
> > > > > > > > > > > for this functionality.
> > > > > > > > > > >
> > > > > > > > > > > Regards,
> > > > > > > > > > > --
> > > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > вт, 4 сент. 2018 г. в 6:52, Roman Shtykh
> > > >
> > > > <rshtykh@yahoo.com.invalid
> > > > > > :
> > > > > > > > > > >
> > > > > > > > > > > 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
> > > > > > > > > >
> > > > > > > > > > <
> > > > > > > > > > > daradurvs@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 <
> > > > >
> > > > > nizhikov@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.
> > > > > > > > > > >
> > > > >
> > > > >
>
Re: Apache Ignite 2.7 release
Posted by Paul Anderson <de...@gmail.com>.
Hi, may I ask for IGNITE-9298 to be included in 2.7 pls
On Tue, Sep 18, 2018 at 1:03 PM Nikolay Izhikov <ni...@apache.org> wrote:
> Hello, folks.
>
> Thanks for the comments.
>
> I will follow them.
>
> В Вт, 18/09/2018 в 13:31 +0300, Anton Vinogradov пишет:
> > Nikolay,
> >
> > 1) *Do not* create ignite-2.7 branch until we're not started preparation
> to
> > real 2.7.
> > Use some temporary branch for this check instead, eg.
> > ignite-2.7-release-test
> >
> > 2) Please make sure you'll not cause real release actions (maven release
> > and so on).
> > Perform only vote_* steps.
> >
> > 3) Make sure you'll remove all tags, branches, and other RC artifacts
> after
> > check.
> >
> > 4) Mark this release as RC0 to make sure it will be clear to everybody
> that
> > it's a check.
> >
> >
> > вт, 18 сент. 2018 г. в 13:24, Dmitriy Setrakyan <ds...@apache.org>:
> >
> > > If it is an Ignite release, then it has to pass through the vote. If
> not,
> > > then you can do the test without publishing or uploading the release.
> > >
> > > D.
> > >
> > > On Tue, Sep 18, 2018 at 1:18 PM Petr Ivanov <mr...@gmail.com>
> wrote:
> > >
> > > > Ok.
> > > >
> > > > In case of TC questions — ask me.
> > > >
> > > >
> > > >
> > > > > On 18 Sep 2018, at 13:16, Nikolay Izhikov <ni...@apache.org>
> wrote:
> > > > >
> > > > > Hello, Petr.
> > > > >
> > > > > I want to make ignite-2.7 branch today.
> > > > > And execute release procedure based on this branch.
> > > > >
> > > > > However, ignite-2.7 branch will be copy of master until code freeze
> > >
> > > date.
> > > > >
> > > > > В Вт, 18/09/2018 в 13:13 +0300, Petr Ivanov пишет:
> > > > > > Will it be just a test or there is already ignite-2.7 branch?
> > > > > >
> > > > > > Fabric removal related TC modifications are not ready yet, and
> code is
> > > >
> > > > not in master.
> > > > > >
> > > > > >
> > > > > >
> > > > > > > On 18 Sep 2018, at 13:07, Nikolay Izhikov <nizhikov@apache.org
> >
> > >
> > > wrote:
> > > > > > >
> > > > > > > Hello, Igniters.
> > > > > > >
> > > > > > > I want to start and release procedures and make an RC1 build.
> > > > > > >
> > > > > > > It has a 2 intention:
> > > > > > >
> > > > > > > 1. I want to walk through all release steps to make sure they
> all
> > > >
> > > > works for me.
> > > > > > > So I will be fully ready on release date.
> > > > > > >
> > > > > > > 2. We have updated some dependencies in 2.7 and we need to
> make sure
> > > >
> > > > binary build is still workable.
> > > > > > >
> > > > > > > Any objections?
> > > > > > >
> > > > > > >
> > > > > > > В Пт, 14/09/2018 в 18:52 +0300, Alexey Goncharuk пишет:
> > > > > > > > We already have all the mechanics in place to work with
> properties -
> > > >
> > > > we use
> > > > > > > > ignite.build and ignite.revision from ignite.properties
> which are
> > > >
> > > > adjusted
> > > > > > > > during the build in the binary package.
> > > > > > > >
> > > > > > > > Should I create the ticket if there are no objections?
> > > > > > > >
> > > > > > > > пт, 14 сент. 2018 г. в 13:22, Ilya Kasnacheev <
> > > >
> > > > ilya.kasnacheev@gmail.com>:
> > > > > > > >
> > > > > > > > > Hello!
> > > > > > > > >
> > > > > > > > > So now there's an issue that this script makes source
> change after
> > > >
> > > > every
> > > > > > > > > build, show up in git status.
> > > > > > > > >
> > > > > > > > > What we could do to it:
> > > > > > > > > - Commit the changes after the build, once. In hopes that
> it won't
> > > >
> > > > change
> > > > > > > > > very often. With benefit that we could do that right now,
> before
> > >
> > > the
> > > > code
> > > > > > > > > freeze.
> > > > > > > > > - Move these values to a properties file from both pom.xml
> and
> > > > > > > > > IgniteProvider.java. Any problems with this approach?
> We'll just
> > > >
> > > > read them
> > > > > > > > > from classpath properties file.
> > > > > > > > > - Update the links in the file once and remove them from
> build
> > > >
> > > > process. Why
> > > > > > > > > were they added to build process in the first place - to
> make them
> > > > > > > > > configurable during build?
> > > > > > > > >
> > > > > > > > > Regards,
> > > > > > > > > --
> > > > > > > > > Ilya Kasnacheev
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > вт, 11 сент. 2018 г. в 5:53, Roman Shtykh <
> rshtykh@yahoo.com>:
> > > > > > > > >
> > > > > > > > > > Ilya,
> > > > > > > > > >
> > > > > > > > > > The "latest" version is the default, and resolved by
> > > > > > > > > > https://ignite.apache.org/latest which is used by our
> web site
> > > >
> > > > when a
> > > > > > > > > > user download the latest Ignite version. And I think
> this is the
> > > > > > > > >
> > > > > > > > > authority
> > > > > > > > > > to judge of the latest official release (pom.xml you
> suggest can
> > > >
> > > > have
> > > > > > > > > > SNAPSHOTs etc.).
> > > > > > > > > > Also, as I explained during our review sessions,
> > >
> > > ignite-mesos-2.6.0
> > > > is a
> > > > > > > > > > driver and doesn't mean you need to have Ignite 2.6.0.
> User can
> > >
> > > run
> > > > any
> > > > > > > > > > version of Ignite he/she specifies. By default, it's
> "latest" but
> > >
> > > a
> > > > user
> > > > > > > > > > can specify any version needed, even from a non-archive
> URL.
> > > > > > > > > >
> > > > > > > > > > In short, what we have now
> > > > > > > > > > 1. mesos driver (ignite-mesos-x.x.x) will use "latest"
> version by
> > > >
> > > > default
> > > > > > > > > > -> it will try to resolve the latest officially releases
> version
> > >
> > > of
> > > > > > > > >
> > > > > > > > > Apache
> > > > > > > > > > Ignite, find the closest mirror and download Ignite in a
> minute.
> > >
> > > If
> > > > the
> > > > > > > > > > version resolution fails, we fall back to the slow
> apache archive
> > > >
> > > > (as you
> > > > > > > > > > suggest; in my opinion we better fail-fast instead of
> waiting for
> > > >
> > > > hours
> > > > > > > > >
> > > > > > > > > to
> > > > > > > > > > download, so the user can choose another download option
> (3))
> > > > > > > > > > 2. If the user specifies the version explicitly, it goes
> to the
> > >
> > > slow
> > > > > > > > > > apache archive.
> > > > > > > > > > 3. The user can put ignite zip file on his/her http
> server and
> > > >
> > > > provide
> > > > > > > > >
> > > > > > > > > the
> > > > > > > > > > URL as a parameter to the driver, if options 1 and 2
> don't work.
> > > > > > > > > >
> > > > > > > > > > As you see, there are 3 options. And I just fix the 1st
> one with
> > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-9388 and
> don't
> > >
> > > change
> > > > the
> > > > > > > > > > original logic (which I find reasonable) documented on
> our site
> > >
> > > -- I
> > > > > > > > >
> > > > > > > > > don't
> > > > > > > > > > see how it blocks anything.
> > > > > > > > > >
> > > > > > > > > > Roman Shtykh
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Monday, September 10, 2018, 6:16:15 p.m. GMT+9, Ilya
> > >
> > > Kasnacheev <
> > > > > > > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Hello!
> > > > > > > > > >
> > > > > > > > > > There's still two issues with the submission.
> > > > > > > > > >
> > > > > > > > > > The first one is that we're downloading "latest" version
> from
> > > >
> > > > preferred
> > > > > > > > > > mirror but a specified version, such as "2.6", we're
> also going to
> > > > > > > > >
> > > > > > > > > download
> > > > > > > > > > from "slow" archive.apache.org/dist.
> > > > > > > > > > That's a great limitation for this change, since most
> real
> > > >
> > > > deployments of
> > > > > > > > > > Apache Ignite will have their Ignite version pegged to a
> specific
> > > > > > > > >
> > > > > > > > > release.
> > > > > > > > > > But in this case there's no win in download speed.
> > > > > > > > > > *In my opinion it is a blocker.*
> > > > > > > > > >
> > > > > > > > > > The second one is that we can't download anything when
> we failed
> > >
> > > to
> > > > > > > > > > resolve "latest". My idea is that we should try and
> download last
> > > >
> > > > known
> > > > > > > > > > version in this case, which can be pushed to source from
> pom.xml,
> > > >
> > > > as we
> > > > > > > > > > already do with URLs. So if you could not resolve
> "latest" you
> > >
> > > will
> > > > > > > > > > download 2.7.0.
> > > > > > > > > >
> > > > > > > > > > Buuut, maybe it's not necessary, maybe we should just
> *discourage
> > > > > > > > > > "latest"*, which is in my opinion almost always a bad
> idea.
> > > > > > > > > >
> > > > > > > > > > WDYT?
> > > > > > > > > >
> > > > > > > > > > Regards,
> > > > > > > > > > --
> > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > вс, 9 сент. 2018 г. в 5:47, Roman Shtykh <
> rshtykh@yahoo.com>:
> > > > > > > > > >
> > > > > > > > > > Hi Ilya,
> > > > > > > > > >
> > > > > > > > > > Sorry, missed that.
> > > > > > > > > > Added now.
> > > > > > > > > >
> > > > > > > > > > --
> > > > > > > > > > Roman Shtykh
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Thursday, September 6, 2018, 6:16:58 p.m. GMT+9, Ilya
> > >
> > > Kasnacheev
> > > > <
> > > > > > > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Hello!
> > > > > > > > > >
> > > > > > > > > > The last of my requests still standing is that we should
> fall-back
> > > >
> > > > to
> > > > > > > > > > single URL download in case of error with 'latest'
> version.
> > > >
> > > > Everything
> > > > > > > > >
> > > > > > > > > else
> > > > > > > > > > looks good to me.
> > > > > > > > > >
> > > > > > > > > > Can we do that? I'm really worried that Apache API will
> go sour.
> > > > > > > > > >
> > > > > > > > > > Regards,
> > > > > > > > > > --
> > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > чт, 6 сент. 2018 г. в 8:56, Roman Shtykh <
> rshtykh@yahoo.com>:
> > > > > > > > > >
> > > > > > > > > > Hi Ilya,
> > > > > > > > > >
> > > > > > > > > > Thanks again.
> > > > > > > > > >
> > > > > > > > > > 1) Done.
> > > > > > > > > > 2) Used catch() for latest version.
> > > > > > > > > >
> > > > > > > > > > Please see my comments on github.
> > > > > > > > > > --
> > > > > > > > > > Roman Shtykh
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Wednesday, September 5, 2018, 11:30:10 p.m. GMT+9,
> Ilya
> > > >
> > > > Kasnacheev <
> > > > > > > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Hello!
> > > > > > > > > >
> > > > > > > > > > I've left a new wave of replies.
> > > > > > > > > >
> > > > > > > > > > Basically, 1) let's keep DOWNLOAD_URL_PATTERN string
> value inlined
> > > >
> > > > so
> > > > > > > > > > that it will work even if build process is broken (would
> be useful
> > > >
> > > > for
> > > > > > > > >
> > > > > > > > > e.g.
> > > > > > > > > > developing out of IDE)
> > > > > > > > > > And also I urge you to catch() around new fragile Apache
> JSON API
> > > > > > > > > > resolving, and download the 'current' version instead,
> as defined
> > >
> > > by
> > > > > > > > > > ignite-mesos version.
> > > > > > > > > >
> > > > > > > > > > This is because this module is not under continuouos
> scrutiny so
> > > >
> > > > extra
> > > > > > > > > > care should be applied.
> > > > > > > > > > --
> > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > вт, 4 сент. 2018 г. в 13:42, Roman Shtykh <
> rshtykh@yahoo.com>:
> > > > > > > > > >
> > > > > > > > > > Thanks, Ilya!
> > > > > > > > > > I will check your comments, and discuss it at JIRA.
> > > > > > > > > >
> > > > > > > > > > --
> > > > > > > > > > Roman Shtykh
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Tuesday, September 4, 2018, 7:17:53 p.m. GMT+9, Ilya
> > >
> > > Kasnacheev <
> > > > > > > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Hello!
> > > > > > > > > >
> > > > > > > > > > IGNITE-9408 <
> https://issues.apache.org/jira/browse/IGNITE-9408>
> > > >
> > > > looks
> > > > > > > > > > good to me and may be merged right away.
> > > > > > > > > >
> > > > > > > > > > IGNITE-9388 <
> https://issues.apache.org/jira/browse/IGNITE-9388>
> > > >
> > > > needs
> > > > > > > > > > more work in my opinion, I have commented the PR. I also
> advice
> > > >
> > > > having
> > > > > > > > >
> > > > > > > > > test
> > > > > > > > > > for this functionality.
> > > > > > > > > >
> > > > > > > > > > Regards,
> > > > > > > > > > --
> > > > > > > > > > Ilya Kasnacheev
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > вт, 4 сент. 2018 г. в 6:52, Roman Shtykh
> > >
> > > <rshtykh@yahoo.com.invalid
> > > > > :
> > > > > > > > > >
> > > > > > > > > > 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
> > > > > > > > >
> > > > > > > > > <
> > > > > > > > > > daradurvs@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 <
> > > >
> > > > nizhikov@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.
> > > > > > > > > >
> > > >
> > > >
Re: Apache Ignite 2.7 release
Posted by Nikolay Izhikov <ni...@apache.org>.
Hello, folks.
Thanks for the comments.
I will follow them.
В Вт, 18/09/2018 в 13:31 +0300, Anton Vinogradov пишет:
> Nikolay,
>
> 1) *Do not* create ignite-2.7 branch until we're not started preparation to
> real 2.7.
> Use some temporary branch for this check instead, eg.
> ignite-2.7-release-test
>
> 2) Please make sure you'll not cause real release actions (maven release
> and so on).
> Perform only vote_* steps.
>
> 3) Make sure you'll remove all tags, branches, and other RC artifacts after
> check.
>
> 4) Mark this release as RC0 to make sure it will be clear to everybody that
> it's a check.
>
>
> вт, 18 сент. 2018 г. в 13:24, Dmitriy Setrakyan <ds...@apache.org>:
>
> > If it is an Ignite release, then it has to pass through the vote. If not,
> > then you can do the test without publishing or uploading the release.
> >
> > D.
> >
> > On Tue, Sep 18, 2018 at 1:18 PM Petr Ivanov <mr...@gmail.com> wrote:
> >
> > > Ok.
> > >
> > > In case of TC questions — ask me.
> > >
> > >
> > >
> > > > On 18 Sep 2018, at 13:16, Nikolay Izhikov <ni...@apache.org> wrote:
> > > >
> > > > Hello, Petr.
> > > >
> > > > I want to make ignite-2.7 branch today.
> > > > And execute release procedure based on this branch.
> > > >
> > > > However, ignite-2.7 branch will be copy of master until code freeze
> >
> > date.
> > > >
> > > > В Вт, 18/09/2018 в 13:13 +0300, Petr Ivanov пишет:
> > > > > Will it be just a test or there is already ignite-2.7 branch?
> > > > >
> > > > > Fabric removal related TC modifications are not ready yet, and code is
> > >
> > > not in master.
> > > > >
> > > > >
> > > > >
> > > > > > On 18 Sep 2018, at 13:07, Nikolay Izhikov <ni...@apache.org>
> >
> > wrote:
> > > > > >
> > > > > > Hello, Igniters.
> > > > > >
> > > > > > I want to start and release procedures and make an RC1 build.
> > > > > >
> > > > > > It has a 2 intention:
> > > > > >
> > > > > > 1. I want to walk through all release steps to make sure they all
> > >
> > > works for me.
> > > > > > So I will be fully ready on release date.
> > > > > >
> > > > > > 2. We have updated some dependencies in 2.7 and we need to make sure
> > >
> > > binary build is still workable.
> > > > > >
> > > > > > Any objections?
> > > > > >
> > > > > >
> > > > > > В Пт, 14/09/2018 в 18:52 +0300, Alexey Goncharuk пишет:
> > > > > > > We already have all the mechanics in place to work with properties -
> > >
> > > we use
> > > > > > > ignite.build and ignite.revision from ignite.properties which are
> > >
> > > adjusted
> > > > > > > during the build in the binary package.
> > > > > > >
> > > > > > > Should I create the ticket if there are no objections?
> > > > > > >
> > > > > > > пт, 14 сент. 2018 г. в 13:22, Ilya Kasnacheev <
> > >
> > > ilya.kasnacheev@gmail.com>:
> > > > > > >
> > > > > > > > Hello!
> > > > > > > >
> > > > > > > > So now there's an issue that this script makes source change after
> > >
> > > every
> > > > > > > > build, show up in git status.
> > > > > > > >
> > > > > > > > What we could do to it:
> > > > > > > > - Commit the changes after the build, once. In hopes that it won't
> > >
> > > change
> > > > > > > > very often. With benefit that we could do that right now, before
> >
> > the
> > > code
> > > > > > > > freeze.
> > > > > > > > - Move these values to a properties file from both pom.xml and
> > > > > > > > IgniteProvider.java. Any problems with this approach? We'll just
> > >
> > > read them
> > > > > > > > from classpath properties file.
> > > > > > > > - Update the links in the file once and remove them from build
> > >
> > > process. Why
> > > > > > > > were they added to build process in the first place - to make them
> > > > > > > > configurable during build?
> > > > > > > >
> > > > > > > > Regards,
> > > > > > > > --
> > > > > > > > Ilya Kasnacheev
> > > > > > > >
> > > > > > > >
> > > > > > > > вт, 11 сент. 2018 г. в 5:53, Roman Shtykh <rs...@yahoo.com>:
> > > > > > > >
> > > > > > > > > Ilya,
> > > > > > > > >
> > > > > > > > > The "latest" version is the default, and resolved by
> > > > > > > > > https://ignite.apache.org/latest which is used by our web site
> > >
> > > when a
> > > > > > > > > user download the latest Ignite version. And I think this is the
> > > > > > > >
> > > > > > > > authority
> > > > > > > > > to judge of the latest official release (pom.xml you suggest can
> > >
> > > have
> > > > > > > > > SNAPSHOTs etc.).
> > > > > > > > > Also, as I explained during our review sessions,
> >
> > ignite-mesos-2.6.0
> > > is a
> > > > > > > > > driver and doesn't mean you need to have Ignite 2.6.0. User can
> >
> > run
> > > any
> > > > > > > > > version of Ignite he/she specifies. By default, it's "latest" but
> >
> > a
> > > user
> > > > > > > > > can specify any version needed, even from a non-archive URL.
> > > > > > > > >
> > > > > > > > > In short, what we have now
> > > > > > > > > 1. mesos driver (ignite-mesos-x.x.x) will use "latest" version by
> > >
> > > default
> > > > > > > > > -> it will try to resolve the latest officially releases version
> >
> > of
> > > > > > > >
> > > > > > > > Apache
> > > > > > > > > Ignite, find the closest mirror and download Ignite in a minute.
> >
> > If
> > > the
> > > > > > > > > version resolution fails, we fall back to the slow apache archive
> > >
> > > (as you
> > > > > > > > > suggest; in my opinion we better fail-fast instead of waiting for
> > >
> > > hours
> > > > > > > >
> > > > > > > > to
> > > > > > > > > download, so the user can choose another download option (3))
> > > > > > > > > 2. If the user specifies the version explicitly, it goes to the
> >
> > slow
> > > > > > > > > apache archive.
> > > > > > > > > 3. The user can put ignite zip file on his/her http server and
> > >
> > > provide
> > > > > > > >
> > > > > > > > the
> > > > > > > > > URL as a parameter to the driver, if options 1 and 2 don't work.
> > > > > > > > >
> > > > > > > > > As you see, there are 3 options. And I just fix the 1st one with
> > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-9388 and don't
> >
> > change
> > > the
> > > > > > > > > original logic (which I find reasonable) documented on our site
> >
> > -- I
> > > > > > > >
> > > > > > > > don't
> > > > > > > > > see how it blocks anything.
> > > > > > > > >
> > > > > > > > > Roman Shtykh
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Monday, September 10, 2018, 6:16:15 p.m. GMT+9, Ilya
> >
> > Kasnacheev <
> > > > > > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Hello!
> > > > > > > > >
> > > > > > > > > There's still two issues with the submission.
> > > > > > > > >
> > > > > > > > > The first one is that we're downloading "latest" version from
> > >
> > > preferred
> > > > > > > > > mirror but a specified version, such as "2.6", we're also going to
> > > > > > > >
> > > > > > > > download
> > > > > > > > > from "slow" archive.apache.org/dist.
> > > > > > > > > That's a great limitation for this change, since most real
> > >
> > > deployments of
> > > > > > > > > Apache Ignite will have their Ignite version pegged to a specific
> > > > > > > >
> > > > > > > > release.
> > > > > > > > > But in this case there's no win in download speed.
> > > > > > > > > *In my opinion it is a blocker.*
> > > > > > > > >
> > > > > > > > > The second one is that we can't download anything when we failed
> >
> > to
> > > > > > > > > resolve "latest". My idea is that we should try and download last
> > >
> > > known
> > > > > > > > > version in this case, which can be pushed to source from pom.xml,
> > >
> > > as we
> > > > > > > > > already do with URLs. So if you could not resolve "latest" you
> >
> > will
> > > > > > > > > download 2.7.0.
> > > > > > > > >
> > > > > > > > > Buuut, maybe it's not necessary, maybe we should just *discourage
> > > > > > > > > "latest"*, which is in my opinion almost always a bad idea.
> > > > > > > > >
> > > > > > > > > WDYT?
> > > > > > > > >
> > > > > > > > > Regards,
> > > > > > > > > --
> > > > > > > > > Ilya Kasnacheev
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > вс, 9 сент. 2018 г. в 5:47, Roman Shtykh <rs...@yahoo.com>:
> > > > > > > > >
> > > > > > > > > Hi Ilya,
> > > > > > > > >
> > > > > > > > > Sorry, missed that.
> > > > > > > > > Added now.
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > Roman Shtykh
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Thursday, September 6, 2018, 6:16:58 p.m. GMT+9, Ilya
> >
> > Kasnacheev
> > > <
> > > > > > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Hello!
> > > > > > > > >
> > > > > > > > > The last of my requests still standing is that we should fall-back
> > >
> > > to
> > > > > > > > > single URL download in case of error with 'latest' version.
> > >
> > > Everything
> > > > > > > >
> > > > > > > > else
> > > > > > > > > looks good to me.
> > > > > > > > >
> > > > > > > > > Can we do that? I'm really worried that Apache API will go sour.
> > > > > > > > >
> > > > > > > > > Regards,
> > > > > > > > > --
> > > > > > > > > Ilya Kasnacheev
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > чт, 6 сент. 2018 г. в 8:56, Roman Shtykh <rs...@yahoo.com>:
> > > > > > > > >
> > > > > > > > > Hi Ilya,
> > > > > > > > >
> > > > > > > > > Thanks again.
> > > > > > > > >
> > > > > > > > > 1) Done.
> > > > > > > > > 2) Used catch() for latest version.
> > > > > > > > >
> > > > > > > > > Please see my comments on github.
> > > > > > > > > --
> > > > > > > > > Roman Shtykh
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Wednesday, September 5, 2018, 11:30:10 p.m. GMT+9, Ilya
> > >
> > > Kasnacheev <
> > > > > > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Hello!
> > > > > > > > >
> > > > > > > > > I've left a new wave of replies.
> > > > > > > > >
> > > > > > > > > Basically, 1) let's keep DOWNLOAD_URL_PATTERN string value inlined
> > >
> > > so
> > > > > > > > > that it will work even if build process is broken (would be useful
> > >
> > > for
> > > > > > > >
> > > > > > > > e.g.
> > > > > > > > > developing out of IDE)
> > > > > > > > > And also I urge you to catch() around new fragile Apache JSON API
> > > > > > > > > resolving, and download the 'current' version instead, as defined
> >
> > by
> > > > > > > > > ignite-mesos version.
> > > > > > > > >
> > > > > > > > > This is because this module is not under continuouos scrutiny so
> > >
> > > extra
> > > > > > > > > care should be applied.
> > > > > > > > > --
> > > > > > > > > Ilya Kasnacheev
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > вт, 4 сент. 2018 г. в 13:42, Roman Shtykh <rs...@yahoo.com>:
> > > > > > > > >
> > > > > > > > > Thanks, Ilya!
> > > > > > > > > I will check your comments, and discuss it at JIRA.
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > Roman Shtykh
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Tuesday, September 4, 2018, 7:17:53 p.m. GMT+9, Ilya
> >
> > Kasnacheev <
> > > > > > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Hello!
> > > > > > > > >
> > > > > > > > > IGNITE-9408 <https://issues.apache.org/jira/browse/IGNITE-9408>
> > >
> > > looks
> > > > > > > > > good to me and may be merged right away.
> > > > > > > > >
> > > > > > > > > IGNITE-9388 <https://issues.apache.org/jira/browse/IGNITE-9388>
> > >
> > > needs
> > > > > > > > > more work in my opinion, I have commented the PR. I also advice
> > >
> > > having
> > > > > > > >
> > > > > > > > test
> > > > > > > > > for this functionality.
> > > > > > > > >
> > > > > > > > > Regards,
> > > > > > > > > --
> > > > > > > > > Ilya Kasnacheev
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > вт, 4 сент. 2018 г. в 6:52, Roman Shtykh
> >
> > <rshtykh@yahoo.com.invalid
> > > > :
> > > > > > > > >
> > > > > > > > > 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
> > > > > > > >
> > > > > > > > <
> > > > > > > > > daradurvs@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 <
> > >
> > > nizhikov@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.
> > > > > > > > >
> > >
> > >
Re: Apache Ignite 2.7 release
Posted by Anton Vinogradov <av...@apache.org>.
Nikolay,
1) *Do not* create ignite-2.7 branch until we're not started preparation to
real 2.7.
Use some temporary branch for this check instead, eg.
ignite-2.7-release-test
2) Please make sure you'll not cause real release actions (maven release
and so on).
Perform only vote_* steps.
3) Make sure you'll remove all tags, branches, and other RC artifacts after
check.
4) Mark this release as RC0 to make sure it will be clear to everybody that
it's a check.
вт, 18 сент. 2018 г. в 13:24, Dmitriy Setrakyan <ds...@apache.org>:
> If it is an Ignite release, then it has to pass through the vote. If not,
> then you can do the test without publishing or uploading the release.
>
> D.
>
> On Tue, Sep 18, 2018 at 1:18 PM Petr Ivanov <mr...@gmail.com> wrote:
>
> > Ok.
> >
> > In case of TC questions — ask me.
> >
> >
> >
> > > On 18 Sep 2018, at 13:16, Nikolay Izhikov <ni...@apache.org> wrote:
> > >
> > > Hello, Petr.
> > >
> > > I want to make ignite-2.7 branch today.
> > > And execute release procedure based on this branch.
> > >
> > > However, ignite-2.7 branch will be copy of master until code freeze
> date.
> > >
> > > В Вт, 18/09/2018 в 13:13 +0300, Petr Ivanov пишет:
> > >> Will it be just a test or there is already ignite-2.7 branch?
> > >>
> > >> Fabric removal related TC modifications are not ready yet, and code is
> > not in master.
> > >>
> > >>
> > >>
> > >>> On 18 Sep 2018, at 13:07, Nikolay Izhikov <ni...@apache.org>
> wrote:
> > >>>
> > >>> Hello, Igniters.
> > >>>
> > >>> I want to start and release procedures and make an RC1 build.
> > >>>
> > >>> It has a 2 intention:
> > >>>
> > >>> 1. I want to walk through all release steps to make sure they all
> > works for me.
> > >>> So I will be fully ready on release date.
> > >>>
> > >>> 2. We have updated some dependencies in 2.7 and we need to make sure
> > binary build is still workable.
> > >>>
> > >>> Any objections?
> > >>>
> > >>>
> > >>> В Пт, 14/09/2018 в 18:52 +0300, Alexey Goncharuk пишет:
> > >>>> We already have all the mechanics in place to work with properties -
> > we use
> > >>>> ignite.build and ignite.revision from ignite.properties which are
> > adjusted
> > >>>> during the build in the binary package.
> > >>>>
> > >>>> Should I create the ticket if there are no objections?
> > >>>>
> > >>>> пт, 14 сент. 2018 г. в 13:22, Ilya Kasnacheev <
> > ilya.kasnacheev@gmail.com>:
> > >>>>
> > >>>>> Hello!
> > >>>>>
> > >>>>> So now there's an issue that this script makes source change after
> > every
> > >>>>> build, show up in git status.
> > >>>>>
> > >>>>> What we could do to it:
> > >>>>> - Commit the changes after the build, once. In hopes that it won't
> > change
> > >>>>> very often. With benefit that we could do that right now, before
> the
> > code
> > >>>>> freeze.
> > >>>>> - Move these values to a properties file from both pom.xml and
> > >>>>> IgniteProvider.java. Any problems with this approach? We'll just
> > read them
> > >>>>> from classpath properties file.
> > >>>>> - Update the links in the file once and remove them from build
> > process. Why
> > >>>>> were they added to build process in the first place - to make them
> > >>>>> configurable during build?
> > >>>>>
> > >>>>> Regards,
> > >>>>> --
> > >>>>> Ilya Kasnacheev
> > >>>>>
> > >>>>>
> > >>>>> вт, 11 сент. 2018 г. в 5:53, Roman Shtykh <rs...@yahoo.com>:
> > >>>>>
> > >>>>>> Ilya,
> > >>>>>>
> > >>>>>> The "latest" version is the default, and resolved by
> > >>>>>> https://ignite.apache.org/latest which is used by our web site
> > when a
> > >>>>>> user download the latest Ignite version. And I think this is the
> > >>>>>
> > >>>>> authority
> > >>>>>> to judge of the latest official release (pom.xml you suggest can
> > have
> > >>>>>> SNAPSHOTs etc.).
> > >>>>>> Also, as I explained during our review sessions,
> ignite-mesos-2.6.0
> > is a
> > >>>>>> driver and doesn't mean you need to have Ignite 2.6.0. User can
> run
> > any
> > >>>>>> version of Ignite he/she specifies. By default, it's "latest" but
> a
> > user
> > >>>>>> can specify any version needed, even from a non-archive URL.
> > >>>>>>
> > >>>>>> In short, what we have now
> > >>>>>> 1. mesos driver (ignite-mesos-x.x.x) will use "latest" version by
> > default
> > >>>>>> -> it will try to resolve the latest officially releases version
> of
> > >>>>>
> > >>>>> Apache
> > >>>>>> Ignite, find the closest mirror and download Ignite in a minute.
> If
> > the
> > >>>>>> version resolution fails, we fall back to the slow apache archive
> > (as you
> > >>>>>> suggest; in my opinion we better fail-fast instead of waiting for
> > hours
> > >>>>>
> > >>>>> to
> > >>>>>> download, so the user can choose another download option (3))
> > >>>>>> 2. If the user specifies the version explicitly, it goes to the
> slow
> > >>>>>> apache archive.
> > >>>>>> 3. The user can put ignite zip file on his/her http server and
> > provide
> > >>>>>
> > >>>>> the
> > >>>>>> URL as a parameter to the driver, if options 1 and 2 don't work.
> > >>>>>>
> > >>>>>> As you see, there are 3 options. And I just fix the 1st one with
> > >>>>>> https://issues.apache.org/jira/browse/IGNITE-9388 and don't
> change
> > the
> > >>>>>> original logic (which I find reasonable) documented on our site
> -- I
> > >>>>>
> > >>>>> don't
> > >>>>>> see how it blocks anything.
> > >>>>>>
> > >>>>>> Roman Shtykh
> > >>>>>>
> > >>>>>>
> > >>>>>> On Monday, September 10, 2018, 6:16:15 p.m. GMT+9, Ilya
> Kasnacheev <
> > >>>>>> ilya.kasnacheev@gmail.com> wrote:
> > >>>>>>
> > >>>>>>
> > >>>>>> Hello!
> > >>>>>>
> > >>>>>> There's still two issues with the submission.
> > >>>>>>
> > >>>>>> The first one is that we're downloading "latest" version from
> > preferred
> > >>>>>> mirror but a specified version, such as "2.6", we're also going to
> > >>>>>
> > >>>>> download
> > >>>>>> from "slow" archive.apache.org/dist.
> > >>>>>> That's a great limitation for this change, since most real
> > deployments of
> > >>>>>> Apache Ignite will have their Ignite version pegged to a specific
> > >>>>>
> > >>>>> release.
> > >>>>>> But in this case there's no win in download speed.
> > >>>>>> *In my opinion it is a blocker.*
> > >>>>>>
> > >>>>>> The second one is that we can't download anything when we failed
> to
> > >>>>>> resolve "latest". My idea is that we should try and download last
> > known
> > >>>>>> version in this case, which can be pushed to source from pom.xml,
> > as we
> > >>>>>> already do with URLs. So if you could not resolve "latest" you
> will
> > >>>>>> download 2.7.0.
> > >>>>>>
> > >>>>>> Buuut, maybe it's not necessary, maybe we should just *discourage
> > >>>>>> "latest"*, which is in my opinion almost always a bad idea.
> > >>>>>>
> > >>>>>> WDYT?
> > >>>>>>
> > >>>>>> Regards,
> > >>>>>> --
> > >>>>>> Ilya Kasnacheev
> > >>>>>>
> > >>>>>>
> > >>>>>> вс, 9 сент. 2018 г. в 5:47, Roman Shtykh <rs...@yahoo.com>:
> > >>>>>>
> > >>>>>> Hi Ilya,
> > >>>>>>
> > >>>>>> Sorry, missed that.
> > >>>>>> Added now.
> > >>>>>>
> > >>>>>> --
> > >>>>>> Roman Shtykh
> > >>>>>>
> > >>>>>>
> > >>>>>> On Thursday, September 6, 2018, 6:16:58 p.m. GMT+9, Ilya
> Kasnacheev
> > <
> > >>>>>> ilya.kasnacheev@gmail.com> wrote:
> > >>>>>>
> > >>>>>>
> > >>>>>> Hello!
> > >>>>>>
> > >>>>>> The last of my requests still standing is that we should fall-back
> > to
> > >>>>>> single URL download in case of error with 'latest' version.
> > Everything
> > >>>>>
> > >>>>> else
> > >>>>>> looks good to me.
> > >>>>>>
> > >>>>>> Can we do that? I'm really worried that Apache API will go sour.
> > >>>>>>
> > >>>>>> Regards,
> > >>>>>> --
> > >>>>>> Ilya Kasnacheev
> > >>>>>>
> > >>>>>>
> > >>>>>> чт, 6 сент. 2018 г. в 8:56, Roman Shtykh <rs...@yahoo.com>:
> > >>>>>>
> > >>>>>> Hi Ilya,
> > >>>>>>
> > >>>>>> Thanks again.
> > >>>>>>
> > >>>>>> 1) Done.
> > >>>>>> 2) Used catch() for latest version.
> > >>>>>>
> > >>>>>> Please see my comments on github.
> > >>>>>> --
> > >>>>>> Roman Shtykh
> > >>>>>>
> > >>>>>>
> > >>>>>> On Wednesday, September 5, 2018, 11:30:10 p.m. GMT+9, Ilya
> > Kasnacheev <
> > >>>>>> ilya.kasnacheev@gmail.com> wrote:
> > >>>>>>
> > >>>>>>
> > >>>>>> Hello!
> > >>>>>>
> > >>>>>> I've left a new wave of replies.
> > >>>>>>
> > >>>>>> Basically, 1) let's keep DOWNLOAD_URL_PATTERN string value inlined
> > so
> > >>>>>> that it will work even if build process is broken (would be useful
> > for
> > >>>>>
> > >>>>> e.g.
> > >>>>>> developing out of IDE)
> > >>>>>> And also I urge you to catch() around new fragile Apache JSON API
> > >>>>>> resolving, and download the 'current' version instead, as defined
> by
> > >>>>>> ignite-mesos version.
> > >>>>>>
> > >>>>>> This is because this module is not under continuouos scrutiny so
> > extra
> > >>>>>> care should be applied.
> > >>>>>> --
> > >>>>>> Ilya Kasnacheev
> > >>>>>>
> > >>>>>>
> > >>>>>> вт, 4 сент. 2018 г. в 13:42, Roman Shtykh <rs...@yahoo.com>:
> > >>>>>>
> > >>>>>> Thanks, Ilya!
> > >>>>>> I will check your comments, and discuss it at JIRA.
> > >>>>>>
> > >>>>>> --
> > >>>>>> Roman Shtykh
> > >>>>>>
> > >>>>>>
> > >>>>>> On Tuesday, September 4, 2018, 7:17:53 p.m. GMT+9, Ilya
> Kasnacheev <
> > >>>>>> ilya.kasnacheev@gmail.com> wrote:
> > >>>>>>
> > >>>>>>
> > >>>>>> Hello!
> > >>>>>>
> > >>>>>> IGNITE-9408 <https://issues.apache.org/jira/browse/IGNITE-9408>
> > looks
> > >>>>>> good to me and may be merged right away.
> > >>>>>>
> > >>>>>> IGNITE-9388 <https://issues.apache.org/jira/browse/IGNITE-9388>
> > needs
> > >>>>>> more work in my opinion, I have commented the PR. I also advice
> > having
> > >>>>>
> > >>>>> test
> > >>>>>> for this functionality.
> > >>>>>>
> > >>>>>> Regards,
> > >>>>>> --
> > >>>>>> Ilya Kasnacheev
> > >>>>>>
> > >>>>>>
> > >>>>>> вт, 4 сент. 2018 г. в 6:52, Roman Shtykh
> <rshtykh@yahoo.com.invalid
> > >:
> > >>>>>>
> > >>>>>> 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
> > >>>>>
> > >>>>> <
> > >>>>>> daradurvs@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 <
> > nizhikov@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.
> > >>>>>>
> > >>
> >
> >
>
Re: Apache Ignite 2.7 release
Posted by Dmitriy Setrakyan <ds...@apache.org>.
If it is an Ignite release, then it has to pass through the vote. If not,
then you can do the test without publishing or uploading the release.
D.
On Tue, Sep 18, 2018 at 1:18 PM Petr Ivanov <mr...@gmail.com> wrote:
> Ok.
>
> In case of TC questions — ask me.
>
>
>
> > On 18 Sep 2018, at 13:16, Nikolay Izhikov <ni...@apache.org> wrote:
> >
> > Hello, Petr.
> >
> > I want to make ignite-2.7 branch today.
> > And execute release procedure based on this branch.
> >
> > However, ignite-2.7 branch will be copy of master until code freeze date.
> >
> > В Вт, 18/09/2018 в 13:13 +0300, Petr Ivanov пишет:
> >> Will it be just a test or there is already ignite-2.7 branch?
> >>
> >> Fabric removal related TC modifications are not ready yet, and code is
> not in master.
> >>
> >>
> >>
> >>> On 18 Sep 2018, at 13:07, Nikolay Izhikov <ni...@apache.org> wrote:
> >>>
> >>> Hello, Igniters.
> >>>
> >>> I want to start and release procedures and make an RC1 build.
> >>>
> >>> It has a 2 intention:
> >>>
> >>> 1. I want to walk through all release steps to make sure they all
> works for me.
> >>> So I will be fully ready on release date.
> >>>
> >>> 2. We have updated some dependencies in 2.7 and we need to make sure
> binary build is still workable.
> >>>
> >>> Any objections?
> >>>
> >>>
> >>> В Пт, 14/09/2018 в 18:52 +0300, Alexey Goncharuk пишет:
> >>>> We already have all the mechanics in place to work with properties -
> we use
> >>>> ignite.build and ignite.revision from ignite.properties which are
> adjusted
> >>>> during the build in the binary package.
> >>>>
> >>>> Should I create the ticket if there are no objections?
> >>>>
> >>>> пт, 14 сент. 2018 г. в 13:22, Ilya Kasnacheev <
> ilya.kasnacheev@gmail.com>:
> >>>>
> >>>>> Hello!
> >>>>>
> >>>>> So now there's an issue that this script makes source change after
> every
> >>>>> build, show up in git status.
> >>>>>
> >>>>> What we could do to it:
> >>>>> - Commit the changes after the build, once. In hopes that it won't
> change
> >>>>> very often. With benefit that we could do that right now, before the
> code
> >>>>> freeze.
> >>>>> - Move these values to a properties file from both pom.xml and
> >>>>> IgniteProvider.java. Any problems with this approach? We'll just
> read them
> >>>>> from classpath properties file.
> >>>>> - Update the links in the file once and remove them from build
> process. Why
> >>>>> were they added to build process in the first place - to make them
> >>>>> configurable during build?
> >>>>>
> >>>>> Regards,
> >>>>> --
> >>>>> Ilya Kasnacheev
> >>>>>
> >>>>>
> >>>>> вт, 11 сент. 2018 г. в 5:53, Roman Shtykh <rs...@yahoo.com>:
> >>>>>
> >>>>>> Ilya,
> >>>>>>
> >>>>>> The "latest" version is the default, and resolved by
> >>>>>> https://ignite.apache.org/latest which is used by our web site
> when a
> >>>>>> user download the latest Ignite version. And I think this is the
> >>>>>
> >>>>> authority
> >>>>>> to judge of the latest official release (pom.xml you suggest can
> have
> >>>>>> SNAPSHOTs etc.).
> >>>>>> Also, as I explained during our review sessions, ignite-mesos-2.6.0
> is a
> >>>>>> driver and doesn't mean you need to have Ignite 2.6.0. User can run
> any
> >>>>>> version of Ignite he/she specifies. By default, it's "latest" but a
> user
> >>>>>> can specify any version needed, even from a non-archive URL.
> >>>>>>
> >>>>>> In short, what we have now
> >>>>>> 1. mesos driver (ignite-mesos-x.x.x) will use "latest" version by
> default
> >>>>>> -> it will try to resolve the latest officially releases version of
> >>>>>
> >>>>> Apache
> >>>>>> Ignite, find the closest mirror and download Ignite in a minute. If
> the
> >>>>>> version resolution fails, we fall back to the slow apache archive
> (as you
> >>>>>> suggest; in my opinion we better fail-fast instead of waiting for
> hours
> >>>>>
> >>>>> to
> >>>>>> download, so the user can choose another download option (3))
> >>>>>> 2. If the user specifies the version explicitly, it goes to the slow
> >>>>>> apache archive.
> >>>>>> 3. The user can put ignite zip file on his/her http server and
> provide
> >>>>>
> >>>>> the
> >>>>>> URL as a parameter to the driver, if options 1 and 2 don't work.
> >>>>>>
> >>>>>> As you see, there are 3 options. And I just fix the 1st one with
> >>>>>> https://issues.apache.org/jira/browse/IGNITE-9388 and don't change
> the
> >>>>>> original logic (which I find reasonable) documented on our site -- I
> >>>>>
> >>>>> don't
> >>>>>> see how it blocks anything.
> >>>>>>
> >>>>>> Roman Shtykh
> >>>>>>
> >>>>>>
> >>>>>> On Monday, September 10, 2018, 6:16:15 p.m. GMT+9, Ilya Kasnacheev <
> >>>>>> ilya.kasnacheev@gmail.com> wrote:
> >>>>>>
> >>>>>>
> >>>>>> Hello!
> >>>>>>
> >>>>>> There's still two issues with the submission.
> >>>>>>
> >>>>>> The first one is that we're downloading "latest" version from
> preferred
> >>>>>> mirror but a specified version, such as "2.6", we're also going to
> >>>>>
> >>>>> download
> >>>>>> from "slow" archive.apache.org/dist.
> >>>>>> That's a great limitation for this change, since most real
> deployments of
> >>>>>> Apache Ignite will have their Ignite version pegged to a specific
> >>>>>
> >>>>> release.
> >>>>>> But in this case there's no win in download speed.
> >>>>>> *In my opinion it is a blocker.*
> >>>>>>
> >>>>>> The second one is that we can't download anything when we failed to
> >>>>>> resolve "latest". My idea is that we should try and download last
> known
> >>>>>> version in this case, which can be pushed to source from pom.xml,
> as we
> >>>>>> already do with URLs. So if you could not resolve "latest" you will
> >>>>>> download 2.7.0.
> >>>>>>
> >>>>>> Buuut, maybe it's not necessary, maybe we should just *discourage
> >>>>>> "latest"*, which is in my opinion almost always a bad idea.
> >>>>>>
> >>>>>> WDYT?
> >>>>>>
> >>>>>> Regards,
> >>>>>> --
> >>>>>> Ilya Kasnacheev
> >>>>>>
> >>>>>>
> >>>>>> вс, 9 сент. 2018 г. в 5:47, Roman Shtykh <rs...@yahoo.com>:
> >>>>>>
> >>>>>> Hi Ilya,
> >>>>>>
> >>>>>> Sorry, missed that.
> >>>>>> Added now.
> >>>>>>
> >>>>>> --
> >>>>>> Roman Shtykh
> >>>>>>
> >>>>>>
> >>>>>> On Thursday, September 6, 2018, 6:16:58 p.m. GMT+9, Ilya Kasnacheev
> <
> >>>>>> ilya.kasnacheev@gmail.com> wrote:
> >>>>>>
> >>>>>>
> >>>>>> Hello!
> >>>>>>
> >>>>>> The last of my requests still standing is that we should fall-back
> to
> >>>>>> single URL download in case of error with 'latest' version.
> Everything
> >>>>>
> >>>>> else
> >>>>>> looks good to me.
> >>>>>>
> >>>>>> Can we do that? I'm really worried that Apache API will go sour.
> >>>>>>
> >>>>>> Regards,
> >>>>>> --
> >>>>>> Ilya Kasnacheev
> >>>>>>
> >>>>>>
> >>>>>> чт, 6 сент. 2018 г. в 8:56, Roman Shtykh <rs...@yahoo.com>:
> >>>>>>
> >>>>>> Hi Ilya,
> >>>>>>
> >>>>>> Thanks again.
> >>>>>>
> >>>>>> 1) Done.
> >>>>>> 2) Used catch() for latest version.
> >>>>>>
> >>>>>> Please see my comments on github.
> >>>>>> --
> >>>>>> Roman Shtykh
> >>>>>>
> >>>>>>
> >>>>>> On Wednesday, September 5, 2018, 11:30:10 p.m. GMT+9, Ilya
> Kasnacheev <
> >>>>>> ilya.kasnacheev@gmail.com> wrote:
> >>>>>>
> >>>>>>
> >>>>>> Hello!
> >>>>>>
> >>>>>> I've left a new wave of replies.
> >>>>>>
> >>>>>> Basically, 1) let's keep DOWNLOAD_URL_PATTERN string value inlined
> so
> >>>>>> that it will work even if build process is broken (would be useful
> for
> >>>>>
> >>>>> e.g.
> >>>>>> developing out of IDE)
> >>>>>> And also I urge you to catch() around new fragile Apache JSON API
> >>>>>> resolving, and download the 'current' version instead, as defined by
> >>>>>> ignite-mesos version.
> >>>>>>
> >>>>>> This is because this module is not under continuouos scrutiny so
> extra
> >>>>>> care should be applied.
> >>>>>> --
> >>>>>> Ilya Kasnacheev
> >>>>>>
> >>>>>>
> >>>>>> вт, 4 сент. 2018 г. в 13:42, Roman Shtykh <rs...@yahoo.com>:
> >>>>>>
> >>>>>> Thanks, Ilya!
> >>>>>> I will check your comments, and discuss it at JIRA.
> >>>>>>
> >>>>>> --
> >>>>>> Roman Shtykh
> >>>>>>
> >>>>>>
> >>>>>> On Tuesday, September 4, 2018, 7:17:53 p.m. GMT+9, Ilya Kasnacheev <
> >>>>>> ilya.kasnacheev@gmail.com> wrote:
> >>>>>>
> >>>>>>
> >>>>>> Hello!
> >>>>>>
> >>>>>> IGNITE-9408 <https://issues.apache.org/jira/browse/IGNITE-9408>
> looks
> >>>>>> good to me and may be merged right away.
> >>>>>>
> >>>>>> IGNITE-9388 <https://issues.apache.org/jira/browse/IGNITE-9388>
> needs
> >>>>>> more work in my opinion, I have commented the PR. I also advice
> having
> >>>>>
> >>>>> test
> >>>>>> for this functionality.
> >>>>>>
> >>>>>> Regards,
> >>>>>> --
> >>>>>> Ilya Kasnacheev
> >>>>>>
> >>>>>>
> >>>>>> вт, 4 сент. 2018 г. в 6:52, Roman Shtykh <rshtykh@yahoo.com.invalid
> >:
> >>>>>>
> >>>>>> 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
> >>>>>
> >>>>> <
> >>>>>> daradurvs@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 <
> nizhikov@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.
> >>>>>>
> >>
>
>
Re: Apache Ignite 2.7 release
Posted by Petr Ivanov <mr...@gmail.com>.
Ok.
In case of TC questions — ask me.
> On 18 Sep 2018, at 13:16, Nikolay Izhikov <ni...@apache.org> wrote:
>
> Hello, Petr.
>
> I want to make ignite-2.7 branch today.
> And execute release procedure based on this branch.
>
> However, ignite-2.7 branch will be copy of master until code freeze date.
>
> В Вт, 18/09/2018 в 13:13 +0300, Petr Ivanov пишет:
>> Will it be just a test or there is already ignite-2.7 branch?
>>
>> Fabric removal related TC modifications are not ready yet, and code is not in master.
>>
>>
>>
>>> On 18 Sep 2018, at 13:07, Nikolay Izhikov <ni...@apache.org> wrote:
>>>
>>> Hello, Igniters.
>>>
>>> I want to start and release procedures and make an RC1 build.
>>>
>>> It has a 2 intention:
>>>
>>> 1. I want to walk through all release steps to make sure they all works for me.
>>> So I will be fully ready on release date.
>>>
>>> 2. We have updated some dependencies in 2.7 and we need to make sure binary build is still workable.
>>>
>>> Any objections?
>>>
>>>
>>> В Пт, 14/09/2018 в 18:52 +0300, Alexey Goncharuk пишет:
>>>> We already have all the mechanics in place to work with properties - we use
>>>> ignite.build and ignite.revision from ignite.properties which are adjusted
>>>> during the build in the binary package.
>>>>
>>>> Should I create the ticket if there are no objections?
>>>>
>>>> пт, 14 сент. 2018 г. в 13:22, Ilya Kasnacheev <il...@gmail.com>:
>>>>
>>>>> Hello!
>>>>>
>>>>> So now there's an issue that this script makes source change after every
>>>>> build, show up in git status.
>>>>>
>>>>> What we could do to it:
>>>>> - Commit the changes after the build, once. In hopes that it won't change
>>>>> very often. With benefit that we could do that right now, before the code
>>>>> freeze.
>>>>> - Move these values to a properties file from both pom.xml and
>>>>> IgniteProvider.java. Any problems with this approach? We'll just read them
>>>>> from classpath properties file.
>>>>> - Update the links in the file once and remove them from build process. Why
>>>>> were they added to build process in the first place - to make them
>>>>> configurable during build?
>>>>>
>>>>> Regards,
>>>>> --
>>>>> Ilya Kasnacheev
>>>>>
>>>>>
>>>>> вт, 11 сент. 2018 г. в 5:53, Roman Shtykh <rs...@yahoo.com>:
>>>>>
>>>>>> Ilya,
>>>>>>
>>>>>> The "latest" version is the default, and resolved by
>>>>>> https://ignite.apache.org/latest which is used by our web site when a
>>>>>> user download the latest Ignite version. And I think this is the
>>>>>
>>>>> authority
>>>>>> to judge of the latest official release (pom.xml you suggest can have
>>>>>> SNAPSHOTs etc.).
>>>>>> Also, as I explained during our review sessions, ignite-mesos-2.6.0 is a
>>>>>> driver and doesn't mean you need to have Ignite 2.6.0. User can run any
>>>>>> version of Ignite he/she specifies. By default, it's "latest" but a user
>>>>>> can specify any version needed, even from a non-archive URL.
>>>>>>
>>>>>> In short, what we have now
>>>>>> 1. mesos driver (ignite-mesos-x.x.x) will use "latest" version by default
>>>>>> -> it will try to resolve the latest officially releases version of
>>>>>
>>>>> Apache
>>>>>> Ignite, find the closest mirror and download Ignite in a minute. If the
>>>>>> version resolution fails, we fall back to the slow apache archive (as you
>>>>>> suggest; in my opinion we better fail-fast instead of waiting for hours
>>>>>
>>>>> to
>>>>>> download, so the user can choose another download option (3))
>>>>>> 2. If the user specifies the version explicitly, it goes to the slow
>>>>>> apache archive.
>>>>>> 3. The user can put ignite zip file on his/her http server and provide
>>>>>
>>>>> the
>>>>>> URL as a parameter to the driver, if options 1 and 2 don't work.
>>>>>>
>>>>>> As you see, there are 3 options. And I just fix the 1st one with
>>>>>> https://issues.apache.org/jira/browse/IGNITE-9388 and don't change the
>>>>>> original logic (which I find reasonable) documented on our site -- I
>>>>>
>>>>> don't
>>>>>> see how it blocks anything.
>>>>>>
>>>>>> Roman Shtykh
>>>>>>
>>>>>>
>>>>>> On Monday, September 10, 2018, 6:16:15 p.m. GMT+9, Ilya Kasnacheev <
>>>>>> ilya.kasnacheev@gmail.com> wrote:
>>>>>>
>>>>>>
>>>>>> Hello!
>>>>>>
>>>>>> There's still two issues with the submission.
>>>>>>
>>>>>> The first one is that we're downloading "latest" version from preferred
>>>>>> mirror but a specified version, such as "2.6", we're also going to
>>>>>
>>>>> download
>>>>>> from "slow" archive.apache.org/dist.
>>>>>> That's a great limitation for this change, since most real deployments of
>>>>>> Apache Ignite will have their Ignite version pegged to a specific
>>>>>
>>>>> release.
>>>>>> But in this case there's no win in download speed.
>>>>>> *In my opinion it is a blocker.*
>>>>>>
>>>>>> The second one is that we can't download anything when we failed to
>>>>>> resolve "latest". My idea is that we should try and download last known
>>>>>> version in this case, which can be pushed to source from pom.xml, as we
>>>>>> already do with URLs. So if you could not resolve "latest" you will
>>>>>> download 2.7.0.
>>>>>>
>>>>>> Buuut, maybe it's not necessary, maybe we should just *discourage
>>>>>> "latest"*, which is in my opinion almost always a bad idea.
>>>>>>
>>>>>> WDYT?
>>>>>>
>>>>>> Regards,
>>>>>> --
>>>>>> Ilya Kasnacheev
>>>>>>
>>>>>>
>>>>>> вс, 9 сент. 2018 г. в 5:47, Roman Shtykh <rs...@yahoo.com>:
>>>>>>
>>>>>> Hi Ilya,
>>>>>>
>>>>>> Sorry, missed that.
>>>>>> Added now.
>>>>>>
>>>>>> --
>>>>>> Roman Shtykh
>>>>>>
>>>>>>
>>>>>> On Thursday, September 6, 2018, 6:16:58 p.m. GMT+9, Ilya Kasnacheev <
>>>>>> ilya.kasnacheev@gmail.com> wrote:
>>>>>>
>>>>>>
>>>>>> Hello!
>>>>>>
>>>>>> The last of my requests still standing is that we should fall-back to
>>>>>> single URL download in case of error with 'latest' version. Everything
>>>>>
>>>>> else
>>>>>> looks good to me.
>>>>>>
>>>>>> Can we do that? I'm really worried that Apache API will go sour.
>>>>>>
>>>>>> Regards,
>>>>>> --
>>>>>> Ilya Kasnacheev
>>>>>>
>>>>>>
>>>>>> чт, 6 сент. 2018 г. в 8:56, Roman Shtykh <rs...@yahoo.com>:
>>>>>>
>>>>>> Hi Ilya,
>>>>>>
>>>>>> Thanks again.
>>>>>>
>>>>>> 1) Done.
>>>>>> 2) Used catch() for latest version.
>>>>>>
>>>>>> Please see my comments on github.
>>>>>> --
>>>>>> Roman Shtykh
>>>>>>
>>>>>>
>>>>>> On Wednesday, September 5, 2018, 11:30:10 p.m. GMT+9, Ilya Kasnacheev <
>>>>>> ilya.kasnacheev@gmail.com> wrote:
>>>>>>
>>>>>>
>>>>>> Hello!
>>>>>>
>>>>>> I've left a new wave of replies.
>>>>>>
>>>>>> Basically, 1) let's keep DOWNLOAD_URL_PATTERN string value inlined so
>>>>>> that it will work even if build process is broken (would be useful for
>>>>>
>>>>> e.g.
>>>>>> developing out of IDE)
>>>>>> And also I urge you to catch() around new fragile Apache JSON API
>>>>>> resolving, and download the 'current' version instead, as defined by
>>>>>> ignite-mesos version.
>>>>>>
>>>>>> This is because this module is not under continuouos scrutiny so extra
>>>>>> care should be applied.
>>>>>> --
>>>>>> Ilya Kasnacheev
>>>>>>
>>>>>>
>>>>>> вт, 4 сент. 2018 г. в 13:42, Roman Shtykh <rs...@yahoo.com>:
>>>>>>
>>>>>> Thanks, Ilya!
>>>>>> I will check your comments, and discuss it at JIRA.
>>>>>>
>>>>>> --
>>>>>> Roman Shtykh
>>>>>>
>>>>>>
>>>>>> On Tuesday, September 4, 2018, 7:17:53 p.m. GMT+9, Ilya Kasnacheev <
>>>>>> ilya.kasnacheev@gmail.com> wrote:
>>>>>>
>>>>>>
>>>>>> Hello!
>>>>>>
>>>>>> IGNITE-9408 <https://issues.apache.org/jira/browse/IGNITE-9408> looks
>>>>>> good to me and may be merged right away.
>>>>>>
>>>>>> IGNITE-9388 <https://issues.apache.org/jira/browse/IGNITE-9388> needs
>>>>>> more work in my opinion, I have commented the PR. I also advice having
>>>>>
>>>>> test
>>>>>> for this functionality.
>>>>>>
>>>>>> Regards,
>>>>>> --
>>>>>> Ilya Kasnacheev
>>>>>>
>>>>>>
>>>>>> вт, 4 сент. 2018 г. в 6:52, Roman Shtykh <rs...@yahoo.com.invalid>:
>>>>>>
>>>>>> 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
>>>>>
>>>>> <
>>>>>> daradurvs@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 <ni...@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.
>>>>>>
>>
Re: Apache Ignite 2.7 release
Posted by Nikolay Izhikov <ni...@apache.org>.
Hello, Petr.
I want to make ignite-2.7 branch today.
And execute release procedure based on this branch.
However, ignite-2.7 branch will be copy of master until code freeze date.
В Вт, 18/09/2018 в 13:13 +0300, Petr Ivanov пишет:
> Will it be just a test or there is already ignite-2.7 branch?
>
> Fabric removal related TC modifications are not ready yet, and code is not in master.
>
>
>
> > On 18 Sep 2018, at 13:07, Nikolay Izhikov <ni...@apache.org> wrote:
> >
> > Hello, Igniters.
> >
> > I want to start and release procedures and make an RC1 build.
> >
> > It has a 2 intention:
> >
> > 1. I want to walk through all release steps to make sure they all works for me.
> > So I will be fully ready on release date.
> >
> > 2. We have updated some dependencies in 2.7 and we need to make sure binary build is still workable.
> >
> > Any objections?
> >
> >
> > В Пт, 14/09/2018 в 18:52 +0300, Alexey Goncharuk пишет:
> > > We already have all the mechanics in place to work with properties - we use
> > > ignite.build and ignite.revision from ignite.properties which are adjusted
> > > during the build in the binary package.
> > >
> > > Should I create the ticket if there are no objections?
> > >
> > > пт, 14 сент. 2018 г. в 13:22, Ilya Kasnacheev <il...@gmail.com>:
> > >
> > > > Hello!
> > > >
> > > > So now there's an issue that this script makes source change after every
> > > > build, show up in git status.
> > > >
> > > > What we could do to it:
> > > > - Commit the changes after the build, once. In hopes that it won't change
> > > > very often. With benefit that we could do that right now, before the code
> > > > freeze.
> > > > - Move these values to a properties file from both pom.xml and
> > > > IgniteProvider.java. Any problems with this approach? We'll just read them
> > > > from classpath properties file.
> > > > - Update the links in the file once and remove them from build process. Why
> > > > were they added to build process in the first place - to make them
> > > > configurable during build?
> > > >
> > > > Regards,
> > > > --
> > > > Ilya Kasnacheev
> > > >
> > > >
> > > > вт, 11 сент. 2018 г. в 5:53, Roman Shtykh <rs...@yahoo.com>:
> > > >
> > > > > Ilya,
> > > > >
> > > > > The "latest" version is the default, and resolved by
> > > > > https://ignite.apache.org/latest which is used by our web site when a
> > > > > user download the latest Ignite version. And I think this is the
> > > >
> > > > authority
> > > > > to judge of the latest official release (pom.xml you suggest can have
> > > > > SNAPSHOTs etc.).
> > > > > Also, as I explained during our review sessions, ignite-mesos-2.6.0 is a
> > > > > driver and doesn't mean you need to have Ignite 2.6.0. User can run any
> > > > > version of Ignite he/she specifies. By default, it's "latest" but a user
> > > > > can specify any version needed, even from a non-archive URL.
> > > > >
> > > > > In short, what we have now
> > > > > 1. mesos driver (ignite-mesos-x.x.x) will use "latest" version by default
> > > > > -> it will try to resolve the latest officially releases version of
> > > >
> > > > Apache
> > > > > Ignite, find the closest mirror and download Ignite in a minute. If the
> > > > > version resolution fails, we fall back to the slow apache archive (as you
> > > > > suggest; in my opinion we better fail-fast instead of waiting for hours
> > > >
> > > > to
> > > > > download, so the user can choose another download option (3))
> > > > > 2. If the user specifies the version explicitly, it goes to the slow
> > > > > apache archive.
> > > > > 3. The user can put ignite zip file on his/her http server and provide
> > > >
> > > > the
> > > > > URL as a parameter to the driver, if options 1 and 2 don't work.
> > > > >
> > > > > As you see, there are 3 options. And I just fix the 1st one with
> > > > > https://issues.apache.org/jira/browse/IGNITE-9388 and don't change the
> > > > > original logic (which I find reasonable) documented on our site -- I
> > > >
> > > > don't
> > > > > see how it blocks anything.
> > > > >
> > > > > Roman Shtykh
> > > > >
> > > > >
> > > > > On Monday, September 10, 2018, 6:16:15 p.m. GMT+9, Ilya Kasnacheev <
> > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > >
> > > > >
> > > > > Hello!
> > > > >
> > > > > There's still two issues with the submission.
> > > > >
> > > > > The first one is that we're downloading "latest" version from preferred
> > > > > mirror but a specified version, such as "2.6", we're also going to
> > > >
> > > > download
> > > > > from "slow" archive.apache.org/dist.
> > > > > That's a great limitation for this change, since most real deployments of
> > > > > Apache Ignite will have their Ignite version pegged to a specific
> > > >
> > > > release.
> > > > > But in this case there's no win in download speed.
> > > > > *In my opinion it is a blocker.*
> > > > >
> > > > > The second one is that we can't download anything when we failed to
> > > > > resolve "latest". My idea is that we should try and download last known
> > > > > version in this case, which can be pushed to source from pom.xml, as we
> > > > > already do with URLs. So if you could not resolve "latest" you will
> > > > > download 2.7.0.
> > > > >
> > > > > Buuut, maybe it's not necessary, maybe we should just *discourage
> > > > > "latest"*, which is in my opinion almost always a bad idea.
> > > > >
> > > > > WDYT?
> > > > >
> > > > > Regards,
> > > > > --
> > > > > Ilya Kasnacheev
> > > > >
> > > > >
> > > > > вс, 9 сент. 2018 г. в 5:47, Roman Shtykh <rs...@yahoo.com>:
> > > > >
> > > > > Hi Ilya,
> > > > >
> > > > > Sorry, missed that.
> > > > > Added now.
> > > > >
> > > > > --
> > > > > Roman Shtykh
> > > > >
> > > > >
> > > > > On Thursday, September 6, 2018, 6:16:58 p.m. GMT+9, Ilya Kasnacheev <
> > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > >
> > > > >
> > > > > Hello!
> > > > >
> > > > > The last of my requests still standing is that we should fall-back to
> > > > > single URL download in case of error with 'latest' version. Everything
> > > >
> > > > else
> > > > > looks good to me.
> > > > >
> > > > > Can we do that? I'm really worried that Apache API will go sour.
> > > > >
> > > > > Regards,
> > > > > --
> > > > > Ilya Kasnacheev
> > > > >
> > > > >
> > > > > чт, 6 сент. 2018 г. в 8:56, Roman Shtykh <rs...@yahoo.com>:
> > > > >
> > > > > Hi Ilya,
> > > > >
> > > > > Thanks again.
> > > > >
> > > > > 1) Done.
> > > > > 2) Used catch() for latest version.
> > > > >
> > > > > Please see my comments on github.
> > > > > --
> > > > > Roman Shtykh
> > > > >
> > > > >
> > > > > On Wednesday, September 5, 2018, 11:30:10 p.m. GMT+9, Ilya Kasnacheev <
> > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > >
> > > > >
> > > > > Hello!
> > > > >
> > > > > I've left a new wave of replies.
> > > > >
> > > > > Basically, 1) let's keep DOWNLOAD_URL_PATTERN string value inlined so
> > > > > that it will work even if build process is broken (would be useful for
> > > >
> > > > e.g.
> > > > > developing out of IDE)
> > > > > And also I urge you to catch() around new fragile Apache JSON API
> > > > > resolving, and download the 'current' version instead, as defined by
> > > > > ignite-mesos version.
> > > > >
> > > > > This is because this module is not under continuouos scrutiny so extra
> > > > > care should be applied.
> > > > > --
> > > > > Ilya Kasnacheev
> > > > >
> > > > >
> > > > > вт, 4 сент. 2018 г. в 13:42, Roman Shtykh <rs...@yahoo.com>:
> > > > >
> > > > > Thanks, Ilya!
> > > > > I will check your comments, and discuss it at JIRA.
> > > > >
> > > > > --
> > > > > Roman Shtykh
> > > > >
> > > > >
> > > > > On Tuesday, September 4, 2018, 7:17:53 p.m. GMT+9, Ilya Kasnacheev <
> > > > > ilya.kasnacheev@gmail.com> wrote:
> > > > >
> > > > >
> > > > > Hello!
> > > > >
> > > > > IGNITE-9408 <https://issues.apache.org/jira/browse/IGNITE-9408> looks
> > > > > good to me and may be merged right away.
> > > > >
> > > > > IGNITE-9388 <https://issues.apache.org/jira/browse/IGNITE-9388> needs
> > > > > more work in my opinion, I have commented the PR. I also advice having
> > > >
> > > > test
> > > > > for this functionality.
> > > > >
> > > > > Regards,
> > > > > --
> > > > > Ilya Kasnacheev
> > > > >
> > > > >
> > > > > вт, 4 сент. 2018 г. в 6:52, Roman Shtykh <rs...@yahoo.com.invalid>:
> > > > >
> > > > > 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
> > > >
> > > > <
> > > > > daradurvs@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 <ni...@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.
> > > > >
>
>
Re: Apache Ignite 2.7 release
Posted by Petr Ivanov <mr...@gmail.com>.
Will it be just a test or there is already ignite-2.7 branch?
Fabric removal related TC modifications are not ready yet, and code is not in master.
> On 18 Sep 2018, at 13:07, Nikolay Izhikov <ni...@apache.org> wrote:
>
> Hello, Igniters.
>
> I want to start and release procedures and make an RC1 build.
>
> It has a 2 intention:
>
> 1. I want to walk through all release steps to make sure they all works for me.
> So I will be fully ready on release date.
>
> 2. We have updated some dependencies in 2.7 and we need to make sure binary build is still workable.
>
> Any objections?
>
>
> В Пт, 14/09/2018 в 18:52 +0300, Alexey Goncharuk пишет:
>> We already have all the mechanics in place to work with properties - we use
>> ignite.build and ignite.revision from ignite.properties which are adjusted
>> during the build in the binary package.
>>
>> Should I create the ticket if there are no objections?
>>
>> пт, 14 сент. 2018 г. в 13:22, Ilya Kasnacheev <il...@gmail.com>:
>>
>>> Hello!
>>>
>>> So now there's an issue that this script makes source change after every
>>> build, show up in git status.
>>>
>>> What we could do to it:
>>> - Commit the changes after the build, once. In hopes that it won't change
>>> very often. With benefit that we could do that right now, before the code
>>> freeze.
>>> - Move these values to a properties file from both pom.xml and
>>> IgniteProvider.java. Any problems with this approach? We'll just read them
>>> from classpath properties file.
>>> - Update the links in the file once and remove them from build process. Why
>>> were they added to build process in the first place - to make them
>>> configurable during build?
>>>
>>> Regards,
>>> --
>>> Ilya Kasnacheev
>>>
>>>
>>> вт, 11 сент. 2018 г. в 5:53, Roman Shtykh <rs...@yahoo.com>:
>>>
>>>> Ilya,
>>>>
>>>> The "latest" version is the default, and resolved by
>>>> https://ignite.apache.org/latest which is used by our web site when a
>>>> user download the latest Ignite version. And I think this is the
>>>
>>> authority
>>>> to judge of the latest official release (pom.xml you suggest can have
>>>> SNAPSHOTs etc.).
>>>> Also, as I explained during our review sessions, ignite-mesos-2.6.0 is a
>>>> driver and doesn't mean you need to have Ignite 2.6.0. User can run any
>>>> version of Ignite he/she specifies. By default, it's "latest" but a user
>>>> can specify any version needed, even from a non-archive URL.
>>>>
>>>> In short, what we have now
>>>> 1. mesos driver (ignite-mesos-x.x.x) will use "latest" version by default
>>>> -> it will try to resolve the latest officially releases version of
>>>
>>> Apache
>>>> Ignite, find the closest mirror and download Ignite in a minute. If the
>>>> version resolution fails, we fall back to the slow apache archive (as you
>>>> suggest; in my opinion we better fail-fast instead of waiting for hours
>>>
>>> to
>>>> download, so the user can choose another download option (3))
>>>> 2. If the user specifies the version explicitly, it goes to the slow
>>>> apache archive.
>>>> 3. The user can put ignite zip file on his/her http server and provide
>>>
>>> the
>>>> URL as a parameter to the driver, if options 1 and 2 don't work.
>>>>
>>>> As you see, there are 3 options. And I just fix the 1st one with
>>>> https://issues.apache.org/jira/browse/IGNITE-9388 and don't change the
>>>> original logic (which I find reasonable) documented on our site -- I
>>>
>>> don't
>>>> see how it blocks anything.
>>>>
>>>> Roman Shtykh
>>>>
>>>>
>>>> On Monday, September 10, 2018, 6:16:15 p.m. GMT+9, Ilya Kasnacheev <
>>>> ilya.kasnacheev@gmail.com> wrote:
>>>>
>>>>
>>>> Hello!
>>>>
>>>> There's still two issues with the submission.
>>>>
>>>> The first one is that we're downloading "latest" version from preferred
>>>> mirror but a specified version, such as "2.6", we're also going to
>>>
>>> download
>>>> from "slow" archive.apache.org/dist.
>>>> That's a great limitation for this change, since most real deployments of
>>>> Apache Ignite will have their Ignite version pegged to a specific
>>>
>>> release.
>>>> But in this case there's no win in download speed.
>>>> *In my opinion it is a blocker.*
>>>>
>>>> The second one is that we can't download anything when we failed to
>>>> resolve "latest". My idea is that we should try and download last known
>>>> version in this case, which can be pushed to source from pom.xml, as we
>>>> already do with URLs. So if you could not resolve "latest" you will
>>>> download 2.7.0.
>>>>
>>>> Buuut, maybe it's not necessary, maybe we should just *discourage
>>>> "latest"*, which is in my opinion almost always a bad idea.
>>>>
>>>> WDYT?
>>>>
>>>> Regards,
>>>> --
>>>> Ilya Kasnacheev
>>>>
>>>>
>>>> вс, 9 сент. 2018 г. в 5:47, Roman Shtykh <rs...@yahoo.com>:
>>>>
>>>> Hi Ilya,
>>>>
>>>> Sorry, missed that.
>>>> Added now.
>>>>
>>>> --
>>>> Roman Shtykh
>>>>
>>>>
>>>> On Thursday, September 6, 2018, 6:16:58 p.m. GMT+9, Ilya Kasnacheev <
>>>> ilya.kasnacheev@gmail.com> wrote:
>>>>
>>>>
>>>> Hello!
>>>>
>>>> The last of my requests still standing is that we should fall-back to
>>>> single URL download in case of error with 'latest' version. Everything
>>>
>>> else
>>>> looks good to me.
>>>>
>>>> Can we do that? I'm really worried that Apache API will go sour.
>>>>
>>>> Regards,
>>>> --
>>>> Ilya Kasnacheev
>>>>
>>>>
>>>> чт, 6 сент. 2018 г. в 8:56, Roman Shtykh <rs...@yahoo.com>:
>>>>
>>>> Hi Ilya,
>>>>
>>>> Thanks again.
>>>>
>>>> 1) Done.
>>>> 2) Used catch() for latest version.
>>>>
>>>> Please see my comments on github.
>>>> --
>>>> Roman Shtykh
>>>>
>>>>
>>>> On Wednesday, September 5, 2018, 11:30:10 p.m. GMT+9, Ilya Kasnacheev <
>>>> ilya.kasnacheev@gmail.com> wrote:
>>>>
>>>>
>>>> Hello!
>>>>
>>>> I've left a new wave of replies.
>>>>
>>>> Basically, 1) let's keep DOWNLOAD_URL_PATTERN string value inlined so
>>>> that it will work even if build process is broken (would be useful for
>>>
>>> e.g.
>>>> developing out of IDE)
>>>> And also I urge you to catch() around new fragile Apache JSON API
>>>> resolving, and download the 'current' version instead, as defined by
>>>> ignite-mesos version.
>>>>
>>>> This is because this module is not under continuouos scrutiny so extra
>>>> care should be applied.
>>>> --
>>>> Ilya Kasnacheev
>>>>
>>>>
>>>> вт, 4 сент. 2018 г. в 13:42, Roman Shtykh <rs...@yahoo.com>:
>>>>
>>>> Thanks, Ilya!
>>>> I will check your comments, and discuss it at JIRA.
>>>>
>>>> --
>>>> Roman Shtykh
>>>>
>>>>
>>>> On Tuesday, September 4, 2018, 7:17:53 p.m. GMT+9, Ilya Kasnacheev <
>>>> ilya.kasnacheev@gmail.com> wrote:
>>>>
>>>>
>>>> Hello!
>>>>
>>>> IGNITE-9408 <https://issues.apache.org/jira/browse/IGNITE-9408> looks
>>>> good to me and may be merged right away.
>>>>
>>>> IGNITE-9388 <https://issues.apache.org/jira/browse/IGNITE-9388> needs
>>>> more work in my opinion, I have commented the PR. I also advice having
>>>
>>> test
>>>> for this functionality.
>>>>
>>>> Regards,
>>>> --
>>>> Ilya Kasnacheev
>>>>
>>>>
>>>> вт, 4 сент. 2018 г. в 6:52, Roman Shtykh <rs...@yahoo.com.invalid>:
>>>>
>>>> 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
>>>
>>> <
>>>> daradurvs@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 <ni...@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.
>>>>
Re: Apache Ignite 2.7 release
Posted by Nikolay Izhikov <ni...@apache.org>.
Hello, Igniters.
I want to start and release procedures and make an RC1 build.
It has a 2 intention:
1. I want to walk through all release steps to make sure they all works for me.
So I will be fully ready on release date.
2. We have updated some dependencies in 2.7 and we need to make sure binary build is still workable.
Any objections?
В Пт, 14/09/2018 в 18:52 +0300, Alexey Goncharuk пишет:
> We already have all the mechanics in place to work with properties - we use
> ignite.build and ignite.revision from ignite.properties which are adjusted
> during the build in the binary package.
>
> Should I create the ticket if there are no objections?
>
> пт, 14 сент. 2018 г. в 13:22, Ilya Kasnacheev <il...@gmail.com>:
>
> > Hello!
> >
> > So now there's an issue that this script makes source change after every
> > build, show up in git status.
> >
> > What we could do to it:
> > - Commit the changes after the build, once. In hopes that it won't change
> > very often. With benefit that we could do that right now, before the code
> > freeze.
> > - Move these values to a properties file from both pom.xml and
> > IgniteProvider.java. Any problems with this approach? We'll just read them
> > from classpath properties file.
> > - Update the links in the file once and remove them from build process. Why
> > were they added to build process in the first place - to make them
> > configurable during build?
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
> > вт, 11 сент. 2018 г. в 5:53, Roman Shtykh <rs...@yahoo.com>:
> >
> > > Ilya,
> > >
> > > The "latest" version is the default, and resolved by
> > > https://ignite.apache.org/latest which is used by our web site when a
> > > user download the latest Ignite version. And I think this is the
> >
> > authority
> > > to judge of the latest official release (pom.xml you suggest can have
> > > SNAPSHOTs etc.).
> > > Also, as I explained during our review sessions, ignite-mesos-2.6.0 is a
> > > driver and doesn't mean you need to have Ignite 2.6.0. User can run any
> > > version of Ignite he/she specifies. By default, it's "latest" but a user
> > > can specify any version needed, even from a non-archive URL.
> > >
> > > In short, what we have now
> > > 1. mesos driver (ignite-mesos-x.x.x) will use "latest" version by default
> > > -> it will try to resolve the latest officially releases version of
> >
> > Apache
> > > Ignite, find the closest mirror and download Ignite in a minute. If the
> > > version resolution fails, we fall back to the slow apache archive (as you
> > > suggest; in my opinion we better fail-fast instead of waiting for hours
> >
> > to
> > > download, so the user can choose another download option (3))
> > > 2. If the user specifies the version explicitly, it goes to the slow
> > > apache archive.
> > > 3. The user can put ignite zip file on his/her http server and provide
> >
> > the
> > > URL as a parameter to the driver, if options 1 and 2 don't work.
> > >
> > > As you see, there are 3 options. And I just fix the 1st one with
> > > https://issues.apache.org/jira/browse/IGNITE-9388 and don't change the
> > > original logic (which I find reasonable) documented on our site -- I
> >
> > don't
> > > see how it blocks anything.
> > >
> > > Roman Shtykh
> > >
> > >
> > > On Monday, September 10, 2018, 6:16:15 p.m. GMT+9, Ilya Kasnacheev <
> > > ilya.kasnacheev@gmail.com> wrote:
> > >
> > >
> > > Hello!
> > >
> > > There's still two issues with the submission.
> > >
> > > The first one is that we're downloading "latest" version from preferred
> > > mirror but a specified version, such as "2.6", we're also going to
> >
> > download
> > > from "slow" archive.apache.org/dist.
> > > That's a great limitation for this change, since most real deployments of
> > > Apache Ignite will have their Ignite version pegged to a specific
> >
> > release.
> > > But in this case there's no win in download speed.
> > > *In my opinion it is a blocker.*
> > >
> > > The second one is that we can't download anything when we failed to
> > > resolve "latest". My idea is that we should try and download last known
> > > version in this case, which can be pushed to source from pom.xml, as we
> > > already do with URLs. So if you could not resolve "latest" you will
> > > download 2.7.0.
> > >
> > > Buuut, maybe it's not necessary, maybe we should just *discourage
> > > "latest"*, which is in my opinion almost always a bad idea.
> > >
> > > WDYT?
> > >
> > > Regards,
> > > --
> > > Ilya Kasnacheev
> > >
> > >
> > > вс, 9 сент. 2018 г. в 5:47, Roman Shtykh <rs...@yahoo.com>:
> > >
> > > Hi Ilya,
> > >
> > > Sorry, missed that.
> > > Added now.
> > >
> > > --
> > > Roman Shtykh
> > >
> > >
> > > On Thursday, September 6, 2018, 6:16:58 p.m. GMT+9, Ilya Kasnacheev <
> > > ilya.kasnacheev@gmail.com> wrote:
> > >
> > >
> > > Hello!
> > >
> > > The last of my requests still standing is that we should fall-back to
> > > single URL download in case of error with 'latest' version. Everything
> >
> > else
> > > looks good to me.
> > >
> > > Can we do that? I'm really worried that Apache API will go sour.
> > >
> > > Regards,
> > > --
> > > Ilya Kasnacheev
> > >
> > >
> > > чт, 6 сент. 2018 г. в 8:56, Roman Shtykh <rs...@yahoo.com>:
> > >
> > > Hi Ilya,
> > >
> > > Thanks again.
> > >
> > > 1) Done.
> > > 2) Used catch() for latest version.
> > >
> > > Please see my comments on github.
> > > --
> > > Roman Shtykh
> > >
> > >
> > > On Wednesday, September 5, 2018, 11:30:10 p.m. GMT+9, Ilya Kasnacheev <
> > > ilya.kasnacheev@gmail.com> wrote:
> > >
> > >
> > > Hello!
> > >
> > > I've left a new wave of replies.
> > >
> > > Basically, 1) let's keep DOWNLOAD_URL_PATTERN string value inlined so
> > > that it will work even if build process is broken (would be useful for
> >
> > e.g.
> > > developing out of IDE)
> > > And also I urge you to catch() around new fragile Apache JSON API
> > > resolving, and download the 'current' version instead, as defined by
> > > ignite-mesos version.
> > >
> > > This is because this module is not under continuouos scrutiny so extra
> > > care should be applied.
> > > --
> > > Ilya Kasnacheev
> > >
> > >
> > > вт, 4 сент. 2018 г. в 13:42, Roman Shtykh <rs...@yahoo.com>:
> > >
> > > Thanks, Ilya!
> > > I will check your comments, and discuss it at JIRA.
> > >
> > > --
> > > Roman Shtykh
> > >
> > >
> > > On Tuesday, September 4, 2018, 7:17:53 p.m. GMT+9, Ilya Kasnacheev <
> > > ilya.kasnacheev@gmail.com> wrote:
> > >
> > >
> > > Hello!
> > >
> > > IGNITE-9408 <https://issues.apache.org/jira/browse/IGNITE-9408> looks
> > > good to me and may be merged right away.
> > >
> > > IGNITE-9388 <https://issues.apache.org/jira/browse/IGNITE-9388> needs
> > > more work in my opinion, I have commented the PR. I also advice having
> >
> > test
> > > for this functionality.
> > >
> > > Regards,
> > > --
> > > Ilya Kasnacheev
> > >
> > >
> > > вт, 4 сент. 2018 г. в 6:52, Roman Shtykh <rs...@yahoo.com.invalid>:
> > >
> > > 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
> >
> > <
> > > daradurvs@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 <ni...@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.
> > >
> > >
Re: Apache Ignite 2.7 release
Posted by Alexey Goncharuk <al...@gmail.com>.
We already have all the mechanics in place to work with properties - we use
ignite.build and ignite.revision from ignite.properties which are adjusted
during the build in the binary package.
Should I create the ticket if there are no objections?
пт, 14 сент. 2018 г. в 13:22, Ilya Kasnacheev <il...@gmail.com>:
> Hello!
>
> So now there's an issue that this script makes source change after every
> build, show up in git status.
>
> What we could do to it:
> - Commit the changes after the build, once. In hopes that it won't change
> very often. With benefit that we could do that right now, before the code
> freeze.
> - Move these values to a properties file from both pom.xml and
> IgniteProvider.java. Any problems with this approach? We'll just read them
> from classpath properties file.
> - Update the links in the file once and remove them from build process. Why
> were they added to build process in the first place - to make them
> configurable during build?
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> вт, 11 сент. 2018 г. в 5:53, Roman Shtykh <rs...@yahoo.com>:
>
> > Ilya,
> >
> > The "latest" version is the default, and resolved by
> > https://ignite.apache.org/latest which is used by our web site when a
> > user download the latest Ignite version. And I think this is the
> authority
> > to judge of the latest official release (pom.xml you suggest can have
> > SNAPSHOTs etc.).
> > Also, as I explained during our review sessions, ignite-mesos-2.6.0 is a
> > driver and doesn't mean you need to have Ignite 2.6.0. User can run any
> > version of Ignite he/she specifies. By default, it's "latest" but a user
> > can specify any version needed, even from a non-archive URL.
> >
> > In short, what we have now
> > 1. mesos driver (ignite-mesos-x.x.x) will use "latest" version by default
> > -> it will try to resolve the latest officially releases version of
> Apache
> > Ignite, find the closest mirror and download Ignite in a minute. If the
> > version resolution fails, we fall back to the slow apache archive (as you
> > suggest; in my opinion we better fail-fast instead of waiting for hours
> to
> > download, so the user can choose another download option (3))
> > 2. If the user specifies the version explicitly, it goes to the slow
> > apache archive.
> > 3. The user can put ignite zip file on his/her http server and provide
> the
> > URL as a parameter to the driver, if options 1 and 2 don't work.
> >
> > As you see, there are 3 options. And I just fix the 1st one with
> > https://issues.apache.org/jira/browse/IGNITE-9388 and don't change the
> > original logic (which I find reasonable) documented on our site -- I
> don't
> > see how it blocks anything.
> >
> > Roman Shtykh
> >
> >
> > On Monday, September 10, 2018, 6:16:15 p.m. GMT+9, Ilya Kasnacheev <
> > ilya.kasnacheev@gmail.com> wrote:
> >
> >
> > Hello!
> >
> > There's still two issues with the submission.
> >
> > The first one is that we're downloading "latest" version from preferred
> > mirror but a specified version, such as "2.6", we're also going to
> download
> > from "slow" archive.apache.org/dist.
> > That's a great limitation for this change, since most real deployments of
> > Apache Ignite will have their Ignite version pegged to a specific
> release.
> > But in this case there's no win in download speed.
> > *In my opinion it is a blocker.*
> >
> > The second one is that we can't download anything when we failed to
> > resolve "latest". My idea is that we should try and download last known
> > version in this case, which can be pushed to source from pom.xml, as we
> > already do with URLs. So if you could not resolve "latest" you will
> > download 2.7.0.
> >
> > Buuut, maybe it's not necessary, maybe we should just *discourage
> > "latest"*, which is in my opinion almost always a bad idea.
> >
> > WDYT?
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
> > вс, 9 сент. 2018 г. в 5:47, Roman Shtykh <rs...@yahoo.com>:
> >
> > Hi Ilya,
> >
> > Sorry, missed that.
> > Added now.
> >
> > --
> > Roman Shtykh
> >
> >
> > On Thursday, September 6, 2018, 6:16:58 p.m. GMT+9, Ilya Kasnacheev <
> > ilya.kasnacheev@gmail.com> wrote:
> >
> >
> > Hello!
> >
> > The last of my requests still standing is that we should fall-back to
> > single URL download in case of error with 'latest' version. Everything
> else
> > looks good to me.
> >
> > Can we do that? I'm really worried that Apache API will go sour.
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
> > чт, 6 сент. 2018 г. в 8:56, Roman Shtykh <rs...@yahoo.com>:
> >
> > Hi Ilya,
> >
> > Thanks again.
> >
> > 1) Done.
> > 2) Used catch() for latest version.
> >
> > Please see my comments on github.
> > --
> > Roman Shtykh
> >
> >
> > On Wednesday, September 5, 2018, 11:30:10 p.m. GMT+9, Ilya Kasnacheev <
> > ilya.kasnacheev@gmail.com> wrote:
> >
> >
> > Hello!
> >
> > I've left a new wave of replies.
> >
> > Basically, 1) let's keep DOWNLOAD_URL_PATTERN string value inlined so
> > that it will work even if build process is broken (would be useful for
> e.g.
> > developing out of IDE)
> > And also I urge you to catch() around new fragile Apache JSON API
> > resolving, and download the 'current' version instead, as defined by
> > ignite-mesos version.
> >
> > This is because this module is not under continuouos scrutiny so extra
> > care should be applied.
> > --
> > Ilya Kasnacheev
> >
> >
> > вт, 4 сент. 2018 г. в 13:42, Roman Shtykh <rs...@yahoo.com>:
> >
> > Thanks, Ilya!
> > I will check your comments, and discuss it at JIRA.
> >
> > --
> > Roman Shtykh
> >
> >
> > On Tuesday, September 4, 2018, 7:17:53 p.m. GMT+9, Ilya Kasnacheev <
> > ilya.kasnacheev@gmail.com> wrote:
> >
> >
> > Hello!
> >
> > IGNITE-9408 <https://issues.apache.org/jira/browse/IGNITE-9408> looks
> > good to me and may be merged right away.
> >
> > IGNITE-9388 <https://issues.apache.org/jira/browse/IGNITE-9388> needs
> > more work in my opinion, I have commented the PR. I also advice having
> test
> > for this functionality.
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
> > вт, 4 сент. 2018 г. в 6:52, Roman Shtykh <rs...@yahoo.com.invalid>:
> >
> > 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
> <
> > daradurvs@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 <ni...@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.
> >
> >
>
Re: Apache Ignite 2.7 release
Posted by Ilya Kasnacheev <il...@gmail.com>.
Hello!
So now there's an issue that this script makes source change after every
build, show up in git status.
What we could do to it:
- Commit the changes after the build, once. In hopes that it won't change
very often. With benefit that we could do that right now, before the code
freeze.
- Move these values to a properties file from both pom.xml and
IgniteProvider.java. Any problems with this approach? We'll just read them
from classpath properties file.
- Update the links in the file once and remove them from build process. Why
were they added to build process in the first place - to make them
configurable during build?
Regards,
--
Ilya Kasnacheev
вт, 11 сент. 2018 г. в 5:53, Roman Shtykh <rs...@yahoo.com>:
> Ilya,
>
> The "latest" version is the default, and resolved by
> https://ignite.apache.org/latest which is used by our web site when a
> user download the latest Ignite version. And I think this is the authority
> to judge of the latest official release (pom.xml you suggest can have
> SNAPSHOTs etc.).
> Also, as I explained during our review sessions, ignite-mesos-2.6.0 is a
> driver and doesn't mean you need to have Ignite 2.6.0. User can run any
> version of Ignite he/she specifies. By default, it's "latest" but a user
> can specify any version needed, even from a non-archive URL.
>
> In short, what we have now
> 1. mesos driver (ignite-mesos-x.x.x) will use "latest" version by default
> -> it will try to resolve the latest officially releases version of Apache
> Ignite, find the closest mirror and download Ignite in a minute. If the
> version resolution fails, we fall back to the slow apache archive (as you
> suggest; in my opinion we better fail-fast instead of waiting for hours to
> download, so the user can choose another download option (3))
> 2. If the user specifies the version explicitly, it goes to the slow
> apache archive.
> 3. The user can put ignite zip file on his/her http server and provide the
> URL as a parameter to the driver, if options 1 and 2 don't work.
>
> As you see, there are 3 options. And I just fix the 1st one with
> https://issues.apache.org/jira/browse/IGNITE-9388 and don't change the
> original logic (which I find reasonable) documented on our site -- I don't
> see how it blocks anything.
>
> Roman Shtykh
>
>
> On Monday, September 10, 2018, 6:16:15 p.m. GMT+9, Ilya Kasnacheev <
> ilya.kasnacheev@gmail.com> wrote:
>
>
> Hello!
>
> There's still two issues with the submission.
>
> The first one is that we're downloading "latest" version from preferred
> mirror but a specified version, such as "2.6", we're also going to download
> from "slow" archive.apache.org/dist.
> That's a great limitation for this change, since most real deployments of
> Apache Ignite will have their Ignite version pegged to a specific release.
> But in this case there's no win in download speed.
> *In my opinion it is a blocker.*
>
> The second one is that we can't download anything when we failed to
> resolve "latest". My idea is that we should try and download last known
> version in this case, which can be pushed to source from pom.xml, as we
> already do with URLs. So if you could not resolve "latest" you will
> download 2.7.0.
>
> Buuut, maybe it's not necessary, maybe we should just *discourage
> "latest"*, which is in my opinion almost always a bad idea.
>
> WDYT?
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> вс, 9 сент. 2018 г. в 5:47, Roman Shtykh <rs...@yahoo.com>:
>
> Hi Ilya,
>
> Sorry, missed that.
> Added now.
>
> --
> Roman Shtykh
>
>
> On Thursday, September 6, 2018, 6:16:58 p.m. GMT+9, Ilya Kasnacheev <
> ilya.kasnacheev@gmail.com> wrote:
>
>
> Hello!
>
> The last of my requests still standing is that we should fall-back to
> single URL download in case of error with 'latest' version. Everything else
> looks good to me.
>
> Can we do that? I'm really worried that Apache API will go sour.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> чт, 6 сент. 2018 г. в 8:56, Roman Shtykh <rs...@yahoo.com>:
>
> Hi Ilya,
>
> Thanks again.
>
> 1) Done.
> 2) Used catch() for latest version.
>
> Please see my comments on github.
> --
> Roman Shtykh
>
>
> On Wednesday, September 5, 2018, 11:30:10 p.m. GMT+9, Ilya Kasnacheev <
> ilya.kasnacheev@gmail.com> wrote:
>
>
> Hello!
>
> I've left a new wave of replies.
>
> Basically, 1) let's keep DOWNLOAD_URL_PATTERN string value inlined so
> that it will work even if build process is broken (would be useful for e.g.
> developing out of IDE)
> And also I urge you to catch() around new fragile Apache JSON API
> resolving, and download the 'current' version instead, as defined by
> ignite-mesos version.
>
> This is because this module is not under continuouos scrutiny so extra
> care should be applied.
> --
> Ilya Kasnacheev
>
>
> вт, 4 сент. 2018 г. в 13:42, Roman Shtykh <rs...@yahoo.com>:
>
> Thanks, Ilya!
> I will check your comments, and discuss it at JIRA.
>
> --
> Roman Shtykh
>
>
> On Tuesday, September 4, 2018, 7:17:53 p.m. GMT+9, Ilya Kasnacheev <
> ilya.kasnacheev@gmail.com> wrote:
>
>
> Hello!
>
> IGNITE-9408 <https://issues.apache.org/jira/browse/IGNITE-9408> looks
> good to me and may be merged right away.
>
> IGNITE-9388 <https://issues.apache.org/jira/browse/IGNITE-9388> needs
> more work in my opinion, I have commented the PR. I also advice having test
> for this functionality.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> вт, 4 сент. 2018 г. в 6:52, Roman Shtykh <rs...@yahoo.com.invalid>:
>
> 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 <
> daradurvs@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 <ni...@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.
>
>
Re: Apache Ignite 2.7 release
Posted by Ilya Kasnacheev <il...@gmail.com>.
Hello!
Thank you for the clarifications! Your change looks good to me now.
Regards,
--
Ilya Kasnacheev
вт, 11 сент. 2018 г. в 5:53, Roman Shtykh <rs...@yahoo.com>:
> Ilya,
>
> The "latest" version is the default, and resolved by
> https://ignite.apache.org/latest which is used by our web site when a
> user download the latest Ignite version. And I think this is the authority
> to judge of the latest official release (pom.xml you suggest can have
> SNAPSHOTs etc.).
> Also, as I explained during our review sessions, ignite-mesos-2.6.0 is a
> driver and doesn't mean you need to have Ignite 2.6.0. User can run any
> version of Ignite he/she specifies. By default, it's "latest" but a user
> can specify any version needed, even from a non-archive URL.
>
> In short, what we have now
> 1. mesos driver (ignite-mesos-x.x.x) will use "latest" version by default
> -> it will try to resolve the latest officially releases version of Apache
> Ignite, find the closest mirror and download Ignite in a minute. If the
> version resolution fails, we fall back to the slow apache archive (as you
> suggest; in my opinion we better fail-fast instead of waiting for hours to
> download, so the user can choose another download option (3))
> 2. If the user specifies the version explicitly, it goes to the slow
> apache archive.
> 3. The user can put ignite zip file on his/her http server and provide the
> URL as a parameter to the driver, if options 1 and 2 don't work.
>
> As you see, there are 3 options. And I just fix the 1st one with
> https://issues.apache.org/jira/browse/IGNITE-9388 and don't change the
> original logic (which I find reasonable) documented on our site -- I don't
> see how it blocks anything.
>
> Roman Shtykh
>
>
> On Monday, September 10, 2018, 6:16:15 p.m. GMT+9, Ilya Kasnacheev <
> ilya.kasnacheev@gmail.com> wrote:
>
>
> Hello!
>
> There's still two issues with the submission.
>
> The first one is that we're downloading "latest" version from preferred
> mirror but a specified version, such as "2.6", we're also going to download
> from "slow" archive.apache.org/dist.
> That's a great limitation for this change, since most real deployments of
> Apache Ignite will have their Ignite version pegged to a specific release.
> But in this case there's no win in download speed.
> *In my opinion it is a blocker.*
>
> The second one is that we can't download anything when we failed to
> resolve "latest". My idea is that we should try and download last known
> version in this case, which can be pushed to source from pom.xml, as we
> already do with URLs. So if you could not resolve "latest" you will
> download 2.7.0.
>
> Buuut, maybe it's not necessary, maybe we should just *discourage
> "latest"*, which is in my opinion almost always a bad idea.
>
> WDYT?
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> вс, 9 сент. 2018 г. в 5:47, Roman Shtykh <rs...@yahoo.com>:
>
> Hi Ilya,
>
> Sorry, missed that.
> Added now.
>
> --
> Roman Shtykh
>
>
> On Thursday, September 6, 2018, 6:16:58 p.m. GMT+9, Ilya Kasnacheev <
> ilya.kasnacheev@gmail.com> wrote:
>
>
> Hello!
>
> The last of my requests still standing is that we should fall-back to
> single URL download in case of error with 'latest' version. Everything else
> looks good to me.
>
> Can we do that? I'm really worried that Apache API will go sour.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> чт, 6 сент. 2018 г. в 8:56, Roman Shtykh <rs...@yahoo.com>:
>
> Hi Ilya,
>
> Thanks again.
>
> 1) Done.
> 2) Used catch() for latest version.
>
> Please see my comments on github.
> --
> Roman Shtykh
>
>
> On Wednesday, September 5, 2018, 11:30:10 p.m. GMT+9, Ilya Kasnacheev <
> ilya.kasnacheev@gmail.com> wrote:
>
>
> Hello!
>
> I've left a new wave of replies.
>
> Basically, 1) let's keep DOWNLOAD_URL_PATTERN string value inlined so
> that it will work even if build process is broken (would be useful for e.g.
> developing out of IDE)
> And also I urge you to catch() around new fragile Apache JSON API
> resolving, and download the 'current' version instead, as defined by
> ignite-mesos version.
>
> This is because this module is not under continuouos scrutiny so extra
> care should be applied.
> --
> Ilya Kasnacheev
>
>
> вт, 4 сент. 2018 г. в 13:42, Roman Shtykh <rs...@yahoo.com>:
>
> Thanks, Ilya!
> I will check your comments, and discuss it at JIRA.
>
> --
> Roman Shtykh
>
>
> On Tuesday, September 4, 2018, 7:17:53 p.m. GMT+9, Ilya Kasnacheev <
> ilya.kasnacheev@gmail.com> wrote:
>
>
> Hello!
>
> IGNITE-9408 <https://issues.apache.org/jira/browse/IGNITE-9408> looks
> good to me and may be merged right away.
>
> IGNITE-9388 <https://issues.apache.org/jira/browse/IGNITE-9388> needs
> more work in my opinion, I have commented the PR. I also advice having test
> for this functionality.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> вт, 4 сент. 2018 г. в 6:52, Roman Shtykh <rs...@yahoo.com.invalid>:
>
> 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 <
> daradurvs@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 <ni...@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.
>
>
Re: Apache Ignite 2.7 release
Posted by Roman Shtykh <rs...@yahoo.com.INVALID>.
Ilya,
The "latest" version is the default, and resolved by https://ignite.apache.org/latest which is used by our web site when a user download the latest Ignite version. And I think this is the authority to judge of the latest official release (pom.xml you suggest can have SNAPSHOTs etc.).Also, as I explained during our review sessions, ignite-mesos-2.6.0 is a driver and doesn't mean you need to have Ignite 2.6.0. User can run any version of Ignite he/she specifies. By default, it's "latest" but a user can specify any version needed, even from a non-archive URL.
In short, what we have now1. mesos driver (ignite-mesos-x.x.x) will use "latest" version by default -> it will try to resolve the latest officially releases version of Apache Ignite, find the closest mirror and download Ignite in a minute. If the version resolution fails, we fall back to the slow apache archive (as you suggest; in my opinion we better fail-fast instead of waiting for hours to download, so the user can choose another download option (3))2. If the user specifies the version explicitly, it goes to the slow apache archive.
3. The user can put ignite zip file on his/her http server and provide the URL as a parameter to the driver, if options 1 and 2 don't work.
As you see, there are 3 options. And I just fix the 1st one with https://issues.apache.org/jira/browse/IGNITE-9388 and don't change the original logic (which I find reasonable) documented on our site -- I don't see how it blocks anything.
Roman Shtykh
On Monday, September 10, 2018, 6:16:15 p.m. GMT+9, Ilya Kasnacheev <il...@gmail.com> wrote:
Hello!
There's still two issues with the submission.
The first one is that we're downloading "latest" version from preferred mirror but a specified version, such as "2.6", we're also going to download from "slow" archive.apache.org/dist.That's a great limitation for this change, since most real deployments of Apache Ignite will have their Ignite version pegged to a specific release. But in this case there's no win in download speed.In my opinion it is a blocker.
The second one is that we can't download anything when we failed to resolve "latest". My idea is that we should try and download last known version in this case, which can be pushed to source from pom.xml, as we already do with URLs. So if you could not resolve "latest" you will download 2.7.0.
Buuut, maybe it's not necessary, maybe we should just discourage "latest", which is in my opinion almost always a bad idea.
WDYT?
Regards,
--
Ilya Kasnacheev
вс, 9 сент. 2018 г. в 5:47, Roman Shtykh <rs...@yahoo.com>:
Hi Ilya,
Sorry, missed that.
Added now.
--
Roman Shtykh
On Thursday, September 6, 2018, 6:16:58 p.m. GMT+9, Ilya Kasnacheev <il...@gmail.com> wrote:
Hello!
The last of my requests still standing is that we should fall-back to single URL download in case of error with 'latest' version. Everything else looks good to me.
Can we do that? I'm really worried that Apache API will go sour.
Regards,
--
Ilya Kasnacheev
чт, 6 сент. 2018 г. в 8:56, Roman Shtykh <rs...@yahoo.com>:
Hi Ilya,
Thanks again.
1) Done.2) Used catch() for latest version.
Please see my comments on github.
--
Roman Shtykh
On Wednesday, September 5, 2018, 11:30:10 p.m. GMT+9, Ilya Kasnacheev <il...@gmail.com> wrote:
Hello!
I've left a new wave of replies.
Basically, 1) let's keep DOWNLOAD_URL_PATTERN string value inlined so that it will work even if build process is broken (would be useful for e.g. developing out of IDE)
And also I urge you to catch() around new fragile Apache JSON API resolving, and download the 'current' version instead, as defined by ignite-mesos version.
This is because this module is not under continuouos scrutiny so extra care should be applied.--
Ilya Kasnacheev
вт, 4 сент. 2018 г. в 13:42, Roman Shtykh <rs...@yahoo.com>:
Thanks, Ilya!I will check your comments, and discuss it at JIRA.
--
Roman Shtykh
On Tuesday, September 4, 2018, 7:17:53 p.m. GMT+9, Ilya Kasnacheev <il...@gmail.com> wrote:
Hello!
IGNITE-9408 looks good to me and may be merged right away.
IGNITE-9388 needs more work in my opinion, I have commented the PR. I also advice having test for this functionality.
Regards,
--
Ilya Kasnacheev
вт, 4 сент. 2018 г. в 6:52, Roman Shtykh <rs...@yahoo.com.invalid>:
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 <da...@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 <ni...@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.
Re: Apache Ignite 2.7 release
Posted by Ilya Kasnacheev <il...@gmail.com>.
Hello!
There's still two issues with the submission.
The first one is that we're downloading "latest" version from preferred
mirror but a specified version, such as "2.6", we're also going to download
from "slow" archive.apache.org/dist.
That's a great limitation for this change, since most real deployments of
Apache Ignite will have their Ignite version pegged to a specific release.
But in this case there's no win in download speed.
*In my opinion it is a blocker.*
The second one is that we can't download anything when we failed to resolve
"latest". My idea is that we should try and download last known version in
this case, which can be pushed to source from pom.xml, as we already do
with URLs. So if you could not resolve "latest" you will download 2.7.0.
Buuut, maybe it's not necessary, maybe we should just *discourage "latest"*,
which is in my opinion almost always a bad idea.
WDYT?
Regards,
--
Ilya Kasnacheev
вс, 9 сент. 2018 г. в 5:47, Roman Shtykh <rs...@yahoo.com>:
> Hi Ilya,
>
> Sorry, missed that.
> Added now.
>
> --
> Roman Shtykh
>
>
> On Thursday, September 6, 2018, 6:16:58 p.m. GMT+9, Ilya Kasnacheev <
> ilya.kasnacheev@gmail.com> wrote:
>
>
> Hello!
>
> The last of my requests still standing is that we should fall-back to
> single URL download in case of error with 'latest' version. Everything else
> looks good to me.
>
> Can we do that? I'm really worried that Apache API will go sour.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> чт, 6 сент. 2018 г. в 8:56, Roman Shtykh <rs...@yahoo.com>:
>
> Hi Ilya,
>
> Thanks again.
>
> 1) Done.
> 2) Used catch() for latest version.
>
> Please see my comments on github.
> --
> Roman Shtykh
>
>
> On Wednesday, September 5, 2018, 11:30:10 p.m. GMT+9, Ilya Kasnacheev <
> ilya.kasnacheev@gmail.com> wrote:
>
>
> Hello!
>
> I've left a new wave of replies.
>
> Basically, 1) let's keep DOWNLOAD_URL_PATTERN string value inlined so
> that it will work even if build process is broken (would be useful for e.g.
> developing out of IDE)
> And also I urge you to catch() around new fragile Apache JSON API
> resolving, and download the 'current' version instead, as defined by
> ignite-mesos version.
>
> This is because this module is not under continuouos scrutiny so extra
> care should be applied.
> --
> Ilya Kasnacheev
>
>
> вт, 4 сент. 2018 г. в 13:42, Roman Shtykh <rs...@yahoo.com>:
>
> Thanks, Ilya!
> I will check your comments, and discuss it at JIRA.
>
> --
> Roman Shtykh
>
>
> On Tuesday, September 4, 2018, 7:17:53 p.m. GMT+9, Ilya Kasnacheev <
> ilya.kasnacheev@gmail.com> wrote:
>
>
> Hello!
>
> IGNITE-9408 <https://issues.apache.org/jira/browse/IGNITE-9408> looks
> good to me and may be merged right away.
>
> IGNITE-9388 <https://issues.apache.org/jira/browse/IGNITE-9388> needs
> more work in my opinion, I have commented the PR. I also advice having test
> for this functionality.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> вт, 4 сент. 2018 г. в 6:52, Roman Shtykh <rs...@yahoo.com.invalid>:
>
> 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 <
> daradurvs@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 <ni...@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.
>
>
Re: Apache Ignite 2.7 release
Posted by Roman Shtykh <rs...@yahoo.com.INVALID>.
Thanks, Ilya!I will check your comments, and discuss it at JIRA.
--
Roman Shtykh
On Tuesday, September 4, 2018, 7:17:53 p.m. GMT+9, Ilya Kasnacheev <il...@gmail.com> wrote:
Hello!
IGNITE-9408 looks good to me and may be merged right away.
IGNITE-9388 needs more work in my opinion, I have commented the PR. I also advice having test for this functionality.
Regards,
--
Ilya Kasnacheev
вт, 4 сент. 2018 г. в 6:52, Roman Shtykh <rs...@yahoo.com.invalid>:
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 <da...@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 <ni...@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.
Re: Apache Ignite 2.7 release
Posted by Ilya Kasnacheev <il...@gmail.com>.
Hello!
IGNITE-9408 <https://issues.apache.org/jira/browse/IGNITE-9408> looks good
to me and may be merged right away.
IGNITE-9388 <https://issues.apache.org/jira/browse/IGNITE-9388> needs more
work in my opinion, I have commented the PR. I also advice having test for
this functionality.
Regards,
--
Ilya Kasnacheev
вт, 4 сент. 2018 г. в 6:52, Roman Shtykh <rs...@yahoo.com.invalid>:
> 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 <
> daradurvs@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 <ni...@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.
Re: Apache Ignite 2.7 release
Posted by Roman Shtykh <rs...@yahoo.com.INVALID>.
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 <da...@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 <ni...@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.
Re: Apache Ignite 2.7 release
Posted by Vyacheslav Daradur <da...@gmail.com>.
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 <ni...@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.
Re: Apache Ignite 2.7 release
Posted by Nikolay Izhikov <ni...@apache.org>.
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
Re: Apache Ignite 2.7 release
Posted by Yakov Zhdanov <yz...@apache.org>.
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
Re: Apache Ignite 2.7 release
Posted by Maxim Muzafarov <ma...@gmail.com>.
Denis, Nikolai,
Suppose, issue IGNITE-7165 [1] is already included in the release scope,
but I think I can mention it here.
It's about re-balance optimization - now client node join\left doesn't
affect re-balance process.
In general, it's not so much about client node as about if assignments not
change re-balance will not
be interrupted. I've provided all implementation details in JIRA comment
[2]. Hope it will help
someone with further optimizations.
[1] https://issues.apache.org/jira/browse/IGNITE-7165
[2]
https://issues.apache.org/jira/browse/IGNITE-7165?focusedCommentId=16561092&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16561092
On Wed, 29 Aug 2018 at 02:43 Denis Magda <dm...@apache.org> wrote:
> Nikolay, Igniters, let me help you with the list.
>
> That what I was tracking on my side (something we can announce). Don't have
> a JIRA ticket for every ticket but CC-ed everyone who claimed to be in
> charge. Nikolay, please work with the community members to add these
> capabilities to the release wiki page. If something doesn't get delivered
> then let's exclude it.
>
> 1. Partition map exchange optimizations. Are we releasing any of them?
> *(Sergey
> Chugunov, Andrey Mashenkov)*
>
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-25%3A+Partition+Map+Exchange+hangs+resolving
>
> 2. Java 9/10/11 Support. Are we on track to support it better? *(Peter,
> Vladimir)*.
>
> 3. SQL *(Vladimir)*:
>
> - Transactional SQL beta?
> - Basic monitoring facilities (inline index alerts, page reads/writes
> per type)?
> - SQL index update optimizations? (
>
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-19%3A+SQL+index+update+optimizations
> )
> - ODBC/JDBC session management
> - Result set offload to disk. Looks it doesn't get to the release?
> https://issues.apache.org/jira/browse/IGNITE-7526
>
> 4. JCache 1.1 support. Completed!
>
> 5. Transparent data encryption? What exactly goes in 2.7? *(Nikolay)*.
>
> 6. Ignite + Informatica integration
>
> 7. Ignite and Spring Session integration (heard it was done but the ticket
> is still Open):
> https://issues.apache.org/jira/browse/IGNITE-2741
>
> 8. Service Grid 2.0. What exactly goes in 2.7? (*Vyacheslav)*
>
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-17%3A+Oil+Change+in+Service+Grid
>
> 9. Ignite Multi Map *(Amir, Anton)*
> https://issues.apache.org/jira/browse/IGNITE-640
>
> 10. Thin Clients:
>
> - Node.JS (https://issues.apache.org/jira/browse/IGNITE-7777) - *Pavel
> Petroshenko*
> - Python (https://issues.apache.org/jira/browse/IGNITE-7782) - *Pavel
> Petroshenko, **Dmitry Melnichuk*
> - PHP (https://issues.apache.org/jira/browse/IGNITE-7783) - *Pavel P.,
> Ekaterina*
> - C++: *Igor S.*
> - Affinity awareness for thin clients (*Igor S.*):
>
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-23%3A+Best+Effort+Affinity+for+thin+clients
>
> 11. Machine and Deep Learning (preprocessing APIs, TensorFlow integration,
> extra algorithms) - *Yuri and our ML experts*
>
>
>
> On Tue, Aug 28, 2018 at 10:17 AM Dmitriy Setrakyan <ds...@apache.org>
> wrote:
>
> > Hi Nikolai,
> >
> > Generally looks OK, however, It is hard to comment on your schedule
> without
> > seeing a full list of all must-have features we plan to add to this
> > release. I am hoping that the community will see this list at some point.
> >
> > D.
> >
> > On Tue, Aug 28, 2018 at 8:23 AM, Nikolay Izhikov <ni...@apache.org>
> > wrote:
> >
> > > Hello, Igniters.
> > >
> > > I think we should discuss the release schedule.
> > >
> > > Current dates are following:
> > >
> > > * Code Freeze: September 30, 2018
> > > * Voting Date: October 1, 2018
> > > * Release Date: October 15, 2018
> > >
> > > We discussed it privately with Vladimir Ozerov.
> > >
> > > Is seems better to reschedule a bit:
> > >
> > > * 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 - October 08.
> > >
> > > What do you think?
> > >
> > >
> > > В Сб, 25/08/2018 в 00:57 +0300, Dmitriy Pavlov пишет:
> > > > I hope Vyacheslav can comment better than me. I suppose it is, more
> or
> > > > less, rectifications and clarifications of design aspects. Not
> overall
> > > > redesign.
> > > >
> > > > I also hope Igniters, especially Services experts, will join the
> > > discussion
> > > > in the separate topic. Now after a couple of days there is no
> reaction.
> > > >
> > > > сб, 25 авг. 2018 г. в 0:53, Dmitriy Setrakyan <dsetrakyan@apache.org
> >:
> > > >
> > > > > On Fri, Aug 24, 2018 at 2:50 PM, Dmitriy Pavlov <
> > dpavlov.spb@gmail.com
> > > >
> > > > > wrote:
> > > > >
> > > > > > Hi Dmitriy, I suppose it highly depends on how fast community
> will
> > > come
> > > > >
> > > > > to
> > > > > > a consensus about design. So it is up to us to make this happen
> > > > > >
> > > > >
> > > > > I am confused then. If we are still discussing design, then we are
> > > miles
> > > > > away. Do you know if there anything in service grid that has
> already
> > > been
> > > > > implemented and can be released?
> > > > >
> > >
> >
>
--
--
Maxim Muzafarov
Re: Apache Ignite 2.7 release
Posted by Юрий Бабак <y....@gmail.com>.
Denis, Nikolay, Igniters,
This is a list of planned ML features for Apache Ignite 2.7 release:
- Tensor Flow integration (
https://issues.apache.org/jira/browse/IGNITE-8670)
- Data preprocessing (https://issues.apache.org/jira/browse/IGNITE-8662)
- Model validation (https://issues.apache.org/jira/browse/IGNITE-8665)
- Random forest algorithm (
https://issues.apache.org/jira/browse/IGNITE-8840)
- Gradient boosted trees (
https://issues.apache.org/jira/browse/IGNITE-7149)
- ANN algorithm (https://issues.apache.org/jira/browse/IGNITE-9261)
- ML tutorial (https://issues.apache.org/jira/browse/IGNITE-8741)
- And other improvements of ML module like a bugfixes, code cleanup,
optimizations, etc
Regards,
Yury
ср, 29 авг. 2018 г. в 2:43, Denis Magda <dm...@apache.org>:
> Nikolay, Igniters, let me help you with the list.
>
> That what I was tracking on my side (something we can announce). Don't have
> a JIRA ticket for every ticket but CC-ed everyone who claimed to be in
> charge. Nikolay, please work with the community members to add these
> capabilities to the release wiki page. If something doesn't get delivered
> then let's exclude it.
>
> 1. Partition map exchange optimizations. Are we releasing any of them?
> *(Sergey
> Chugunov, Andrey Mashenkov)*
>
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-25%3A+Partition+Map+Exchange+hangs+resolving
>
> 2. Java 9/10/11 Support. Are we on track to support it better? *(Peter,
> Vladimir)*.
>
> 3. SQL *(Vladimir)*:
>
> - Transactional SQL beta?
> - Basic monitoring facilities (inline index alerts, page reads/writes
> per type)?
> - SQL index update optimizations? (
>
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-19%3A+SQL+index+update+optimizations
> )
> - ODBC/JDBC session management
> - Result set offload to disk. Looks it doesn't get to the release?
> https://issues.apache.org/jira/browse/IGNITE-7526
>
> 4. JCache 1.1 support. Completed!
>
> 5. Transparent data encryption? What exactly goes in 2.7? *(Nikolay)*.
>
> 6. Ignite + Informatica integration
>
> 7. Ignite and Spring Session integration (heard it was done but the ticket
> is still Open):
> https://issues.apache.org/jira/browse/IGNITE-2741
>
> 8. Service Grid 2.0. What exactly goes in 2.7? (*Vyacheslav)*
>
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-17%3A+Oil+Change+in+Service+Grid
>
> 9. Ignite Multi Map *(Amir, Anton)*
> https://issues.apache.org/jira/browse/IGNITE-640
>
> 10. Thin Clients:
>
> - Node.JS (https://issues.apache.org/jira/browse/IGNITE-7777) - *Pavel
> Petroshenko*
> - Python (https://issues.apache.org/jira/browse/IGNITE-7782) - *Pavel
> Petroshenko, **Dmitry Melnichuk*
> - PHP (https://issues.apache.org/jira/browse/IGNITE-7783) - *Pavel P.,
> Ekaterina*
> - C++: *Igor S.*
> - Affinity awareness for thin clients (*Igor S.*):
>
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-23%3A+Best+Effort+Affinity+for+thin+clients
>
> 11. Machine and Deep Learning (preprocessing APIs, TensorFlow integration,
> extra algorithms) - *Yuri and our ML experts*
>
>
>
> On Tue, Aug 28, 2018 at 10:17 AM Dmitriy Setrakyan <ds...@apache.org>
> wrote:
>
> > Hi Nikolai,
> >
> > Generally looks OK, however, It is hard to comment on your schedule
> without
> > seeing a full list of all must-have features we plan to add to this
> > release. I am hoping that the community will see this list at some point.
> >
> > D.
> >
> > On Tue, Aug 28, 2018 at 8:23 AM, Nikolay Izhikov <ni...@apache.org>
> > wrote:
> >
> > > Hello, Igniters.
> > >
> > > I think we should discuss the release schedule.
> > >
> > > Current dates are following:
> > >
> > > * Code Freeze: September 30, 2018
> > > * Voting Date: October 1, 2018
> > > * Release Date: October 15, 2018
> > >
> > > We discussed it privately with Vladimir Ozerov.
> > >
> > > Is seems better to reschedule a bit:
> > >
> > > * 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 - October 08.
> > >
> > > What do you think?
> > >
> > >
> > > В Сб, 25/08/2018 в 00:57 +0300, Dmitriy Pavlov пишет:
> > > > I hope Vyacheslav can comment better than me. I suppose it is, more
> or
> > > > less, rectifications and clarifications of design aspects. Not
> overall
> > > > redesign.
> > > >
> > > > I also hope Igniters, especially Services experts, will join the
> > > discussion
> > > > in the separate topic. Now after a couple of days there is no
> reaction.
> > > >
> > > > сб, 25 авг. 2018 г. в 0:53, Dmitriy Setrakyan <dsetrakyan@apache.org
> >:
> > > >
> > > > > On Fri, Aug 24, 2018 at 2:50 PM, Dmitriy Pavlov <
> > dpavlov.spb@gmail.com
> > > >
> > > > > wrote:
> > > > >
> > > > > > Hi Dmitriy, I suppose it highly depends on how fast community
> will
> > > come
> > > > >
> > > > > to
> > > > > > a consensus about design. So it is up to us to make this happen
> > > > > >
> > > > >
> > > > > I am confused then. If we are still discussing design, then we are
> > > miles
> > > > > away. Do you know if there anything in service grid that has
> already
> > > been
> > > > > implemented and can be released?
> > > > >
> > >
> >
>
Re: Apache Ignite 2.7 release
Posted by Denis Magda <dm...@apache.org>.
Nikolay, Igniters, let me help you with the list.
That what I was tracking on my side (something we can announce). Don't have
a JIRA ticket for every ticket but CC-ed everyone who claimed to be in
charge. Nikolay, please work with the community members to add these
capabilities to the release wiki page. If something doesn't get delivered
then let's exclude it.
1. Partition map exchange optimizations. Are we releasing any of them? *(Sergey
Chugunov, Andrey Mashenkov)*
https://cwiki.apache.org/confluence/display/IGNITE/IEP-25%3A+Partition+Map+Exchange+hangs+resolving
2. Java 9/10/11 Support. Are we on track to support it better? *(Peter,
Vladimir)*.
3. SQL *(Vladimir)*:
- Transactional SQL beta?
- Basic monitoring facilities (inline index alerts, page reads/writes
per type)?
- SQL index update optimizations? (
https://cwiki.apache.org/confluence/display/IGNITE/IEP-19%3A+SQL+index+update+optimizations
)
- ODBC/JDBC session management
- Result set offload to disk. Looks it doesn't get to the release?
https://issues.apache.org/jira/browse/IGNITE-7526
4. JCache 1.1 support. Completed!
5. Transparent data encryption? What exactly goes in 2.7? *(Nikolay)*.
6. Ignite + Informatica integration
7. Ignite and Spring Session integration (heard it was done but the ticket
is still Open):
https://issues.apache.org/jira/browse/IGNITE-2741
8. Service Grid 2.0. What exactly goes in 2.7? (*Vyacheslav)*
https://cwiki.apache.org/confluence/display/IGNITE/IEP-17%3A+Oil+Change+in+Service+Grid
9. Ignite Multi Map *(Amir, Anton)*
https://issues.apache.org/jira/browse/IGNITE-640
10. Thin Clients:
- Node.JS (https://issues.apache.org/jira/browse/IGNITE-7777) - *Pavel
Petroshenko*
- Python (https://issues.apache.org/jira/browse/IGNITE-7782) - *Pavel
Petroshenko, **Dmitry Melnichuk*
- PHP (https://issues.apache.org/jira/browse/IGNITE-7783) - *Pavel P.,
Ekaterina*
- C++: *Igor S.*
- Affinity awareness for thin clients (*Igor S.*):
https://cwiki.apache.org/confluence/display/IGNITE/IEP-23%3A+Best+Effort+Affinity+for+thin+clients
11. Machine and Deep Learning (preprocessing APIs, TensorFlow integration,
extra algorithms) - *Yuri and our ML experts*
On Tue, Aug 28, 2018 at 10:17 AM Dmitriy Setrakyan <ds...@apache.org>
wrote:
> Hi Nikolai,
>
> Generally looks OK, however, It is hard to comment on your schedule without
> seeing a full list of all must-have features we plan to add to this
> release. I am hoping that the community will see this list at some point.
>
> D.
>
> On Tue, Aug 28, 2018 at 8:23 AM, Nikolay Izhikov <ni...@apache.org>
> wrote:
>
> > Hello, Igniters.
> >
> > I think we should discuss the release schedule.
> >
> > Current dates are following:
> >
> > * Code Freeze: September 30, 2018
> > * Voting Date: October 1, 2018
> > * Release Date: October 15, 2018
> >
> > We discussed it privately with Vladimir Ozerov.
> >
> > Is seems better to reschedule a bit:
> >
> > * 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 - October 08.
> >
> > What do you think?
> >
> >
> > В Сб, 25/08/2018 в 00:57 +0300, Dmitriy Pavlov пишет:
> > > I hope Vyacheslav can comment better than me. I suppose it is, more or
> > > less, rectifications and clarifications of design aspects. Not overall
> > > redesign.
> > >
> > > I also hope Igniters, especially Services experts, will join the
> > discussion
> > > in the separate topic. Now after a couple of days there is no reaction.
> > >
> > > сб, 25 авг. 2018 г. в 0:53, Dmitriy Setrakyan <ds...@apache.org>:
> > >
> > > > On Fri, Aug 24, 2018 at 2:50 PM, Dmitriy Pavlov <
> dpavlov.spb@gmail.com
> > >
> > > > wrote:
> > > >
> > > > > Hi Dmitriy, I suppose it highly depends on how fast community will
> > come
> > > >
> > > > to
> > > > > a consensus about design. So it is up to us to make this happen
> > > > >
> > > >
> > > > I am confused then. If we are still discussing design, then we are
> > miles
> > > > away. Do you know if there anything in service grid that has already
> > been
> > > > implemented and can be released?
> > > >
> >
>
Re: Apache Ignite 2.7 release
Posted by Dmitriy Setrakyan <ds...@apache.org>.
Hi Nikolai,
Generally looks OK, however, It is hard to comment on your schedule without
seeing a full list of all must-have features we plan to add to this
release. I am hoping that the community will see this list at some point.
D.
On Tue, Aug 28, 2018 at 8:23 AM, Nikolay Izhikov <ni...@apache.org>
wrote:
> Hello, Igniters.
>
> I think we should discuss the release schedule.
>
> Current dates are following:
>
> * Code Freeze: September 30, 2018
> * Voting Date: October 1, 2018
> * Release Date: October 15, 2018
>
> We discussed it privately with Vladimir Ozerov.
>
> Is seems better to reschedule a bit:
>
> * 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 - October 08.
>
> What do you think?
>
>
> В Сб, 25/08/2018 в 00:57 +0300, Dmitriy Pavlov пишет:
> > I hope Vyacheslav can comment better than me. I suppose it is, more or
> > less, rectifications and clarifications of design aspects. Not overall
> > redesign.
> >
> > I also hope Igniters, especially Services experts, will join the
> discussion
> > in the separate topic. Now after a couple of days there is no reaction.
> >
> > сб, 25 авг. 2018 г. в 0:53, Dmitriy Setrakyan <ds...@apache.org>:
> >
> > > On Fri, Aug 24, 2018 at 2:50 PM, Dmitriy Pavlov <dpavlov.spb@gmail.com
> >
> > > wrote:
> > >
> > > > Hi Dmitriy, I suppose it highly depends on how fast community will
> come
> > >
> > > to
> > > > a consensus about design. So it is up to us to make this happen
> > > >
> > >
> > > I am confused then. If we are still discussing design, then we are
> miles
> > > away. Do you know if there anything in service grid that has already
> been
> > > implemented and can be released?
> > >
>
Re: Apache Ignite 2.7 release
Posted by Nikolay Izhikov <ni...@apache.org>.
Hello, Igniters.
I think we should discuss the release schedule.
Current dates are following:
* Code Freeze: September 30, 2018
* Voting Date: October 1, 2018
* Release Date: October 15, 2018
We discussed it privately with Vladimir Ozerov.
Is seems better to reschedule a bit:
* 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 - October 08.
What do you think?
В Сб, 25/08/2018 в 00:57 +0300, Dmitriy Pavlov пишет:
> I hope Vyacheslav can comment better than me. I suppose it is, more or
> less, rectifications and clarifications of design aspects. Not overall
> redesign.
>
> I also hope Igniters, especially Services experts, will join the discussion
> in the separate topic. Now after a couple of days there is no reaction.
>
> сб, 25 авг. 2018 г. в 0:53, Dmitriy Setrakyan <ds...@apache.org>:
>
> > On Fri, Aug 24, 2018 at 2:50 PM, Dmitriy Pavlov <dp...@gmail.com>
> > wrote:
> >
> > > Hi Dmitriy, I suppose it highly depends on how fast community will come
> >
> > to
> > > a consensus about design. So it is up to us to make this happen
> > >
> >
> > I am confused then. If we are still discussing design, then we are miles
> > away. Do you know if there anything in service grid that has already been
> > implemented and can be released?
> >
Re: Apache Ignite 2.7 release
Posted by Dmitriy Pavlov <dp...@gmail.com>.
I hope Vyacheslav can comment better than me. I suppose it is, more or
less, rectifications and clarifications of design aspects. Not overall
redesign.
I also hope Igniters, especially Services experts, will join the discussion
in the separate topic. Now after a couple of days there is no reaction.
сб, 25 авг. 2018 г. в 0:53, Dmitriy Setrakyan <ds...@apache.org>:
> On Fri, Aug 24, 2018 at 2:50 PM, Dmitriy Pavlov <dp...@gmail.com>
> wrote:
>
> > Hi Dmitriy, I suppose it highly depends on how fast community will come
> to
> > a consensus about design. So it is up to us to make this happen
> >
>
> I am confused then. If we are still discussing design, then we are miles
> away. Do you know if there anything in service grid that has already been
> implemented and can be released?
>
Re: Apache Ignite 2.7 release
Posted by Dmitriy Setrakyan <ds...@apache.org>.
On Fri, Aug 24, 2018 at 2:50 PM, Dmitriy Pavlov <dp...@gmail.com>
wrote:
> Hi Dmitriy, I suppose it highly depends on how fast community will come to
> a consensus about design. So it is up to us to make this happen
>
I am confused then. If we are still discussing design, then we are miles
away. Do you know if there anything in service grid that has already been
implemented and can be released?
Re: Apache Ignite 2.7 release
Posted by Dmitriy Pavlov <dp...@gmail.com>.
Hi Dmitriy, I suppose it highly depends on how fast community will come to
a consensus about design. So it is up to us to make this happen
сб, 25 авг. 2018 г. в 0:05, Dmitriy Setrakyan <ds...@apache.org>:
> Nikolai,
>
> To my knowledge, some significant changes to the service grid
> implementation were going to make it into 2.7. However, I am right now
> seeing other threads about the service grid in which the new design is just
> being discussed. This shows that service grid is not release ready.
>
> Do you know whether it is ready or not? Can we get a list of tickets on the
> service grid that we should be monitoring?
>
> D.
>
>
> On Fri, Aug 24, 2018 at 5:01 AM, Nikolay Izhikov <ni...@apache.org>
> wrote:
>
> > Hello, Yakov.
> >
> > Blocker Tickets.
> >
> > Open:
> >
> > IGNITE-9184 Mikhail Cherkasov Cluster hangs during concurrent
> > node restart and continues query registration
> > IGNITE-8552 Vladimir Ozerov Unable to use date as
> > primary key
> > IGNITE-6980 Aleksey Plekhanov Automatic cancelling of hanging
> > Ignite operations
> > IGNITE-8671 Peter Ivanov Provide instructions on running
> > Apache Ignite on Windows 10 WSL Environment
> > IGNITE-7009 Vladimir Ozerov NPE when Ignite persistence is
> > enabled for Hadoop accelerator
> > IGNITE-8803 Alexey Goncharuk Need to fix Ignite QUIET log
> output
> > IGNITE-8802 Alexey Goncharuk Need to fix Ignite INFO output
> > IGNITE-5618 Dmitriy Pavlov .NET: Ignite fails with OOM on
> > startup under x86 (32 bit) with default configuration
> > IGNITE-9352 Unassigned Web Console: Investigate how
> > correctly use package-lock.json
> > IGNITE-9347 Unassigned Attempt to start a dynamic cache
> > with invalid configuration leads to exchange worker death
> > IGNITE-9202 Unassigned .NET `TestRemoteNodes` fails with
> > "Failed to map SQL query to topology"
> > IGNITE-7793 Unassigned SQL does not work if value has
> > index filed which name equals to affinity key name
> > IGNITE-8890 Unassigned Ignite YARN Kerberos - Delegation
> > Token renewal
> > IGNITE-8771 Unassigned OutOfMemory in Cache2 suite in
> > master branch on TC
> > IGNITE-8770 Unassigned OutOfMemory in Queries1 suite in
> > master branch on TC
> > IGNITE-8767 Unassigned JavaClient test suite times out
> in
> > master branch
> > IGNITE-5302 Unassigned Empty LOST partition may be used
> > as OWNING after resetting lost partitions
> > IGNITE-7813 Unassigned Method org/apache/ignite/cache/
> > hibernate/HibernateRegionFactory.start(Lorg/hibernate/boot/spi/
> > SessionFactoryOptions;Ljava/util/Properties;)V is abstract
> > IGNITE-8523 Unassigned Java and Scala spark examples are
> > mixed
> > IGNITE-8772 Unassigned WebSessionFilter does not work
> > with jetty 9.4 anymore
> > IGNITE-6064 Unassigned Rework control.sh script
> > IGNITE-8454 Unassigned Hadoop module compilation failure
> > under JDK9
> > IGNITE-7620 Unassigned Not able to run query in Ignite
> > YARN
> >
> > In Progress:
> >
> >
> > IGNITE-9305 Pavel Pereslegin Wrong off-heap size is reported
> > for a node
> > IGNITE-7728 Artem Budnikov Put together a doc that shows how
> > to blend SQL with k/v APIs
> > IGNITE-7721 ruchir choudhry Apache Ignite web session
> > clustering stack after login success
> >
> > Patch Available:
> >
> > IGNITE-9068 Ilya Lantukh Node fails to stop when
> > CacheObjectBinaryProcessor.addMeta() is executed inside guard()/unguard()
> > IGNITE-7251 Anton Vinogradov Remove term "fabric" from Ignite
> > deliverables
> > IGNITE-9030 Peter Ivanov Apache Ignite 2.7 Linux packages
> > version update
> >
> > В Пт, 24/08/2018 в 14:47 +0300, Yakov Zhdanov пишет:
> > > Igniters,
> > >
> > > We should definitely expand the list of important tickets adding
> tickets
> > > related to (1) Partition Map Exchange speed up and (2) SQL memory
> > > optimization tickets. Alex Goncharuk, Vladimir, can you please add
> labels
> > > to corresponding tickets.
> > >
> > > Also we have several blocker tickets (mostly related to failing tests)
> > not
> > > yet assigned to anyone. Nikolay, can you please list those tickets and
> > ask
> > > community to pick them up?
> > >
> > > We have 556 open tickets now according to [1]. This seems a bit to
> much.
> > > Can I ask everyone to review tickets assigned to yourselves and move
> > those
> > > that will not be fixed. Then Nikolay will process the ones that are not
> > > assigned yet. Nikolay, can you take a look please?
> > >
> > > --Yakov
> > >
> > > 2018-08-24 12:58 GMT+03:00 Nikolay Izhikov <ni...@apache.org>:
> > >
> > > > Hello, Dmitriy.
> > > >
> > > > Release page - [1]
> > > >
> > > > > I think it is important to include the links to all important Jira
> > > >
> > > > tickets> in this thread
> > > >
> > > > Open:
> > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-6980 - Automatic
> > cancelling
> > > > of hanging Ignite operations
> > > > 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
> > > > https://issues.apache.org/jira/browse/IGNITE-6507 - Commit can be
> > lost in
> > > > network split scenario
> > > >
> > > > In Progress:
> > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-9349
> > > >
> > > > Patch Available:
> > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-7251 - Remove term
> > "fabric"
> > > > from Ignite deliverables
> > > >
> > > >
> > > > Resolved:
> > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-8780 - File I/O
> > operations
> > > > must be retried if buffer hasn't read/written completely
> > > > https://issues.apache.org/jira/browse/IGNITE-5059 - Implement
> logistic
> > > > regression
> > > > https://issues.apache.org/jira/browse/IGNITE-3478 - Multi-version
> > > > concurrency control
> > > > https://issues.apache.org/jira/browse/IGNITE-9340 - Update jetty
> > version
> > > > in Apache Ignite (ignite-rest-http)
> > > >
> > > >
> > > >
> > > > [1] https://cwiki.apache.org/confluence/display/IGNITE/
> > Apache+Ignite+2.7
> > > >
> > > > В Пт, 24/08/2018 в 10:47 +0300, Nikolay Izhikov пишет:
> > > > > Hello, Pavel.
> > > > >
> > > > > Please, be aware of IGNITE-6055 [1]
> > > > >
> > > > > I'm edit thin protocol in that ticket.
> > > > > I can't support changes in Python and PHP clients, because, they
> are
> > not
> > > >
> > > > merged in master, yet.
> > > > > Write me, If you have any questions about new fields.
> > > > >
> > > > > [1] https://issues.apache.org/jira/browse/IGNITE-6055
> > > > >
> > > > > В Чт, 23/08/2018 в 18:02 -0700, Pavel Petroshenko пишет:
> > > > > > Hi Nikolay,
> > > > > >
> > > > > > Python [1], PHP [2], and Node.js [3] thin clients will get into
> the
> > > >
> > > > release.
> > > > > >
> > > > > > Thanks,
> > > > > > 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 Tue, Aug 21, 2018 at 12:20 PM, Dmitriy Setrakyan <
> > > >
> > > > dsetrakyan@apache.org> wrote:
> > > > > > > Thanks, Nikolay!
> > > > > > >
> > > > > > > I think it is important to include the links to all important
> > Jira
> > > >
> > > > tickets
> > > > > > > in this thread, so that the community can track them.
> > > > > > >
> > > > > > > D.
> > > > > > >
> > > > > > > On Tue, Aug 21, 2018 at 12:06 AM, Nikolay Izhikov <
> > > >
> > > > nizhikov@apache.org>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Hello, Dmitriy.
> > > > > > > >
> > > > > > > > I think Transparent Data Encryption will be available in 2.7
> > > > > > > >
> > > > > > > > В Пн, 20/08/2018 в 13:20 -0700, Dmitriy Setrakyan пишет:
> > > > > > > > > Hi Nikolay,
> > > > > > > > >
> > > > > > > > > Thanks for being the release manager!
> > > > > > > > >
> > > > > > > > > I am getting a bit lost in all these tickets. Can we
> specify
> > some
> > > > > > > > > high-level tickets, that are not plain bug fixes, which
> will
> > be
> > > > > > > >
> > > > > > > > interesting
> > > > > > > > > for the community to notice?
> > > > > > > > >
> > > > > > > > > For example, here are some significant tasks that the
> > community
> > > >
> > > > is either
> > > > > > > > > working on or has been working on:
> > > > > > > > >
> > > > > > > > > - Node.JS client
> > > > > > > > > - Python client
> > > > > > > > > - Transactional SQL (MVCC)
> > > > > > > > > - service grid stabilization
> > > > > > > > > - SQL memory utilization improvements
> > > > > > > > > - more?
> > > > > > > > >
> > > > > > > > > Can you please solicit status from the community for these
> > tasks?
> > > > > > > > >
> > > > > > > > > D.
> > > > > > > > >
> > > > > > > > > On Mon, Aug 20, 2018 at 11:22 AM, Nikolay Izhikov <
> > > >
> > > > nizhikov@apache.org>
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Hello, Igniters.
> > > > > > > > > >
> > > > > > > > > > I'm release manager of Apache Ignite 2.7.
> > > > > > > > > >
> > > > > > > > > > It's time to start discussion of release. [1]
> > > > > > > > > >
> > > > > > > > > > Current code freeze date is September, 30.
> > > > > > > > > > If you have any objections - please, responsd to this
> > thread.
> > > > > > > > > >
> > > > > > > > > > [1] https://cwiki.apache.org/confluence/display/IGNITE/
> > > > > > > >
> > > > > > > > Apache+Ignite+2.7
> > > > > > > >
> >
>
Re: Apache Ignite 2.7 release
Posted by Dmitriy Setrakyan <ds...@apache.org>.
Nikolai,
To my knowledge, some significant changes to the service grid
implementation were going to make it into 2.7. However, I am right now
seeing other threads about the service grid in which the new design is just
being discussed. This shows that service grid is not release ready.
Do you know whether it is ready or not? Can we get a list of tickets on the
service grid that we should be monitoring?
D.
On Fri, Aug 24, 2018 at 5:01 AM, Nikolay Izhikov <ni...@apache.org>
wrote:
> Hello, Yakov.
>
> Blocker Tickets.
>
> Open:
>
> IGNITE-9184 Mikhail Cherkasov Cluster hangs during concurrent
> node restart and continues query registration
> IGNITE-8552 Vladimir Ozerov Unable to use date as
> primary key
> IGNITE-6980 Aleksey Plekhanov Automatic cancelling of hanging
> Ignite operations
> IGNITE-8671 Peter Ivanov Provide instructions on running
> Apache Ignite on Windows 10 WSL Environment
> IGNITE-7009 Vladimir Ozerov NPE when Ignite persistence is
> enabled for Hadoop accelerator
> IGNITE-8803 Alexey Goncharuk Need to fix Ignite QUIET log output
> IGNITE-8802 Alexey Goncharuk Need to fix Ignite INFO output
> IGNITE-5618 Dmitriy Pavlov .NET: Ignite fails with OOM on
> startup under x86 (32 bit) with default configuration
> IGNITE-9352 Unassigned Web Console: Investigate how
> correctly use package-lock.json
> IGNITE-9347 Unassigned Attempt to start a dynamic cache
> with invalid configuration leads to exchange worker death
> IGNITE-9202 Unassigned .NET `TestRemoteNodes` fails with
> "Failed to map SQL query to topology"
> IGNITE-7793 Unassigned SQL does not work if value has
> index filed which name equals to affinity key name
> IGNITE-8890 Unassigned Ignite YARN Kerberos - Delegation
> Token renewal
> IGNITE-8771 Unassigned OutOfMemory in Cache2 suite in
> master branch on TC
> IGNITE-8770 Unassigned OutOfMemory in Queries1 suite in
> master branch on TC
> IGNITE-8767 Unassigned JavaClient test suite times out in
> master branch
> IGNITE-5302 Unassigned Empty LOST partition may be used
> as OWNING after resetting lost partitions
> IGNITE-7813 Unassigned Method org/apache/ignite/cache/
> hibernate/HibernateRegionFactory.start(Lorg/hibernate/boot/spi/
> SessionFactoryOptions;Ljava/util/Properties;)V is abstract
> IGNITE-8523 Unassigned Java and Scala spark examples are
> mixed
> IGNITE-8772 Unassigned WebSessionFilter does not work
> with jetty 9.4 anymore
> IGNITE-6064 Unassigned Rework control.sh script
> IGNITE-8454 Unassigned Hadoop module compilation failure
> under JDK9
> IGNITE-7620 Unassigned Not able to run query in Ignite
> YARN
>
> In Progress:
>
>
> IGNITE-9305 Pavel Pereslegin Wrong off-heap size is reported
> for a node
> IGNITE-7728 Artem Budnikov Put together a doc that shows how
> to blend SQL with k/v APIs
> IGNITE-7721 ruchir choudhry Apache Ignite web session
> clustering stack after login success
>
> Patch Available:
>
> IGNITE-9068 Ilya Lantukh Node fails to stop when
> CacheObjectBinaryProcessor.addMeta() is executed inside guard()/unguard()
> IGNITE-7251 Anton Vinogradov Remove term "fabric" from Ignite
> deliverables
> IGNITE-9030 Peter Ivanov Apache Ignite 2.7 Linux packages
> version update
>
> В Пт, 24/08/2018 в 14:47 +0300, Yakov Zhdanov пишет:
> > Igniters,
> >
> > We should definitely expand the list of important tickets adding tickets
> > related to (1) Partition Map Exchange speed up and (2) SQL memory
> > optimization tickets. Alex Goncharuk, Vladimir, can you please add labels
> > to corresponding tickets.
> >
> > Also we have several blocker tickets (mostly related to failing tests)
> not
> > yet assigned to anyone. Nikolay, can you please list those tickets and
> ask
> > community to pick them up?
> >
> > We have 556 open tickets now according to [1]. This seems a bit to much.
> > Can I ask everyone to review tickets assigned to yourselves and move
> those
> > that will not be fixed. Then Nikolay will process the ones that are not
> > assigned yet. Nikolay, can you take a look please?
> >
> > --Yakov
> >
> > 2018-08-24 12:58 GMT+03:00 Nikolay Izhikov <ni...@apache.org>:
> >
> > > Hello, Dmitriy.
> > >
> > > Release page - [1]
> > >
> > > > I think it is important to include the links to all important Jira
> > >
> > > tickets> in this thread
> > >
> > > Open:
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-6980 - Automatic
> cancelling
> > > of hanging Ignite operations
> > > 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
> > > https://issues.apache.org/jira/browse/IGNITE-6507 - Commit can be
> lost in
> > > network split scenario
> > >
> > > In Progress:
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-9349
> > >
> > > Patch Available:
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-7251 - Remove term
> "fabric"
> > > from Ignite deliverables
> > >
> > >
> > > Resolved:
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-8780 - File I/O
> operations
> > > must be retried if buffer hasn't read/written completely
> > > https://issues.apache.org/jira/browse/IGNITE-5059 - Implement logistic
> > > regression
> > > https://issues.apache.org/jira/browse/IGNITE-3478 - Multi-version
> > > concurrency control
> > > https://issues.apache.org/jira/browse/IGNITE-9340 - Update jetty
> version
> > > in Apache Ignite (ignite-rest-http)
> > >
> > >
> > >
> > > [1] https://cwiki.apache.org/confluence/display/IGNITE/
> Apache+Ignite+2.7
> > >
> > > В Пт, 24/08/2018 в 10:47 +0300, Nikolay Izhikov пишет:
> > > > Hello, Pavel.
> > > >
> > > > Please, be aware of IGNITE-6055 [1]
> > > >
> > > > I'm edit thin protocol in that ticket.
> > > > I can't support changes in Python and PHP clients, because, they are
> not
> > >
> > > merged in master, yet.
> > > > Write me, If you have any questions about new fields.
> > > >
> > > > [1] https://issues.apache.org/jira/browse/IGNITE-6055
> > > >
> > > > В Чт, 23/08/2018 в 18:02 -0700, Pavel Petroshenko пишет:
> > > > > Hi Nikolay,
> > > > >
> > > > > Python [1], PHP [2], and Node.js [3] thin clients will get into the
> > >
> > > release.
> > > > >
> > > > > Thanks,
> > > > > 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 Tue, Aug 21, 2018 at 12:20 PM, Dmitriy Setrakyan <
> > >
> > > dsetrakyan@apache.org> wrote:
> > > > > > Thanks, Nikolay!
> > > > > >
> > > > > > I think it is important to include the links to all important
> Jira
> > >
> > > tickets
> > > > > > in this thread, so that the community can track them.
> > > > > >
> > > > > > D.
> > > > > >
> > > > > > On Tue, Aug 21, 2018 at 12:06 AM, Nikolay Izhikov <
> > >
> > > nizhikov@apache.org>
> > > > > > wrote:
> > > > > >
> > > > > > > Hello, Dmitriy.
> > > > > > >
> > > > > > > I think Transparent Data Encryption will be available in 2.7
> > > > > > >
> > > > > > > В Пн, 20/08/2018 в 13:20 -0700, Dmitriy Setrakyan пишет:
> > > > > > > > Hi Nikolay,
> > > > > > > >
> > > > > > > > Thanks for being the release manager!
> > > > > > > >
> > > > > > > > I am getting a bit lost in all these tickets. Can we specify
> some
> > > > > > > > high-level tickets, that are not plain bug fixes, which will
> be
> > > > > > >
> > > > > > > interesting
> > > > > > > > for the community to notice?
> > > > > > > >
> > > > > > > > For example, here are some significant tasks that the
> community
> > >
> > > is either
> > > > > > > > working on or has been working on:
> > > > > > > >
> > > > > > > > - Node.JS client
> > > > > > > > - Python client
> > > > > > > > - Transactional SQL (MVCC)
> > > > > > > > - service grid stabilization
> > > > > > > > - SQL memory utilization improvements
> > > > > > > > - more?
> > > > > > > >
> > > > > > > > Can you please solicit status from the community for these
> tasks?
> > > > > > > >
> > > > > > > > D.
> > > > > > > >
> > > > > > > > On Mon, Aug 20, 2018 at 11:22 AM, Nikolay Izhikov <
> > >
> > > nizhikov@apache.org>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Hello, Igniters.
> > > > > > > > >
> > > > > > > > > I'm release manager of Apache Ignite 2.7.
> > > > > > > > >
> > > > > > > > > It's time to start discussion of release. [1]
> > > > > > > > >
> > > > > > > > > Current code freeze date is September, 30.
> > > > > > > > > If you have any objections - please, responsd to this
> thread.
> > > > > > > > >
> > > > > > > > > [1] https://cwiki.apache.org/confluence/display/IGNITE/
> > > > > > >
> > > > > > > Apache+Ignite+2.7
> > > > > > >
>
Re: Apache Ignite 2.7 release
Posted by Nikolay Izhikov <ni...@apache.org>.
Hello, Yakov.
Blocker Tickets.
Open:
IGNITE-9184 Mikhail Cherkasov Cluster hangs during concurrent node restart and continues query registration
IGNITE-8552 Vladimir Ozerov Unable to use date as primary key
IGNITE-6980 Aleksey Plekhanov Automatic cancelling of hanging Ignite operations
IGNITE-8671 Peter Ivanov Provide instructions on running Apache Ignite on Windows 10 WSL Environment
IGNITE-7009 Vladimir Ozerov NPE when Ignite persistence is enabled for Hadoop accelerator
IGNITE-8803 Alexey Goncharuk Need to fix Ignite QUIET log output
IGNITE-8802 Alexey Goncharuk Need to fix Ignite INFO output
IGNITE-5618 Dmitriy Pavlov .NET: Ignite fails with OOM on startup under x86 (32 bit) with default configuration
IGNITE-9352 Unassigned Web Console: Investigate how correctly use package-lock.json
IGNITE-9347 Unassigned Attempt to start a dynamic cache with invalid configuration leads to exchange worker death
IGNITE-9202 Unassigned .NET `TestRemoteNodes` fails with "Failed to map SQL query to topology"
IGNITE-7793 Unassigned SQL does not work if value has index filed which name equals to affinity key name
IGNITE-8890 Unassigned Ignite YARN Kerberos - Delegation Token renewal
IGNITE-8771 Unassigned OutOfMemory in Cache2 suite in master branch on TC
IGNITE-8770 Unassigned OutOfMemory in Queries1 suite in master branch on TC
IGNITE-8767 Unassigned JavaClient test suite times out in master branch
IGNITE-5302 Unassigned Empty LOST partition may be used as OWNING after resetting lost partitions
IGNITE-7813 Unassigned Method org/apache/ignite/cache/hibernate/HibernateRegionFactory.start(Lorg/hibernate/boot/spi/SessionFactoryOptions;Ljava/util/Properties;)V is abstract
IGNITE-8523 Unassigned Java and Scala spark examples are mixed
IGNITE-8772 Unassigned WebSessionFilter does not work with jetty 9.4 anymore
IGNITE-6064 Unassigned Rework control.sh script
IGNITE-8454 Unassigned Hadoop module compilation failure under JDK9
IGNITE-7620 Unassigned Not able to run query in Ignite YARN
In Progress:
IGNITE-9305 Pavel Pereslegin Wrong off-heap size is reported for a node
IGNITE-7728 Artem Budnikov Put together a doc that shows how to blend SQL with k/v APIs
IGNITE-7721 ruchir choudhry Apache Ignite web session clustering stack after login success
Patch Available:
IGNITE-9068 Ilya Lantukh Node fails to stop when CacheObjectBinaryProcessor.addMeta() is executed inside guard()/unguard()
IGNITE-7251 Anton Vinogradov Remove term "fabric" from Ignite deliverables
IGNITE-9030 Peter Ivanov Apache Ignite 2.7 Linux packages version update
В Пт, 24/08/2018 в 14:47 +0300, Yakov Zhdanov пишет:
> Igniters,
>
> We should definitely expand the list of important tickets adding tickets
> related to (1) Partition Map Exchange speed up and (2) SQL memory
> optimization tickets. Alex Goncharuk, Vladimir, can you please add labels
> to corresponding tickets.
>
> Also we have several blocker tickets (mostly related to failing tests) not
> yet assigned to anyone. Nikolay, can you please list those tickets and ask
> community to pick them up?
>
> We have 556 open tickets now according to [1]. This seems a bit to much.
> Can I ask everyone to review tickets assigned to yourselves and move those
> that will not be fixed. Then Nikolay will process the ones that are not
> assigned yet. Nikolay, can you take a look please?
>
> --Yakov
>
> 2018-08-24 12:58 GMT+03:00 Nikolay Izhikov <ni...@apache.org>:
>
> > Hello, Dmitriy.
> >
> > Release page - [1]
> >
> > > I think it is important to include the links to all important Jira
> >
> > tickets> in this thread
> >
> > Open:
> >
> > https://issues.apache.org/jira/browse/IGNITE-6980 - Automatic cancelling
> > of hanging Ignite operations
> > 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
> > https://issues.apache.org/jira/browse/IGNITE-6507 - Commit can be lost in
> > network split scenario
> >
> > In Progress:
> >
> > https://issues.apache.org/jira/browse/IGNITE-9349
> >
> > Patch Available:
> >
> > https://issues.apache.org/jira/browse/IGNITE-7251 - Remove term "fabric"
> > from Ignite deliverables
> >
> >
> > Resolved:
> >
> > https://issues.apache.org/jira/browse/IGNITE-8780 - File I/O operations
> > must be retried if buffer hasn't read/written completely
> > https://issues.apache.org/jira/browse/IGNITE-5059 - Implement logistic
> > regression
> > https://issues.apache.org/jira/browse/IGNITE-3478 - Multi-version
> > concurrency control
> > https://issues.apache.org/jira/browse/IGNITE-9340 - Update jetty version
> > in Apache Ignite (ignite-rest-http)
> >
> >
> >
> > [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.7
> >
> > В Пт, 24/08/2018 в 10:47 +0300, Nikolay Izhikov пишет:
> > > Hello, Pavel.
> > >
> > > Please, be aware of IGNITE-6055 [1]
> > >
> > > I'm edit thin protocol in that ticket.
> > > I can't support changes in Python and PHP clients, because, they are not
> >
> > merged in master, yet.
> > > Write me, If you have any questions about new fields.
> > >
> > > [1] https://issues.apache.org/jira/browse/IGNITE-6055
> > >
> > > В Чт, 23/08/2018 в 18:02 -0700, Pavel Petroshenko пишет:
> > > > Hi Nikolay,
> > > >
> > > > Python [1], PHP [2], and Node.js [3] thin clients will get into the
> >
> > release.
> > > >
> > > > Thanks,
> > > > 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 Tue, Aug 21, 2018 at 12:20 PM, Dmitriy Setrakyan <
> >
> > dsetrakyan@apache.org> wrote:
> > > > > Thanks, Nikolay!
> > > > >
> > > > > I think it is important to include the links to all important Jira
> >
> > tickets
> > > > > in this thread, so that the community can track them.
> > > > >
> > > > > D.
> > > > >
> > > > > On Tue, Aug 21, 2018 at 12:06 AM, Nikolay Izhikov <
> >
> > nizhikov@apache.org>
> > > > > wrote:
> > > > >
> > > > > > Hello, Dmitriy.
> > > > > >
> > > > > > I think Transparent Data Encryption will be available in 2.7
> > > > > >
> > > > > > В Пн, 20/08/2018 в 13:20 -0700, Dmitriy Setrakyan пишет:
> > > > > > > Hi Nikolay,
> > > > > > >
> > > > > > > Thanks for being the release manager!
> > > > > > >
> > > > > > > I am getting a bit lost in all these tickets. Can we specify some
> > > > > > > high-level tickets, that are not plain bug fixes, which will be
> > > > > >
> > > > > > interesting
> > > > > > > for the community to notice?
> > > > > > >
> > > > > > > For example, here are some significant tasks that the community
> >
> > is either
> > > > > > > working on or has been working on:
> > > > > > >
> > > > > > > - Node.JS client
> > > > > > > - Python client
> > > > > > > - Transactional SQL (MVCC)
> > > > > > > - service grid stabilization
> > > > > > > - SQL memory utilization improvements
> > > > > > > - more?
> > > > > > >
> > > > > > > Can you please solicit status from the community for these tasks?
> > > > > > >
> > > > > > > D.
> > > > > > >
> > > > > > > On Mon, Aug 20, 2018 at 11:22 AM, Nikolay Izhikov <
> >
> > nizhikov@apache.org>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Hello, Igniters.
> > > > > > > >
> > > > > > > > I'm release manager of Apache Ignite 2.7.
> > > > > > > >
> > > > > > > > It's time to start discussion of release. [1]
> > > > > > > >
> > > > > > > > Current code freeze date is September, 30.
> > > > > > > > If you have any objections - please, responsd to this thread.
> > > > > > > >
> > > > > > > > [1] https://cwiki.apache.org/confluence/display/IGNITE/
> > > > > >
> > > > > > Apache+Ignite+2.7
> > > > > >
Re: Apache Ignite 2.7 release
Posted by Yakov Zhdanov <yz...@apache.org>.
Igniters,
We should definitely expand the list of important tickets adding tickets
related to (1) Partition Map Exchange speed up and (2) SQL memory
optimization tickets. Alex Goncharuk, Vladimir, can you please add labels
to corresponding tickets.
Also we have several blocker tickets (mostly related to failing tests) not
yet assigned to anyone. Nikolay, can you please list those tickets and ask
community to pick them up?
We have 556 open tickets now according to [1]. This seems a bit to much.
Can I ask everyone to review tickets assigned to yourselves and move those
that will not be fixed. Then Nikolay will process the ones that are not
assigned yet. Nikolay, can you take a look please?
--Yakov
2018-08-24 12:58 GMT+03:00 Nikolay Izhikov <ni...@apache.org>:
> Hello, Dmitriy.
>
> Release page - [1]
>
> > I think it is important to include the links to all important Jira
> tickets> in this thread
>
> Open:
>
> https://issues.apache.org/jira/browse/IGNITE-6980 - Automatic cancelling
> of hanging Ignite operations
> 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
> https://issues.apache.org/jira/browse/IGNITE-6507 - Commit can be lost in
> network split scenario
>
> In Progress:
>
> https://issues.apache.org/jira/browse/IGNITE-9349
>
> Patch Available:
>
> https://issues.apache.org/jira/browse/IGNITE-7251 - Remove term "fabric"
> from Ignite deliverables
>
>
> Resolved:
>
> https://issues.apache.org/jira/browse/IGNITE-8780 - File I/O operations
> must be retried if buffer hasn't read/written completely
> https://issues.apache.org/jira/browse/IGNITE-5059 - Implement logistic
> regression
> https://issues.apache.org/jira/browse/IGNITE-3478 - Multi-version
> concurrency control
> https://issues.apache.org/jira/browse/IGNITE-9340 - Update jetty version
> in Apache Ignite (ignite-rest-http)
>
>
>
> [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.7
>
> В Пт, 24/08/2018 в 10:47 +0300, Nikolay Izhikov пишет:
> > Hello, Pavel.
> >
> > Please, be aware of IGNITE-6055 [1]
> >
> > I'm edit thin protocol in that ticket.
> > I can't support changes in Python and PHP clients, because, they are not
> merged in master, yet.
> > Write me, If you have any questions about new fields.
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-6055
> >
> > В Чт, 23/08/2018 в 18:02 -0700, Pavel Petroshenko пишет:
> > > Hi Nikolay,
> > >
> > > Python [1], PHP [2], and Node.js [3] thin clients will get into the
> release.
> > >
> > > Thanks,
> > > 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 Tue, Aug 21, 2018 at 12:20 PM, Dmitriy Setrakyan <
> dsetrakyan@apache.org> wrote:
> > > > Thanks, Nikolay!
> > > >
> > > > I think it is important to include the links to all important Jira
> tickets
> > > > in this thread, so that the community can track them.
> > > >
> > > > D.
> > > >
> > > > On Tue, Aug 21, 2018 at 12:06 AM, Nikolay Izhikov <
> nizhikov@apache.org>
> > > > wrote:
> > > >
> > > > > Hello, Dmitriy.
> > > > >
> > > > > I think Transparent Data Encryption will be available in 2.7
> > > > >
> > > > > В Пн, 20/08/2018 в 13:20 -0700, Dmitriy Setrakyan пишет:
> > > > > > Hi Nikolay,
> > > > > >
> > > > > > Thanks for being the release manager!
> > > > > >
> > > > > > I am getting a bit lost in all these tickets. Can we specify some
> > > > > > high-level tickets, that are not plain bug fixes, which will be
> > > > >
> > > > > interesting
> > > > > > for the community to notice?
> > > > > >
> > > > > > For example, here are some significant tasks that the community
> is either
> > > > > > working on or has been working on:
> > > > > >
> > > > > > - Node.JS client
> > > > > > - Python client
> > > > > > - Transactional SQL (MVCC)
> > > > > > - service grid stabilization
> > > > > > - SQL memory utilization improvements
> > > > > > - more?
> > > > > >
> > > > > > Can you please solicit status from the community for these tasks?
> > > > > >
> > > > > > D.
> > > > > >
> > > > > > On Mon, Aug 20, 2018 at 11:22 AM, Nikolay Izhikov <
> nizhikov@apache.org>
> > > > > > wrote:
> > > > > >
> > > > > > > Hello, Igniters.
> > > > > > >
> > > > > > > I'm release manager of Apache Ignite 2.7.
> > > > > > >
> > > > > > > It's time to start discussion of release. [1]
> > > > > > >
> > > > > > > Current code freeze date is September, 30.
> > > > > > > If you have any objections - please, responsd to this thread.
> > > > > > >
> > > > > > > [1] https://cwiki.apache.org/confluence/display/IGNITE/
> > > > >
> > > > > Apache+Ignite+2.7
> > > > >
>
Re: Apache Ignite 2.7 release
Posted by Nikolay Izhikov <ni...@apache.org>.
Hello, Dmitriy.
Release page - [1]
> I think it is important to include the links to all important Jira tickets> in this thread
Open:
https://issues.apache.org/jira/browse/IGNITE-6980 - Automatic cancelling of hanging Ignite operations
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
https://issues.apache.org/jira/browse/IGNITE-6507 - Commit can be lost in network split scenario
In Progress:
https://issues.apache.org/jira/browse/IGNITE-9349
Patch Available:
https://issues.apache.org/jira/browse/IGNITE-7251 - Remove term "fabric" from Ignite deliverables
Resolved:
https://issues.apache.org/jira/browse/IGNITE-8780 - File I/O operations must be retried if buffer hasn't read/written completely
https://issues.apache.org/jira/browse/IGNITE-5059 - Implement logistic regression
https://issues.apache.org/jira/browse/IGNITE-3478 - Multi-version concurrency control
https://issues.apache.org/jira/browse/IGNITE-9340 - Update jetty version in Apache Ignite (ignite-rest-http)
[1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.7
В Пт, 24/08/2018 в 10:47 +0300, Nikolay Izhikov пишет:
> Hello, Pavel.
>
> Please, be aware of IGNITE-6055 [1]
>
> I'm edit thin protocol in that ticket.
> I can't support changes in Python and PHP clients, because, they are not merged in master, yet.
> Write me, If you have any questions about new fields.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-6055
>
> В Чт, 23/08/2018 в 18:02 -0700, Pavel Petroshenko пишет:
> > Hi Nikolay,
> >
> > Python [1], PHP [2], and Node.js [3] thin clients will get into the release.
> >
> > Thanks,
> > 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 Tue, Aug 21, 2018 at 12:20 PM, Dmitriy Setrakyan <ds...@apache.org> wrote:
> > > Thanks, Nikolay!
> > >
> > > I think it is important to include the links to all important Jira tickets
> > > in this thread, so that the community can track them.
> > >
> > > D.
> > >
> > > On Tue, Aug 21, 2018 at 12:06 AM, Nikolay Izhikov <ni...@apache.org>
> > > wrote:
> > >
> > > > Hello, Dmitriy.
> > > >
> > > > I think Transparent Data Encryption will be available in 2.7
> > > >
> > > > В Пн, 20/08/2018 в 13:20 -0700, Dmitriy Setrakyan пишет:
> > > > > Hi Nikolay,
> > > > >
> > > > > Thanks for being the release manager!
> > > > >
> > > > > I am getting a bit lost in all these tickets. Can we specify some
> > > > > high-level tickets, that are not plain bug fixes, which will be
> > > >
> > > > interesting
> > > > > for the community to notice?
> > > > >
> > > > > For example, here are some significant tasks that the community is either
> > > > > working on or has been working on:
> > > > >
> > > > > - Node.JS client
> > > > > - Python client
> > > > > - Transactional SQL (MVCC)
> > > > > - service grid stabilization
> > > > > - SQL memory utilization improvements
> > > > > - more?
> > > > >
> > > > > Can you please solicit status from the community for these tasks?
> > > > >
> > > > > D.
> > > > >
> > > > > On Mon, Aug 20, 2018 at 11:22 AM, Nikolay Izhikov <ni...@apache.org>
> > > > > wrote:
> > > > >
> > > > > > Hello, Igniters.
> > > > > >
> > > > > > I'm release manager of Apache Ignite 2.7.
> > > > > >
> > > > > > It's time to start discussion of release. [1]
> > > > > >
> > > > > > Current code freeze date is September, 30.
> > > > > > If you have any objections - please, responsd to this thread.
> > > > > >
> > > > > > [1] https://cwiki.apache.org/confluence/display/IGNITE/
> > > >
> > > > Apache+Ignite+2.7
> > > >
Re: Apache Ignite 2.7 release
Posted by Pavel Petroshenko <pa...@petroshenko.com>.
Thank you, Nikolay. Will do.
p.
On Tue, Aug 28, 2018 at 12:05 AM, Nikolay Izhikov <ni...@apache.org>
wrote:
> Hello, Pavel.
>
> IGNITE-6055 merged to master.
>
> Please, update your code accordingly.
> You can take edits in CPP, .Net, NodeJS thin clients as example.
>
> В Пт, 24/08/2018 в 21:49 +0300, Nikolay Izhikov пишет:
> > PR is fully ready.
> >
> > I'm waiting final approve from Vladimir Ozerov.
> >
> > Hope, This will be merged in master on Monday :).
> >
> > В Пт, 24/08/2018 в 11:47 -0700, Pavel Petroshenko пишет:
> > > Hi Nikolay,
> > >
> > > Thank you for the heads up. The dependency should be resolved before
> the clients are merged to master, so the sooner you merge the PR the better.
> > >
> > > p.
> > >
> > > On Fri, Aug 24, 2018 at 12:47 AM, Nikolay Izhikov <ni...@apache.org>
> wrote:
> > > > Hello, Pavel.
> > > >
> > > > Please, be aware of IGNITE-6055 [1]
> > > >
> > > > I'm edit thin protocol in that ticket.
> > > > I can't support changes in Python and PHP clients, because, they are
> not merged in master, yet.
> > > > Write me, If you have any questions about new fields.
> > > >
> > > > [1] https://issues.apache.org/jira/browse/IGNITE-6055
> > > >
> > > > В Чт, 23/08/2018 в 18:02 -0700, Pavel Petroshenko пишет:
> > > > > Hi Nikolay,
> > > > >
> > > > > Python [1], PHP [2], and Node.js [3] thin clients will get into
> the release.
> > > > >
> > > > > Thanks,
> > > > > 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 Tue, Aug 21, 2018 at 12:20 PM, Dmitriy Setrakyan <
> dsetrakyan@apache.org> wrote:
> > > > > > Thanks, Nikolay!
> > > > > >
> > > > > > I think it is important to include the links to all important
> Jira tickets
> > > > > > in this thread, so that the community can track them.
> > > > > >
> > > > > > D.
> > > > > >
> > > > > > On Tue, Aug 21, 2018 at 12:06 AM, Nikolay Izhikov <
> nizhikov@apache.org>
> > > > > > wrote:
> > > > > >
> > > > > > > Hello, Dmitriy.
> > > > > > >
> > > > > > > I think Transparent Data Encryption will be available in 2.7
> > > > > > >
> > > > > > > В Пн, 20/08/2018 в 13:20 -0700, Dmitriy Setrakyan пишет:
> > > > > > > > Hi Nikolay,
> > > > > > > >
> > > > > > > > Thanks for being the release manager!
> > > > > > > >
> > > > > > > > I am getting a bit lost in all these tickets. Can we specify
> some
> > > > > > > > high-level tickets, that are not plain bug fixes, which will
> be
> > > > > > >
> > > > > > > interesting
> > > > > > > > for the community to notice?
> > > > > > > >
> > > > > > > > For example, here are some significant tasks that the
> community is either
> > > > > > > > working on or has been working on:
> > > > > > > >
> > > > > > > > - Node.JS client
> > > > > > > > - Python client
> > > > > > > > - Transactional SQL (MVCC)
> > > > > > > > - service grid stabilization
> > > > > > > > - SQL memory utilization improvements
> > > > > > > > - more?
> > > > > > > >
> > > > > > > > Can you please solicit status from the community for these
> tasks?
> > > > > > > >
> > > > > > > > D.
> > > > > > > >
> > > > > > > > On Mon, Aug 20, 2018 at 11:22 AM, Nikolay Izhikov <
> nizhikov@apache.org>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Hello, Igniters.
> > > > > > > > >
> > > > > > > > > I'm release manager of Apache Ignite 2.7.
> > > > > > > > >
> > > > > > > > > It's time to start discussion of release. [1]
> > > > > > > > >
> > > > > > > > > Current code freeze date is September, 30.
> > > > > > > > > If you have any objections - please, responsd to this
> thread.
> > > > > > > > >
> > > > > > > > > [1] https://cwiki.apache.org/confluence/display/IGNITE/
> > > > > > >
> > > > > > > Apache+Ignite+2.7
> > > > > > >
> > > > >
> > > > >
>
Re: Apache Ignite 2.7 release
Posted by Nikolay Izhikov <ni...@apache.org>.
Hello, Pavel.
IGNITE-6055 merged to master.
Please, update your code accordingly.
You can take edits in CPP, .Net, NodeJS thin clients as example.
В Пт, 24/08/2018 в 21:49 +0300, Nikolay Izhikov пишет:
> PR is fully ready.
>
> I'm waiting final approve from Vladimir Ozerov.
>
> Hope, This will be merged in master on Monday :).
>
> В Пт, 24/08/2018 в 11:47 -0700, Pavel Petroshenko пишет:
> > Hi Nikolay,
> >
> > Thank you for the heads up. The dependency should be resolved before the clients are merged to master, so the sooner you merge the PR the better.
> >
> > p.
> >
> > On Fri, Aug 24, 2018 at 12:47 AM, Nikolay Izhikov <ni...@apache.org> wrote:
> > > Hello, Pavel.
> > >
> > > Please, be aware of IGNITE-6055 [1]
> > >
> > > I'm edit thin protocol in that ticket.
> > > I can't support changes in Python and PHP clients, because, they are not merged in master, yet.
> > > Write me, If you have any questions about new fields.
> > >
> > > [1] https://issues.apache.org/jira/browse/IGNITE-6055
> > >
> > > В Чт, 23/08/2018 в 18:02 -0700, Pavel Petroshenko пишет:
> > > > Hi Nikolay,
> > > >
> > > > Python [1], PHP [2], and Node.js [3] thin clients will get into the release.
> > > >
> > > > Thanks,
> > > > 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 Tue, Aug 21, 2018 at 12:20 PM, Dmitriy Setrakyan <ds...@apache.org> wrote:
> > > > > Thanks, Nikolay!
> > > > >
> > > > > I think it is important to include the links to all important Jira tickets
> > > > > in this thread, so that the community can track them.
> > > > >
> > > > > D.
> > > > >
> > > > > On Tue, Aug 21, 2018 at 12:06 AM, Nikolay Izhikov <ni...@apache.org>
> > > > > wrote:
> > > > >
> > > > > > Hello, Dmitriy.
> > > > > >
> > > > > > I think Transparent Data Encryption will be available in 2.7
> > > > > >
> > > > > > В Пн, 20/08/2018 в 13:20 -0700, Dmitriy Setrakyan пишет:
> > > > > > > Hi Nikolay,
> > > > > > >
> > > > > > > Thanks for being the release manager!
> > > > > > >
> > > > > > > I am getting a bit lost in all these tickets. Can we specify some
> > > > > > > high-level tickets, that are not plain bug fixes, which will be
> > > > > >
> > > > > > interesting
> > > > > > > for the community to notice?
> > > > > > >
> > > > > > > For example, here are some significant tasks that the community is either
> > > > > > > working on or has been working on:
> > > > > > >
> > > > > > > - Node.JS client
> > > > > > > - Python client
> > > > > > > - Transactional SQL (MVCC)
> > > > > > > - service grid stabilization
> > > > > > > - SQL memory utilization improvements
> > > > > > > - more?
> > > > > > >
> > > > > > > Can you please solicit status from the community for these tasks?
> > > > > > >
> > > > > > > D.
> > > > > > >
> > > > > > > On Mon, Aug 20, 2018 at 11:22 AM, Nikolay Izhikov <ni...@apache.org>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Hello, Igniters.
> > > > > > > >
> > > > > > > > I'm release manager of Apache Ignite 2.7.
> > > > > > > >
> > > > > > > > It's time to start discussion of release. [1]
> > > > > > > >
> > > > > > > > Current code freeze date is September, 30.
> > > > > > > > If you have any objections - please, responsd to this thread.
> > > > > > > >
> > > > > > > > [1] https://cwiki.apache.org/confluence/display/IGNITE/
> > > > > >
> > > > > > Apache+Ignite+2.7
> > > > > >
> > > >
> > > >
Re: Apache Ignite 2.7 release
Posted by Nikolay Izhikov <ni...@apache.org>.
PR is fully ready.
I'm waiting final approve from Vladimir Ozerov.
Hope, This will be merged in master on Monday :).
В Пт, 24/08/2018 в 11:47 -0700, Pavel Petroshenko пишет:
> Hi Nikolay,
>
> Thank you for the heads up. The dependency should be resolved before the clients are merged to master, so the sooner you merge the PR the better.
>
> p.
>
> On Fri, Aug 24, 2018 at 12:47 AM, Nikolay Izhikov <ni...@apache.org> wrote:
> > Hello, Pavel.
> >
> > Please, be aware of IGNITE-6055 [1]
> >
> > I'm edit thin protocol in that ticket.
> > I can't support changes in Python and PHP clients, because, they are not merged in master, yet.
> > Write me, If you have any questions about new fields.
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-6055
> >
> > В Чт, 23/08/2018 в 18:02 -0700, Pavel Petroshenko пишет:
> > > Hi Nikolay,
> > >
> > > Python [1], PHP [2], and Node.js [3] thin clients will get into the release.
> > >
> > > Thanks,
> > > 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 Tue, Aug 21, 2018 at 12:20 PM, Dmitriy Setrakyan <ds...@apache.org> wrote:
> > > > Thanks, Nikolay!
> > > >
> > > > I think it is important to include the links to all important Jira tickets
> > > > in this thread, so that the community can track them.
> > > >
> > > > D.
> > > >
> > > > On Tue, Aug 21, 2018 at 12:06 AM, Nikolay Izhikov <ni...@apache.org>
> > > > wrote:
> > > >
> > > > > Hello, Dmitriy.
> > > > >
> > > > > I think Transparent Data Encryption will be available in 2.7
> > > > >
> > > > > В Пн, 20/08/2018 в 13:20 -0700, Dmitriy Setrakyan пишет:
> > > > > > Hi Nikolay,
> > > > > >
> > > > > > Thanks for being the release manager!
> > > > > >
> > > > > > I am getting a bit lost in all these tickets. Can we specify some
> > > > > > high-level tickets, that are not plain bug fixes, which will be
> > > > > interesting
> > > > > > for the community to notice?
> > > > > >
> > > > > > For example, here are some significant tasks that the community is either
> > > > > > working on or has been working on:
> > > > > >
> > > > > > - Node.JS client
> > > > > > - Python client
> > > > > > - Transactional SQL (MVCC)
> > > > > > - service grid stabilization
> > > > > > - SQL memory utilization improvements
> > > > > > - more?
> > > > > >
> > > > > > Can you please solicit status from the community for these tasks?
> > > > > >
> > > > > > D.
> > > > > >
> > > > > > On Mon, Aug 20, 2018 at 11:22 AM, Nikolay Izhikov <ni...@apache.org>
> > > > > > wrote:
> > > > > >
> > > > > > > Hello, Igniters.
> > > > > > >
> > > > > > > I'm release manager of Apache Ignite 2.7.
> > > > > > >
> > > > > > > It's time to start discussion of release. [1]
> > > > > > >
> > > > > > > Current code freeze date is September, 30.
> > > > > > > If you have any objections - please, responsd to this thread.
> > > > > > >
> > > > > > > [1] https://cwiki.apache.org/confluence/display/IGNITE/
> > > > > Apache+Ignite+2.7
> > > > >
> > >
> > >
>
>
Re: Apache Ignite 2.7 release
Posted by Pavel Petroshenko <pa...@petroshenko.com>.
Hi Nikolay,
Thank you for the heads up. The dependency should be resolved before the
clients are merged to master, so the sooner you merge the PR the better.
p.
On Fri, Aug 24, 2018 at 12:47 AM, Nikolay Izhikov <ni...@apache.org>
wrote:
> Hello, Pavel.
>
> Please, be aware of IGNITE-6055 [1]
>
> I'm edit thin protocol in that ticket.
> I can't support changes in Python and PHP clients, because, they are not
> merged in master, yet.
> Write me, If you have any questions about new fields.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-6055
>
> В Чт, 23/08/2018 в 18:02 -0700, Pavel Petroshenko пишет:
> > Hi Nikolay,
> >
> > Python [1], PHP [2], and Node.js [3] thin clients will get into the
> release.
> >
> > Thanks,
> > 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 Tue, Aug 21, 2018 at 12:20 PM, Dmitriy Setrakyan <
> dsetrakyan@apache.org> wrote:
> > > Thanks, Nikolay!
> > >
> > > I think it is important to include the links to all important Jira
> tickets
> > > in this thread, so that the community can track them.
> > >
> > > D.
> > >
> > > On Tue, Aug 21, 2018 at 12:06 AM, Nikolay Izhikov <nizhikov@apache.org
> >
> > > wrote:
> > >
> > > > Hello, Dmitriy.
> > > >
> > > > I think Transparent Data Encryption will be available in 2.7
> > > >
> > > > В Пн, 20/08/2018 в 13:20 -0700, Dmitriy Setrakyan пишет:
> > > > > Hi Nikolay,
> > > > >
> > > > > Thanks for being the release manager!
> > > > >
> > > > > I am getting a bit lost in all these tickets. Can we specify some
> > > > > high-level tickets, that are not plain bug fixes, which will be
> > > > interesting
> > > > > for the community to notice?
> > > > >
> > > > > For example, here are some significant tasks that the community is
> either
> > > > > working on or has been working on:
> > > > >
> > > > > - Node.JS client
> > > > > - Python client
> > > > > - Transactional SQL (MVCC)
> > > > > - service grid stabilization
> > > > > - SQL memory utilization improvements
> > > > > - more?
> > > > >
> > > > > Can you please solicit status from the community for these tasks?
> > > > >
> > > > > D.
> > > > >
> > > > > On Mon, Aug 20, 2018 at 11:22 AM, Nikolay Izhikov <
> nizhikov@apache.org>
> > > > > wrote:
> > > > >
> > > > > > Hello, Igniters.
> > > > > >
> > > > > > I'm release manager of Apache Ignite 2.7.
> > > > > >
> > > > > > It's time to start discussion of release. [1]
> > > > > >
> > > > > > Current code freeze date is September, 30.
> > > > > > If you have any objections - please, responsd to this thread.
> > > > > >
> > > > > > [1] https://cwiki.apache.org/confluence/display/IGNITE/
> > > > Apache+Ignite+2.7
> > > >
> >
> >
>
Re: Apache Ignite 2.7 release
Posted by Nikolay Izhikov <ni...@apache.org>.
Hello, Pavel.
Please, be aware of IGNITE-6055 [1]
I'm edit thin protocol in that ticket.
I can't support changes in Python and PHP clients, because, they are not merged in master, yet.
Write me, If you have any questions about new fields.
[1] https://issues.apache.org/jira/browse/IGNITE-6055
В Чт, 23/08/2018 в 18:02 -0700, Pavel Petroshenko пишет:
> Hi Nikolay,
>
> Python [1], PHP [2], and Node.js [3] thin clients will get into the release.
>
> Thanks,
> 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 Tue, Aug 21, 2018 at 12:20 PM, Dmitriy Setrakyan <ds...@apache.org> wrote:
> > Thanks, Nikolay!
> >
> > I think it is important to include the links to all important Jira tickets
> > in this thread, so that the community can track them.
> >
> > D.
> >
> > On Tue, Aug 21, 2018 at 12:06 AM, Nikolay Izhikov <ni...@apache.org>
> > wrote:
> >
> > > Hello, Dmitriy.
> > >
> > > I think Transparent Data Encryption will be available in 2.7
> > >
> > > В Пн, 20/08/2018 в 13:20 -0700, Dmitriy Setrakyan пишет:
> > > > Hi Nikolay,
> > > >
> > > > Thanks for being the release manager!
> > > >
> > > > I am getting a bit lost in all these tickets. Can we specify some
> > > > high-level tickets, that are not plain bug fixes, which will be
> > > interesting
> > > > for the community to notice?
> > > >
> > > > For example, here are some significant tasks that the community is either
> > > > working on or has been working on:
> > > >
> > > > - Node.JS client
> > > > - Python client
> > > > - Transactional SQL (MVCC)
> > > > - service grid stabilization
> > > > - SQL memory utilization improvements
> > > > - more?
> > > >
> > > > Can you please solicit status from the community for these tasks?
> > > >
> > > > D.
> > > >
> > > > On Mon, Aug 20, 2018 at 11:22 AM, Nikolay Izhikov <ni...@apache.org>
> > > > wrote:
> > > >
> > > > > Hello, Igniters.
> > > > >
> > > > > I'm release manager of Apache Ignite 2.7.
> > > > >
> > > > > It's time to start discussion of release. [1]
> > > > >
> > > > > Current code freeze date is September, 30.
> > > > > If you have any objections - please, responsd to this thread.
> > > > >
> > > > > [1] https://cwiki.apache.org/confluence/display/IGNITE/
> > > Apache+Ignite+2.7
> > >
>
>
Re: Apache Ignite 2.7 release
Posted by Pavel Petroshenko <pa...@petroshenko.com>.
Hi Nikolay,
Python [1], PHP [2], and Node.js [3] thin clients will get into the release.
Thanks,
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 Tue, Aug 21, 2018 at 12:20 PM, Dmitriy Setrakyan <ds...@apache.org>
wrote:
> Thanks, Nikolay!
>
> I think it is important to include the links to all important Jira tickets
> in this thread, so that the community can track them.
>
> D.
>
> On Tue, Aug 21, 2018 at 12:06 AM, Nikolay Izhikov <ni...@apache.org>
> wrote:
>
> > Hello, Dmitriy.
> >
> > I think Transparent Data Encryption will be available in 2.7
> >
> > В Пн, 20/08/2018 в 13:20 -0700, Dmitriy Setrakyan пишет:
> > > Hi Nikolay,
> > >
> > > Thanks for being the release manager!
> > >
> > > I am getting a bit lost in all these tickets. Can we specify some
> > > high-level tickets, that are not plain bug fixes, which will be
> > interesting
> > > for the community to notice?
> > >
> > > For example, here are some significant tasks that the community is
> either
> > > working on or has been working on:
> > >
> > > - Node.JS client
> > > - Python client
> > > - Transactional SQL (MVCC)
> > > - service grid stabilization
> > > - SQL memory utilization improvements
> > > - more?
> > >
> > > Can you please solicit status from the community for these tasks?
> > >
> > > D.
> > >
> > > On Mon, Aug 20, 2018 at 11:22 AM, Nikolay Izhikov <nizhikov@apache.org
> >
> > > wrote:
> > >
> > > > Hello, Igniters.
> > > >
> > > > I'm release manager of Apache Ignite 2.7.
> > > >
> > > > It's time to start discussion of release. [1]
> > > >
> > > > Current code freeze date is September, 30.
> > > > If you have any objections - please, responsd to this thread.
> > > >
> > > > [1] https://cwiki.apache.org/confluence/display/IGNITE/
> > Apache+Ignite+2.7
> >
>
Re: Apache Ignite 2.7 release
Posted by Dmitriy Setrakyan <ds...@apache.org>.
Thanks, Nikolay!
I think it is important to include the links to all important Jira tickets
in this thread, so that the community can track them.
D.
On Tue, Aug 21, 2018 at 12:06 AM, Nikolay Izhikov <ni...@apache.org>
wrote:
> Hello, Dmitriy.
>
> I think Transparent Data Encryption will be available in 2.7
>
> В Пн, 20/08/2018 в 13:20 -0700, Dmitriy Setrakyan пишет:
> > Hi Nikolay,
> >
> > Thanks for being the release manager!
> >
> > I am getting a bit lost in all these tickets. Can we specify some
> > high-level tickets, that are not plain bug fixes, which will be
> interesting
> > for the community to notice?
> >
> > For example, here are some significant tasks that the community is either
> > working on or has been working on:
> >
> > - Node.JS client
> > - Python client
> > - Transactional SQL (MVCC)
> > - service grid stabilization
> > - SQL memory utilization improvements
> > - more?
> >
> > Can you please solicit status from the community for these tasks?
> >
> > D.
> >
> > On Mon, Aug 20, 2018 at 11:22 AM, Nikolay Izhikov <ni...@apache.org>
> > wrote:
> >
> > > Hello, Igniters.
> > >
> > > I'm release manager of Apache Ignite 2.7.
> > >
> > > It's time to start discussion of release. [1]
> > >
> > > Current code freeze date is September, 30.
> > > If you have any objections - please, responsd to this thread.
> > >
> > > [1] https://cwiki.apache.org/confluence/display/IGNITE/
> Apache+Ignite+2.7
>
Re: Apache Ignite 2.7 release
Posted by Nikolay Izhikov <ni...@apache.org>.
Hello, Dmitriy.
I think Transparent Data Encryption will be available in 2.7
В Пн, 20/08/2018 в 13:20 -0700, Dmitriy Setrakyan пишет:
> Hi Nikolay,
>
> Thanks for being the release manager!
>
> I am getting a bit lost in all these tickets. Can we specify some
> high-level tickets, that are not plain bug fixes, which will be interesting
> for the community to notice?
>
> For example, here are some significant tasks that the community is either
> working on or has been working on:
>
> - Node.JS client
> - Python client
> - Transactional SQL (MVCC)
> - service grid stabilization
> - SQL memory utilization improvements
> - more?
>
> Can you please solicit status from the community for these tasks?
>
> D.
>
> On Mon, Aug 20, 2018 at 11:22 AM, Nikolay Izhikov <ni...@apache.org>
> wrote:
>
> > Hello, Igniters.
> >
> > I'm release manager of Apache Ignite 2.7.
> >
> > It's time to start discussion of release. [1]
> >
> > Current code freeze date is September, 30.
> > If you have any objections - please, responsd to this thread.
> >
> > [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.7
Re: Apache Ignite 2.7 release
Posted by Dmitriy Setrakyan <ds...@apache.org>.
Hi Nikolay,
Thanks for being the release manager!
I am getting a bit lost in all these tickets. Can we specify some
high-level tickets, that are not plain bug fixes, which will be interesting
for the community to notice?
For example, here are some significant tasks that the community is either
working on or has been working on:
- Node.JS client
- Python client
- Transactional SQL (MVCC)
- service grid stabilization
- SQL memory utilization improvements
- more?
Can you please solicit status from the community for these tasks?
D.
On Mon, Aug 20, 2018 at 11:22 AM, Nikolay Izhikov <ni...@apache.org>
wrote:
> Hello, Igniters.
>
> I'm release manager of Apache Ignite 2.7.
>
> It's time to start discussion of release. [1]
>
> Current code freeze date is September, 30.
> If you have any objections - please, responsd to this thread.
>
> [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.7