Re: [VOTE] Release Apache Ignite 3.0.0-alpha3 RC1
Val, Good point, let's upload nupkg files to SVN for both 2.x and 3.x RCs. On Thu, Oct 14, 2021 at 11:49 PM Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Pavel, > > Since it's possible to test packages locally as you described, we can > simply upload them to SVN [1] for RC testing. Let's start doing this with > the next release. > > I also assume this will be useful for both 2.x and 3.x, right? > > [1] https://dist.apache.org/repos/dist/dev/ignite > > -Val > > On Thu, Oct 14, 2021 at 12:15 PM Pavel Tupitsyn > wrote: > > > Igor, you can test the actual packages locally: > > - Download artifacts [1] into a local folder > > - dotnet add package Apache.Ignite --version 3.0.0-alpha3 --source > > /my/folder > > > > There is no concept of staging on nuget.org, any publish is permanent. > > We can probably publish a version with "-rc1" suffix for a release > > candidate, let's try this next time. > > > > [1] > > > > > https://ci.ignite.apache.org/buildConfiguration/ignite3_Release_Build_DotnetBinaries/6223120?buildTab=artifacts#%2Fnuget > > > > On Thu, Oct 14, 2021 at 8:06 PM Valentin Kulichenko < > > valentin.kuliche...@gmail.com> wrote: > > > > > Igor, > > > > > > As far as I understand, we can't upload the NuGet package anywhere, > which > > > is unfortunate. If you want to try the .NET client before the release, > > you > > > can build from sources. > > > > > > -Val > > > > > > On Thu, Oct 14, 2021 at 8:16 AM Igor Sapego > wrote: > > > > > > > Sorry, > > > > > > > > I meant we need to publish the package as part of RC, so it can be > > > > reviewed. > > > > > > > > Best Regards, > > > > Igor > > > > > > > > > > > > On Thu, Oct 14, 2021 at 11:34 AM Igor Sapego > > wrote: > > > > > > > > > Val, > > > > > > > > > > I think we need to upload the nuget package we want to upload so > the > > > > > community > > > > > would know what we are going to upload and can check that > everything > > is > > > > > right. > > > > > > > > > > WDYT? > > > > > > > > > > Best Regards, > > > > > Igor > > > > > > > > > > > > > > > On Wed, Oct 13, 2021 at 8:03 PM Valentin Kulichenko < > > > > > valentin.kuliche...@gmail.com> wrote: > > > > > > > > > >> Pavel, > > > > >> > > > > >> You've mentioned in the ticket that "Note that NuGet, > unfortunately, > > > has > > > > >> no > > > > >> concept of "staging" (unlike Maven). A package with the given > > version > > > > can > > > > >> be published only once, and it can't be undone. We can only > publish > > > the > > > > >> packages after the successful vote." > > > > >> > > > > >> With that, will you be okay if we proceed with the release, and > > upload > > > > the > > > > >> NuGet package after the vote is accepted? > > > > >> > > > > >> We can then have a separate discussion on the overall packaging > > > > approach. > > > > >> > > > > >> -Val > > > > >> > > > > >> On Wed, Oct 13, 2021 at 9:57 AM Valentin Kulichenko < > > > > >> valentin.kuliche...@gmail.com> wrote: > > > > >> > > > > >> > Hi Pavel, > > > > >> > > > > > >> > That's actually by design. The current packaging model assumes > > that > > > we > > > > >> use > > > > >> > Maven/NuGet to deliver binaries - both for servers side and > client > > > > >> side. In > > > > >> > case you have any objections to the overall approach, we surely > > can > > > > >> have a > > > > >> > discussion, but I propose we do this separately after the > release. > > > > >> > > > > > >> > However, it's great that you pointed this out as we indeed don't > > > have > > > > >> the > > > > >> > .NET package deployed. I've created a blocker ticket for this: > > > > >> > https://issues.apache.org/jira/browse/IGNITE-15741 > > > > >> > > > > > >> > Java client is deployed to Maven staging and examples are > > > > >> > fully-functional, so we are good on that part. > > > > >> > > > > > >> > -Val > > > > >> > > > > > >> > On Wed, Oct 13, 2021 at 9:11 AM Pavel Tupitsyn < > > > ptupit...@apache.org> > > > > >> > wrote: > > > > >> > > > > > >> >> To clarify, Java thin client has the following features: > > > > >> >> - Table API > > > > >> >> - Key-value API > > > > >> >> - JDBC driver > > > > >> >> > > > > >> >> .NET thin client: > > > > >> >> - Table API > > > > >> >> > > > > >> >> I think all of this should be included in the binary release. > > > > >> >> > > > > >> >> On Wed, Oct 13, 2021 at 10:10 AM Pavel Tupitsyn < > > > > ptupit...@apache.org> > > > > >> >> wrote: > > > > >> >> > > > > >> >> > -1 (binding) > > > > >> >> > > > > > >> >> > Java thin client and .NET thin client are missing from the > > binary > > > > >> >> package. > > > > >> >> > > > > > >> >> > > > > > >> >> > On Wed, Oct 13, 2021 at 3:03 AM Saikat Maitra < > > > > >> saikat.mai...@gmail.com> > > > > >> >> > wrote: > > > > >> >> > > > > > >> >> >> +1 (binding) > > > > >> >> >> > > > > >> >> >> Regards > > > > >> >> >> Saikat > > > > >> >> >> > > > > >> >> >> On Tue, Oct 12, 2021 at 5:03 PM Denis Magda < > > dma...@apache.org> > > > > >> wrote: > > > > >> >> >> > > > >
[DISCUSSION][IEP-80] Breaking changes in Ignite-2.x
Hello, Igniters. I’ve prepared IEP-80 [1] to track breaking changes that should be done in Ignite 2.x. We agreed on the following algorithm to deal with breaking changes: - Ignite 2.[x] - deprecate the API + notification of the users. - Ignite 2.[x+1] - API removal. I propose to start these improvements with the d&r (depuration & removal) of the following features: - LOCAL caches - MVCC caches - legacy service grid implementation - legacy JMX metrics beans. Deprecation in 2.12 Removal in 2.13 Please, share your opinion. [1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=191334475
Re: [DISCUSSION][IEP-80] Breaking changes in Ignite-2.x
+1 for deprecation in the 2.12 release пт, 15 окт. 2021 г. в 15:35, Nikolay Izhikov : > > Hello, Igniters. > > I’ve prepared IEP-80 [1] to track breaking changes that should be done in > Ignite 2.x. > > We agreed on the following algorithm to deal with breaking changes: > > - Ignite 2.[x] - deprecate the API + notification of the users. > - Ignite 2.[x+1] - API removal. > > > I propose to start these improvements with the d&r (depuration & removal) of > the following features: > > - LOCAL caches > - MVCC caches > - legacy service grid implementation > - legacy JMX metrics beans. > > Deprecation in 2.12 > Removal in 2.13 > > Please, share your opinion. > > [1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=191334475 -- Best wishes, Amelchev Nikita
Re: [DISCUSSION][IEP-80] Breaking changes in Ignite-2.x
+1 On Fri, Oct 15, 2021 at 3:41 PM Nikita Amelchev wrote: > +1 for deprecation in the 2.12 release > > пт, 15 окт. 2021 г. в 15:35, Nikolay Izhikov : > > > > Hello, Igniters. > > > > I’ve prepared IEP-80 [1] to track breaking changes that should be done > in Ignite 2.x. > > > > We agreed on the following algorithm to deal with breaking changes: > > > > - Ignite 2.[x] - deprecate the API + notification of the users. > > - Ignite 2.[x+1] - API removal. > > > > > > I propose to start these improvements with the d&r (depuration & > removal) of the following features: > > > > - LOCAL caches > > - MVCC caches > > - legacy service grid implementation > > - legacy JMX metrics beans. > > > > Deprecation in 2.12 > > Removal in 2.13 > > > > Please, share your opinion. > > > > [1] > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=191334475 > > > > -- > Best wishes, > Amelchev Nikita >
[ANNOUNCE] The 2.12 release branch creation
Hello, Igniters. I announce scope freeze for the Apache Ignite 2.12 release. I have created the ignite-2.12 branch for the release. Only critical issues can be added to the scope. Please, discuss with the community to add new issues. Code freeze is planned for Friday, October 29. All not-critical unresolved issues at the code freeze date will be moved to the next release. The wiki page with the release info: https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.12 -- Best wishes, Amelchev Nikita
Re: [DISCUSSION][IEP-80] Breaking changes in Ignite-2.x
Let's deprecate RebalanceDelay and RebalanceMode=NONE also. [1] https://issues.apache.org/jira/browse/IGNITE-12662 [2] https://issues.apache.org/jira/browse/IGNITE-14613 On Fri, 15 Oct 2021 at 15:46, Anton Vinogradov wrote: > > +1 > > On Fri, Oct 15, 2021 at 3:41 PM Nikita Amelchev > wrote: > > > +1 for deprecation in the 2.12 release > > > > пт, 15 окт. 2021 г. в 15:35, Nikolay Izhikov : > > > > > > Hello, Igniters. > > > > > > I’ve prepared IEP-80 [1] to track breaking changes that should be done > > in Ignite 2.x. > > > > > > We agreed on the following algorithm to deal with breaking changes: > > > > > > - Ignite 2.[x] - deprecate the API + notification of the users. > > > - Ignite 2.[x+1] - API removal. > > > > > > > > > I propose to start these improvements with the d&r (depuration & > > removal) of the following features: > > > > > > - LOCAL caches > > > - MVCC caches > > > - legacy service grid implementation > > > - legacy JMX metrics beans. > > > > > > Deprecation in 2.12 > > > Removal in 2.13 > > > > > > Please, share your opinion. > > > > > > [1] > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=191334475 > > > > > > > > -- > > Best wishes, > > Amelchev Nikita > >
Re: [DISCUSSION][IEP-80] Breaking changes in Ignite-2.x
THanks, Maksim. Tickets included in IEP scope and marked for d&r in 2.12-2.13 > 15 окт. 2021 г., в 16:03, Maxim Muzafarov написал(а): > > Let's deprecate RebalanceDelay and RebalanceMode=NONE also. > > [1] https://issues.apache.org/jira/browse/IGNITE-12662 > [2] https://issues.apache.org/jira/browse/IGNITE-14613 > > On Fri, 15 Oct 2021 at 15:46, Anton Vinogradov wrote: >> >> +1 >> >> On Fri, Oct 15, 2021 at 3:41 PM Nikita Amelchev >> wrote: >> >>> +1 for deprecation in the 2.12 release >>> >>> пт, 15 окт. 2021 г. в 15:35, Nikolay Izhikov : Hello, Igniters. I’ve prepared IEP-80 [1] to track breaking changes that should be done >>> in Ignite 2.x. We agreed on the following algorithm to deal with breaking changes: - Ignite 2.[x] - deprecate the API + notification of the users. - Ignite 2.[x+1] - API removal. I propose to start these improvements with the d&r (depuration & >>> removal) of the following features: - LOCAL caches - MVCC caches - legacy service grid implementation - legacy JMX metrics beans. Deprecation in 2.12 Removal in 2.13 Please, share your opinion. [1] >>> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=191334475 >>> >>> >>> >>> -- >>> Best wishes, >>> Amelchev Nikita >>>
