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,
>
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.
>
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
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,
>
> I
> 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,
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 who
Andrey N. Gura created IGNITE-12910:
---
Summary: SqlViewExporterSpi uses log method which must not be used
in production code
Key: IGNITE-12910
URL: https://issues.apache.org/jira/browse/IGNITE-12910
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 start
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 г.
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 tick
Alexander Korenshteyn created IGNITE-12911:
--
Summary: B+Tree Corrupted exception when using a key extracted
from a value object --- and SQL enabled.
Key: IGNITE-12911
URL: https://issues.apache.org/jira/b
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
12 matches
Mail list logo
