You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by Alex Plehanov <pl...@gmail.com> on 2023/03/29 18:56:53 UTC

Apache Ignite 2.15 RELEASE [Time, Scope, Manager]

Dear Ignite Community!

I suggest starting Apache Ignite 2.15 release activities.

We've accumulated more than two hundred resolved issues [1] with new
features and bug fixes which are waiting for release.
The major changes related to the proposed release:
- Incremental snapshots.
- Java thin client improvements (logging, connections balancing,
    events listening, endpoints discovery)
- Calcite based SQL engine improvements (memory quotas, index scans
optimisations).
- Reworked permission management for system tasks.
- Removed some deprecated functionality (daemon nodes, visorcmd, legacy JMX
beans)
etc.

I want to propose myself to be the release manager of the planning release.

I propose the following timeline:

Scope Freeze: April 08, 2023
Code Freeze: April 15, 2023
Voting Date: April 22, 2023
Release Date: April 29, 2023

[1].
https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20in%20(2.15))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)

WDYT?

Re: Apache Ignite 2.15 RELEASE [Time, Scope, Manager]

Posted by Maxim Muzafarov <mm...@apache.org>.
+1

On Wed, 29 Mar 2023 at 20:57, Alex Plehanov <pl...@gmail.com> wrote:
>
> Dear Ignite Community!
>
> I suggest starting Apache Ignite 2.15 release activities.
>
> We've accumulated more than two hundred resolved issues [1] with new
> features and bug fixes which are waiting for release.
> The major changes related to the proposed release:
> - Incremental snapshots.
> - Java thin client improvements (logging, connections balancing,
>     events listening, endpoints discovery)
> - Calcite based SQL engine improvements (memory quotas, index scans
> optimisations).
> - Reworked permission management for system tasks.
> - Removed some deprecated functionality (daemon nodes, visorcmd, legacy JMX
> beans)
> etc.
>
> I want to propose myself to be the release manager of the planning release.
>
> I propose the following timeline:
>
> Scope Freeze: April 08, 2023
> Code Freeze: April 15, 2023
> Voting Date: April 22, 2023
> Release Date: April 29, 2023
>
> [1].
> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20in%20(2.15))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)
>
> WDYT?

Re: Apache Ignite 2.15 RELEASE [Time, Scope, Manager]

Posted by 18624049226 <18...@163.com>.
Hi Alex,

The following PR need to be merged:

https://issues.apache.org/jira/browse/IGNITE-19349

