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 <xxt...@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 <ptupit...@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 <vova199...@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.
> > >
> >
>

Reply via email to