You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by Pavel Tupitsyn <pt...@apache.org> on 2024/11/13 12:42:05 UTC
Re: Apache Ignite 3.0.0 RELEASE [Time, Scope, Manager]
There are still 5 important unresolved tasks, moving the dates again.
Considering various holidays across the globe nearing the end of the year:
Scope Freeze: December 16, 2024
Code Freeze: December 23, 2024
Voting Date: January 6, 2025
Release Date: January 13, 2025
On Wed, Oct 9, 2024 at 9:34 AM Pavel Tupitsyn <pt...@apache.org> wrote:
> Metastorage Compaction and some other important tickets [1] are still
> unresolved. Let's postpone the release further.
>
> Proposed dates:
> Scope Freeze: November 11, 2024
> Code Freeze: November 18, 2024
> Voting Date: November 25, 2024
> Release Date: December 02, 2024
>
> [1]
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=318606750#ApacheIgnite3.0.0-Themostimportantreleasetasks
>
> On Fri, Oct 4, 2024 at 3:59 PM Pavel Tupitsyn <pt...@apache.org>
> wrote:
>
>> Thanks Vladimir, this ticket is already tracked as a requirement for the
>> release [1]
>> I'll keep an eye on the progress and move the dates if necessary.
>>
>> [1]
>> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=318606750#ApacheIgnite3.0.0-Themostimportantreleasetasks
>>
>> On Fri, Oct 4, 2024 at 2:44 PM Vladimir Pligin <vo...@yandex.ru>
>> wrote:
>>
>>> Hi guys,
>>>
>>> I'd like to highlight that there's still an unfinished epic (
>>> https://issues.apache.org/jira/browse/IGNITE-20166) related to the
>>> compaction triggers for meta store. It's marked as "Important" in Jira and
>>> it totally reflects it's severity. Currently nodes of a cluster are being
>>> slowly overflown by meta store data ingestion. This is indeed a
>>> user-exposed behavior. Let's consider postponing the release to let this
>>> activity finish up.
>>>
>>>
>>> > Preliminary YCSB benchmark results added to the release page [1]
>>> >
>>> > [1]
>>> >
>>> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=318606750#ApacheIgnite3.0.0-Benchmarks
>>> >
>>> > On Fri, Sep 13, 2024 at 10:09 AM Pavel Tupitsyn <pt...@apache.org>
>>> > wrote:
>>> >
>>> >> I agree that the tickets listed above are important for the release.
>>> Let's
>>> >> move the dates by 4 weeks:
>>> >>
>>> >> Scope Freeze: October 11, 2024
>>> >> Code Freeze: October 18, 2024
>>> >> Voting Date: October 25, 2024
>>> >> Release Date: October 31, 2024
>>> >>
>>> >> On Thu, Sep 12, 2024 at 4:22 PM Alexei Scherbakov <
>>> >> alexey.scherbakoff@gmail.com> wrote:
>>> >>
>>> >>> +1
>>> >>>
>>> >>> I suggest to dig to the bottom of [1] before release.
>>> >>>
>>> >>> [1] https://issues.apache.org/jira/browse/IGNITE-23199
>>> >>>
>>> >>> чт, 12 сент. 2024 г. в 09:35, Roman Puchkovskiy <
>>> >>> roman.puchkovskiy@gmail.com
>>> >>>>:
>>> >>>
>>> >>>> +1.
>>> >>>>
>>> >>>> I would also like to include the following issues into the release
>>> >>> scope:
>>> >>>>
>>> >>>> * [1] to make sure we don't keep garbage after a partition
>>> destruction
>>> >>>> * [2] and [3] to make it easier to maintain binary compatibility
>>> after
>>> >>>> the release
>>> >>>> * [4] as it's required by [3]
>>> >>>>
>>> >>>> It seems that about 1 or 2 weeks are needed to implement those.
>>> >>>>
>>> >>>> [1] - https://issues.apache.org/jira/browse/IGNITE-18703
>>> >>>> [2] - https://issues.apache.org/jira/browse/IGNITE-23135
>>> >>>> [3] - https://issues.apache.org/jira/browse/IGNITE-23197
>>> >>>> [4] - https://issues.apache.org/jira/browse/IGNITE-15119
>>> >>>>
>>> >>>> Regards,
>>> >>>> Roman Puchkovskiy
>>> >>>>
>>> >>>> ср, 11 сент. 2024 г. в 17:29, Igor Sapego <is...@apache.org>:
>>> >>>> >
>>> >>>> > Igniters,
>>> >>>> >
>>> >>>> > I think it is important to include at least basic Python support
>>> in
>>> >>> the
>>> >>>> > initial release.
>>> >>>> > I'm working on the DB API Driver [1], and we need to implement the
>>> >>>> following
>>> >>>> > tasks to consider it "release ready": [2] [3] [4] [5]. I expect
>>> those
>>> >>> in
>>> >>>> > 3-4 weeks.
>>> >>>> >
>>> >>>> > [1] - https://issues.apache.org/jira/browse/IGNITE-22719
>>> >>>> > [2] - https://issues.apache.org/jira/browse/IGNITE-22740
>>> >>>> > [3] - https://issues.apache.org/jira/browse/IGNITE-22744
>>> >>>> > [4] - https://issues.apache.org/jira/browse/IGNITE-22745
>>> >>>> > [5] - https://issues.apache.org/jira/browse/IGNITE-22746
>>> >>>> >
>>> >>>> > Best Regards,
>>> >>>> > Igor
>>> >>>> >
>>> >>>> >
>>> >>>> > On Tue, Sep 10, 2024 at 6:43 AM Mikhail Pochatkin <
>>> >>>> m.a.pochatkin@gmail.com>
>>> >>>> > wrote:
>>> >>>> >
>>> >>>> > > +1
>>> >>>> > >
>>> >>>> > > чт, 29 авг. 2024 г. в 13:50, Pavel Tupitsyn <
>>> ptupitsyn@apache.org>:
>>> >>>> > >
>>> >>>> > > > Dear Ignite Community!
>>> >>>> > > >
>>> >>>> > > > I suggest starting Apache Ignite 3.0.0 release activities.
>>> >>>> > > >
>>> >>>> > > > beta1 was released almost 2 years ago, and the product has
>>> matured
>>> >>>> > > greatly
>>> >>>> > > > since then.
>>> >>>> > > > - The public API is stable
>>> >>>> > > > - Performance is greatly improved [1]
>>> >>>> > > > - More than 2000 tickets resolved [2]
>>> >>>> > > >
>>> >>>> > > > I would like to be the release manager. Proposed timeline:
>>> >>>> > > >
>>> >>>> > > > Scope Freeze: September 13, 2024
>>> >>>> > > > Code Freeze: September 20, 2024
>>> >>>> > > > Voting Date: September 27, 2022
>>> >>>> > > > Release Date: October 03, 2022
>>> >>>> > > >
>>> >>>> > > > WDYT?
>>> >>>> > > >
>>> >>>> > > > [1] https://issues.apache.org/jira/browse/IGNITE-19479
>>> >>>> > > > [2]
>>> >>>> > > >
>>> >>>> > > >
>>> >>>> > >
>>> >>>>
>>> >>>
>>> https://issues.apache.org/jira/issues/?jql=labels%3Dignite-3%20%20and%20fixVersion%20%3D%203.0.0-beta2%20and%20status%3Dresolved
>>> >>>> > > >
>>> >>>> > >
>>> >>>> > >
>>> >>>> > > --
>>> >>>> > > best regards,
>>> >>>> > > Pochatkin Mikhail.
>>> >>>> > >
>>> >>>>
>>> >>>
>>> >>> --
>>> >>>
>>> >>> Best regards,
>>> >>> Alexei Scherbakov
>>> -- С уважением, Владимир Плигин.
>>>
>>
Re: Apache Ignite 3.0.0 RELEASE [Time, Scope, Manager]
Posted by Pavel Tupitsyn <pt...@apache.org>.
ANNOUNCE: code freeze begins now.
All tickets for 3.0 are complete, except for version bump [1] and release
notes [2] - I will handle those tomorrow.
No more changes in ignite-3.0 branch, unless we find any critical issues.
[1] https://issues.apache.org/jira/browse/IGNITE-24280
[2] https://issues.apache.org/jira/browse/IGNITE-24279
On Wed, Jan 22, 2025 at 2:00 PM Pavel Pereslegin <xx...@gmail.com> wrote:
> Hello.
>
> I suggest including this task [1] in the release.
>
> It changes the jdbc client protocol. I hope that the review of the proposed
> patch will be completed today.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-24053
>
>
>
> вт, 21 янв. 2025 г. в 20:28, Pavel Tupitsyn <pt...@apache.org>:
>
> > Following an in-person discussion with Vladimir Pligin and Alexander
> Lapin,
> > we concluded that Metastorage Compaction can require up to 3 weeks to
> > complete.
> > As a result, it should be postponed to ensure the release of version 3.0
> > before the Ignite Summit.
> >
> > Metastorage Compaction is an important feature that controls memory and
> > storage usage under continuous load.
> > We will release it in version 3.1 or 3.0.1 as soon as possible.
> >
> > - Branch ignite-3.0 created from main.
> > - Proposed code freeze is tomorrow (Jan 22)
> > - Only two incomplete tickets are in scope: IGNITE-24276, IGNITE-24200
> >
> > Let me know if you have any objections.
> >
> > On Mon, Jan 20, 2025 at 11:00 AM Vladimir Pligin <vo...@yandex.ru>
> > wrote:
> >
> > > The tickets for metastorage compaction are still in progress. There is
> a
> > > small ticket to fully enable it -
> > > https://issues.apache.org/jira/browse/IGNITE-23280, but it's blocked
> by
> > > IGNITE-23280 and IGNITE-23466. I propose the hold the release for a few
> > > more days.
> > >
> >
>
Re: Apache Ignite 3.0.0 RELEASE [Time, Scope, Manager]
Posted by Pavel Pereslegin <xx...@gmail.com>.
Hello.
I suggest including this task [1] in the release.
It changes the jdbc client protocol. I hope that the review of the proposed
patch will be completed today.
[1] https://issues.apache.org/jira/browse/IGNITE-24053
вт, 21 янв. 2025 г. в 20:28, Pavel Tupitsyn <pt...@apache.org>:
> Following an in-person discussion with Vladimir Pligin and Alexander Lapin,
> we concluded that Metastorage Compaction can require up to 3 weeks to
> complete.
> As a result, it should be postponed to ensure the release of version 3.0
> before the Ignite Summit.
>
> Metastorage Compaction is an important feature that controls memory and
> storage usage under continuous load.
> We will release it in version 3.1 or 3.0.1 as soon as possible.
>
> - Branch ignite-3.0 created from main.
> - Proposed code freeze is tomorrow (Jan 22)
> - Only two incomplete tickets are in scope: IGNITE-24276, IGNITE-24200
>
> Let me know if you have any objections.
>
> On Mon, Jan 20, 2025 at 11:00 AM Vladimir Pligin <vo...@yandex.ru>
> wrote:
>
> > The tickets for metastorage compaction are still in progress. There is a
> > small ticket to fully enable it -
> > https://issues.apache.org/jira/browse/IGNITE-23280, but it's blocked by
> > IGNITE-23280 and IGNITE-23466. I propose the hold the release for a few
> > more days.
> >
>
Re: Apache Ignite 3.0.0 RELEASE [Time, Scope, Manager]
Posted by Pavel Tupitsyn <pt...@apache.org>.
Following an in-person discussion with Vladimir Pligin and Alexander Lapin,
we concluded that Metastorage Compaction can require up to 3 weeks to
complete.
As a result, it should be postponed to ensure the release of version 3.0
before the Ignite Summit.
Metastorage Compaction is an important feature that controls memory and
storage usage under continuous load.
We will release it in version 3.1 or 3.0.1 as soon as possible.
- Branch ignite-3.0 created from main.
- Proposed code freeze is tomorrow (Jan 22)
- Only two incomplete tickets are in scope: IGNITE-24276, IGNITE-24200
Let me know if you have any objections.
On Mon, Jan 20, 2025 at 11:00 AM Vladimir Pligin <vo...@yandex.ru>
wrote:
> The tickets for metastorage compaction are still in progress. There is a
> small ticket to fully enable it -
> https://issues.apache.org/jira/browse/IGNITE-23280, but it's blocked by
> IGNITE-23280 and IGNITE-23466. I propose the hold the release for a few
> more days.
>
Re:Apache Ignite 3.0.0 RELEASE [Time, Scope, Manager]
Posted by Vladimir Pligin <vo...@yandex.ru>.
The tickets for metastorage compaction are still in progress. There is a small ticket to fully enable it - https://issues.apache.org/jira/browse/IGNITE-23280, but it's blocked by IGNITE-23280 and IGNITE-23466. I propose the hold the release for a few more days.
Re: Apache Ignite 3.0.0 RELEASE [Time, Scope, Manager]
Posted by Pavel Tupitsyn <pt...@apache.org>.
- ignite-3.0 branch deleted
- all resolved tickets with fixVersion = 3.1 changed to fixVersion = 3.0
- new projected code freeze date - Jan 20
For now, please use the 3.0 fixVersion when resolving tickets as we've been
doing before.
If there is a change that we don't want to include in 3.0, let me know in
this thread.
On Tue, Jan 14, 2025 at 12:12 PM Pavel Tupitsyn <pt...@apache.org>
wrote:
> Metastorage compaction takes more time than expected
> (IGNITE-23280, IGNITE-23466), and we have a lot of small fixes coming every
> day.
>
> Proposal:
> - Move code freeze to Jan 20 (next Monday)
> - Delete ignite-3.0 branch to avoid spending time on cherry-picks
> - Cut ignite-3.0 again after the code freeze
>
> Let me know if you have any concerns or objections before tomorrow.
>
> On Tue, Jan 14, 2025 at 11:43 AM Andrey Mashenkov <
> andrey.mashenkov@gmail.com> wrote:
>
>> Hi, Pavel.
>>
>> I've found a bug in BinaryTupleComparator, which is used by Indexes,
>> that byte[] comparison is non-conformed with SQL standard.
>> The fix is ready [1] and merged to master.
>> The fix breaks ordering in Indexes for byte strings that affects binary
>> compatibility between versions.
>>
>> Can we add a fix to the 3.0?
>>
>> [1] https://issues.apache.org/jira/browse/IGNITE-24176
>>
>>
>> On Mon, Jan 13, 2025 at 7:30 PM Pavel Tupitsyn <pt...@apache.org>
>> wrote:
>>
>> > Mikhail, no objections. Please merge to main and cherry-pick to
>> ignite-3.0
>> > (I've set the fix version accordingly).
>> >
>> > Looks like we have to postpone the code freeze, I'll post an update
>> > tomorrow.
>> >
>> > On Mon, Jan 13, 2025 at 6:15 PM Mikhail Pochatkin <
>> m.a.pochatkin@gmail.com
>> > >
>> > wrote:
>> >
>> > > Hi, guys. I have fixed a bug in CLI with incorrect SQL exception
>> handling
>> > > (IGNITE-24179). Any objections to merge it before code freeze?
>> > >
>> > > пн, 13 янв. 2025 г. в 08:45, Pavel Tupitsyn <pt...@apache.org>:
>> > >
>> > > > > Found a very nasty error IGNITE-24186, I think it's worth adding,
>> > since
>> > > > we might not be able to restart the cluster.
>> > > >
>> > > > Kirill, are you going to work on this? Any ETA?
>> > > >
>> > > >
>> > > > > worth adding this performance fix into the scope IGNITE-24163
>> > > >
>> > > > Already done and cherry-picked, nice.
>> > > >
>> > > > On Sun, Jan 12, 2025 at 10:00 PM Nusrat Shakarov <
>> nusrat558@gmail.com>
>> > > > wrote:
>> > > >
>> > > > > Considering that we have EventLog-related tickets in the scope, I
>> > think
>> > > > it
>> > > > > is also worth adding this performance fix into the scope
>> IGNITE-24163
>> > > > >
>> > > > > On Sat, 11 Jan 2025 at 11:18, ткаленко кирилл <
>> tkalkirill@yandex.ru>
>> > > > > wrote:
>> > > > >
>> > > > > > Found a very nasty error IGNITE-24186, I think it's worth
>> adding,
>> > > since
>> > > > > we
>> > > > > > might not be able to restart the cluster.
>> > > > > >
>> > > > >
>> > > >
>> > >
>> > >
>> > > --
>> > > best regards,
>> > > Pochatkin Mikhail.
>> > >
>> >
>>
>>
>> --
>> Best regards,
>> Andrey V. Mashenkov
>>
>
Re: Apache Ignite 3.0.0 RELEASE [Time, Scope, Manager]
Posted by Pavel Tupitsyn <pt...@apache.org>.
Metastorage compaction takes more time than expected
(IGNITE-23280, IGNITE-23466), and we have a lot of small fixes coming every
day.
Proposal:
- Move code freeze to Jan 20 (next Monday)
- Delete ignite-3.0 branch to avoid spending time on cherry-picks
- Cut ignite-3.0 again after the code freeze
Let me know if you have any concerns or objections before tomorrow.
On Tue, Jan 14, 2025 at 11:43 AM Andrey Mashenkov <
andrey.mashenkov@gmail.com> wrote:
> Hi, Pavel.
>
> I've found a bug in BinaryTupleComparator, which is used by Indexes,
> that byte[] comparison is non-conformed with SQL standard.
> The fix is ready [1] and merged to master.
> The fix breaks ordering in Indexes for byte strings that affects binary
> compatibility between versions.
>
> Can we add a fix to the 3.0?
>
> [1] https://issues.apache.org/jira/browse/IGNITE-24176
>
>
> On Mon, Jan 13, 2025 at 7:30 PM Pavel Tupitsyn <pt...@apache.org>
> wrote:
>
> > Mikhail, no objections. Please merge to main and cherry-pick to
> ignite-3.0
> > (I've set the fix version accordingly).
> >
> > Looks like we have to postpone the code freeze, I'll post an update
> > tomorrow.
> >
> > On Mon, Jan 13, 2025 at 6:15 PM Mikhail Pochatkin <
> m.a.pochatkin@gmail.com
> > >
> > wrote:
> >
> > > Hi, guys. I have fixed a bug in CLI with incorrect SQL exception
> handling
> > > (IGNITE-24179). Any objections to merge it before code freeze?
> > >
> > > пн, 13 янв. 2025 г. в 08:45, Pavel Tupitsyn <pt...@apache.org>:
> > >
> > > > > Found a very nasty error IGNITE-24186, I think it's worth adding,
> > since
> > > > we might not be able to restart the cluster.
> > > >
> > > > Kirill, are you going to work on this? Any ETA?
> > > >
> > > >
> > > > > worth adding this performance fix into the scope IGNITE-24163
> > > >
> > > > Already done and cherry-picked, nice.
> > > >
> > > > On Sun, Jan 12, 2025 at 10:00 PM Nusrat Shakarov <
> nusrat558@gmail.com>
> > > > wrote:
> > > >
> > > > > Considering that we have EventLog-related tickets in the scope, I
> > think
> > > > it
> > > > > is also worth adding this performance fix into the scope
> IGNITE-24163
> > > > >
> > > > > On Sat, 11 Jan 2025 at 11:18, ткаленко кирилл <
> tkalkirill@yandex.ru>
> > > > > wrote:
> > > > >
> > > > > > Found a very nasty error IGNITE-24186, I think it's worth adding,
> > > since
> > > > > we
> > > > > > might not be able to restart the cluster.
> > > > > >
> > > > >
> > > >
> > >
> > >
> > > --
> > > best regards,
> > > Pochatkin Mikhail.
> > >
> >
>
>
> --
> Best regards,
> Andrey V. Mashenkov
>
Re: Apache Ignite 3.0.0 RELEASE [Time, Scope, Manager]
Posted by Andrey Mashenkov <an...@gmail.com>.
Hi, Pavel.
I've found a bug in BinaryTupleComparator, which is used by Indexes,
that byte[] comparison is non-conformed with SQL standard.
The fix is ready [1] and merged to master.
The fix breaks ordering in Indexes for byte strings that affects binary
compatibility between versions.
Can we add a fix to the 3.0?
[1] https://issues.apache.org/jira/browse/IGNITE-24176
On Mon, Jan 13, 2025 at 7:30 PM Pavel Tupitsyn <pt...@apache.org> wrote:
> Mikhail, no objections. Please merge to main and cherry-pick to ignite-3.0
> (I've set the fix version accordingly).
>
> Looks like we have to postpone the code freeze, I'll post an update
> tomorrow.
>
> On Mon, Jan 13, 2025 at 6:15 PM Mikhail Pochatkin <m.a.pochatkin@gmail.com
> >
> wrote:
>
> > Hi, guys. I have fixed a bug in CLI with incorrect SQL exception handling
> > (IGNITE-24179). Any objections to merge it before code freeze?
> >
> > пн, 13 янв. 2025 г. в 08:45, Pavel Tupitsyn <pt...@apache.org>:
> >
> > > > Found a very nasty error IGNITE-24186, I think it's worth adding,
> since
> > > we might not be able to restart the cluster.
> > >
> > > Kirill, are you going to work on this? Any ETA?
> > >
> > >
> > > > worth adding this performance fix into the scope IGNITE-24163
> > >
> > > Already done and cherry-picked, nice.
> > >
> > > On Sun, Jan 12, 2025 at 10:00 PM Nusrat Shakarov <nu...@gmail.com>
> > > wrote:
> > >
> > > > Considering that we have EventLog-related tickets in the scope, I
> think
> > > it
> > > > is also worth adding this performance fix into the scope IGNITE-24163
> > > >
> > > > On Sat, 11 Jan 2025 at 11:18, ткаленко кирилл <tk...@yandex.ru>
> > > > wrote:
> > > >
> > > > > Found a very nasty error IGNITE-24186, I think it's worth adding,
> > since
> > > > we
> > > > > might not be able to restart the cluster.
> > > > >
> > > >
> > >
> >
> >
> > --
> > best regards,
> > Pochatkin Mikhail.
> >
>
--
Best regards,
Andrey V. Mashenkov
Re: Apache Ignite 3.0.0 RELEASE [Time, Scope, Manager]
Posted by Pavel Tupitsyn <pt...@apache.org>.
Mikhail, no objections. Please merge to main and cherry-pick to ignite-3.0
(I've set the fix version accordingly).
Looks like we have to postpone the code freeze, I'll post an update
tomorrow.
On Mon, Jan 13, 2025 at 6:15 PM Mikhail Pochatkin <m....@gmail.com>
wrote:
> Hi, guys. I have fixed a bug in CLI with incorrect SQL exception handling
> (IGNITE-24179). Any objections to merge it before code freeze?
>
> пн, 13 янв. 2025 г. в 08:45, Pavel Tupitsyn <pt...@apache.org>:
>
> > > Found a very nasty error IGNITE-24186, I think it's worth adding, since
> > we might not be able to restart the cluster.
> >
> > Kirill, are you going to work on this? Any ETA?
> >
> >
> > > worth adding this performance fix into the scope IGNITE-24163
> >
> > Already done and cherry-picked, nice.
> >
> > On Sun, Jan 12, 2025 at 10:00 PM Nusrat Shakarov <nu...@gmail.com>
> > wrote:
> >
> > > Considering that we have EventLog-related tickets in the scope, I think
> > it
> > > is also worth adding this performance fix into the scope IGNITE-24163
> > >
> > > On Sat, 11 Jan 2025 at 11:18, ткаленко кирилл <tk...@yandex.ru>
> > > wrote:
> > >
> > > > Found a very nasty error IGNITE-24186, I think it's worth adding,
> since
> > > we
> > > > might not be able to restart the cluster.
> > > >
> > >
> >
>
>
> --
> best regards,
> Pochatkin Mikhail.
>
Re: Apache Ignite 3.0.0 RELEASE [Time, Scope, Manager]
Posted by Mikhail Pochatkin <m....@gmail.com>.
Hi, guys. I have fixed a bug in CLI with incorrect SQL exception handling
(IGNITE-24179). Any objections to merge it before code freeze?
пн, 13 янв. 2025 г. в 08:45, Pavel Tupitsyn <pt...@apache.org>:
> > Found a very nasty error IGNITE-24186, I think it's worth adding, since
> we might not be able to restart the cluster.
>
> Kirill, are you going to work on this? Any ETA?
>
>
> > worth adding this performance fix into the scope IGNITE-24163
>
> Already done and cherry-picked, nice.
>
> On Sun, Jan 12, 2025 at 10:00 PM Nusrat Shakarov <nu...@gmail.com>
> wrote:
>
> > Considering that we have EventLog-related tickets in the scope, I think
> it
> > is also worth adding this performance fix into the scope IGNITE-24163
> >
> > On Sat, 11 Jan 2025 at 11:18, ткаленко кирилл <tk...@yandex.ru>
> > wrote:
> >
> > > Found a very nasty error IGNITE-24186, I think it's worth adding, since
> > we
> > > might not be able to restart the cluster.
> > >
> >
>
--
best regards,
Pochatkin Mikhail.
Re: Apache Ignite 3.0.0 RELEASE [Time, Scope, Manager]
Posted by Pavel Tupitsyn <pt...@apache.org>.
> Found a very nasty error IGNITE-24186, I think it's worth adding, since
we might not be able to restart the cluster.
Kirill, are you going to work on this? Any ETA?
> worth adding this performance fix into the scope IGNITE-24163
Already done and cherry-picked, nice.
On Sun, Jan 12, 2025 at 10:00 PM Nusrat Shakarov <nu...@gmail.com>
wrote:
> Considering that we have EventLog-related tickets in the scope, I think it
> is also worth adding this performance fix into the scope IGNITE-24163
>
> On Sat, 11 Jan 2025 at 11:18, ткаленко кирилл <tk...@yandex.ru>
> wrote:
>
> > Found a very nasty error IGNITE-24186, I think it's worth adding, since
> we
> > might not be able to restart the cluster.
> >
>
Re: Apache Ignite 3.0.0 RELEASE [Time, Scope, Manager]
Posted by Nusrat Shakarov <nu...@gmail.com>.
Considering that we have EventLog-related tickets in the scope, I think it
is also worth adding this performance fix into the scope IGNITE-24163
On Sat, 11 Jan 2025 at 11:18, ткаленко кирилл <tk...@yandex.ru> wrote:
> Found a very nasty error IGNITE-24186, I think it's worth adding, since we
> might not be able to restart the cluster.
>
Re:Apache Ignite 3.0.0 RELEASE [Time, Scope, Manager]
Posted by ткаленко кирилл <tk...@yandex.ru>.
Found a very nasty error IGNITE-24186, I think it's worth adding, since we might not be able to restart the cluster.
Re: Apache Ignite 3.0.0 RELEASE [Time, Scope, Manager]
Posted by Pavel Tupitsyn <pt...@apache.org>.
Ignite 3.0 scope is now frozen:
- all issues without an "important" label moved to 3.1
- ignite-3.0 branch created from main
- the following 11 tickets are in scope: IGNITE-24162, IGNITE-24159,
IGNITE-24059, IGNITE-23920, IGNITE-23891, IGNITE-23888, IGNITE-23867,
IGNITE-23747, IGNITE-23736, IGNITE-20166, IGNITE-19510
- those tickets should be merged to main, then cherry-picked to ignite-3.0
- to include additional tickets into the scope, please post in this thread
Code freeze is planned for Jan 13 (next Monday), let's focus on the
tickets above.
On Tue, Jan 7, 2025 at 12:18 PM Pavel Tupitsyn <pt...@apache.org> wrote:
> Thanks Ivan, added to the "important task" list.
>
> The scope freeze will be announced later today.
>
> On Tue, Jan 7, 2025 at 11:56 AM Ivan Artiukhov <m....@gmail.com> wrote:
>
>> The following possible blocker regarding c3p0 connection pools has been
>> found recently:
>>
>> [1] - https://issues.apache.org/jira/browse/IGNITE-24159
>>
>> I'd suggest including it into the release scope.
>>
>> пн, 16 дек. 2024 г. в 11:18, Pavel Tupitsyn <pt...@apache.org>:
>>
>> > RO TX timeouts [1] and related tasks are still in the works.
>> > Moving the dates again:
>> >
>> > Scope Freeze: January 06, 2025
>> > Code Freeze: January 13, 2025
>> > Voting Date: January 27, 2025
>> > Release Date: February 4, 2025
>> >
>> > [1] https://issues.apache.org/jira/browse/IGNITE-23747
>> >
>> > On Wed, Nov 13, 2024 at 2:42 PM Pavel Tupitsyn <pt...@apache.org>
>> > wrote:
>> >
>> > > There are still 5 important unresolved tasks, moving the dates again.
>> > > Considering various holidays across the globe nearing the end of the
>> > year:
>> > >
>> > > Scope Freeze: December 16, 2024
>> > > Code Freeze: December 23, 2024
>> > > Voting Date: January 6, 2025
>> > > Release Date: January 13, 2025
>> > >
>> > > On Wed, Oct 9, 2024 at 9:34 AM Pavel Tupitsyn <pt...@apache.org>
>> > > wrote:
>> > >
>> > >> Metastorage Compaction and some other important tickets [1] are still
>> > >> unresolved. Let's postpone the release further.
>> > >>
>> > >> Proposed dates:
>> > >> Scope Freeze: November 11, 2024
>> > >> Code Freeze: November 18, 2024
>> > >> Voting Date: November 25, 2024
>> > >> Release Date: December 02, 2024
>> > >>
>> > >> [1]
>> > >>
>> >
>> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=318606750#ApacheIgnite3.0.0-Themostimportantreleasetasks
>> > >>
>> > >> On Fri, Oct 4, 2024 at 3:59 PM Pavel Tupitsyn <pt...@apache.org>
>> > >> wrote:
>> > >>
>> > >>> Thanks Vladimir, this ticket is already tracked as a requirement for
>> > the
>> > >>> release [1]
>> > >>> I'll keep an eye on the progress and move the dates if necessary.
>> > >>>
>> > >>> [1]
>> > >>>
>> >
>> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=318606750#ApacheIgnite3.0.0-Themostimportantreleasetasks
>> > >>>
>> > >>> On Fri, Oct 4, 2024 at 2:44 PM Vladimir Pligin <
>> vova199107@yandex.ru>
>> > >>> wrote:
>> > >>>
>> > >>>> Hi guys,
>> > >>>>
>> > >>>> I'd like to highlight that there's still an unfinished epic (
>> > >>>> https://issues.apache.org/jira/browse/IGNITE-20166) related to the
>> > >>>> compaction triggers for meta store. It's marked as "Important" in
>> > Jira and
>> > >>>> it totally reflects it's severity. Currently nodes of a cluster are
>> > being
>> > >>>> slowly overflown by meta store data ingestion. This is indeed a
>> > >>>> user-exposed behavior. Let's consider postponing the release to let
>> > this
>> > >>>> activity finish up.
>> > >>>>
>> > >>>>
>> > >>>> > Preliminary YCSB benchmark results added to the release page [1]
>> > >>>> >
>> > >>>> > [1]
>> > >>>> >
>> > >>>>
>> >
>> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=318606750#ApacheIgnite3.0.0-Benchmarks
>> > >>>> >
>> > >>>> > On Fri, Sep 13, 2024 at 10:09 AM Pavel Tupitsyn <
>> > ptupitsyn@apache.org
>> > >>>> >
>> > >>>> > wrote:
>> > >>>> >
>> > >>>> >> I agree that the tickets listed above are important for the
>> > release.
>> > >>>> Let's
>> > >>>> >> move the dates by 4 weeks:
>> > >>>> >>
>> > >>>> >> Scope Freeze: October 11, 2024
>> > >>>> >> Code Freeze: October 18, 2024
>> > >>>> >> Voting Date: October 25, 2024
>> > >>>> >> Release Date: October 31, 2024
>> > >>>> >>
>> > >>>> >> On Thu, Sep 12, 2024 at 4:22 PM Alexei Scherbakov <
>> > >>>> >> alexey.scherbakoff@gmail.com> wrote:
>> > >>>> >>
>> > >>>> >>> +1
>> > >>>> >>>
>> > >>>> >>> I suggest to dig to the bottom of [1] before release.
>> > >>>> >>>
>> > >>>> >>> [1] https://issues.apache.org/jira/browse/IGNITE-23199
>> > >>>> >>>
>> > >>>> >>> чт, 12 сент. 2024 г. в 09:35, Roman Puchkovskiy <
>> > >>>> >>> roman.puchkovskiy@gmail.com
>> > >>>> >>>>:
>> > >>>> >>>
>> > >>>> >>>> +1.
>> > >>>> >>>>
>> > >>>> >>>> I would also like to include the following issues into the
>> > release
>> > >>>> >>> scope:
>> > >>>> >>>>
>> > >>>> >>>> * [1] to make sure we don't keep garbage after a partition
>> > >>>> destruction
>> > >>>> >>>> * [2] and [3] to make it easier to maintain binary
>> compatibility
>> > >>>> after
>> > >>>> >>>> the release
>> > >>>> >>>> * [4] as it's required by [3]
>> > >>>> >>>>
>> > >>>> >>>> It seems that about 1 or 2 weeks are needed to implement
>> those.
>> > >>>> >>>>
>> > >>>> >>>> [1] - https://issues.apache.org/jira/browse/IGNITE-18703
>> > >>>> >>>> [2] - https://issues.apache.org/jira/browse/IGNITE-23135
>> > >>>> >>>> [3] - https://issues.apache.org/jira/browse/IGNITE-23197
>> > >>>> >>>> [4] - https://issues.apache.org/jira/browse/IGNITE-15119
>> > >>>> >>>>
>> > >>>> >>>> Regards,
>> > >>>> >>>> Roman Puchkovskiy
>> > >>>> >>>>
>> > >>>> >>>> ср, 11 сент. 2024 г. в 17:29, Igor Sapego <isapego@apache.org
>> >:
>> > >>>> >>>> >
>> > >>>> >>>> > Igniters,
>> > >>>> >>>> >
>> > >>>> >>>> > I think it is important to include at least basic Python
>> > support
>> > >>>> in
>> > >>>> >>> the
>> > >>>> >>>> > initial release.
>> > >>>> >>>> > I'm working on the DB API Driver [1], and we need to
>> implement
>> > >>>> the
>> > >>>> >>>> following
>> > >>>> >>>> > tasks to consider it "release ready": [2] [3] [4] [5]. I
>> expect
>> > >>>> those
>> > >>>> >>> in
>> > >>>> >>>> > 3-4 weeks.
>> > >>>> >>>> >
>> > >>>> >>>> > [1] - https://issues.apache.org/jira/browse/IGNITE-22719
>> > >>>> >>>> > [2] - https://issues.apache.org/jira/browse/IGNITE-22740
>> > >>>> >>>> > [3] - https://issues.apache.org/jira/browse/IGNITE-22744
>> > >>>> >>>> > [4] - https://issues.apache.org/jira/browse/IGNITE-22745
>> > >>>> >>>> > [5] - https://issues.apache.org/jira/browse/IGNITE-22746
>> > >>>> >>>> >
>> > >>>> >>>> > Best Regards,
>> > >>>> >>>> > Igor
>> > >>>> >>>> >
>> > >>>> >>>> >
>> > >>>> >>>> > On Tue, Sep 10, 2024 at 6:43 AM Mikhail Pochatkin <
>> > >>>> >>>> m.a.pochatkin@gmail.com>
>> > >>>> >>>> > wrote:
>> > >>>> >>>> >
>> > >>>> >>>> > > +1
>> > >>>> >>>> > >
>> > >>>> >>>> > > чт, 29 авг. 2024 г. в 13:50, Pavel Tupitsyn <
>> > >>>> ptupitsyn@apache.org>:
>> > >>>> >>>> > >
>> > >>>> >>>> > > > Dear Ignite Community!
>> > >>>> >>>> > > >
>> > >>>> >>>> > > > I suggest starting Apache Ignite 3.0.0 release
>> activities.
>> > >>>> >>>> > > >
>> > >>>> >>>> > > > beta1 was released almost 2 years ago, and the product
>> has
>> > >>>> matured
>> > >>>> >>>> > > greatly
>> > >>>> >>>> > > > since then.
>> > >>>> >>>> > > > - The public API is stable
>> > >>>> >>>> > > > - Performance is greatly improved [1]
>> > >>>> >>>> > > > - More than 2000 tickets resolved [2]
>> > >>>> >>>> > > >
>> > >>>> >>>> > > > I would like to be the release manager. Proposed
>> timeline:
>> > >>>> >>>> > > >
>> > >>>> >>>> > > > Scope Freeze: September 13, 2024
>> > >>>> >>>> > > > Code Freeze: September 20, 2024
>> > >>>> >>>> > > > Voting Date: September 27, 2022
>> > >>>> >>>> > > > Release Date: October 03, 2022
>> > >>>> >>>> > > >
>> > >>>> >>>> > > > WDYT?
>> > >>>> >>>> > > >
>> > >>>> >>>> > > > [1] https://issues.apache.org/jira/browse/IGNITE-19479
>> > >>>> >>>> > > > [2]
>> > >>>> >>>> > > >
>> > >>>> >>>> > > >
>> > >>>> >>>> > >
>> > >>>> >>>>
>> > >>>> >>>
>> > >>>>
>> >
>> https://issues.apache.org/jira/issues/?jql=labels%3Dignite-3%20%20and%20fixVersion%20%3D%203.0.0-beta2%20and%20status%3Dresolved
>> > >>>> >>>> > > >
>> > >>>> >>>> > >
>> > >>>> >>>> > >
>> > >>>> >>>> > > --
>> > >>>> >>>> > > best regards,
>> > >>>> >>>> > > Pochatkin Mikhail.
>> > >>>> >>>> > >
>> > >>>> >>>>
>> > >>>> >>>
>> > >>>> >>> --
>> > >>>> >>>
>> > >>>> >>> Best regards,
>> > >>>> >>> Alexei Scherbakov
>> > >>>> -- С уважением, Владимир Плигин.
>> > >>>>
>> > >>>
>> >
>>
>
Re: Apache Ignite 3.0.0 RELEASE [Time, Scope, Manager]
Posted by Pavel Tupitsyn <pt...@apache.org>.
Thanks Ivan, added to the "important task" list.
The scope freeze will be announced later today.
On Tue, Jan 7, 2025 at 11:56 AM Ivan Artiukhov <m....@gmail.com> wrote:
> The following possible blocker regarding c3p0 connection pools has been
> found recently:
>
> [1] - https://issues.apache.org/jira/browse/IGNITE-24159
>
> I'd suggest including it into the release scope.
>
> пн, 16 дек. 2024 г. в 11:18, Pavel Tupitsyn <pt...@apache.org>:
>
> > RO TX timeouts [1] and related tasks are still in the works.
> > Moving the dates again:
> >
> > Scope Freeze: January 06, 2025
> > Code Freeze: January 13, 2025
> > Voting Date: January 27, 2025
> > Release Date: February 4, 2025
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-23747
> >
> > On Wed, Nov 13, 2024 at 2:42 PM Pavel Tupitsyn <pt...@apache.org>
> > wrote:
> >
> > > There are still 5 important unresolved tasks, moving the dates again.
> > > Considering various holidays across the globe nearing the end of the
> > year:
> > >
> > > Scope Freeze: December 16, 2024
> > > Code Freeze: December 23, 2024
> > > Voting Date: January 6, 2025
> > > Release Date: January 13, 2025
> > >
> > > On Wed, Oct 9, 2024 at 9:34 AM Pavel Tupitsyn <pt...@apache.org>
> > > wrote:
> > >
> > >> Metastorage Compaction and some other important tickets [1] are still
> > >> unresolved. Let's postpone the release further.
> > >>
> > >> Proposed dates:
> > >> Scope Freeze: November 11, 2024
> > >> Code Freeze: November 18, 2024
> > >> Voting Date: November 25, 2024
> > >> Release Date: December 02, 2024
> > >>
> > >> [1]
> > >>
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=318606750#ApacheIgnite3.0.0-Themostimportantreleasetasks
> > >>
> > >> On Fri, Oct 4, 2024 at 3:59 PM Pavel Tupitsyn <pt...@apache.org>
> > >> wrote:
> > >>
> > >>> Thanks Vladimir, this ticket is already tracked as a requirement for
> > the
> > >>> release [1]
> > >>> I'll keep an eye on the progress and move the dates if necessary.
> > >>>
> > >>> [1]
> > >>>
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=318606750#ApacheIgnite3.0.0-Themostimportantreleasetasks
> > >>>
> > >>> On Fri, Oct 4, 2024 at 2:44 PM Vladimir Pligin <vova199107@yandex.ru
> >
> > >>> wrote:
> > >>>
> > >>>> Hi guys,
> > >>>>
> > >>>> I'd like to highlight that there's still an unfinished epic (
> > >>>> https://issues.apache.org/jira/browse/IGNITE-20166) related to the
> > >>>> compaction triggers for meta store. It's marked as "Important" in
> > Jira and
> > >>>> it totally reflects it's severity. Currently nodes of a cluster are
> > being
> > >>>> slowly overflown by meta store data ingestion. This is indeed a
> > >>>> user-exposed behavior. Let's consider postponing the release to let
> > this
> > >>>> activity finish up.
> > >>>>
> > >>>>
> > >>>> > Preliminary YCSB benchmark results added to the release page [1]
> > >>>> >
> > >>>> > [1]
> > >>>> >
> > >>>>
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=318606750#ApacheIgnite3.0.0-Benchmarks
> > >>>> >
> > >>>> > On Fri, Sep 13, 2024 at 10:09 AM Pavel Tupitsyn <
> > ptupitsyn@apache.org
> > >>>> >
> > >>>> > wrote:
> > >>>> >
> > >>>> >> I agree that the tickets listed above are important for the
> > release.
> > >>>> Let's
> > >>>> >> move the dates by 4 weeks:
> > >>>> >>
> > >>>> >> Scope Freeze: October 11, 2024
> > >>>> >> Code Freeze: October 18, 2024
> > >>>> >> Voting Date: October 25, 2024
> > >>>> >> Release Date: October 31, 2024
> > >>>> >>
> > >>>> >> On Thu, Sep 12, 2024 at 4:22 PM Alexei Scherbakov <
> > >>>> >> alexey.scherbakoff@gmail.com> wrote:
> > >>>> >>
> > >>>> >>> +1
> > >>>> >>>
> > >>>> >>> I suggest to dig to the bottom of [1] before release.
> > >>>> >>>
> > >>>> >>> [1] https://issues.apache.org/jira/browse/IGNITE-23199
> > >>>> >>>
> > >>>> >>> чт, 12 сент. 2024 г. в 09:35, Roman Puchkovskiy <
> > >>>> >>> roman.puchkovskiy@gmail.com
> > >>>> >>>>:
> > >>>> >>>
> > >>>> >>>> +1.
> > >>>> >>>>
> > >>>> >>>> I would also like to include the following issues into the
> > release
> > >>>> >>> scope:
> > >>>> >>>>
> > >>>> >>>> * [1] to make sure we don't keep garbage after a partition
> > >>>> destruction
> > >>>> >>>> * [2] and [3] to make it easier to maintain binary
> compatibility
> > >>>> after
> > >>>> >>>> the release
> > >>>> >>>> * [4] as it's required by [3]
> > >>>> >>>>
> > >>>> >>>> It seems that about 1 or 2 weeks are needed to implement those.
> > >>>> >>>>
> > >>>> >>>> [1] - https://issues.apache.org/jira/browse/IGNITE-18703
> > >>>> >>>> [2] - https://issues.apache.org/jira/browse/IGNITE-23135
> > >>>> >>>> [3] - https://issues.apache.org/jira/browse/IGNITE-23197
> > >>>> >>>> [4] - https://issues.apache.org/jira/browse/IGNITE-15119
> > >>>> >>>>
> > >>>> >>>> Regards,
> > >>>> >>>> Roman Puchkovskiy
> > >>>> >>>>
> > >>>> >>>> ср, 11 сент. 2024 г. в 17:29, Igor Sapego <isapego@apache.org
> >:
> > >>>> >>>> >
> > >>>> >>>> > Igniters,
> > >>>> >>>> >
> > >>>> >>>> > I think it is important to include at least basic Python
> > support
> > >>>> in
> > >>>> >>> the
> > >>>> >>>> > initial release.
> > >>>> >>>> > I'm working on the DB API Driver [1], and we need to
> implement
> > >>>> the
> > >>>> >>>> following
> > >>>> >>>> > tasks to consider it "release ready": [2] [3] [4] [5]. I
> expect
> > >>>> those
> > >>>> >>> in
> > >>>> >>>> > 3-4 weeks.
> > >>>> >>>> >
> > >>>> >>>> > [1] - https://issues.apache.org/jira/browse/IGNITE-22719
> > >>>> >>>> > [2] - https://issues.apache.org/jira/browse/IGNITE-22740
> > >>>> >>>> > [3] - https://issues.apache.org/jira/browse/IGNITE-22744
> > >>>> >>>> > [4] - https://issues.apache.org/jira/browse/IGNITE-22745
> > >>>> >>>> > [5] - https://issues.apache.org/jira/browse/IGNITE-22746
> > >>>> >>>> >
> > >>>> >>>> > Best Regards,
> > >>>> >>>> > Igor
> > >>>> >>>> >
> > >>>> >>>> >
> > >>>> >>>> > On Tue, Sep 10, 2024 at 6:43 AM Mikhail Pochatkin <
> > >>>> >>>> m.a.pochatkin@gmail.com>
> > >>>> >>>> > wrote:
> > >>>> >>>> >
> > >>>> >>>> > > +1
> > >>>> >>>> > >
> > >>>> >>>> > > чт, 29 авг. 2024 г. в 13:50, Pavel Tupitsyn <
> > >>>> ptupitsyn@apache.org>:
> > >>>> >>>> > >
> > >>>> >>>> > > > Dear Ignite Community!
> > >>>> >>>> > > >
> > >>>> >>>> > > > I suggest starting Apache Ignite 3.0.0 release
> activities.
> > >>>> >>>> > > >
> > >>>> >>>> > > > beta1 was released almost 2 years ago, and the product
> has
> > >>>> matured
> > >>>> >>>> > > greatly
> > >>>> >>>> > > > since then.
> > >>>> >>>> > > > - The public API is stable
> > >>>> >>>> > > > - Performance is greatly improved [1]
> > >>>> >>>> > > > - More than 2000 tickets resolved [2]
> > >>>> >>>> > > >
> > >>>> >>>> > > > I would like to be the release manager. Proposed
> timeline:
> > >>>> >>>> > > >
> > >>>> >>>> > > > Scope Freeze: September 13, 2024
> > >>>> >>>> > > > Code Freeze: September 20, 2024
> > >>>> >>>> > > > Voting Date: September 27, 2022
> > >>>> >>>> > > > Release Date: October 03, 2022
> > >>>> >>>> > > >
> > >>>> >>>> > > > WDYT?
> > >>>> >>>> > > >
> > >>>> >>>> > > > [1] https://issues.apache.org/jira/browse/IGNITE-19479
> > >>>> >>>> > > > [2]
> > >>>> >>>> > > >
> > >>>> >>>> > > >
> > >>>> >>>> > >
> > >>>> >>>>
> > >>>> >>>
> > >>>>
> >
> https://issues.apache.org/jira/issues/?jql=labels%3Dignite-3%20%20and%20fixVersion%20%3D%203.0.0-beta2%20and%20status%3Dresolved
> > >>>> >>>> > > >
> > >>>> >>>> > >
> > >>>> >>>> > >
> > >>>> >>>> > > --
> > >>>> >>>> > > best regards,
> > >>>> >>>> > > Pochatkin Mikhail.
> > >>>> >>>> > >
> > >>>> >>>>
> > >>>> >>>
> > >>>> >>> --
> > >>>> >>>
> > >>>> >>> Best regards,
> > >>>> >>> Alexei Scherbakov
> > >>>> -- С уважением, Владимир Плигин.
> > >>>>
> > >>>
> >
>
Re: Apache Ignite 3.0.0 RELEASE [Time, Scope, Manager]
Posted by Ivan Artiukhov <m....@gmail.com>.
The following possible blocker regarding c3p0 connection pools has been
found recently:
[1] - https://issues.apache.org/jira/browse/IGNITE-24159
I'd suggest including it into the release scope.
пн, 16 дек. 2024 г. в 11:18, Pavel Tupitsyn <pt...@apache.org>:
> RO TX timeouts [1] and related tasks are still in the works.
> Moving the dates again:
>
> Scope Freeze: January 06, 2025
> Code Freeze: January 13, 2025
> Voting Date: January 27, 2025
> Release Date: February 4, 2025
>
> [1] https://issues.apache.org/jira/browse/IGNITE-23747
>
> On Wed, Nov 13, 2024 at 2:42 PM Pavel Tupitsyn <pt...@apache.org>
> wrote:
>
> > There are still 5 important unresolved tasks, moving the dates again.
> > Considering various holidays across the globe nearing the end of the
> year:
> >
> > Scope Freeze: December 16, 2024
> > Code Freeze: December 23, 2024
> > Voting Date: January 6, 2025
> > Release Date: January 13, 2025
> >
> > On Wed, Oct 9, 2024 at 9:34 AM Pavel Tupitsyn <pt...@apache.org>
> > wrote:
> >
> >> Metastorage Compaction and some other important tickets [1] are still
> >> unresolved. Let's postpone the release further.
> >>
> >> Proposed dates:
> >> Scope Freeze: November 11, 2024
> >> Code Freeze: November 18, 2024
> >> Voting Date: November 25, 2024
> >> Release Date: December 02, 2024
> >>
> >> [1]
> >>
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=318606750#ApacheIgnite3.0.0-Themostimportantreleasetasks
> >>
> >> On Fri, Oct 4, 2024 at 3:59 PM Pavel Tupitsyn <pt...@apache.org>
> >> wrote:
> >>
> >>> Thanks Vladimir, this ticket is already tracked as a requirement for
> the
> >>> release [1]
> >>> I'll keep an eye on the progress and move the dates if necessary.
> >>>
> >>> [1]
> >>>
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=318606750#ApacheIgnite3.0.0-Themostimportantreleasetasks
> >>>
> >>> On Fri, Oct 4, 2024 at 2:44 PM Vladimir Pligin <vo...@yandex.ru>
> >>> wrote:
> >>>
> >>>> Hi guys,
> >>>>
> >>>> I'd like to highlight that there's still an unfinished epic (
> >>>> https://issues.apache.org/jira/browse/IGNITE-20166) related to the
> >>>> compaction triggers for meta store. It's marked as "Important" in
> Jira and
> >>>> it totally reflects it's severity. Currently nodes of a cluster are
> being
> >>>> slowly overflown by meta store data ingestion. This is indeed a
> >>>> user-exposed behavior. Let's consider postponing the release to let
> this
> >>>> activity finish up.
> >>>>
> >>>>
> >>>> > Preliminary YCSB benchmark results added to the release page [1]
> >>>> >
> >>>> > [1]
> >>>> >
> >>>>
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=318606750#ApacheIgnite3.0.0-Benchmarks
> >>>> >
> >>>> > On Fri, Sep 13, 2024 at 10:09 AM Pavel Tupitsyn <
> ptupitsyn@apache.org
> >>>> >
> >>>> > wrote:
> >>>> >
> >>>> >> I agree that the tickets listed above are important for the
> release.
> >>>> Let's
> >>>> >> move the dates by 4 weeks:
> >>>> >>
> >>>> >> Scope Freeze: October 11, 2024
> >>>> >> Code Freeze: October 18, 2024
> >>>> >> Voting Date: October 25, 2024
> >>>> >> Release Date: October 31, 2024
> >>>> >>
> >>>> >> On Thu, Sep 12, 2024 at 4:22 PM Alexei Scherbakov <
> >>>> >> alexey.scherbakoff@gmail.com> wrote:
> >>>> >>
> >>>> >>> +1
> >>>> >>>
> >>>> >>> I suggest to dig to the bottom of [1] before release.
> >>>> >>>
> >>>> >>> [1] https://issues.apache.org/jira/browse/IGNITE-23199
> >>>> >>>
> >>>> >>> чт, 12 сент. 2024 г. в 09:35, Roman Puchkovskiy <
> >>>> >>> roman.puchkovskiy@gmail.com
> >>>> >>>>:
> >>>> >>>
> >>>> >>>> +1.
> >>>> >>>>
> >>>> >>>> I would also like to include the following issues into the
> release
> >>>> >>> scope:
> >>>> >>>>
> >>>> >>>> * [1] to make sure we don't keep garbage after a partition
> >>>> destruction
> >>>> >>>> * [2] and [3] to make it easier to maintain binary compatibility
> >>>> after
> >>>> >>>> the release
> >>>> >>>> * [4] as it's required by [3]
> >>>> >>>>
> >>>> >>>> It seems that about 1 or 2 weeks are needed to implement those.
> >>>> >>>>
> >>>> >>>> [1] - https://issues.apache.org/jira/browse/IGNITE-18703
> >>>> >>>> [2] - https://issues.apache.org/jira/browse/IGNITE-23135
> >>>> >>>> [3] - https://issues.apache.org/jira/browse/IGNITE-23197
> >>>> >>>> [4] - https://issues.apache.org/jira/browse/IGNITE-15119
> >>>> >>>>
> >>>> >>>> Regards,
> >>>> >>>> Roman Puchkovskiy
> >>>> >>>>
> >>>> >>>> ср, 11 сент. 2024 г. в 17:29, Igor Sapego <is...@apache.org>:
> >>>> >>>> >
> >>>> >>>> > Igniters,
> >>>> >>>> >
> >>>> >>>> > I think it is important to include at least basic Python
> support
> >>>> in
> >>>> >>> the
> >>>> >>>> > initial release.
> >>>> >>>> > I'm working on the DB API Driver [1], and we need to implement
> >>>> the
> >>>> >>>> following
> >>>> >>>> > tasks to consider it "release ready": [2] [3] [4] [5]. I expect
> >>>> those
> >>>> >>> in
> >>>> >>>> > 3-4 weeks.
> >>>> >>>> >
> >>>> >>>> > [1] - https://issues.apache.org/jira/browse/IGNITE-22719
> >>>> >>>> > [2] - https://issues.apache.org/jira/browse/IGNITE-22740
> >>>> >>>> > [3] - https://issues.apache.org/jira/browse/IGNITE-22744
> >>>> >>>> > [4] - https://issues.apache.org/jira/browse/IGNITE-22745
> >>>> >>>> > [5] - https://issues.apache.org/jira/browse/IGNITE-22746
> >>>> >>>> >
> >>>> >>>> > Best Regards,
> >>>> >>>> > Igor
> >>>> >>>> >
> >>>> >>>> >
> >>>> >>>> > On Tue, Sep 10, 2024 at 6:43 AM Mikhail Pochatkin <
> >>>> >>>> m.a.pochatkin@gmail.com>
> >>>> >>>> > wrote:
> >>>> >>>> >
> >>>> >>>> > > +1
> >>>> >>>> > >
> >>>> >>>> > > чт, 29 авг. 2024 г. в 13:50, Pavel Tupitsyn <
> >>>> ptupitsyn@apache.org>:
> >>>> >>>> > >
> >>>> >>>> > > > Dear Ignite Community!
> >>>> >>>> > > >
> >>>> >>>> > > > I suggest starting Apache Ignite 3.0.0 release activities.
> >>>> >>>> > > >
> >>>> >>>> > > > beta1 was released almost 2 years ago, and the product has
> >>>> matured
> >>>> >>>> > > greatly
> >>>> >>>> > > > since then.
> >>>> >>>> > > > - The public API is stable
> >>>> >>>> > > > - Performance is greatly improved [1]
> >>>> >>>> > > > - More than 2000 tickets resolved [2]
> >>>> >>>> > > >
> >>>> >>>> > > > I would like to be the release manager. Proposed timeline:
> >>>> >>>> > > >
> >>>> >>>> > > > Scope Freeze: September 13, 2024
> >>>> >>>> > > > Code Freeze: September 20, 2024
> >>>> >>>> > > > Voting Date: September 27, 2022
> >>>> >>>> > > > Release Date: October 03, 2022
> >>>> >>>> > > >
> >>>> >>>> > > > WDYT?
> >>>> >>>> > > >
> >>>> >>>> > > > [1] https://issues.apache.org/jira/browse/IGNITE-19479
> >>>> >>>> > > > [2]
> >>>> >>>> > > >
> >>>> >>>> > > >
> >>>> >>>> > >
> >>>> >>>>
> >>>> >>>
> >>>>
> https://issues.apache.org/jira/issues/?jql=labels%3Dignite-3%20%20and%20fixVersion%20%3D%203.0.0-beta2%20and%20status%3Dresolved
> >>>> >>>> > > >
> >>>> >>>> > >
> >>>> >>>> > >
> >>>> >>>> > > --
> >>>> >>>> > > best regards,
> >>>> >>>> > > Pochatkin Mikhail.
> >>>> >>>> > >
> >>>> >>>>
> >>>> >>>
> >>>> >>> --
> >>>> >>>
> >>>> >>> Best regards,
> >>>> >>> Alexei Scherbakov
> >>>> -- С уважением, Владимир Плигин.
> >>>>
> >>>
>
Re: Apache Ignite 3.0.0 RELEASE [Time, Scope, Manager]
Posted by Pavel Tupitsyn <pt...@apache.org>.
RO TX timeouts [1] and related tasks are still in the works.
Moving the dates again:
Scope Freeze: January 06, 2025
Code Freeze: January 13, 2025
Voting Date: January 27, 2025
Release Date: February 4, 2025
[1] https://issues.apache.org/jira/browse/IGNITE-23747
On Wed, Nov 13, 2024 at 2:42 PM Pavel Tupitsyn <pt...@apache.org> wrote:
> There are still 5 important unresolved tasks, moving the dates again.
> Considering various holidays across the globe nearing the end of the year:
>
> Scope Freeze: December 16, 2024
> Code Freeze: December 23, 2024
> Voting Date: January 6, 2025
> Release Date: January 13, 2025
>
> On Wed, Oct 9, 2024 at 9:34 AM Pavel Tupitsyn <pt...@apache.org>
> wrote:
>
>> Metastorage Compaction and some other important tickets [1] are still
>> unresolved. Let's postpone the release further.
>>
>> Proposed dates:
>> Scope Freeze: November 11, 2024
>> Code Freeze: November 18, 2024
>> Voting Date: November 25, 2024
>> Release Date: December 02, 2024
>>
>> [1]
>> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=318606750#ApacheIgnite3.0.0-Themostimportantreleasetasks
>>
>> On Fri, Oct 4, 2024 at 3:59 PM Pavel Tupitsyn <pt...@apache.org>
>> wrote:
>>
>>> Thanks Vladimir, this ticket is already tracked as a requirement for the
>>> release [1]
>>> I'll keep an eye on the progress and move the dates if necessary.
>>>
>>> [1]
>>> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=318606750#ApacheIgnite3.0.0-Themostimportantreleasetasks
>>>
>>> On Fri, Oct 4, 2024 at 2:44 PM Vladimir Pligin <vo...@yandex.ru>
>>> wrote:
>>>
>>>> Hi guys,
>>>>
>>>> I'd like to highlight that there's still an unfinished epic (
>>>> https://issues.apache.org/jira/browse/IGNITE-20166) related to the
>>>> compaction triggers for meta store. It's marked as "Important" in Jira and
>>>> it totally reflects it's severity. Currently nodes of a cluster are being
>>>> slowly overflown by meta store data ingestion. This is indeed a
>>>> user-exposed behavior. Let's consider postponing the release to let this
>>>> activity finish up.
>>>>
>>>>
>>>> > Preliminary YCSB benchmark results added to the release page [1]
>>>> >
>>>> > [1]
>>>> >
>>>> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=318606750#ApacheIgnite3.0.0-Benchmarks
>>>> >
>>>> > On Fri, Sep 13, 2024 at 10:09 AM Pavel Tupitsyn <ptupitsyn@apache.org
>>>> >
>>>> > wrote:
>>>> >
>>>> >> I agree that the tickets listed above are important for the release.
>>>> Let's
>>>> >> move the dates by 4 weeks:
>>>> >>
>>>> >> Scope Freeze: October 11, 2024
>>>> >> Code Freeze: October 18, 2024
>>>> >> Voting Date: October 25, 2024
>>>> >> Release Date: October 31, 2024
>>>> >>
>>>> >> On Thu, Sep 12, 2024 at 4:22 PM Alexei Scherbakov <
>>>> >> alexey.scherbakoff@gmail.com> wrote:
>>>> >>
>>>> >>> +1
>>>> >>>
>>>> >>> I suggest to dig to the bottom of [1] before release.
>>>> >>>
>>>> >>> [1] https://issues.apache.org/jira/browse/IGNITE-23199
>>>> >>>
>>>> >>> чт, 12 сент. 2024 г. в 09:35, Roman Puchkovskiy <
>>>> >>> roman.puchkovskiy@gmail.com
>>>> >>>>:
>>>> >>>
>>>> >>>> +1.
>>>> >>>>
>>>> >>>> I would also like to include the following issues into the release
>>>> >>> scope:
>>>> >>>>
>>>> >>>> * [1] to make sure we don't keep garbage after a partition
>>>> destruction
>>>> >>>> * [2] and [3] to make it easier to maintain binary compatibility
>>>> after
>>>> >>>> the release
>>>> >>>> * [4] as it's required by [3]
>>>> >>>>
>>>> >>>> It seems that about 1 or 2 weeks are needed to implement those.
>>>> >>>>
>>>> >>>> [1] - https://issues.apache.org/jira/browse/IGNITE-18703
>>>> >>>> [2] - https://issues.apache.org/jira/browse/IGNITE-23135
>>>> >>>> [3] - https://issues.apache.org/jira/browse/IGNITE-23197
>>>> >>>> [4] - https://issues.apache.org/jira/browse/IGNITE-15119
>>>> >>>>
>>>> >>>> Regards,
>>>> >>>> Roman Puchkovskiy
>>>> >>>>
>>>> >>>> ср, 11 сент. 2024 г. в 17:29, Igor Sapego <is...@apache.org>:
>>>> >>>> >
>>>> >>>> > Igniters,
>>>> >>>> >
>>>> >>>> > I think it is important to include at least basic Python support
>>>> in
>>>> >>> the
>>>> >>>> > initial release.
>>>> >>>> > I'm working on the DB API Driver [1], and we need to implement
>>>> the
>>>> >>>> following
>>>> >>>> > tasks to consider it "release ready": [2] [3] [4] [5]. I expect
>>>> those
>>>> >>> in
>>>> >>>> > 3-4 weeks.
>>>> >>>> >
>>>> >>>> > [1] - https://issues.apache.org/jira/browse/IGNITE-22719
>>>> >>>> > [2] - https://issues.apache.org/jira/browse/IGNITE-22740
>>>> >>>> > [3] - https://issues.apache.org/jira/browse/IGNITE-22744
>>>> >>>> > [4] - https://issues.apache.org/jira/browse/IGNITE-22745
>>>> >>>> > [5] - https://issues.apache.org/jira/browse/IGNITE-22746
>>>> >>>> >
>>>> >>>> > Best Regards,
>>>> >>>> > Igor
>>>> >>>> >
>>>> >>>> >
>>>> >>>> > On Tue, Sep 10, 2024 at 6:43 AM Mikhail Pochatkin <
>>>> >>>> m.a.pochatkin@gmail.com>
>>>> >>>> > wrote:
>>>> >>>> >
>>>> >>>> > > +1
>>>> >>>> > >
>>>> >>>> > > чт, 29 авг. 2024 г. в 13:50, Pavel Tupitsyn <
>>>> ptupitsyn@apache.org>:
>>>> >>>> > >
>>>> >>>> > > > Dear Ignite Community!
>>>> >>>> > > >
>>>> >>>> > > > I suggest starting Apache Ignite 3.0.0 release activities.
>>>> >>>> > > >
>>>> >>>> > > > beta1 was released almost 2 years ago, and the product has
>>>> matured
>>>> >>>> > > greatly
>>>> >>>> > > > since then.
>>>> >>>> > > > - The public API is stable
>>>> >>>> > > > - Performance is greatly improved [1]
>>>> >>>> > > > - More than 2000 tickets resolved [2]
>>>> >>>> > > >
>>>> >>>> > > > I would like to be the release manager. Proposed timeline:
>>>> >>>> > > >
>>>> >>>> > > > Scope Freeze: September 13, 2024
>>>> >>>> > > > Code Freeze: September 20, 2024
>>>> >>>> > > > Voting Date: September 27, 2022
>>>> >>>> > > > Release Date: October 03, 2022
>>>> >>>> > > >
>>>> >>>> > > > WDYT?
>>>> >>>> > > >
>>>> >>>> > > > [1] https://issues.apache.org/jira/browse/IGNITE-19479
>>>> >>>> > > > [2]
>>>> >>>> > > >
>>>> >>>> > > >
>>>> >>>> > >
>>>> >>>>
>>>> >>>
>>>> https://issues.apache.org/jira/issues/?jql=labels%3Dignite-3%20%20and%20fixVersion%20%3D%203.0.0-beta2%20and%20status%3Dresolved
>>>> >>>> > > >
>>>> >>>> > >
>>>> >>>> > >
>>>> >>>> > > --
>>>> >>>> > > best regards,
>>>> >>>> > > Pochatkin Mikhail.
>>>> >>>> > >
>>>> >>>>
>>>> >>>
>>>> >>> --
>>>> >>>
>>>> >>> Best regards,
>>>> >>> Alexei Scherbakov
>>>> -- С уважением, Владимир Плигин.
>>>>
>>>