在 2023/4/19 02:16, Alex Plehanov 写道:
> Hello,
>
> I'm announcing a code freeze for the 2.15 release. Only blockers are
> accepted to the release since this moment.
>
> вт, 11 апр. 2023 г. в 13:25, Pavel Tupitsyn<pt...@apache.org>:
>
>> Alex,
>>
>> Just in case, Bugyard credentials are available to all PMCs in the private
>> SVN repo, see [1]
>>
>>> a lot of changes from 'ignite' to 'gridgain'
>> That's not good, requested changes on that PR.
>>
>> [1]
>>
>> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Document#HowtoDocument-DocumentationFeedbackviaBugyard
>>
>> On Tue, Apr 11, 2023 at 11:58 AM Alex Plehanov<pl...@gmail.com>
>> wrote:
>>
>>> Hello,
>>>
>>> I've merged and cherry-picked to 2.15 IGNITE-17892 and IGNITE-18260. As
>> for
>>> IGNITE-18496, I don't have access to the bugyard and can't validate all
>>> changes. For example, there are a lot of changes from 'ignite' to
>>> 'gridgain', not sure if it's correct or not. As far as this ticket will
>> be
>>> in master I will cherry-pick it into 2.15.
>>>
>>> вт, 11 апр. 2023 г. в 03:03, 18624049226<18...@163.com>:
>>>
>>>> Hi Alex,
>>>>
>>>> Can you help merge the following PR into 2.15 branch? small doc fix.
>>>>
>>>> https://issues.apache.org/jira/browse/IGNITE-17892
>>>>
>>>> https://issues.apache.org/jira/browse/IGNITE-18496
>>>>
>>>> https://issues.apache.org/jira/browse/IGNITE-18260
>>>>
>>>> 在 2023/4/10 21:31, Alex Plehanov 写道:
>>>>> Hello Igniters,
>>>>>
>>>>> I've cut the release branch: 'ignite-2.15'. Please, cherry-pick new
>>>> issues
>>>>> if needed.
>>>>>
>>>>> The 2.15 scope is frozen. Unresolved not-blocking issues will be
>> moved
>>> to
>>>>> the next release on the code freeze stage.
>>>>>
>>>>>
>>>>> пт, 7 апр. 2023 г. в 17:03, Alex Plehanov<pl...@gmail.com>:
>>>>>
>>>>>> Hello Igniters,
>>>>>>
>>>>>> I have created the 2.15 release page [1].
>>>>>>
>>>>>> Also, I've removed from the 2.15 scope some unresolved tickets
>>>> (unassigned
>>>>>> and without activity for a long time). Now we have 13 unresolved
>>> tickets
>>>>>> (not related to documentation).
>>>>>>
>>>>>> I have a plan to cut the release branch next monday (10 Apr). I will
>>>>>> inform you accordingly, when it will be done.
>>>>>>
>>>>>>
>>>>>> [1] :
>>>>>>
>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.15
>>>>>> пт, 31 мар. 2023 г. в 13:18, Jian Chen<ch...@gmail.com>:
>>>>>>
>>>>>>> +1
>>>>>>>
>>>>>>> Вячеслав Коптилин<sl...@gmail.com>于2023年3月31日 周五下午6:12写道:
>>>>>>>
>>>>>>>> +1
>>>>>>>>
>>>>>>>> ср, 29 мар. 2023 г. в 21:57, Alex Plehanov<
>> plehanov.alex@gmail.com
>>>> :
>>>>>>>>> Dear Ignite Community!
>>>>>>>>>
>>>>>>>>> I suggest starting Apache Ignite 2.15 release activities.
>>>>>>>>>
>>>>>>>>> We've accumulated more than two hundred resolved issues [1] with
>>> new
>>>>>>>>> features and bug fixes which are waiting for release.
>>>>>>>>> The major changes related to the proposed release:
>>>>>>>>> - Incremental snapshots.
>>>>>>>>> - Java thin client improvements (logging, connections balancing,
>>>>>>>>>       events listening, endpoints discovery)
>>>>>>>>> - Calcite based SQL engine improvements (memory quotas, index
>> scans
>>>>>>>>> optimisations).
>>>>>>>>> - Reworked permission management for system tasks.
>>>>>>>>> - Removed some deprecated functionality (daemon nodes, visorcmd,
>>>>>>> legacy
>>>>>>>> JMX
>>>>>>>>> beans)
>>>>>>>>> etc.
>>>>>>>>>
>>>>>>>>> I want to propose myself to be the release manager of the
>> planning
>>>>>>>> release.
>>>>>>>>> I propose the following timeline:
>>>>>>>>>
>>>>>>>>> Scope Freeze: April 08, 2023
>>>>>>>>> Code Freeze: April 15, 2023
>>>>>>>>> Voting Date: April 22, 2023
>>>>>>>>> Release Date: April 29, 2023
>>>>>>>>>
>>>>>>>>> [1].
>>>>>>>>>
>>>>>>>>>
>> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20in%20(2.15))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)
>>>>>>>>> WDYT?
>>>>>>>>>

Re: Apache Ignite 2.15 RELEASE [Time, Scope, Manager]

Posted by Alex Plehanov <pl...@gmail.com>.
Hello,

I'm announcing a code freeze for the 2.15 release. Only blockers are
accepted to the release since this moment.

вт, 11 апр. 2023 г. в 13:25, Pavel Tupitsyn <pt...@apache.org>:

