Re: [VOTE] Release Apache Ignite 3.0.0-beta1 RC2
+1 >Среда, 16 ноября 2022, 12:15 +02:00 от Mirza Aliev : > >+1 > >ср, 16 нояб. 2022 г. в 12:51, Igor Sapego < isap...@apache.org >: > >> +1 (binding) >> >> Best Regards, >> Igor >> >> >> On Tue, Nov 15, 2022 at 11:10 PM Vladislav Pyatkov < vldpyat...@gmail.com > >> wrote: >> >> > +1 >> > >> > On Tue, Nov 15, 2022 at 3:35 PM Denis C < moongll...@gmail.com > wrote: >> > > >> > > +1 >> > > >> > > вт, 15 нояб. 2022 г. в 13:33, Alexander Lapin < lapin1...@gmail.com >: >> > > >> > > > +1 >> > > > >> > > > вт, 15 нояб. 2022 г. в 08:48, Pavel Tupitsyn < ptupit...@apache.org >: >> > > > >> > > > > +1 (binding) >> > > > > >> > > > > On Mon, Nov 14, 2022 at 9:05 PM Вячеслав Коптилин < >> > > > > slava.kopti...@gmail.com > >> > > > > wrote: >> > > > > >> > > > > > Dear Community, >> > > > > > >> > > > > > Ignite 3 is moving forward and I think we're in a good spot to >> > release >> > > > > the >> > > > > > first beta version. In the last few months the following major >> > features >> > > > > > have been added: >> > > > > > - RPM and DEB packages: simplified installation and node >> management >> > > > with >> > > > > > system services. >> > > > > > - Client's Partition Awareness: Clients are now aware of data >> > > > > distribution >> > > > > > over the cluster nodes which helps avoid additional network >> > > > transmissions >> > > > > > and lowers operations latency. >> > > > > > - C++ client: Basic C++ client, able to perform operations on >> > data. >> > > > > > - Autogenerated values: now a function can be specified as a >> > default >> > > > > value >> > > > > > generator during a table creation. Currently only gen_random_uuid >> > is >> > > > > > supported. >> > > > > > - SQL Transactions. >> > > > > > - Transactional Protocol: improved locking model, multi-version >> > based >> > > > > > lock-free read-only transactions. >> > > > > > - Storage: A number of improvements to memory-only and on-disk >> > engines >> > > > > > based on Page Memory. >> > > > > > - Indexes: Basic functionality, hash and sorted indexes. >> > > > > > - Client logging: A LoggerFactory may be provided during client >> > > > creation >> > > > > to >> > > > > > specify a custom logger for logs generated by the client. >> > > > > > - Metrics framework: Collection and export of cluster metrics. >> > > > > > >> > > > > > I propose to release 3.0.0-beta1 with the features listed above. >> > > > > > >> > > > > > Release Candidate: >> > > > > > https://dist.apache.org/repos/dist/dev/ignite/3.0.0-beta1-rc2/ >> > > > > > Maven Staging: >> > > > > > >> > > > >> > https://repository.apache.org/content/repositories/orgapacheignite-1556/ >> > > > > > Tag: https://github.com/apache/ignite-3/tree/3.0.0-beta1-rc2 >> > > > > > >> > > > > > +1 - accept Apache Ignite 3.0.0-beta1 RC2 >> > > > > > 0 - don't care either way >> > > > > > -1 - DO NOT accept Apache Ignite 3.0.0-beta1 RC2 (explain why) >> > > > > > >> > > > > > Voting guidelines: https://www.apache.org/foundation/voting.html >> > > > > > How to verify the release: >> > > > https://www.apache.org/info/verification.html >> > > > > > >> > > > > > The vote will be closed on Wednesday, 16 November 2022, 18:00:00 >> > (UTC >> > > > > time) >> > > > > > >> > > > > > >> > > > > >> > > > >> > >> >> https://www.timeanddate.com/countdown/generic?iso=20221116T18=1440=Apache+Ignite+3.0.0-beta1+RC2=cursive=1 >> > > > > > >> > > > > > Thanks, >> > > > > > S. >> > > > > > >> > > > > >> > > > >> > >> > >> > >> > -- >> > Vladislav Pyatkov >> > >> -- Igor Gusev
Re: [ANNOUNCE] SCOPE FREEZE for Apache Ignite 3.0.0 beta 1 RELEASE
Hi Igniters, I’d like to include some doc into beta1 if its not too late https://issues.apache.org/jira/browse/IGNITE-17948 This change should not affect beta functionality. >Пятница, 4 ноября 2022, 12:10 +02:00 от Юрий : > >Hi Igniters, > >I would like to add last one bugfix to the beta1: >https://issues.apache.org/jira/browse/IGNITE-18090 > >It will be ready in a few hours. > >чт, 3 нояб. 2022 г. в 19:28, Alexander Lapin < lapin1...@gmail.com >: > >> Hi Igniters, >> >> I would like to ask you to add one more bugfix to the beta1: >> https://issues.apache.org/jira/browse/IGNITE-18003 >> >> Best regards, >> Aleksandr >> >> вт, 1 нояб. 2022 г. в 17:17, Aleksandr Pakhomov < apk...@gmail.com >: >> >> > Hi Igniters, >> > >> > I would like to ask you to add two more tickets to the beta1: >> > >> > - https://issues.apache.org/jira/browse/IGNITE-18036 < >> > https://issues.apache.org/jira/browse/IGNITE-18036 > >> > - https://issues.apache.org/jira/browse/IGNITE-18025 < >> > https://issues.apache.org/jira/browse/IGNITE-18025 > >> > >> > Both of them now have PR's into the main. >> > >> > Best regards, >> > Aleksandr >> > >> > > On 15 Oct 2022, at 00:45, Andrey Gura < ag...@apache.org > wrote: >> > > >> > > 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 -- Igor Gusev
Re[2]: [ANNOUNCE] Apache Ignite 3.0.0 alpha 5: Code freeze
Please merge the remaining doc issue https://issues.apache.org/jira/browse/IGNITE-17106 >Среда, 8 июня 2022, 15:58 +04:00 от Andrey Gura : > >Thanks, Yuri! > >On Wed, Jun 8, 2022 at 1:48 PM Юрий < jury.gerzhedow...@gmail.com > wrote: >> >> Seems SQL API: Add batched DML queries support [1] will be moved to next >> alpha, so pleas don't waiting for it. >> >> In the same time SQL API: Examples [2] already done and merged to alpha 5 >> branch. >> >> [1] https://issues.apache.org/jira/browse/IGNITE-16963 >> [2] https://issues.apache.org/jira/browse/IGNITE-17088 >> >> пн, 6 июн. 2022 г. в 22:52, Andrey Gura < ag...@apache.org >: >> >> > Igniters, >> > >> > ignite-3.0.0-alpha5 release branch has been created. But the following >> > issues are still in progress: >> > >> > Data rebalancing >> > https://issues.apache.org/jira/browse/IGNITE-14209 >> > >> > SQL API: Add batched DML queries support. >> > https://issues.apache.org/jira/browse/IGNITE-16963 >> > >> > SQL API: Examples. >> > https://issues.apache.org/jira/browse/IGNITE-17088 >> > >> > Please, make sure these commits will be merged to the main and to the >> > release branch. >> > >> > Thanks! >> > >> > On Mon, Jun 6, 2022 at 6:02 PM Aleksandr Pakhomov < apk...@gmail.com > >> > wrote: >> > > >> > > Hi Andrey, >> > > >> > > As for CLI MVP, the planned timeline is today till 21:00. >> > > Probably, will be ready in an hour. Just waiting for CI build. >> > > >> > > Best regards, >> > > Aleksandr >> > > >> > > > On 6 Jun 2022, at 17:56, Andrey Gura < ag...@apache.org > wrote: >> > > > >> > > > Igniters, >> > > > >> > > > our release schedule has shifted a bit. But it is time for a code >> > > > freeze and a new branch creation. >> > > > >> > > > The following issues is still in progress (not an issues status, but >> > > > work state): >> > > > >> > > > Data rebalancing >> > > > https://issues.apache.org/jira/browse/IGNITE-14209 >> > > > >> > > > CLI MVP >> > > > https://issues.apache.org/jira/browse/IGNITE-16971 >> > > > >> > > > [Native Persistence 3.0] End-to-end test for persistent PageMemory >> > > > https://issues.apache.org/jira/browse/IGNITE-17107 >> > > > >> > > > SQL API: Implement query metadata >> > > > https://issues.apache.org/jira/browse/IGNITE-16962 >> > > > >> > > > SQL API: Add batched DML queries support. >> > > > https://issues.apache.org/jira/browse/IGNITE-16963 >> > > > >> > > > SQL API: Examples. >> > > > https://issues.apache.org/jira/browse/IGNITE-17088 >> > > > >> > > > Please, give some planned timelines for these issues. I would like to >> > > > create the ignite-3.0.0-alpha5 branch today and announce Code Freeze. >> > > > Otherwise, extra steps will be required to include the PR's to the >> > > > release branch. >> > > > >> > > > Thanks! >> > > >> > >> >> >> -- >> Живи с улыбкой! :D -- Igor Gusev
Re[2]: [ANNOUNCE] Apache Ignite 3.0.0 alpha 5: Code freeze
Please include these 2 issues into release: https://issues.apache.org/jira/browse/IGNITE-17127 https://issues.apache.org/jira/browse/IGNITE-17106 >Вторник, 7 июня 2022, 19:07 +04:00 от Andrey Gura : > >Aleksandr, > >okay, looks like a harmless change with documentation fixes. Targeted >to the release. Notify me when it will be ready for merge. > >On Tue, Jun 7, 2022 at 6:04 PM Aleksandr Pakhomov < apk...@gmail.com > wrote: >> >> Hi Andrey, >> >> Could you please include this ticket into release? >> https://issues.apache.org/jira/browse/IGNITE-17126 < >> https://issues.apache.org/jira/browse/IGNITE-17126 > >> >> Thanks >> >> > On 6 Jun 2022, at 17:56, Andrey Gura < ag...@apache.org > wrote: >> > >> > Igniters, >> > >> > our release schedule has shifted a bit. But it is time for a code >> > freeze and a new branch creation. >> > >> > The following issues is still in progress (not an issues status, but >> > work state): >> > >> > Data rebalancing >> > https://issues.apache.org/jira/browse/IGNITE-14209 >> > >> > CLI MVP >> > https://issues.apache.org/jira/browse/IGNITE-16971 >> > >> > [Native Persistence 3.0] End-to-end test for persistent PageMemory >> > https://issues.apache.org/jira/browse/IGNITE-17107 >> > >> > SQL API: Implement query metadata >> > https://issues.apache.org/jira/browse/IGNITE-16962 >> > >> > SQL API: Add batched DML queries support. >> > https://issues.apache.org/jira/browse/IGNITE-16963 >> > >> > SQL API: Examples. >> > https://issues.apache.org/jira/browse/IGNITE-17088 >> > >> > Please, give some planned timelines for these issues. I would like to >> > create the ignite-3.0.0-alpha5 branch today and announce Code Freeze. >> > Otherwise, extra steps will be required to include the PR's to the >> > release branch. >> > >> > Thanks! >> -- Igor Gusev
Re[2]: [ANNOUNCE] Apache Ignite 3.0.0 alpha 5: Code freeze
I fixed issues with the PRs mentioned earlier, so hopefully they can be merged. >Вторник, 7 июня 2022, 16:45 +04:00 от Andrey Gura : > >Great! Thanks, Slava! > >On Tue, Jun 7, 2022 at 2:50 PM Вячеслав Коптилин >< slava.kopti...@gmail.com > wrote: >> >> Hello Andrey, >> >> Data rebalancing (https://issues.apache.org/jira/browse/IGNITE-14209) is >> already done and merged to main & ignite-3.0.0-alpha5 branches. >> >> Thanks, >> S. >> >> >> пн, 6 июн. 2022 г. в 22:52, Andrey Gura < ag...@apache.org >: >> >> > Igniters, >> > >> > ignite-3.0.0-alpha5 release branch has been created. But the following >> > issues are still in progress: >> > >> > Data rebalancing >> > https://issues.apache.org/jira/browse/IGNITE-14209 >> > >> > SQL API: Add batched DML queries support. >> > https://issues.apache.org/jira/browse/IGNITE-16963 >> > >> > SQL API: Examples. >> > https://issues.apache.org/jira/browse/IGNITE-17088 >> > >> > Please, make sure these commits will be merged to the main and to the >> > release branch. >> > >> > Thanks! >> > >> > On Mon, Jun 6, 2022 at 6:02 PM Aleksandr Pakhomov < apk...@gmail.com > >> > wrote: >> > > >> > > Hi Andrey, >> > > >> > > As for CLI MVP, the planned timeline is today till 21:00. >> > > Probably, will be ready in an hour. Just waiting for CI build. >> > > >> > > Best regards, >> > > Aleksandr >> > > >> > > > On 6 Jun 2022, at 17:56, Andrey Gura < ag...@apache.org > wrote: >> > > > >> > > > Igniters, >> > > > >> > > > our release schedule has shifted a bit. But it is time for a code >> > > > freeze and a new branch creation. >> > > > >> > > > The following issues is still in progress (not an issues status, but >> > > > work state): >> > > > >> > > > Data rebalancing >> > > > https://issues.apache.org/jira/browse/IGNITE-14209 >> > > > >> > > > CLI MVP >> > > > https://issues.apache.org/jira/browse/IGNITE-16971 >> > > > >> > > > [Native Persistence 3.0] End-to-end test for persistent PageMemory >> > > > https://issues.apache.org/jira/browse/IGNITE-17107 >> > > > >> > > > SQL API: Implement query metadata >> > > > https://issues.apache.org/jira/browse/IGNITE-16962 >> > > > >> > > > SQL API: Add batched DML queries support. >> > > > https://issues.apache.org/jira/browse/IGNITE-16963 >> > > > >> > > > SQL API: Examples. >> > > > https://issues.apache.org/jira/browse/IGNITE-17088 >> > > > >> > > > Please, give some planned timelines for these issues. I would like to >> > > > create the ignite-3.0.0-alpha5 branch today and announce Code Freeze. >> > > > Otherwise, extra steps will be required to include the PR's to the >> > > > release branch. >> > > > >> > > > Thanks! >> > > >> > -- Igor Gusev
Re[2]: [ANNOUNCE] Apache Ignite 3.0.0 alpha 5: Code freeze
Hi, I did some PRs with docs for new features. Can you include them in release? https://github.com/apache/ignite-3/pull/850 https://github.com/apache/ignite-3/pull/856 https://github.com/apache/ignite-3/pull/857 >Вторник, 7 июня 2022, 0:09 +04:00 от Andrey Gura : > >And, of course, there is a code freeze for the release branch. So, >permission is required to make any changes to the release branch. >Don't hesitate to discuss such changes in this topic (except three >issues from the previous post). > >On Mon, Jun 6, 2022 at 10:52 PM Andrey Gura < ag...@apache.org > wrote: >> >> Igniters, >> >> ignite-3.0.0-alpha5 release branch has been created. But the following >> issues are still in progress: >> >> Data rebalancing >> https://issues.apache.org/jira/browse/IGNITE-14209 >> >> SQL API: Add batched DML queries support. >> https://issues.apache.org/jira/browse/IGNITE-16963 >> >> SQL API: Examples. >> https://issues.apache.org/jira/browse/IGNITE-17088 >> >> Please, make sure these commits will be merged to the main and to the >> release branch. >> >> Thanks! >> >> On Mon, Jun 6, 2022 at 6:02 PM Aleksandr Pakhomov < apk...@gmail.com > wrote: >> > >> > Hi Andrey, >> > >> > As for CLI MVP, the planned timeline is today till 21:00. >> > Probably, will be ready in an hour. Just waiting for CI build. >> > >> > Best regards, >> > Aleksandr >> > >> > > On 6 Jun 2022, at 17:56, Andrey Gura < ag...@apache.org > wrote: >> > > >> > > Igniters, >> > > >> > > our release schedule has shifted a bit. But it is time for a code >> > > freeze and a new branch creation. >> > > >> > > The following issues is still in progress (not an issues status, but >> > > work state): >> > > >> > > Data rebalancing >> > > https://issues.apache.org/jira/browse/IGNITE-14209 >> > > >> > > CLI MVP >> > > https://issues.apache.org/jira/browse/IGNITE-16971 >> > > >> > > [Native Persistence 3.0] End-to-end test for persistent PageMemory >> > > https://issues.apache.org/jira/browse/IGNITE-17107 >> > > >> > > SQL API: Implement query metadata >> > > https://issues.apache.org/jira/browse/IGNITE-16962 >> > > >> > > SQL API: Add batched DML queries support. >> > > https://issues.apache.org/jira/browse/IGNITE-16963 >> > > >> > > SQL API: Examples. >> > > https://issues.apache.org/jira/browse/IGNITE-17088 >> > > >> > > Please, give some planned timelines for these issues. I would like to >> > > create the ignite-3.0.0-alpha5 branch today and announce Code Freeze. >> > > Otherwise, extra steps will be required to include the PR's to the >> > > release branch. >> > > >> > > Thanks! >> > -- Igor Gusev
Apache Ignite 2.11
Hello all. I’d also join in on Nikita’s question n what docs are required for release. Currently we only have one doc issue for over 200 tickets resolved in the released, and it looks like we might be missing something. >Hello Igniters! > >I guess that AI 2.11 will include documentation work. >I'll be glad to help with this. >And I'll be happy to know the scope of features that we need to document. > >Regards, >Nikita >пт, 4 июн. 2021 г. в 03:50, 18624049226 < 18624049...@163.com >: >>hello, >> >>can someone can help to merge the following patch into master? >> >>https://issues.apache.org/jira/browse/IGNITE-12852 >> >>This patch has been completed for a long time, and I think it is a >>valuable one. >> >>在 2021/6/3 下午11:12, Dmitry Pavlov 写道: >>> Sure, thanks for your reply >>> >>> Folks, could you please advice how to setup JIRA account integration for >>> non-committers? >>> >>> For the page >>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.11 >>> I can see all issues, but Alexey's login seems to be not sufficient. Can >>> wiki admins set up smth? Or Alexey should do some setup on his own? >>> >>> On 2021/06/03 14:55:25, Maksim Timonin < timonin.ma...@gmail.com > wrote: I mean I'm OK to release it with 2.12. So, I am glad to hear there are chances for 2.11, but I guess we can postpone it. On Thu, Jun 3, 2021 at 5:39 PM Dmitry Pavlov < dpav...@apache.org > wrote: > ok, Maksim, keep us posted. > > We're in the middle of paperwork rigth now, so there is a chance )) > > On 2021/06/03 14:30:55, Maksim Timonin < timonin.ma...@gmail.com > wrote: >>> Regarding non-SQL index API it really depends on readiness. I guess if > it >> is not in the master, we can skip and release it next time. >> >> Hi, Dmitry! Yes, currently it is on review. I'm OK to release it within > the >> next release. >> >> On Thu, Jun 3, 2021 at 5:26 PM Dmitry Pavlov < dpav...@apache.org > >> wrote: >> >>> Hi Alexey, >>> >>> Releasing master as-is makes sence for me. >>> >>> Regarding non-SQL index API it really depends on readiness. I guess if > it >>> is not in the master, we can skip and release it next time. >>> >>> We've a bit overdue initial scope freeze date. It's not a big deal, but >>> still makes sense to start discussion, create and share wiki page and >>> create branch. >>> >>> Since committer privileges required to create branch, could you please >>> notify me in advance. >>> >>> Sincerely, >>> Dmitriy Pavlov >>> >>> On 2021/06/03 14:08:34, < >>> olive.c...@gmail.com > wrote: :scope: Here is a list [1] of 195 tickets, i picked for Apache Ignite 2.11 >>> release Let's start discussion [1] > > https://issues.apache.org/jira/browse/IGNITE-14781?jql=project%20%3D%20IGNITE%20%20AND%20status%20%20%3D%20Resolved%20and%20fixVersion%20%3D%202.11%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC On 2021/05/13 14:27:33, Dmitry Pavlov < dpav...@apache.org > wrote: > Hi Alexey, > > :pmc to sign distribution: > Formally, only PMC member can be a release manager, so part of >>> activities should be picked up by committer and PMC member. If noone > else >>> want to help you here, I would. > :timeline: > And, could you estimate all phases of the release. > > :scope: > I guess we can just pick up master current state and release it. > But >>> if someone has some ideas if we should wait for particular feature to > be >>> completed before branch divergence/release candidate build, please let > know. > Sincerely, > Dmitriy Pavlov > > On 2021/05/13 09:45:02, Алексей Гидаспов < olive.c...@gmail.com > >>> wrote: >> Dear Ignite Community! >> >> I suggest starting Apache Ignite 2.11 release activities. Also >>> suggest >> myself to be a release manager for this release. I plan release > at >>> the end >> of june 2021. >> >> ___ >> >> Best Regards, >> Alexey Gidaspov >> -- Igor Gusev
Joining in
Hi all! I am Igor Gusev, and I am an experienced technical writer. I am learning in-memory processing technologies and would be glad to contribute to the community. Please give me access to Apache Ignite Jira. My JIRA ID is igusev. Thanks in advance! Igor
