Hi, Igniters.

During load testing I found a 5-10% performance drop in the following
tests: PutAllSerializableTxBenchmark, GetAllPutAllTxBenchmark. I am
investigating.

On Mon, Dec 23, 2024 at 4:47 PM Nikita Amelchev <namelc...@apache.org> wrote:
>
> Igniters,
>
> I am doing load testing of the release. It was delayed by
> infrastructure issues. I will start voting as soon as I receive the
> required results.
>
> Thanks for understanding!
>
> On Tue, Dec 17, 2024 at 3:52 PM Nikita Amelchev <namelc...@apache.org> wrote:
> >
> > Hello, Igniters.
> >
> > I'm announcing a code freeze for the 2.17 release. Only blockers are
> > accepted to the release since this moment. The release branch has been
> > cut (ignite-2.17).
> >
> > The ApplicationContext API (IEP-129) has been moved to a next release.
> >
> > Here is updated timeline:
> >
> > Code Freeze: December 17, 2024
> > Voting Date: December 23, 2024
> > Release Date: December 30, 2024
> >
> > On Mon, Dec 9, 2024 at 8:54 PM Nikita Amelchev <namelc...@apache.org> wrote:
> > >
> > > Igniters,
> > >
> > > There are a few issues still in the final review stage that we'd like
> > > to see in 2.17. I suggest we wait for them [1] and cut off the release
> > > branch to stabilize.
> > >
> > > > Could you please add the following ticket 
> > > > https://issues.apache.org/jira/browse/IGNITE-18572 to the release scope?
> > >
> > > Yes, it'll be added.
> > >
> > > [1] IEP-129, IEP-81 Phase 3.
> > >
> > > On Wed, Dec 4, 2024 at 2:17 PM Вячеслав Коптилин
> > > <slava.kopti...@gmail.com> wrote:
> > > >
> > > > Hi Nikita,
> > > >
> > > > Could you please add the following ticket
> > > > https://issues.apache.org/jira/browse/IGNITE-18572 to the release scope?
> > > > The patch has been merged into the master branch
> > > > [275bc22d854a88ded02338d176a6431479535dab]
> > > >
> > > > Thanks,
> > > > S.
> > > >
> > > > пн, 2 дек. 2024 г. в 14:45, Nikita Amelchev <namelc...@apache.org>:
> > > >
> > > > > Igniters,
> > > > >
> > > > > There are several issues in the final review stage that we would like
> > > > > to see in 2.17. I suggest waiting for them [1] and several minor ones
> > > > > [2].
> > > > >
> > > > > Updated timeline:
> > > > >
> > > > > Code Freeze: December 9, 2024
> > > > > Voting Date: December 16, 2024
> > > > > Release Date: December 23, 2024
> > > > >
> > > > > [1] IEP-129, IEP-81 Phase 3.
> > > > > [2]
> > > > > https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.17%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20%20and%20status%20not%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20
> > > > >
> > > > > On Thu, Nov 21, 2024 at 11:42 AM Pavel Tupitsyn <ptupit...@apache.org>
> > > > > wrote:
> > > > > >
> > > > > > Critical issue - node crash on .NET 9, I'm working on it ASAP
> > > > > >
> > > > > > https://issues.apache.org/jira/browse/IGNITE-23732
> > > > > >
> > > > > > On Thu, Nov 21, 2024 at 3:15 AM 18624049226 <18624049...@163.com> 
> > > > > > wrote:
> > > > > >
> > > > > > > Hello Nikita,
> > > > > > >
> > > > > > > I suggest merging the following PRs:
> > > > > > >
> > > > > > > https://issues.apache.org/jira/browse/IGNITE-18572
> > > > > > >
> > > > > > > https://issues.apache.org/jira/browse/IGNITE-21027
> > > > > > >
> > > > > > > https://issues.apache.org/jira/browse/IGNITE-21741
> > > > > > >
> > > > > > > https://issues.apache.org/jira/browse/IGNITE-22437
> > > > > > >
> > > > > > > https://issues.apache.org/jira/browse/IGNITE-23167
> > > > > > >
> > > > > > >
> > > > > > > Among them:
> > > > > > >
> > > > > > > IGNITE-22437: This is a serious memory leak issue, and it is
> > > > > recommended
> > > > > > > that the community give priority attention to it.
> > > > > > >
> > > > > > > IGNITE-21741: I suggest deleting or discarding 
> > > > > > > @IgniteExperimental for
> > > > > > > the following reasons:
> > > > > > >
> > > > > > > 1. The open source software community is a model of sharing and
> > > > > > > collaboration, without providing quality assurance to users, 
> > > > > > > users are
> > > > > > > responsible for their own choices. If users need assurance, they 
> > > > > > > should
> > > > > > > seek the help of GridGain.
> > > > > > >
> > > > > > > 2.This annotation lacks maintenance, and many features have 
> > > > > > > already
> > > > > > > stabilized, but none of them have cancelled the experimental 
> > > > > > > state.
> > > > > > >
> > > > > > > 3.After adding this annotation, users are worried and will not 
> > > > > > > use it,
> > > > > > > resulting in a lack of feedback and the community being unable to
> > > > > > > continue improving these features.
> > > > > > >
> > > > > > >
> > > > > > > 在 2024/11/21 03:12, Nikita Amelchev 写道:
> > > > > > > > Hello, Igniters.
> > > > > > > >
> > > > > > > > I have created the 2.17 release page [1].
> > > > > > > >
> > > > > > > > As a reminder, on the scope freeze, issues that are not ready 
> > > > > > > > for
> > > > > > > > merging will be moved to the next release.
> > > > > > > >
> > > > > > > > Please, feel free to write if some issues are critical to be in 
> > > > > > > > the
> > > > > 2.17.
> > > > > > > >
> > > > > > > > [1]
> > > > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.17
> > > > > > > >
> > > > > > > > On Wed, Nov 13, 2024 at 9:26 AM Pavel 
> > > > > > > > Tupitsyn<ptupit...@apache.org>
> > > > > > > wrote:
> > > > > > > >> +1
> > > > > > > >>
> > > > > > > >> 2.16 was released almost a year ago, some users are worried 
> > > > > > > >> about
> > > > > the
> > > > > > > lack
> > > > > > > >> of updates
> > > > > > > >>
> > > > > > > >> On Tue, Nov 12, 2024 at 11:07 PM Maxim 
> > > > > > > >> Muzafarov<mmu...@apache.org>
> > > > > > > wrote:
> > > > > > > >>
> > > > > > > >>> +1
> > > > > > > >>>
> > > > > > > >>> On Tue, 12 Nov 2024 at 18:41, Nikita 
> > > > > > > >>> Amelchev<namelc...@apache.org
> > > > > >
> > > > > > > >>> wrote:
> > > > > > > >>>> Dear Ignite Community!
> > > > > > > >>>>
> > > > > > > >>>> I suggest starting Apache Ignite 2.17 release activities.
> > > > > > > >>>>
> > > > > > > >>>> We've resolved hundreds of issues [1] with new features and 
> > > > > > > >>>> bug
> > > > > fixes
> > > > > > > >>>> which are waiting for their release date. For example:
> > > > > > > >>>>
> > > > > > > >>>> - Transaction aware SQL queries (IEP-125);
> > > > > > > >>>> - SQL Calcite: Updated Calcite version and a lot of useful 
> > > > > > > >>>> fixes;
> > > > > > > >>>> - Custom metrics introduction (IEP-114);
> > > > > > > >>>> - Removed MVCC;
> > > > > > > >>>> etc.
> > > > > > > >>>>
> > > > > > > >>>> A few more important tickets in a high state of readiness:
> > > > > > > >>>>
> > > > > > > >>>> - ApplicationContext API (IEP-129);
> > > > > > > >>>> - Use IgniteClient instead of GridClient in the control.sh 
> > > > > > > >>>> utility
> > > > > > > >>>> (IEP-81 Phase 3);
> > > > > > > >>>> etc.
> > > > > > > >>>>
> > > > > > > >>>> I want to propose myself to be the release manager of the 
> > > > > > > >>>> planning
> > > > > > > >>> release.
> > > > > > > >>>> I propose the following timeline:
> > > > > > > >>>>
> > > > > > > >>>> Scope Freeze: November 25, 2024
> > > > > > > >>>> Code Freeze: December 2, 2024
> > > > > > > >>>> Voting Date: December 9, 2024
> > > > > > > >>>> Release Date: December 16, 2024
> > > > > > > >>>>
> > > > > > > >>>> WDYT?
> > > > > > > >>>>
> > > > > > > >>>> [1]
> > > > > > > >>>
> > > > > > >
> > > > > https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(2.17))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20AND%20resolution%20in(Fixed%2C%20Done%2C%20Implemented%2C%20Delivered)%20ORDER%20BY%20priority
> > > > > > > >>>> --
> > > > > > > >>>> Best wishes,
> > > > > > > >>>> Amelchev Nikita
> > > > > > > >
> > > > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Best wishes,
> > > > > Amelchev Nikita
> > > > >
> > >
> > >
> > >
> > > --
> > > Best wishes,
> > > Amelchev Nikita
> >
> >
> >
> > --
> > Best wishes,
> > Amelchev Nikita
>
>
>
> --
> Best wishes,
> Amelchev Nikita



-- 
Best wishes,
Amelchev Nikita

Reply via email to