> Alex,
>
> Just in case, Bugyard credentials are available to all PMCs in the private
> SVN repo, see [1]
>
> > a lot of changes from 'ignite' to 'gridgain'
> That's not good, requested changes on that PR.
>
> [1]
>
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Document#HowtoDocument-DocumentationFeedbackviaBugyard
>
> On Tue, Apr 11, 2023 at 11:58 AM Alex Plehanov <pl...@gmail.com>
> wrote:
>
> > Hello,
> >
> > I've merged and cherry-picked to 2.15 IGNITE-17892 and IGNITE-18260. As
> for
> > IGNITE-18496, I don't have access to the bugyard and can't validate all
> > changes. For example, there are a lot of changes from 'ignite' to
> > 'gridgain', not sure if it's correct or not. As far as this ticket will
> be
> > in master I will cherry-pick it into 2.15.
> >
> > вт, 11 апр. 2023 г. в 03:03, 18624049226 <18...@163.com>:
> >
> > > Hi Alex,
> > >
> > > Can you help merge the following PR into 2.15 branch? small doc fix.
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-17892
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-18496
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-18260
> > >
> > > 在 2023/4/10 21:31, Alex Plehanov 写道:
> > > > Hello Igniters,
> > > >
> > > > I've cut the release branch: 'ignite-2.15'. Please, cherry-pick new
> > > issues
> > > > if needed.
> > > >
> > > > The 2.15 scope is frozen. Unresolved not-blocking issues will be
> moved
> > to
> > > > the next release on the code freeze stage.
> > > >
> > > >
> > > > пт, 7 апр. 2023 г. в 17:03, Alex Plehanov<pl...@gmail.com>:
> > > >
> > > >> Hello Igniters,
> > > >>
> > > >> I have created the 2.15 release page [1].
> > > >>
> > > >> Also, I've removed from the 2.15 scope some unresolved tickets
> > > (unassigned
> > > >> and without activity for a long time). Now we have 13 unresolved
> > tickets
> > > >> (not related to documentation).
> > > >>
> > > >> I have a plan to cut the release branch next monday (10 Apr). I will
> > > >> inform you accordingly, when it will be done.
> > > >>
> > > >>
> > > >> [1] :
> > > >>
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.15
> > > >>
> > > >> пт, 31 мар. 2023 г. в 13:18, Jian Chen<ch...@gmail.com>:
> > > >>
> > > >>> +1
> > > >>>
> > > >>> Вячеслав Коптилин<sl...@gmail.com>于2023年3月31日 周五下午6:12写道:
> > > >>>
> > > >>>> +1
> > > >>>>
> > > >>>> ср, 29 мар. 2023 г. в 21:57, Alex Plehanov<
> plehanov.alex@gmail.com
> > >:
> > > >>>>
> > > >>>>> Dear Ignite Community!
> > > >>>>>
> > > >>>>> I suggest starting Apache Ignite 2.15 release activities.
> > > >>>>>
> > > >>>>> We've accumulated more than two hundred resolved issues [1] with
> > new
> > > >>>>> features and bug fixes which are waiting for release.
> > > >>>>> The major changes related to the proposed release:
> > > >>>>> - Incremental snapshots.
> > > >>>>> - Java thin client improvements (logging, connections balancing,
> > > >>>>>      events listening, endpoints discovery)
> > > >>>>> - Calcite based SQL engine improvements (memory quotas, index
> scans
> > > >>>>> optimisations).
> > > >>>>> - Reworked permission management for system tasks.
> > > >>>>> - Removed some deprecated functionality (daemon nodes, visorcmd,
> > > >>> legacy
> > > >>>> JMX
> > > >>>>> beans)
> > > >>>>> etc.
> > > >>>>>
> > > >>>>> I want to propose myself to be the release manager of the
> planning
> > > >>>> release.
> > > >>>>> I propose the following timeline:
> > > >>>>>
> > > >>>>> Scope Freeze: April 08, 2023
> > > >>>>> Code Freeze: April 15, 2023
> > > >>>>> Voting Date: April 22, 2023
> > > >>>>> Release Date: April 29, 2023
> > > >>>>>
> > > >>>>> [1].
> > > >>>>>
> > > >>>>>
> > > >>>
> > >
> >
> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20in%20(2.15))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)
> > > >>>>> WDYT?
> > > >>>>>
> >
>

Re: Apache Ignite 2.15 RELEASE [Time, Scope, Manager]

Posted by Pavel Tupitsyn <pt...@apache.org>.
Alex,

Just in case, Bugyard credentials are available to all PMCs in the private
SVN repo, see [1]

> a lot of changes from 'ignite' to 'gridgain'
That's not good, requested changes on that PR.

[1]
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Document#HowtoDocument-DocumentationFeedbackviaBugyard

On Tue, Apr 11, 2023 at 11:58 AM Alex Plehanov <pl...@gmail.com>
wrote:

