Alexey,
The changes already have been tested, so no TC problems expected.
If this is true, then we need just a few hours to merge them.
From: Alexey Goncharuk
Sent: Wednesday, September 11, 2019 6:03 PM
To: dev
Cc: Dmitriy Govorukhin; Anton Kalashnikov
Subject: Re: Re[2]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)
Alexandr,
I almost sent the vote email :) When do you expect the fix to be in master
and 2.7.6?
ср, 11 сент. 2019 г. в 17:38, Alexandr Shapkin <lexw...@gmail.com>:
Folks,
A critical bug was detected in .NET [1].
I understand that it’s a little bit late, but I propose to include this
issue into the release scope.
PR is ready, currently waiting for a TC visa.
Thoughts?
[1] - https://issues.apache.org/jira/browse/IGNITE-12163
From: Alexey Goncharuk
Sent: Monday, September 9, 2019 5:11 PM
To: dev
Cc: Dmitriy Govorukhin; Anton Kalashnikov
Subject: Re: Re[2]: Apache Ignite 2.7.6 (Time, Scope, and Release
manager)
Igniters,
I just pushed the last ticket to ignite-2.7.6 branch; looks like we are
ready for the next iteration.
Given that Dmitriy Pavlov will be unavailable till the end of this week,
I
will take over the release. TC re-run is started.
чт, 5 сент. 2019 г. в 16:14, Dmitriy Govorukhin <
dmitriy.govoruk...@gmail.com>:
Hi Igniters,
I finished work on https://issues.apache.org/jira/browse/IGNITE-12127,
fix
already in master and ignite-2.7.6
On Wed, Sep 4, 2019 at 2:22 PM Dmitriy Govorukhin <
dmitriy.govoruk...@gmail.com> wrote:
Hi Alexey,
I think that I will finish work on the fix tomorrow. Fix already
completed
but I need to get VISA from TC bot.
On Mon, Sep 2, 2019 at 8:27 PM Alexey Goncharuk <
alexey.goncha...@gmail.com> wrote:
Folks, it looks like I was overly optimistic with the estimates for
the
mentioned two tickets.
Dmitriy, Anton,
Can you share your vision when the issues will be fixed? Perhaps, it
makes
sense to release 2.7.6 with the already fixed issues and schedule
2.7.7?
Neither of them is a regression, so it's ok to release 2.7.6 as it
is
now.
Thoughts?
сб, 31 авг. 2019 г. в 11:37, Alexey Goncharuk <
alexey.goncha...@gmail.com
:
Yes, my bad, forgot to include the link. That's the one.
пт, 30 авг. 2019 г. в 15:01, Maxim Muzafarov <maxmu...@gmail.com
:
Alexey,
Does the issue [1] is related to this [2] discussion on the
user-list?
If yes, I think it is very important to include these fixes to
2.7.6.
[1] https://issues.apache.org/jira/browse/IGNITE-12127
[2]
http://apache-ignite-users.70518.x6.nabble.com/Node-failure-with-quot-Failed-to-write-buffer-quot-error-td29100.html
On Fri, 30 Aug 2019 at 14:26, Alexei Scherbakov
<alexey.scherbak...@gmail.com> wrote:
Alexey,
Looks like important fixes, better to include them.
пт, 30 авг. 2019 г. в 12:51, Alexey Goncharuk <
alexey.goncha...@gmail.com>:
Igniters,
Given that the RC1 vote did not succeed and we are still
waiting
for
a few
minor fixes, may I suggest including these two tickest to the
2.7.6
scope?
https://issues.apache.org/jira/browse/IGNITE-12127
https://issues.apache.org/jira/browse/IGNITE-12128
The first one has been already reported on the dev-list [1],
the
second one
may cause a state when an Ignite node cannot start on
existing
persisted
data. Looking at the tickets, the fixes should be reasonably
easy,
so
it
should not shift 2.7.6 release timeline much.
Thoughts?
ср, 28 авг. 2019 г. в 15:25, Nikolay Izhikov <
nizhi...@apache.org
:
Separate repos for different Spark version is a good idea
for
me.
Anyway, can you help with Spark version migration, for
now?
В Ср, 28/08/2019 в 15:20 +0300, Alexey Zinoviev пишет:
Maybe the best solution today add for each new version of
Spark
the
sub-module (Spark-2.3, Spark-2.4) or the separate
repository
with
modules
for each version or another way with separate repository
and
different
branches like in
https://github.com/datastax/spark-cassandra-connector
3 ways to support different versions with the different
costs
of
support
In the case of separate repository I could help, for
example
ср, 28 авг. 2019 г. в 14:57, Nikolay Izhikov <
nizhi...@apache.org
:
Hello, Alexey.
But the
compatibility with Spark 2.3 will be broken, isn't
it?
Yes.
Do you have any
plans to support the different version of Spark
without
loosing
your
unique
expertise in Spark-Ignite integration?
What do you mean by "my unique expertise"? :)
How do you see support of several Spark version?
В Ср, 28/08/2019 в 14:29 +0300, Alexey Zinoviev пишет:
Dear Nikolay Izhikov
Are you going to update the Ignite-Spark integration
for
Spark 2.4.
But
the
compatibility with Spark 2.3 will be broken, isn't
it?
Do
you
have
any
plans to support the different version of Spark
without
loosing
your
unique
expertise in Spark-Ignite integration?
чт, 15 авг. 2019 г. в 14:54, Nikolay Izhikov <
nizhi...@apache.org
:
Hello, Igniters.
I try to upgrade Spark version but failed.
Seems, internal Spark API(External Catalog, SQL
planner)
that we
use
changed a lot.
So it will take some time to upgrade version.
For now, I work hard to complete the second phase
of
IEP-35
so I
postpone
upgrade Spark version to Ignite 2.8.
В Чт, 15/08/2019 в 14:51 +0300, Dmitriy Pavlov
пишет:
Hi Denis,
Sure, since code freeze is planned for today, I
don't
mind to
include
this
bug.
Ivan, could you complete this issue by 20 August?
BTW #1, Dmitriy Govoruchnin, please reply about
commit
for
https://issues.apache.org/jira/browse/IGNITE-11953?src=confmacro
BTW #2, FYI, release page is now available here
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.7.6
BTW #3, FYI, release related test PR is here
https://github.com/apache/ignite/pull/6775 and
it's
TC
Bot
report is
here:
https://mtcga.gridgain.com/pr.html?serverId=apache&suiteId=IgniteTests24Java8_RunAll&branchForTc=ignite-2.7.6&action=Latest&baseBranchForTc=ignite-2.7.6
чт, 15 авг. 2019 г. в 13:55, Denis Magda <
dma...@apache.org>:
An Ignite user just reported a silly issue that
needs
to be
fixed
in
2.7.6:
https://issues.apache.org/jira/browse/IGNITE-12068
More details and context:
https://stackoverflow.com/questions/57479636/simple-select-query-missing-rows-in-ignite
Ivan, please help us to make it to the release.
-
Denis
On Tue, Aug 13, 2019 at 6:47 AM Denis Magda <
dma...@apache.org
wrote:
IGNITE-12507 (Persistence files are stored to
temp
dir) has
definitely be
added the scope and treated one of the main
release
drivers.
Dmitry, please let us know once the release
wiki
page
is
ready so
that we
can finalize the timelines based on chosen
scope.
-
Denis
On Mon, Aug 12, 2019 at 7:12 PM Dmitriy
Pavlov
<
dpav...@apache.org>
wrote:
Hi,
Thanks to everyone, who participated in the
discussion.
I would like to wait also fix for
https://issues.apache.org/jira/browse/IGNITE-12057
and discussion results for that issue:
https://lists.apache.org/thread.html/498a14b3971950a45ef57f45cc23d2438ce1afba000b586e230927bf@%3Cdev.ignite.apache.org%3E
Since some issues are still open, we'll
probably
move
some
dates
forward,
but it seems we managed to discuss scope
before
scope
freeze.
I consider now the scope is frozen - no new
feature
can
be
added
to the
scope of 2.7.6. We're entering the rampdown
phase.
Sincerely,
Dmitriy Pavlov
See
https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
for
more details.
пн, 12 авг. 2019 г. в 16:37, Zhenya
Stanilovsky
<arzamas...@mail.ru.invalid
:
Hi al,, i also suggest to append [1],
cause
it
could
produce
CorruptedTreeException in some scenario.
[1]
https://issues.apache.org/jira/browse/IGNITE-12061
Hi all,
Can we include
https://issues.apache.org/jira/browse/IGNITE-12060
?
This is
a
https://issues.apache.org/jira/browse/IGNITE-11953
On Fri, Aug 9, 2019 at 10:04 AM Nikolay
Izhikov
<
nizhi...@apache.org
wrote:
Hello, Deni.
Nickolay, could you check if
that's a
quick
upgrade?
Yes, I will take a look.
В Чт, 08/08/2019 в 11:08 -0700, Denis
Magda
пишет:
Dmitry,
Please add this BTree corruption
fix
to
the
scope:
https://issues.apache.org/jira/browse/IGNITE-11953
Plus, I would upgrade our Spark
integration
to
version
2.4
as
long
as
2.3
goes with limitations reported by
our
users:
https://issues.apache.org/jira/browse/IGNITE-12054
Nickolay, could you check if
that's a
quick
upgrade?
-
Denis
On Thu, Aug 8, 2019 at 10:40 AM
Dmitriy
Pavlov <
dpav...@apache.org >
wrote:
Hi Ivan, Ilya, Igniters,
I would like this release would
be
as
minimal
as
possible.
According to dates proposed we
could
freeze
scope at
12.08, 4
days
is
more
than enough to stand up and say,
‘Hey,
I
have
an
urgent
fix’.
But
it is
also ok for me if we decide to
have
more
relaxed
dates.
For now, I suppose the following
fixed
should
be
cherry-picked:
https://issues.apache.org/jira/browse/IGNITE-11767
(Blocker)
GridDhtPartitionsFullMessage
retains
huge
maps
on
heap in
exchange
history
https://issues.apache.org/jira/browse/IGNITE-10451
(Major
Bug)
.NET:
Persistence does not work with
custom
affinity
function
https://issues.apache.org/jira/browse/IGNITE-9562
(Critical
Bug)
Destroyed
cache that resurrected on an old
offline
node
breaks
PME
But I will continue to research
JIRA.
Sincerely,
Dmitriy Pavlov
чт, 8 авг. 2019 г. в 17:30,
Павлухин
Иван
<
vololo...@gmail.com
:
What's the scope for this
release?
Same question.
On the other hand an idea of
2.7.6
release
attracts me
because
having
a practice of doing frequent
minor
releases
can
help
us to
build
reliable and predictable
release
rails.
чт, 8 авг. 2019 г. в 15:09,
Ilya
Kasnacheev <
ilya.kasnach...@gmail.com >:
Hello!
What's the scope for this
release?
Regards,
--
Ilya Kasnacheev
чт, 8 авг. 2019 г. в 15:07,
Dmitriy
Pavlov
<
dpav...@apache.org
:
Hi Apache Ignite
Developers,
We seem to be on the same
page
about 2.8
release,
but
we’ve
started
new
practice - minor releases,
the
first
release
was
2.7.5.
Unfortunately,
there is a couple of issues
still
not
fixed in
that
release,
so I
would
like to propose to prepare
one
more
minor
release
for
Apache
Ignite.
I propose my candidacy to
be
release
manager
once
again.
I could (of course with
help
from
Peter
Ivanov) do
some
additional
efforts
to complete and improve
process
doc
https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
I propose (most optimistic)
dates
for
release
stages:
Scope Freeze: August 12,
2019
Code Freeze: August 15,
2019
Voting Date: August 22,
2019
Release Date: August 27,
2019
WDYT?
If nobody minds, I will
create
branch
2.7.6
based
on
2.7.5
and
set up
in
the TC Bot during the
weekend.
Sincerely,
Dmitriy Pavlov
--
Best regards,
Ivan Pavlukhin
--
Zhenya Stanilovsky
--
Best regards,
Alexei Scherbakov
