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 <ptupit...@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.scherbak...@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.puchkovs...@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 <isap...@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.pochat...@gmail.com>
>>>> > wrote:
>>>> >
>>>> > > +1
>>>> > >
>>>> > > чт, 29 авг. 2024 г. в 13:50, Pavel Tupitsyn <ptupit...@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
-- С уважением, Владимир Плигин.

Reply via email to