> Hello,
>
> I've merged and cherry-picked to 2.15 IGNITE-17892 and IGNITE-18260. As for
> IGNITE-18496, I don't have access to the bugyard and can't validate all
> changes. For example, there are a lot of changes from 'ignite' to
> 'gridgain', not sure if it's correct or not. As far as this ticket will be
> in master I will cherry-pick it into 2.15.
>
> вт, 11 апр. 2023 г. в 03:03, 18624049226 <18...@163.com>:
>
> > Hi Alex,
> >
> > Can you help merge the following PR into 2.15 branch? small doc fix.
> >
> > https://issues.apache.org/jira/browse/IGNITE-17892
> >
> > https://issues.apache.org/jira/browse/IGNITE-18496
> >
> > https://issues.apache.org/jira/browse/IGNITE-18260
> >
> > 在 2023/4/10 21:31, Alex Plehanov 写道:
> > > Hello Igniters,
> > >
> > > I've cut the release branch: 'ignite-2.15'. Please, cherry-pick new
> > issues
> > > if needed.
> > >
> > > The 2.15 scope is frozen. Unresolved not-blocking issues will be moved
> to
> > > the next release on the code freeze stage.
> > >
> > >
> > > пт, 7 апр. 2023 г. в 17:03, Alex Plehanov<pl...@gmail.com>:
> > >
> > >> Hello Igniters,
> > >>
> > >> I have created the 2.15 release page [1].
> > >>
> > >> Also, I've removed from the 2.15 scope some unresolved tickets
> > (unassigned
> > >> and without activity for a long time). Now we have 13 unresolved
> tickets
> > >> (not related to documentation).
> > >>
> > >> I have a plan to cut the release branch next monday (10 Apr). I will
> > >> inform you accordingly, when it will be done.
> > >>
> > >>
> > >> [1] :
> > >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.15
> > >>
> > >> пт, 31 мар. 2023 г. в 13:18, Jian Chen<ch...@gmail.com>:
> > >>
> > >>> +1
> > >>>
> > >>> Вячеслав Коптилин<sl...@gmail.com>于2023年3月31日 周五下午6:12写道:
> > >>>
> > >>>> +1
> > >>>>
> > >>>> ср, 29 мар. 2023 г. в 21:57, Alex Plehanov<plehanov.alex@gmail.com
> >:
> > >>>>
> > >>>>> Dear Ignite Community!
> > >>>>>
> > >>>>> I suggest starting Apache Ignite 2.15 release activities.
> > >>>>>
> > >>>>> We've accumulated more than two hundred resolved issues [1] with
> new
> > >>>>> features and bug fixes which are waiting for release.
> > >>>>> The major changes related to the proposed release:
> > >>>>> - Incremental snapshots.
> > >>>>> - Java thin client improvements (logging, connections balancing,
> > >>>>>      events listening, endpoints discovery)
> > >>>>> - Calcite based SQL engine improvements (memory quotas, index scans
> > >>>>> optimisations).
> > >>>>> - Reworked permission management for system tasks.
> > >>>>> - Removed some deprecated functionality (daemon nodes, visorcmd,
> > >>> legacy
> > >>>> JMX
> > >>>>> beans)
> > >>>>> etc.
> > >>>>>
> > >>>>> I want to propose myself to be the release manager of the planning
> > >>>> release.
> > >>>>> I propose the following timeline:
> > >>>>>
> > >>>>> Scope Freeze: April 08, 2023
> > >>>>> Code Freeze: April 15, 2023
> > >>>>> Voting Date: April 22, 2023
> > >>>>> Release Date: April 29, 2023
> > >>>>>
> > >>>>> [1].
> > >>>>>
> > >>>>>
> > >>>
> >
> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20in%20(2.15))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)
> > >>>>> WDYT?
> > >>>>>
>

Re: Apache Ignite 2.15 RELEASE [Time, Scope, Manager]

Posted by Alex Plehanov <pl...@gmail.com>.
Hello,

I've merged and cherry-picked to 2.15 IGNITE-17892 and IGNITE-18260. As for
IGNITE-18496, I don't have access to the bugyard and can't validate all
changes. For example, there are a lot of changes from 'ignite' to
'gridgain', not sure if it's correct or not. As far as this ticket will be
in master I will cherry-pick it into 2.15.

вт, 11 апр. 2023 г. в 03:03, 18624049226 <18...@163.com>:

