Done, thanks.
> 21 мая 2020 г., в 16:34, Ilya Kasnacheev
> написал(а):
>
> Hello!
>
> Please apply https://github.com/apache/ignite/pull/7832
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> чт, 21 мая 2020 г. в 16:02, Nikolay Izhikov :
>
>> Hello, Ilya.
>>
>> Actually, I’m uploading RC0 right
Hello!
Please apply https://github.com/apache/ignite/pull/7832
Regards,
--
Ilya Kasnacheev
чт, 21 мая 2020 г. в 16:02, Nikolay Izhikov :
> Hello, Ilya.
>
> Actually, I’m uploading RC0 right now.
> Let’s include these fixes in RC1, if you don’t mind?
>
> > 21 мая 2020 г., в 16:00, Ilya
Hello, Ilya.
Actually, I’m uploading RC0 right now.
Let’s include these fixes in RC1, if you don’t mind?
> 21 мая 2020 г., в 16:00, Ilya Kasnacheev
> написал(а):
>
> Hello!
>
> Do you mind if I push additional change to fix English in some of these
> entries? A lot of these has times not
Hello!
Do you mind if I push additional change to fix English in some of these
entries? A lot of these has times not concording with "fixed".
Regards,
--
Ilya Kasnacheev
ср, 20 мая 2020 г. в 15:47, Nikolay Izhikov :
> Hello, Igniters.
>
> I prepared a PR with release notes.
> Please, take a
Hello, Igniters.
I prepared a PR with release notes.
Please, take a look [1]
[1] https://github.com/apache/ignite/pull/7821
> 20 мая 2020 г., в 13:06, Nikolay Izhikov написал(а):
>
> Hello, Jury.
>
> It seems we reached code freeze step for 2.8.1 release.
> I will prepare rc for it shortly.
Hello, Jury.
It seems we reached code freeze step for 2.8.1 release.
I will prepare rc for it shortly.
> 14 мая 2020 г., в 11:08, Юрий написал(а):
>
> Nikolay,
>
> Release 2.8.1 are delayed and announced dates [1] at release page is not
> actual. Could you update it to reflect current vision
Nikolay,
Release 2.8.1 are delayed and announced dates [1] at release page is not
actual. Could you update it to reflect current vision of release date?
[1]. https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8.1
чт, 7 мая 2020 г. в 17:23, Nikolay Izhikov :
> Done.
>
>
> > 7
Done.
> 7 мая 2020 г., в 13:20, Denis Garus написал(а):
>
> Nikolay,
> could we add the simple improvement [1] to 2.8.1 scope?
>
> 1. https://issues.apache.org/jira/browse/IGNITE-12983
>
> чт, 30 апр. 2020 г. в 11:26, Alex Plehanov :
>
>> Nikolay,
>>
>> TC results: [1], [2]
>> I've
Nikolay,
could we add the simple improvement [1] to 2.8.1 scope?
1. https://issues.apache.org/jira/browse/IGNITE-12983
чт, 30 апр. 2020 г. в 11:26, Alex Plehanov :
> Nikolay,
>
> TC results: [1], [2]
> I've cherry-picked IGNITE-12933 and IGNITE-12855 to 2.8.1
>
> [1]:
>
>
Nikolay,
TC results: [1], [2]
I've cherry-picked IGNITE-12933 and IGNITE-12855 to 2.8.1
[1]:
https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull%2F7754%2Fhead=Latest=ignite-2.8.1
[2]:
Hello, Alex.
+1 from me.
> 28 апр. 2020 г., в 15:03, Alex Plehanov написал(а):
>
> Hello guys,
>
> While we are still waiting for some tickets to resolve I propose to
> cherry-pick to 2.8.1 two more bugfixes:
> IGNITE-12933 Fixed node failure after put incorrect key class for cache
> with
Hello guys,
While we are still waiting for some tickets to resolve I propose to
cherry-pick to 2.8.1 two more bugfixes:
IGNITE-12933 Fixed node failure after put incorrect key class for cache
with indexed types
IGNITE-12855 Fixed node failure with concurrent get operation and entry
expiration
Taras.
Thank you, very much!
You changes merged to 2.8.1 branch.
Igniters,
We have 10 tickets scheduled for 2.8.1 release:
OPEN:
IGNITE-11687Concurrent WAL replay & log may fail with CRC error on read -
Dmitriy Govorukhin
IGNITE-12346.NET: Platform error:System.NullReferenceException
Hi,
Nikolay, i've created PR [1] that contains the SQL-related tickets to
port into 2.8.1:
IGNITE-12790 Introduce distributed SQL configuration and ability to
disable SQL functions.
IGNITE-12887 Fix handle type mismatch exception on compare values while
traversing index tree.
IGNITE-12848
Hello, Igniters.
I propose to cherry-pick to 2.8.1 ticket [1].
In addition to adding a new metric, it fixes a bug when, after deactivation,
GridDhtPartitionsExchangeFuture#rebalanced flag was not reset. And therefore,
it can be different on nodes that are already in the cluster from newly
Hello, Ivan.
I think we can include this improvements.
Please, go ahead.
> 22 апр. 2020 г., в 10:21, Ivan Bessonov написал(а):
>
> Hi Igniters,
>
> I'm continuing with IGNITE-12756 PR creation. It turned out that we need 3
> more cherry-picks
> to avoid massive code changes. Tests started
Hi Igniters,
I'm continuing with IGNITE-12756 PR creation. It turned out that we need 3
more cherry-picks
to avoid massive code changes. Tests started failing after my initial
attempt to create that PR.
So, in total I have PR with 6 commits in it. Some of them fix components
and tests for them,
Hello, Nikolay.
This has been fixed by increasing the test timeout in IGNITE-12683 [1][2].
[1] https://issues.apache.org/jira/browse/IGNITE-12683
[2]
https://github.com/apache/ignite/commit/bf394a77e1de6432e493eb2818243a82b577f11e
вт, 21 апр. 2020 г. в 18:28, Nikolay Izhikov :
>
> Hello,
Nikolay,
@Peter Ivanov or @Dmitriy Pavlov
should
be able to help with the TeamCity Bot setup. Let's put all the knowledge on
paper once you figure it out.
-
Denis
On Tue, Apr 21, 2020 at 2:53 AM Nikolay Izhikov wrote:
> Igniters.
>
> Can someone from Grid Gain help me with setup TC bot to
Hello, Igniters.
While cherry-picking to 2.8.1 I found flaky test regarding BPlusTree [1], [2]
All failures of this tests relates to PR’s based on 2.8.
It seems we hav fix in master but doesn’t have it in 2.8 and 2.8.1
Can someone suggest, what commit fixes this tests?
[1]
Sure, here's PR with 3 cherry-picked commits that I mentioned:
https://github.com/apache/ignite/pull/7708
вт, 21 апр. 2020 г. в 17:17, Nikolay Izhikov :
> OK then, let’s include it in the 2.8.1
>
> Ivan, can you, please, prepare PR in the ignite-2.8.1 branch that contain
> cherry-pick for all
OK then, let’s include it in the 2.8.1
Ivan, can you, please, prepare PR in the ignite-2.8.1 branch that contain
cherry-pick for all required commits?
> 21 апр. 2020 г., в 17:01, Andrey Gura написал(а):
>
> Hi
>
>> IGNITE-12735 - Metric exporter implementation could lead to
>>
Hi
> IGNITE-12735 - Metric exporter implementation could lead to
> NullPointerException from gauge which invoke communication
> IGNITE-12568 - MessageFactory implementations refactoring
> Personally, I’m against any refactoring improvements in bug fix release.
> So, I propose to exclude
Taras,
Great news! Thank you!
Let me know, when you got the visa.
> 21 апр. 2020 г., в 14:02, Taras Ledkov написал(а):
>
> Hi,
>
> Nikolay, i've created PR [1] that contains the SQL-related tickets to port
> into 2.8.1:
> - IGNITE-12790 Introduce distributed SQL configuration and ability to
Hi,
Nikolay, i've created PR [1] that contains the SQL-related tickets to
port into 2.8.1:
- IGNITE-12790 Introduce distributed SQL configuration and ability to
disable SQL functions.
- IGNITE-12887 Fix handle type mismatch exception on compare values
while traversing index tree.
-
Igniters.
Can someone from Grid Gain help me with setup TC bot to monitor ignite-2.8.1
branch?
> 21 апр. 2020 г., в 11:11, Nikolay Izhikov написал(а):
>
>> I've cherry-picked IGNITE-12734 to 2.8.1 branch.
>
>
> Thanks!
>
>> considering commit "683f22e64f IGNITE-12756 TcpCommunication SPI
> I've cherry-picked IGNITE-12734 to 2.8.1 branch.
Thanks!
> considering commit "683f22e64f IGNITE-12756 TcpCommunication SPI metrics
>> improvement" - it depends
>> on https://issues.apache.org/jira/browse/IGNITE-12735 and
>> https://issues.apache.org/jira/browse/IGNITE-12568,
>> both were
Nikolay,
I've cherry-picked IGNITE-12734 to 2.8.1 branch.
вт, 21 апр. 2020 г. в 10:02, Ivan Bessonov :
> Hello, Igniters,
>
> considering commit "683f22e64f IGNITE-12756 TcpCommunication SPI metrics
> improvement" - it depends
> on https://issues.apache.org/jira/browse/IGNITE-12735 and
>
Hello, Igniters,
considering commit "683f22e64f IGNITE-12756 TcpCommunication SPI metrics
improvement" - it depends
on https://issues.apache.org/jira/browse/IGNITE-12735 and
https://issues.apache.org/jira/browse/IGNITE-12568,
both were targeted to 2.9, but this has to be changed probably.
There
Hello, Igniters.
I perform cherry-pick for most commits targeted for 2.8.1 release.
TC bot results -
https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull%2F7690%2Fhead=Latest=pull%2F7102%2Fhead
I need help with cherry picking the following commits:
- 4e6cd2ce04
Hello, Igniters.
After some scripting I got the following lists of commits to transfer from
master to 2.8.1
It will be very helpful if someone double check my results.
I did the following:
1. Export all resolved tickets targeted to 2.8.1 from Mira
2. Found commit difference between 2.8.0 and
Thanks, I will keep the original ticket in patch available then and leave a
comment.
Let us know if need any help with moving commits to the release branch.
пт, 17 апр. 2020 г. в 18:18, Nikolay Izhikov :
> Please, don’t cherry pick tickets to 2.8.1
> It seems I have to cherry pick many previous
Please, don’t cherry pick tickets to 2.8.1
It seems I have to cherry pick many previous tickets for 2.8.1 to avoid
conflicts.
> 17 апр. 2020 г., в 18:01, Alexey Goncharuk
> написал(а):
>
> Nikolay,
>
> If I merge a ticket that is already targeted for 2.8.1 to master, do you
> prefer this
Nikolay,
If I merge a ticket that is already targeted for 2.8.1 to master, do you
prefer this ticket to be cherry-picket to 2.8.1 yourself or should I merge
it to the release branch?
пт, 17 апр. 2020 г. в 16:55, Ivan Pavlukhin :
> Great!
>
> Best regards,
> Ivan Pavlukhin
>
> пт, 17 апр. 2020
Great!
Best regards,
Ivan Pavlukhin
пт, 17 апр. 2020 г. в 12:48, Nikolay Izhikov :
>
> OK, let’s try it
>
> > I do not know who is a manager for 2.8.1.
>
> I am.
>
>
> > 17 апр. 2020 г., в 12:42, Ivan Pavlukhin написал(а):
> >
> >> We didn’t it for the previous releases.
> >> Why we should
OK, let’s try it
> I do not know who is a manager for 2.8.1.
I am.
> 17 апр. 2020 г., в 12:42, Ivan Pavlukhin написал(а):
>
>> We didn’t it for the previous releases.
>> Why we should start to do it?)
>
> Because it seems to be a good thing, is not it? I suppose it is
> important to know
> We didn’t it for the previous releases.
> Why we should start to do it?)
Because it seems to be a good thing, is not it? I suppose it is
important to know who is a release manager (the current thread subject
has a "Manager" keyword). E.g. I do not know who is a manager for
2.8.1.
Best regards,
Hello,
> Should not we reflect on the release page [1] who is a release manager?
We didn’t it for the previous releases.
Why we should start to do it?)
> I suggest to include these fixes into 2.8.1 release:
Thanks, included.
> 17 апр. 2020 г., в 12:20, Ivan Rakov написал(а):
>
> Hi,
>
>
Hi,
I suggest to include these fixes into 2.8.1 release:
https://issues.apache.org/jira/browse/IGNITE-12101
https://issues.apache.org/jira/browse/IGNITE-12651
On Fri, Apr 17, 2020 at 11:32 AM Ivan Pavlukhin wrote:
> Hi folks,
>
> A side note from an external spectator. Should not we reflect on
Hi folks,
A side note from an external spectator. Should not we reflect on the
release page [1] who is a release manager?
[1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8.1
Best regards,
Ivan Pavlukhin
пт, 17 апр. 2020 г. в 11:11, Nikolay Izhikov :
>
> Hello, Igniters.
Hello, Igniters.
I’ve added all tickets proposed in this thread to 2.8.1 scope [1]
For now we have
61 resolved tickets.
19 unresolved tickets.
[1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8.1
> 17 апр. 2020 г., в 01:38, Alex Plehanov написал(а):
>
> Hello guys,
>
Hello guys,
I propose to cherry-pick to 2.8.1 following bug-fixes too, which are
already in master:
Scan query over an evicted partition can cause node failure (IGNITE-12734
[1])
Java thin client: There were problems with deserialization of some types on
the client-side, these types can't be used
Nikolay,
Probably, we should not wait for all blocker issues in minor bug-fix
releases except very special cases. I think we should release all
accumulated bug-fixes `as is` and schedule the next 2.8.2 release.
This will allow as to have shorten minor releases.
On Thu, 16 Apr 2020 at 18:17,
Hello, Igniters.
I’m started to work on this 2.8.1 release [1]
Resolved issues for release(28) - [2]
Unresolved issues for release(30) - [3]
My next step:
1. I want to double-check that all commits for the tickets with the
fixVersion=2.8.1 presented in corresponding release branch.
And
This ticket is very important too, as for me [1] Anton Kalashnikov, what do you
think ?
[1] https://issues.apache.org/jira/browse/IGNITE-12801
>Folks,
>
>I'd like to add ticket IGNITE-12805 "NullPointerException on node restart
>when 3rd party persistence and Ignite native persistence are
Folks,
I'd like to add ticket IGNITE-12805 "NullPointerException on node restart
when 3rd party persistence and Ignite native persistence are used" to
ignite-2.8.1 scope.
[1] https://issues.apache.org/jira/browse/IGNITE-12805
Thanks,
S.
вт, 7 апр. 2020 г. в 19:57, Ilya Kasnacheev :
> Hello!
Hello!
Done!
Regards,
--
Ilya Kasnacheev
вт, 7 апр. 2020 г. в 12:31, Sergey :
> Hi,
>
> I'm proposing to add
> https://issues.apache.org/jira/browse/IGNITE-12549 (fix iterators/scan
> queries for replicated caches)
> to 2.8.1.
>
> Best regards,
> Sergey Kosarev.
>
>
> вс, 5 апр. 2020 г. в
Hi,
I'm proposing to add
https://issues.apache.org/jira/browse/IGNITE-12549 (fix iterators/scan
queries for replicated caches)
to 2.8.1.
Best regards,
Sergey Kosarev.
вс, 5 апр. 2020 г. в 01:22, Saikat Maitra :
> Hi,
>
> I observed that we already have release 2.8.1 branch
>
Hi,
I observed that we already have release 2.8.1 branch
https://github.com/apache/ignite/tree/ignite-2.8.1
In that case we should be ok to merge these 2 open PRs in master to make it
available for 2.9.0 release.
https://github.com/apache/ignite/pull/7240
Igniters,
I support Nikolay Izhikov as the release manager of 2.8.1 Apache
Ignite release. Since no one else of committers, PMCs expressed a
desire to lead this release I think we can close this question and
focus on the release scope and dates.
Ivan,
You helped me configuring TC.Bot that
Hi,
I propose to add the issue [1] related to SQL query execution to this scope.
We had omitted this case and Ignite 2.8 contains serious SQL issue:
cursor of a local query is not thread-safe.
It is root cause of several SQL issue, e.g. JDBC thin client cannot
execute query from replicated
Could we add features to the scope of this release? Or we will fix known
bugs only?
чт, 19 мар. 2020 г., 17:59 Nikolay Izhikov :
> I want to be a release manager.
>
>
> > 19 марта 2020 г., в 17:52, Denis Magda написал(а):
> >
> > Igniters,
> >
> > As long as 2.8.1 is inevitable and we already
I want to be a release manager.
> 19 марта 2020 г., в 17:52, Denis Magda написал(а):
>
> Igniters,
>
> As long as 2.8.1 is inevitable and we already keep adding critical issues
> to the working queue, let's settle on the release time frames and decide
> who will be a release manager. This is
Igniters,
As long as 2.8.1 is inevitable and we already keep adding critical issues
to the working queue, let's settle on the release time frames and decide
who will be a release manager. This is the time proposed by Maxim and,
personally, I concur with such a schedule:
- Scope Freeze: April
Folks,
I'd like to add ticket IGNITE-12774 Transaction hangs after too many open
files NIO exception [1] to ignite-2.8.1 scope.
[1] https://issues.apache.org/jira/browse/IGNITE-12774
ср, 18 мар. 2020 г. в 16:53, Maxim Muzafarov :
> Folks,
>
> Can we add ignite-2.8.1 [2] branch under TC.Bot
Folks,
Can we add ignite-2.8.1 [2] branch under TC.Bot protection [1]?
[1] https://mtcga.gridgain.com/guard.html
[2] https://github.com/apache/ignite/tree/ignite-2.8.1
On Mon, 16 Mar 2020 at 16:32, Alexey Goncharuk
wrote:
>
> Folks,
>
> I've walked through all the commits to master since 2.8
Folks,
I've walked through all the commits to master since 2.8 branch was cut and
filtered some tickets that in my opinion are worth including to 2.8.1
release below (note that they are ready end the effort of including them to
the release should be low as long as there are no implicit
Hello, guys.
I propose myself as a release manager for 2.8.1.
> 16 марта 2020 г., в 14:19, kpushenko написал(а):
>
> Hi, igniters!
>
> I would like to propose a discussion of version 2.9 and scope releases for
> 2020 to another discussion thread.
>
> I understand that there is no objection
Hi, igniters!
I would like to propose a discussion of version 2.9 and scope releases for
2020 to another discussion thread.
I understand that there is no objection to release 2.8.1.
I support the date from Maxim and dmagda ~ 1 month to May 1.
I offer my help with the release of Ignite 2.8.1. I
Aleksey,
> My propose:
> ~ June 01 - 2.8.1
> ~ September 01 - 2.8.2
> ~ November 01 - 2.9.0
What is your motivation for such release schedule? I believe release
should be features/fixes driven not by time/deadline driven.
We can release 2.8.x versions every week yet (as maintenance
releases).
Folks,
Not sure that we will be moving in the right direction discussing dates
with no clarity of what is to be released in a specific version. Instead,
let's talk out our plans/tasks first and then put them on a timeline. That
certainly applies to big releases such as 2.9 that deserve a
Hello, Igniters.
I propose to cherry-pick this bug-fix ticket to the 2.8.1:
IGNITE-12728 The cache#putAllAsync method does not collect statistics [1]
[1] https://issues.apache.org/jira/browse/IGNITE-12728
чт, 12 мар. 2020 г. в 18:27, Maxim Muzafarov :
>
> Alexey,
>
> > Now it’s not clear why
Alexey,
> Now it’s not clear why consumers should fix bugs themselves if they don’t
> have the opportunity to get the expected delivery time.
Fully agree.
Users should see the release plan for the current year.
On Thu, 12 Mar 2020 at 18:16, Aleksey Chetaev wrote:
>
> I don’t see the donator
I don’t see the donator desire here. This desire is to give AI consumers more
frequent releases with bug fix and understanding when we, as a community,
will release new, announced features to them.
Now it’s not clear why consumers should fix bugs themselves, if they don’t
have the opportunity to
Hello, Petr.
> I thought the release cycle should be community driven, not single donator.
We are the part of the global Ignite community, itn’t it?
If you know some reason to postpone bug fix releases, please, write it down.
> what's the haste with next minor version?
Users of the Ignite
Great dates for released, I support mr. Chetaev
чт, 12 мар. 2020 г., 17:38 Aleksey Chetaev :
> Hi, Igniters!
> I propose to discuss immediately the timing of 2.9.0 and interim releases!
> My propose:
> ~ June 01 - 2.8.1
> ~ September 01 - 2.8.2
> ~ November 01 - 2.9.0
>
> Sberbank team, for its
I thought the release cycle should be community driven, not single donator.
Should not 2.8.1 be bug fixing / stabilising release with release date as soon
as all issues are resolved?
Also — what's the haste with next minor version? Cannot we deliver next fix
versions with per-feature release
Hi, Igniters!
I propose to discuss immediately the timing of 2.9.0 and interim releases!
My propose:
~ June 01 - 2.8.1
~ September 01 - 2.8.2
~ November 01 - 2.9.0
Sberbank team, for its part, is ready to take on the work of management
interim releases.
Regards,
Aleksey Chetaev.
--
Sent
Hello, Igniters.
I propose to add these tickets to the 2.8.1 scope
[1] Disallow silent deactivation in CLI and REST -
https://issues.apache.org/jira/browse/IGNITE-12701
[2] Compute job system view - https://issues.apache.org/jira/browse/IGNITE-12745
[3] Transaction operations metrics -
Hi!
I don't see https://issues.apache.org/jira/browse/IGNITE-12582 in future
release plan. Append it too, please
On Thu, 12 Mar 2020 at 17:12, Ilya Kasnacheev
wrote:
> Hello!
>
> I have marked https://issues.apache.org/jira/browse/IGNITE-12672 to 2.8.1
> since it is an important Spring Data
Hello!
I have marked https://issues.apache.org/jira/browse/IGNITE-12672 to 2.8.1
since it is an important Spring Data issue with trivial fix.
"Query annotations are not working if statement keywords are in lower case"
We should make sure that all fixes in 2.8.1 also end up in master - needs
to
Igniters,
Let's start a discussion about the next Apache Ignite 2.8.1 bugfix
release. The following things need to be discussed:
- time/deadlines
- scope of the release
- a release manager candidate
My personal vision that the 2.8.1 release is a bugfix release, so
`improvement` issues are
72 matches
Mail list logo
