Guys,

I've merged https://issues.apache.org/jira/browse/IGNITE-17590 to main and
I really think it should be included in this release, because without it
current
C++ client implementation is pretty much useless. And it does not affect any
other parts of the product except for the C++ part anyway so there won't be
additional risks for the core of the product.

Best Regards,
Igor


On Tue, Nov 1, 2022 at 2:08 PM Вячеслав Коптилин <slava.kopti...@gmail.com>
wrote:

> Hello Mikhail,
>
> I agree that these tickets should be included in the release. Let's prepare
> corresponding pull-request(s).
>
> Thanks,
> Slava.
>
>
> пт, 28 окт. 2022 г. в 18:07, Mikhail Pochatkin <mpochat...@unison.team>:
>
> > Hello, I would like to add following tickets to ignite-3.0.0-beta1
> > [IGNITE-17966] Fix problem with stuck Gradle processes in .NET tests -
> ASF
> > JIRA (apache.org) <https://issues.apache.org/jira/browse/IGNITE-17966>
> > [IGNITE-17965] Enable remote build cache for Gradle - ASF JIRA (
> apache.org
> > )
> > <https://issues.apache.org/jira/browse/IGNITE-17965>
> > [IGNITE-17980] ./gradlew clean build -x test fails - ASF JIRA (
> apache.org)
> > <https://issues.apache.org/jira/browse/IGNITE-17980>
> > [IGNITE-18009] Fix gradle build - ASF JIRA (apache.org)
> > <https://issues.apache.org/jira/browse/IGNITE-18009>
> >
> > These tickets need to unblock problems with Gradle build and required for
> > packaging scope of beta1. Thanks!
> >
> > On Mon, Oct 24, 2022 at 10:27 PM Mikhail Pochatkin
> <mpochat...@unison.team
> > >
> > wrote:
> >
> > > Hello, Igniters.
> > >
> > > I want to point out that the current beta seems to be blocked by
> > > [IGNITE-17966] <https://issues.apache.org/jira/browse/IGNITE-17966>.
> The
> > > main problem is that we cannot enable Gradle build on CI at this
> moment,
> > > but we need it because all beta distributions are implemented via
> Gradle
> > > build. So, I am trying to fix it in a short time.
> > >
> > > On Sat, Oct 22, 2022 at 5:35 PM Stanislav Lukyanov <
> > stanlukya...@gmail.com>
> > > wrote:
> > >
> > >> There are 11 unresolved tickets in the scope now, 4 In Progress and 7
> > >> Patch Available.
> > >>
> > >> I think we should try to set the code freeze according to the ticket
> > >> estimates instead of just setting it to the end of next week. I'll
> work
> > >> with each ticket owner to determine the critical path.
> > >>
> > >> I also saw an Open ticket that was added to the scope outside of the
> > >> process. I descoped it already, but we need to be careful of new
> tickets
> > >> being added to the scope.
> > >>
> > >> Thanks,
> > >> Stan
> > >>
> > >> > On 20 Oct 2022, at 15:59, Вячеслав Коптилин <
> slava.kopti...@gmail.com
> > >
> > >> wrote:
> > >> >
> > >> > Hello Alexandr,
> > >> >
> > >> > Ok, I added these tickets to the scope.
> > >> >
> > >> > There are 12 tickets that are not resolved and included into the
> > scope.
> > >> So,
> > >> > we have to move the code freeze to the end of next week.
> > >> >
> > >> > Thanks,
> > >> > Slava.
> > >> >
> > >> > чт, 20 окт. 2022 г. в 08:36, Aleksandr Pakhomov <apk...@gmail.com>:
> > >> >
> > >> >> Hi, Igniters.
> > >> >>
> > >> >> I would like to ask you to add a couple of tickets that are
> required
> > >> for
> > >> >> packaging:
> > >> >>
> > >> >> https://issues.apache.org/jira/browse/IGNITE-17781 <
> > >> >> https://issues.apache.org/jira/browse/IGNITE-17781>
> > >> >> https://issues.apache.org/jira/browse/IGNITE-17773 <
> > >> >> https://issues.apache.org/jira/browse/IGNITE-17773>
> > >> >>
> > >> >> These tickets are the last tickets in the packaging scope for
> beta1.
> > >> >>
> > >> >> --
> > >> >> Best regards,
> > >> >> Aleksandr
> > >> >>
> > >> >>> On 19 Oct 2022, at 21:48, Вячеслав Коптилин <
> > slava.kopti...@gmail.com
> > >> >
> > >> >> wrote:
> > >> >>>
> > >> >>> Hi Yuriy,
> > >> >>>
> > >> >>> Let's add them. I hope that these three tasks are the last ones.
> > >> >>>
> > >> >>> Thanks,
> > >> >>> S.
> > >> >>>
> > >> >>> ср, 19 окт. 2022 г. в 16:41, Юрий <jury.gerzhedow...@gmail.com>:
> > >> >>>
> > >> >>>> Slava, thank you.
> > >> >>>>
> > >> >>>> During cherry picking one of aforementioned ticket was observed
> > >> >> dependency
> > >> >>>> on
> > >> >>>> https://issues.apache.org/jira/browse/IGNITE-17907
> > >> >>>> https://issues.apache.org/jira/browse/IGNITE-17671
> > >> >>>> https://issues.apache.org/jira/browse/IGNITE-17816
> > >> >>>>
> > >> >>>> So, I propose adding them into the release scope.
> > >> >>>>
> > >> >>>> ср, 19 окт. 2022 г. в 15:53, Вячеслав Коптилин <
> > >> >> slava.kopti...@gmail.com>:
> > >> >>>>
> > >> >>>>> Hi Yuriy,
> > >> >>>>>
> > >> >>>>> I agree, let's add them to the scope.
> > >> >>>>>
> > >> >>>>> Thanks,
> > >> >>>>> S.
> > >> >>>>>
> > >> >>>>>
> > >> >>>>> ср, 19 окт. 2022 г. в 15:20, Юрий <jury.gerzhedow...@gmail.com
> >:
> > >> >>>>>
> > >> >>>>>> Dear Release managers and Igniters,
> > >> >>>>>>
> > >> >>>>>> I would like to add the following tickets to Ignite 3.0.0
> beta1:
> > >> >>>>>>
> > >> >>>>>> https://issues.apache.org/jira/browse/IGNITE-17820 -
> improvement
> > >> SQL
> > >> >>>> and
> > >> >>>>>> required for the next ticket
> > >> >>>>>> https://issues.apache.org/jira/browse/IGNITE-17748 - related
> to
> > >> >>>> support
> > >> >>>>> of
> > >> >>>>>> indexes
> > >> >>>>>> https://issues.apache.org/jira/browse/IGNITE-17612 - fix issue
> > >> when
> > >> >>>> some
> > >> >>>>>> queries couldn't be done.
> > >> >>>>>> https://issues.apache.org/jira/browse/IGNITE-17330 - support
> RO
> > >> >>>>>> transaction
> > >> >>>>>> by SQL
> > >> >>>>>> https://issues.apache.org/jira/browse/IGNITE-17859 - index
> > filling
> > >> >>>>>> https://issues.apache.org/jira/browse/IGNITE-17813 - related
> to
> > >> >>>> support
> > >> >>>>>> indexes by SQL
> > >> >>>>>> https://issues.apache.org/jira/browse/IGNITE-17655 - related
> to
> > >> >>>> support
> > >> >>>>>> indexes by SQL
> > >> >>>>>>
> > >> >>>>>> ср, 19 окт. 2022 г. в 12:11, Вячеслав Коптилин <
> > >> >>>> slava.kopti...@gmail.com
> > >> >>>>>> :
> > >> >>>>>>
> > >> >>>>>>> Hello Alexander,
> > >> >>>>>>>
> > >> >>>>>>> Thank you for pointing this out. I fully support including RO
> > >> >>>>>> transactions
> > >> >>>>>>> into the scope of Ignite 3.0.0-beta1 release.
> > >> >>>>>>>
> > >> >>>>>>> Thanks,
> > >> >>>>>>> S.
> > >> >>>>>>>
> > >> >>>>>>>
> > >> >>>>>>> ср, 19 окт. 2022 г. в 11:42, Alexander Lapin <
> > lapin1...@gmail.com
> > >> >:
> > >> >>>>>>>
> > >> >>>>>>>> Igniters,
> > >> >>>>>>>>
> > >> >>>>>>>> I would like to add following tickets to ignite-3.0.0-beta1
> > >> >>>>>>>> https://issues.apache.org/jira/browse/IGNITE-17806
> > >> >>>>>>>> https://issues.apache.org/jira/browse/IGNITE-17759
> > >> >>>>>>>> https://issues.apache.org/jira/browse/IGNITE-17637
> > >> >>>>>>>> https://issues.apache.org/jira/browse/IGNITE-17263
> > >> >>>>>>>> https://issues.apache.org/jira/browse/IGNITE-17260
> > >> >>>>>>>>
> > >> >>>>>>>> It's all about read-only transactions.
> > >> >>>>>>>>
> > >> >>>>>>>> Best regards,
> > >> >>>>>>>> Alexander
> > >> >>>>>>>>
> > >> >>>>>>>> пт, 14 окт. 2022 г. в 19:45, Andrey Gura <ag...@apache.org>:
> > >> >>>>>>>>
> > >> >>>>>>>>> Igniters,
> > >> >>>>>>>>>
> > >> >>>>>>>>> The 'ignite-3.0.0-beta1' branch was created (the latest
> commit
> > >> is
> > >> >>>>>>>>> 8160ef31ecf8d49f227562b6f0ab090c6b4438c1).
> > >> >>>>>>>>>
> > >> >>>>>>>>> The scope for the release is frozen.
> > >> >>>>>>>>>
> > >> >>>>>>>>> It means the following:
> > >> >>>>>>>>>
> > >> >>>>>>>>> - Any issue could be added to the release (fixVersion ==
> > >> >>>>> 3.0.0-beta1)
> > >> >>>>>>>>> only after discussion with the community and a release
> manager
> > >> in
> > >> >>>>>> this
> > >> >>>>>>>>> thread.
> > >> >>>>>>>>> - Any commit to the release branch must be also applied to
> the
> > >> >>>>> 'main'
> > >> >>>>>>>>> branch.
> > >> >>>>>>>>>
> > >> >>>>>>>>
> > >> >>>>>>>
> > >> >>>>>>
> > >> >>>>>>
> > >> >>>>>> --
> > >> >>>>>> Живи с улыбкой! :D
> > >> >>>>>>
> > >> >>>>>
> > >> >>>>
> > >> >>>>
> > >> >>>> --
> > >> >>>> Живи с улыбкой! :D
> > >> >>>>
> > >> >>
> > >> >>
> > >>
> > >>
> >
>

Reply via email to