> Hi Alex,
>
> Can you help merge the following PR into 2.15 branch? small doc fix.
>
> https://issues.apache.org/jira/browse/IGNITE-17892
>
> https://issues.apache.org/jira/browse/IGNITE-18496
>
> https://issues.apache.org/jira/browse/IGNITE-18260
>
> 在 2023/4/10 21:31, Alex Plehanov 写道:
> > Hello Igniters,
> >
> > I've cut the release branch: 'ignite-2.15'. Please, cherry-pick new
> issues
> > if needed.
> >
> > The 2.15 scope is frozen. Unresolved not-blocking issues will be moved to
> > the next release on the code freeze stage.
> >
> >
> > пт, 7 апр. 2023 г. в 17:03, Alex Plehanov<pl...@gmail.com>:
> >
> >> Hello Igniters,
> >>
> >> I have created the 2.15 release page [1].
> >>
> >> Also, I've removed from the 2.15 scope some unresolved tickets
> (unassigned
> >> and without activity for a long time). Now we have 13 unresolved tickets
> >> (not related to documentation).
> >>
> >> I have a plan to cut the release branch next monday (10 Apr). I will
> >> inform you accordingly, when it will be done.
> >>
> >>
> >> [1] :
> >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.15
> >>
> >> пт, 31 мар. 2023 г. в 13:18, Jian Chen<ch...@gmail.com>:
> >>
> >>> +1
> >>>
> >>> Вячеслав Коптилин<sl...@gmail.com>于2023年3月31日 周五下午6:12写道:
> >>>
> >>>> +1
> >>>>
> >>>> ср, 29 мар. 2023 г. в 21:57, Alex Plehanov<pl...@gmail.com>:
> >>>>
> >>>>> Dear Ignite Community!
> >>>>>
> >>>>> I suggest starting Apache Ignite 2.15 release activities.
> >>>>>
> >>>>> We've accumulated more than two hundred resolved issues [1] with new
> >>>>> features and bug fixes which are waiting for release.
> >>>>> The major changes related to the proposed release:
> >>>>> - Incremental snapshots.
> >>>>> - Java thin client improvements (logging, connections balancing,
> >>>>>      events listening, endpoints discovery)
> >>>>> - Calcite based SQL engine improvements (memory quotas, index scans
> >>>>> optimisations).
> >>>>> - Reworked permission management for system tasks.
> >>>>> - Removed some deprecated functionality (daemon nodes, visorcmd,
> >>> legacy
> >>>> JMX
> >>>>> beans)
> >>>>> etc.
> >>>>>
> >>>>> I want to propose myself to be the release manager of the planning
> >>>> release.
> >>>>> I propose the following timeline:
> >>>>>
> >>>>> Scope Freeze: April 08, 2023
> >>>>> Code Freeze: April 15, 2023
> >>>>> Voting Date: April 22, 2023
> >>>>> Release Date: April 29, 2023
> >>>>>
> >>>>> [1].
> >>>>>
> >>>>>
> >>>
> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20in%20(2.15))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)
> >>>>> WDYT?
> >>>>>

Re: Apache Ignite 2.15 RELEASE [Time, Scope, Manager]

Posted by 18624049226 <18...@163.com>.
Hi Alex,

Can you help merge the following PR into 2.15 branch? small doc fix.

https://issues.apache.org/jira/browse/IGNITE-17892

https://issues.apache.org/jira/browse/IGNITE-18496

https://issues.apache.org/jira/browse/IGNITE-18260

在 2023/4/10 21:31, Alex Plehanov 写道:
> Hello Igniters,
>
> I've cut the release branch: 'ignite-2.15'. Please, cherry-pick new issues
> if needed.
>
> The 2.15 scope is frozen. Unresolved not-blocking issues will be moved to
> the next release on the code freeze stage.
>
>
> пт, 7 апр. 2023 г. в 17:03, Alex Plehanov<pl...@gmail.com>:
>
>> Hello Igniters,
>>
>> I have created the 2.15 release page [1].
>>
>> Also, I've removed from the 2.15 scope some unresolved tickets (unassigned
>> and without activity for a long time). Now we have 13 unresolved tickets
>> (not related to documentation).
>>
>> I have a plan to cut the release branch next monday (10 Apr). I will
>> inform you accordingly, when it will be done.
>>
>>
>> [1] :
>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.15
>>
>> пт, 31 мар. 2023 г. в 13:18, Jian Chen<ch...@gmail.com>:
>>
>>> +1
>>>
>>> Вячеслав Коптилин<sl...@gmail.com>于2023年3月31日 周五下午6:12写道:
>>>
>>>> +1
>>>>
>>>> ср, 29 мар. 2023 г. в 21:57, Alex Plehanov<pl...@gmail.com>:
>>>>
>>>>> Dear Ignite Community!
>>>>>
>>>>> I suggest starting Apache Ignite 2.15 release activities.
>>>>>
>>>>> We've accumulated more than two hundred resolved issues [1] with new
>>>>> features and bug fixes which are waiting for release.
>>>>> The major changes related to the proposed release:
>>>>> - Incremental snapshots.
>>>>> - Java thin client improvements (logging, connections balancing,
>>>>>      events listening, endpoints discovery)
>>>>> - Calcite based SQL engine improvements (memory quotas, index scans
>>>>> optimisations).
>>>>> - Reworked permission management for system tasks.
>>>>> - Removed some deprecated functionality (daemon nodes, visorcmd,
>>> legacy
>>>> JMX
>>>>> beans)
>>>>> etc.
>>>>>
>>>>> I want to propose myself to be the release manager of the planning
>>>> release.
>>>>> I propose the following timeline:
>>>>>
>>>>> Scope Freeze: April 08, 2023
>>>>> Code Freeze: April 15, 2023
>>>>> Voting Date: April 22, 2023
>>>>> Release Date: April 29, 2023
>>>>>
>>>>> [1].
>>>>>
>>>>>
>>> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20in%20(2.15))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)
>>>>> WDYT?
>>>>>

Re: Apache Ignite 2.15 RELEASE [Time, Scope, Manager]

Posted by Alex Plehanov <pl...@gmail.com>.
Hello Igniters,

I've cut the release branch: 'ignite-2.15'. Please, cherry-pick new issues
if needed.

The 2.15 scope is frozen. Unresolved not-blocking issues will be moved to
the next release on the code freeze stage.


пт, 7 апр. 2023 г. в 17:03, Alex Plehanov <pl...@gmail.com>:

> Hello Igniters,
>
> I have created the 2.15 release page [1].
>
> Also, I've removed from the 2.15 scope some unresolved tickets (unassigned
> and without activity for a long time). Now we have 13 unresolved tickets
> (not related to documentation).
>
> I have a plan to cut the release branch next monday (10 Apr). I will
> inform you accordingly, when it will be done.
>
>
> [1] :
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.15
>
> пт, 31 мар. 2023 г. в 13:18, Jian Chen <ch...@gmail.com>:
>
>> +1
>>
>> Вячеслав Коптилин <sl...@gmail.com>于2023年3月31日 周五下午6:12写道:
>>
>> > +1
>> >
>> > ср, 29 мар. 2023 г. в 21:57, Alex Plehanov <pl...@gmail.com>:
>> >
>> > > Dear Ignite Community!
>> > >
>> > > I suggest starting Apache Ignite 2.15 release activities.
>> > >
>> > > We've accumulated more than two hundred resolved issues [1] with new
>> > > features and bug fixes which are waiting for release.
>> > > The major changes related to the proposed release:
>> > > - Incremental snapshots.
>> > > - Java thin client improvements (logging, connections balancing,
>> > >     events listening, endpoints discovery)
>> > > - Calcite based SQL engine improvements (memory quotas, index scans
>> > > optimisations).
>> > > - Reworked permission management for system tasks.
>> > > - Removed some deprecated functionality (daemon nodes, visorcmd,
>> legacy
>> > JMX
>> > > beans)
>> > > etc.
>> > >
>> > > I want to propose myself to be the release manager of the planning
>> > release.
>> > >
>> > > I propose the following timeline:
>> > >
>> > > Scope Freeze: April 08, 2023
>> > > Code Freeze: April 15, 2023
>> > > Voting Date: April 22, 2023
>> > > Release Date: April 29, 2023
>> > >
>> > > [1].
>> > >
>> > >
>> >
>> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20in%20(2.15))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)
>> > >
>> > > WDYT?
>> > >
>> >
>>
>

Re: Apache Ignite 2.15 RELEASE [Time, Scope, Manager]

Posted by Alex Plehanov <pl...@gmail.com>.
Hello Igniters,

I have created the 2.15 release page [1].

Also, I've removed from the 2.15 scope some unresolved tickets (unassigned
and without activity for a long time). Now we have 13 unresolved tickets
(not related to documentation).

I have a plan to cut the release branch next monday (10 Apr). I will inform
you accordingly, when it will be done.


[1] : https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.15

пт, 31 мар. 2023 г. в 13:18, Jian Chen <ch...@gmail.com>:

> +1
>
> Вячеслав Коптилин <sl...@gmail.com>于2023年3月31日 周五下午6:12写道:
>
> > +1
> >
> > ср, 29 мар. 2023 г. в 21:57, Alex Plehanov <pl...@gmail.com>:
> >
> > > Dear Ignite Community!
> > >
> > > I suggest starting Apache Ignite 2.15 release activities.
> > >
> > > We've accumulated more than two hundred resolved issues [1] with new
> > > features and bug fixes which are waiting for release.
> > > The major changes related to the proposed release:
> > > - Incremental snapshots.
> > > - Java thin client improvements (logging, connections balancing,
> > >     events listening, endpoints discovery)
> > > - Calcite based SQL engine improvements (memory quotas, index scans
> > > optimisations).
> > > - Reworked permission management for system tasks.
> > > - Removed some deprecated functionality (daemon nodes, visorcmd, legacy
> > JMX
> > > beans)
> > > etc.
> > >
> > > I want to propose myself to be the release manager of the planning
> > release.
> > >
> > > I propose the following timeline:
> > >
> > > Scope Freeze: April 08, 2023
> > > Code Freeze: April 15, 2023
> > > Voting Date: April 22, 2023
> > > Release Date: April 29, 2023
> > >
> > > [1].
> > >
> > >
> >
> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20in%20(2.15))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)
> > >
> > > WDYT?
> > >
> >
>

Re: Apache Ignite 2.15 RELEASE [Time, Scope, Manager]

Posted by Jian Chen <ch...@gmail.com>.
+1

Вячеслав Коптилин <sl...@gmail.com>于2023年3月31日 周五下午6:12写道:

> +1
>
> ср, 29 мар. 2023 г. в 21:57, Alex Plehanov <pl...@gmail.com>:
>
> > Dear Ignite Community!
> >
> > I suggest starting Apache Ignite 2.15 release activities.
> >
> > We've accumulated more than two hundred resolved issues [1] with new
> > features and bug fixes which are waiting for release.
> > The major changes related to the proposed release:
> > - Incremental snapshots.
> > - Java thin client improvements (logging, connections balancing,
> >     events listening, endpoints discovery)
> > - Calcite based SQL engine improvements (memory quotas, index scans
> > optimisations).
> > - Reworked permission management for system tasks.
> > - Removed some deprecated functionality (daemon nodes, visorcmd, legacy
> JMX
> > beans)
> > etc.
> >
> > I want to propose myself to be the release manager of the planning
> release.
> >
> > I propose the following timeline:
> >
> > Scope Freeze: April 08, 2023
> > Code Freeze: April 15, 2023
> > Voting Date: April 22, 2023
> > Release Date: April 29, 2023
> >
> > [1].
> >
> >
> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20in%20(2.15))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)
> >
> > WDYT?
> >
>

Re: Apache Ignite 2.15 RELEASE [Time, Scope, Manager]

Posted by Вячеслав Коптилин <sl...@gmail.com>.
+1

ср, 29 мар. 2023 г. в 21:57, Alex Plehanov <pl...@gmail.com>:

> Dear Ignite Community!
>
> I suggest starting Apache Ignite 2.15 release activities.
>
> We've accumulated more than two hundred resolved issues [1] with new
> features and bug fixes which are waiting for release.
> The major changes related to the proposed release:
> - Incremental snapshots.
> - Java thin client improvements (logging, connections balancing,
>     events listening, endpoints discovery)
> - Calcite based SQL engine improvements (memory quotas, index scans
> optimisations).
> - Reworked permission management for system tasks.
> - Removed some deprecated functionality (daemon nodes, visorcmd, legacy JMX
> beans)
> etc.
>
> I want to propose myself to be the release manager of the planning release.
>
> I propose the following timeline:
>
> Scope Freeze: April 08, 2023
> Code Freeze: April 15, 2023
> Voting Date: April 22, 2023
> Release Date: April 29, 2023
>
> [1].
>
> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20in%20(2.15))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)
>
> WDYT?
>

Re: Apache Ignite 2.15 RELEASE [Time, Scope, Manager]

Posted by Pavel Tupitsyn <pt...@apache.org>.
+1

On Thu, Mar 30, 2023 at 2:08 AM Ilya Kasnacheev <il...@gmail.com>
wrote:

> +1!
> --
> Ilya Kasnacheev
>
>
> ср, 29 мар. 2023 г. в 23:13, Vladimir Steshin <vl...@gmail.com>:
>
> > +1
> >
> > 29.03.2023 21:56, Alex Plehanov пишет:
> > > Dear Ignite Community!
> > >
> > > I suggest starting Apache Ignite 2.15 release activities.
> > >
> > > We've accumulated more than two hundred resolved issues [1] with new
> > > features and bug fixes which are waiting for release.
> > > The major changes related to the proposed release:
> > > - Incremental snapshots.
> > > - Java thin client improvements (logging, connections balancing,
> > >      events listening, endpoints discovery)
> > > - Calcite based SQL engine improvements (memory quotas, index scans
> > > optimisations).
> > > - Reworked permission management for system tasks.
> > > - Removed some deprecated functionality (daemon nodes, visorcmd, legacy
> > JMX
> > > beans)
> > > etc.
> > >
> > > I want to propose myself to be the release manager of the planning
> > release.
> > >
> > > I propose the following timeline:
> > >
> > > Scope Freeze: April 08, 2023
> > > Code Freeze: April 15, 2023
> > > Voting Date: April 22, 2023
> > > Release Date: April 29, 2023
> > >
> > > [1].
> > >
> >
> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20in%20(2.15))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)
> > >
> > > WDYT?
> > >
> >
>

Re: Apache Ignite 2.15 RELEASE [Time, Scope, Manager]

Posted by Ilya Kasnacheev <il...@gmail.com>.
+1!
-- 
Ilya Kasnacheev


ср, 29 мар. 2023 г. в 23:13, Vladimir Steshin <vl...@gmail.com>:

> +1
>
> 29.03.2023 21:56, Alex Plehanov пишет:
> > Dear Ignite Community!
> >
> > I suggest starting Apache Ignite 2.15 release activities.
> >
> > We've accumulated more than two hundred resolved issues [1] with new
> > features and bug fixes which are waiting for release.
> > The major changes related to the proposed release:
> > - Incremental snapshots.
> > - Java thin client improvements (logging, connections balancing,
> >      events listening, endpoints discovery)
> > - Calcite based SQL engine improvements (memory quotas, index scans
> > optimisations).
> > - Reworked permission management for system tasks.
> > - Removed some deprecated functionality (daemon nodes, visorcmd, legacy
> JMX
> > beans)
> > etc.
> >
> > I want to propose myself to be the release manager of the planning
> release.
> >
> > I propose the following timeline:
> >
> > Scope Freeze: April 08, 2023
> > Code Freeze: April 15, 2023
> > Voting Date: April 22, 2023
> > Release Date: April 29, 2023
> >
> > [1].
> >
> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20in%20(2.15))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)
> >
> > WDYT?
> >
>

Re: Apache Ignite 2.15 RELEASE [Time, Scope, Manager]

Posted by Vladimir Steshin <vl...@gmail.com>.
+1

29.03.2023 21:56, Alex Plehanov пишет:
> Dear Ignite Community!
>
> I suggest starting Apache Ignite 2.15 release activities.
>
> We've accumulated more than two hundred resolved issues [1] with new
> features and bug fixes which are waiting for release.
> The major changes related to the proposed release:
> - Incremental snapshots.
> - Java thin client improvements (logging, connections balancing,
>      events listening, endpoints discovery)
> - Calcite based SQL engine improvements (memory quotas, index scans
> optimisations).
> - Reworked permission management for system tasks.
> - Removed some deprecated functionality (daemon nodes, visorcmd, legacy JMX
> beans)
> etc.
>
> I want to propose myself to be the release manager of the planning release.
>
> I propose the following timeline:
>
> Scope Freeze: April 08, 2023
> Code Freeze: April 15, 2023
> Voting Date: April 22, 2023
> Release Date: April 29, 2023
>
> [1].
> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20in%20(2.15))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)
>
> WDYT?
>