Folks,
I've previously mentioned that I'd like to include the [1] issue in
the release. Currently, the status is "Patch Available" and it's
actively reviewing now. I'd be happy if we wait a couple of days and
add this improvement to the release.
I've also created an issue [2] to remove the
+1
I think we should prepare the lists of todos/jira issues to automate
the release cycle.
On Wed, 27 Oct 2021 at 14:13, Ivan Daschinsky wrote:
>
> +0.5 from me
>
> 1. Checked signatures and sha512 sums -- both OK
> 2. Both source packages compiles and tests passed -- OK
> 3. Manually created
t; >
> >
> >> On 13 Oct 2021, at 16:02, Stephen Darlington
> >> wrote:
> >>
> >> Having extensions in Maven Central makes perfect sense for tools that need
> >> to be built and integrated with other code, Spring integrations for
> >&
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:
>
ackage?
> Right now, all the user need is Ignite distributive.
>
>
> > 13 окт. 2021 г., в 14:32, Maxim Muzafarov написал(а):
> >
> > Stephen,
> >
> > I guess the required classes of IP-finders should be in the classpath
> > (libs directory). Currently
> Stephen
>
> > On 13 Oct 2021, at 11:35, Nikita Amelchev wrote:
> >
> > +1 to migrate and include to the Ignite 2.12 scope
> >
> > пн, 20 сент. 2021 г. в 17:09, Denis Magda :
> >>
> >> Perfect, thanks, Maxim!
> >>
> >>
- 0 from me.
This is OK if the projects are different, but not OK if they are
sharing the same version history.
On Tue, 5 Oct 2021 at 13:39, Andrey Mashenkov
wrote:
>
> +1
>
> вт, 5 окт. 2021 г., 13:33 Юрий :
>
> > +1
> >
> > вт, 5 окт. 2021 г. в 02:52, Valentin Kulichenko <
> >
Hello Nikita,
+1 if you will lead this release.
I'd suggest including into the release scope this one issue too:
Snapshot restore must support restoring with indexes rebuild
https://issues.apache.org/jira/browse/IGNITE-14744
Hopefully, it will be completed by the end of October.
On Fri, 24
>
> A few questions:
>
>- Should "dev" be replaced with "2.11" on the picture of the cellular
>clusters deployment section?
>- Will the article be published on our blogs.apache.org page?
>
> -
> Denis
>
>
> On Sat, Sep 18, 2021
of the database:
https://ignite.apache.org/releases/2.11.0/release_notes.html
Download the latest Ignite version from here:
https://ignite.apache.org/download.cgi
Please let us know if you encounter any problems:
https://ignite.apache.org/community/resources.html#ask
Regards,
Maxim Muzafarov
Folks,
I've created an issue [1] to move all cloud-based IP-finders to the
ignite-extensions. The motivation is the same as with migration of
Spring Data integration - to remove integration dependency of the
release cycle on Ignite releases.
[1]
the comments are welcome.
[1]
https://github.com/Mmuzaf/mmuzaf.github.io/blob/main/_post/Release_Newsletter_211.md
On Thu, 16 Sept 2021 at 17:21, Maxim Muzafarov wrote:
>
> Hello, Igniters!
>
> Apache Ignite 2.11.0 release (RC2) has been accepted.
>
> 5 - "+1" votes
niters!
>
> Release pyignite-0.5.2-rc0 has been accepted
>
> The votes received:
> 3 "+1" binding votes
> 3 "+1" votes
>
> There is neither "+0" nor "-1"
>
> Here the votes received:
> - +1 Pavel Tupitsyn (binding)
> - +1 Nicko
Hello, Igniters!
Apache Ignite 2.11.0 release (RC2) has been accepted.
5 - "+1" votes received.
1 - "+0,5" vote received.
Here are the votes received:
- Pavel Tupitsyn (binding)
- Alex Plehanov (binding)
- Nikolay Izhikov (binding)
- Ilya Kasnacheev
- Ivan Daschinsky
- Zhenya Stanilovsky
Ivan,
Can you please clarify in detail what exactly should be fixed? I'm not
familiar with running something from Ignite under the Windows
environment. It's weird if something is not available on the official
site, however available on mirrors. It's not good but not a crime but
doesn't sound like
+1
Built from sources and run examples according to the documentation notes.
On Tue, 14 Sept 2021 at 12:59, Ivan Daschinsky wrote:
>
> Pavel, sometimes it is impossible to use gmail service directly from you
> laptop.
>
> вт, 14 сент. 2021 г. в 12:40, Pavel Tupitsyn :
>
> > > +1
> > >
;
> >> > > 1. 2.12 - deprecation of LOCAL caches.
> >> > > 2. 2.13 - complete removal LOCAL caches from codebase.
> >> > >
> >> > > > 13 сент. 2021 г., в 13:30, Ivan Daschinsky
> >> > > написал(а):
>
Folks,
> Maxim, should we fix it and rebuild RC?
I've cherry-picked the [1] issue to the release branch. This will not
require rebuilding the RC since the issue is related to the
documentation task.
[1] https://issues.apache.org/jira/browse/IGNITE-15503
On Tue, 14 Sept 2021 at 12:37, Pavel
Apache Ignite server and and and old client is requesting
> creation of LOCAL cache?
>
> вс, 12 сент. 2021 г. в 15:10, Maxim Muzafarov :
>
> > Folks,
> >
> > Let's get back to the discussion of obsolete LOCAL caches since a lot
> > of time has passed since the last di
Folks,
Let's get back to the discussion of obsolete LOCAL caches since a lot
of time has passed since the last discussion.
I've created an issue [1] for deprecation. Let's deprecate them at
least at the next 2.12 release.
WDYT?
[1] https://issues.apache.org/jira/browse/IGNITE-15499
On Fri, 27
Dear Community,
The release candidate for the 2.11 version is ready.
I have uploaded a release candidate to:
https://dist.apache.org/repos/dist/dev/ignite/2.11.0-rc2/
https://dist.apache.org/repos/dist/dev/ignite/packages_2.11.0-rc2/
The following staging can be used for testing:
+Ignite+2.11#ApacheIgnite2.11-Benchmarks[PRIMARY_SYNC,LOG_ONLY]
On Thu, 9 Sept 2021 at 21:27, Denis Magda wrote:
>
> Maxim,
>
> I'm good with your plan. Thanks for sharing the details. Let's follow the
> plan and release 2.11 asap.
>
> -
> Denis
>
> On Thu, Sep 9, 2021 at
+1
On Thu, 9 Sept 2021 at 14:08, Nikolay Izhikov wrote:
>
> +1 to release ASAP.
>
> > 9 сент. 2021 г., в 13:43, Ivan Daschinsky написал(а):
> >
> > TC build of release branch --
> > https://tc.sbt-ignite-dev.ru/buildConfiguration/IgniteThinClients_Tests_ThinClientPython/6130289
> >
> > чт, 9
sponsorship matter).
> >
> > Atri, can you please deploy a 2-node cluster in Azure on separate virtual
> > machines to validate that the IP finder works in this configuration? This
> > is a typical usage scenario for the IP finder - multiple node instances
> > span multiple VM
re
> availability. Ignite developers have been requesting the capability for a
> while and here it is. We're blocking it because of a missing automated test
> for a real environment. Who is going to develop those tests and, more
> importantly, sponsor Azure resources?
>
> -
> Denis
>
ated).
> >
> > I don't know, currently, I'm not able to verify the results of this
> > > execution.
> >
> >
> > The module was verified by Atri and Pavel. This looks enough. If you have
> > doubts, you can also double-check the code and work with Atri i
Sept 2021 at 21:18, Atri Sharma wrote:
>
> Maxim,
>
> I thought Pavel has already reported that the tests run fine with a
> valid Azure account?
>
> On Mon, Sep 6, 2021 at 11:10 PM Maxim Muzafarov wrote:
> >
> > Folks,
> >
> > Sorry for the rem
am not sure why is it can be tested by few members?
> > >
> > > Anyone with azure account should be able to test it
> > >
> > > On Fri, 3 Sep 2021, 19:29 Maxim Muzafarov, wrote:
> > >
> > >> Folks,
> > >>
> > >> The GC
, Maxim Muzafarov wrote:
>
> Folks,
>
> The GCP and AWS should also be moved to extensions, but this is a
> discussion for another topic.
>
> I trust you all :-)
> But who can validate the patch [1]? This is a bad practice that only a
> few members be able to tes
core.
> > >
> > > In terms of tests, the azure module has exactly the same type of tests as
> > > the other two modules mentioned above.
> > >
> > > On Fri, 3 Sep 2021, 17:54 Maxim Muzafarov, wrote:
> > >
> > > > Folks,
> > >
lov
>
> пт, 27 авг. 2021 г. в 16:41, Alexey Gidaspov :
>
> > Hi, Maxim!
> >
> > These issues really block release. So we should wait fixes.
> >
> > On 2021/08/27 12:46:24, Maxim Muzafarov wrote:
> > > Folks,
> > >
> > >
> >
it a sufficient reason to downvote release?
> >
> > Would you cast -1 for RC for that case?
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > On 2021/08/27 12:46:24, Maxim Muzafarov wrote:
> > > Folks,
> > >
> > >
> > > I've
://issues.apache.org/jira/browse/IGNITE-14725
[2] https://issues.apache.org/jira/browse/IGNITE-15388
On Mon, 9 Aug 2021 at 16:56, Maxim Muzafarov wrote:
>
> +1
>
> On Mon, 9 Aug 2021 at 16:27, Ivan Daschinsky wrote:
> >
> > I suppose, that https://issues.apache.org/
Folks,
I've created an issue to fix this. I think this is a blocker for the
2.11 release since there is no workaround here.
https://issues.apache.org/jira/browse/IGNITE-15388
On Fri, 27 Aug 2021 at 11:59, Maxim Muzafarov wrote:
>
> I've found the recommendation to bump up the version
ich seems has cached that artifact already.
> I think I can provide it as a file to republish to mvnrepository, but I have
> no such permissions.
>
> Who could help us with uploading it?
>
>
> > On 27 Aug 2021, at 11:23, Maxim Muzafarov wrote:
> >
> > Folks,
&g
Folks,
I've recently tried to build the Apache Ignite project from scratch
and got the following error:
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO]
...@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Hi, Igor!
> > > > > > >
> > > > > > > Now we are in stabilization phase and accepting only block
Ignite Community.
Best Regards,
Maxim Muzafarov
Folks,
The issues mentioned above were successfully resolved and
cherry-picked to the ignite-2.11 branch. Sorry for the delay. I think
we can proceed with the release.
On Thu, 22 Jul 2021 at 15:44, Maxim Muzafarov wrote:
>
> Folks,
>
> Yes, both the fixes [1] [2] will not require
ter side should update http://apache.org/dist/ignite/deb
> link to redirect correctly.
>
>
> Not sure though there is still a way to deliver new packages there.
>
>
>
> > On 23 Jul 2021, at 13:19, Maxim Muzafarov wrote:
> >
> > Folks,
> >
> > Artefacts
Folks,
Artefacts are available here. Is this what we are looking for?
https://apache.jfrog.io/artifactory/ignite-deb/
https://apache.jfrog.io/artifactory/ignite-rpm/
On Fri, 23 Jul 2021 at 12:15, Petr Ivanov wrote:
>
> No mirror.
>
> Also
from
> rc.-1 and run only functional tests for rc.0.
>
> On 2021/07/22 04:44:01, "Николай Ижиков" wrote:
> > +1 to fix both prior to release
> >
> > Отправлено с iPhone
> >
> > > 22 июля 2021 г., в 02:36, Maxim Muzafarov написал(а):
> > &
ted by the end of this week.
Please share your thoughts.
[1] https://issues.apache.org/jira/browse/IGNITE-15146
[2] https://issues.apache.org/jira/browse/IGNITE-15170
On Tue, 20 Jul 2021 at 15:08, Maxim Muzafarov wrote:
>
> Folks,
>
> Since the release branch was created some time ago, sh
Folks,
Since the release branch was created some time ago, should we bump up
the master branch version to the next one?
On Thu, 1 Jul 2021 at 17:15, Alexey Gidaspov wrote:
>
> Hi, Pavel.
>
> I think, it looks like blocker. Please cherry-pick it to 2.11 release branch
>
> On 2021/07/01 09:29:57,
+1 (binding)
On Fri, 2 Jul 2021 at 14:00, Nikolay Izhikov wrote:
>
> +1 (binding)
>
> > 1 июля 2021 г., в 08:35, Petrov Mikhail написал(а):
> >
> > +1
> >
> > Checked on Ubuntu 20.04. Created separate Spring Applications for each
> > version of Spring Data Integrations using the Maven RC
+1 (binding)
On Thu, 1 Jul 2021 at 13:23, Nikolay Izhikov wrote:
>
> +1 (binding)
>
> > 1 июля 2021 г., в 09:29, Petrov Mikhail написал(а):
> >
> > +1
> >
> > Checked on Ubuntu 20.04. Checked built-report and print-statistics scripts
> > for the custom Ignite application. Checked archive
Folks,
The CLI management machinery [1] for snapshots restore procedure
merged to the master branch.
Can we cherry-pick it to the release branch?
[1] https://issues.apache.org/jira/browse/IGNITE-14723
On Tue, 15 Jun 2021 at 12:51, Alexey Gidaspov wrote:
>
> Hi, Nikita!
>
> I think it's ok to
the patch.
[1]
https://github.com/apache/ignite/commit/e32691b9d9ef103aa884cf0d4f48abe9d98c8e50
On Fri, 14 May 2021 at 17:47, Maxim Muzafarov wrote:
>
> Folks,
>
> The JDBC Driver fails with the same error in the PR branch also [2].
> The most suspicious commit is related to the IGN
Folks,
The JDBC Driver fails with the same error in the PR branch also [2].
The most suspicious commit is related to the IGNITE-14575 issue. I've
left comment [2].
Can you re-check the patch?
[1]
Hello, Kirill
+1 for this change, however, there are too many configuration settings
that exist for the user to configure Ignite cluster. It is better to
keep the options that we already have and fix the behaviour of the
rebalance process as you suggested.
On Tue, 4 May 2021 at 19:01, ткаленко
Maxim Muzafarov created IGNITE-14572:
Summary: Include metastorage into snapshot
Key: IGNITE-14572
URL: https://issues.apache.org/jira/browse/IGNITE-14572
Project: Ignite
Issue Type
Folks,
I've briefly checked the total amount of the max length violations:
120 line length - 5540 violations
130 line length - 1891 violations
140 line length - 895 violations
150 line length - 478 violations
I think the 140 max line length might be the best option for us.
On Thu, 15 Apr 2021
+1 for new JIRA issues
-1 for MTCGA notifications
Why we should hide errors from the dev-list? Who should take care of
issues reported by MTCGA.Bot in this case?
We must apply stricter rules for such issues: a commit leading to an
error must be reverted.
On Wed, 14 Apr 2021 at 20:00, Denis
Maxim Muzafarov created IGNITE-14515:
Summary: Support MissingSwitchDefaultCheck checkstyle check
Key: IGNITE-14515
URL: https://issues.apache.org/jira/browse/IGNITE-14515
Project: Ignite
e end of the world but delays the upgrade to the new
> version.
>
> -
> Denis
>
>
> On Mon, Apr 5, 2021 at 6:32 AM Maxim Muzafarov wrote:
>
> > Denis,
> >
> > There is no spring data artifact for the 2.10 release. We should
> > prepare the release o
Denis,
There is no spring data artifact for the 2.10 release. We should
prepare the release of these extensions as fast as possible.
On Fri, 2 Apr 2021 at 20:06, Denis Magda wrote:
>
> Is this the first time we're releasing spring data 2.2 as an ext? Can't
> find any version available for 2.10?
Maxim Muzafarov created IGNITE-14462:
Summary: Enable EmptyCatchBlock checkstyle check
Key: IGNITE-14462
URL: https://issues.apache.org/jira/browse/IGNITE-14462
Project: Ignite
Issue
Hello Nikita,
+1 to follow your suggestion.
Please let me know if you need any help.
I also think the issues mentioned by you can be done in parallel and
they don't block the release :-)
On Thu, 25 Mar 2021 at 17:26, Nikita Amelchev wrote:
>
> Igniters,
>
> Since Ignite 2.10 has been released,
the core module +
cleaning up the mvcc API should be enough to move indexes to the core
module safe.
On Thu, 25 Mar 2021 at 16:14, Maxim Muzafarov wrote:
>
> Folks,
>
>
> I see no reason to postpone this patch. I think we can proceed with
> this patch with the commitment t
Folks,
I see no reason to postpone this patch. I think we can proceed with
this patch with the commitment to remove MVCC from the public API
until the next release (2.11). These changes for sure must be
well-documented but for the 2.10 release, we already have in the
release notes [1] warnings
Hello,
I think the issue definitely must be fixed, so +1 from my side.
BTW, what would be your implementation plan?
I think the [1] issue may be interesting for you.
[1] https://issues.apache.org/jira/browse/IGNITE-13056
On Tue, 23 Mar 2021 at 21:04, ткаленко кирилл wrote:
>
> Hello everyone!
Mikhail,
> Note, that the current PR breaks management of the users via REST because the
> SecurityContext is not propagated properly during REST requests execution.
Do we have a JIRA taks to fix this behaviour or do we need such
behaviour at all?
On Mon, 22 Mar 2021 at 13:34, Nikolay Izhikov
/resources.html#ask
Regards,
Maxim Muzafarov on behalf of the Apache Ignite community.
hnical editors who can suggest style and flow-related
> changes).
>
> -
> Denis
>
>
> On Wed, Mar 17, 2021 at 12:44 PM Maxim Muzafarov wrote:
>
> > Denis,
> >
> > I'm getting the following error while trying to create a new Weblog
> > > Sorry, the
s for the effort!
> > >>
> > >> I think this guide should be much shorter and simple.
> > >> Right now it is intimidating for newcomers.
> > >>
> > >> What they need is basically
> > >> * Register in Jira, pick a ticket, assign
t;
>
> On Wed, Mar 17, 2021 at 12:00 PM Maxim Muzafarov wrote:
>>
>> Denis,
>>
>>
>> I'd like to create a post on the blogs.apache.org news feed with the
>> 2.10 release news. Do I need additional privileges to do this?
>>
>> According to t
n.github.io/Whats-New-In-Ignite-Net-2.10/
>
> On Tue, Mar 16, 2021 at 5:15 PM Maxim Muzafarov wrote:
>
> > Denis,
> >
> >
> > Thank you. I'll prepare a blog post notes for the major 2.10 features.
> > The release hasn't been announced yet, some artefacts stil
oid such
> actions to keep users best interest. But it is not a commitment.
>
> Sincerely
>
>
> чт, 11 мар. 2021 г. в 23:11, Maxim Muzafarov :
>
> > Val,
> >
> >
> > I'm sorry if anything from what I've said sounded disrespectful. All
> > of you are examples for me to fo
gt;
>
> On Mon, Mar 15, 2021 at 8:55 PM Maxim Muzafarov wrote:
>
> > Folks,
> >
> > I've done almost all the release steps with publishing accepted changes.
> > What should I do with an announcement blog post for blogs.apache.org?
> > Should it also be pr
Folks,
I've done almost all the release steps with publishing accepted changes.
What should I do with an announcement blog post for blogs.apache.org?
Should it also be prepared prior to an announcement message?
On Thu, 11 Mar 2021 at 00:10, Maxim Muzafarov wrote:
>
> Pavel,
>
> Tha
Hello,
> Ignite employs both Review-Then-Commit processes.
The Commit-Then-Review (CTR) removed?
> Information for committers
Do we need this on a page for newcomers? I'd like to mention that some
of the committers still use the commit script, however, I think it
will be better to configure
- Zhenya Stanilovsky
- Atri Sharma
- Ilya Kasnacheev (binding)
- Denis Magda (binding)
- Maxim Muzafarov (binding)
Here is the link to the voting thread -
http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Release-Apache-Ignite-2-10-0-RC2-td51718.html
Thank you!
+1 (binding)
On Fri, 12 Mar 2021 at 01:51, Denis Magda wrote:
>
> +1 (binding)
>
> Downloaded the binary package and started a 2-node cluster with the
> ignite.sh script.
>
> -
> Denis
>
>
> On Wed, Mar 10, 2021 at 7:23 PM Maxim Muzafarov wrote:
>
> &g
Maxim Muzafarov created IGNITE-14309:
Summary: Document snapshot check command
Key: IGNITE-14309
URL: https://issues.apache.org/jira/browse/IGNITE-14309
Project: Ignite
Issue Type: Bug
> > Let's make a quick call next week and try to find a compromise which can
> > get the process moving:
> > https://www.meetup.com/Moscow-Apache-Ignite-Meetup/events/276851588/
> >
> > ср, 10 мар. 2021 г. в 16:27, Maxim Muzafarov :
> >
> >
Dear Community,
I have uploaded a release candidate to:
https://dist.apache.org/repos/dist/dev/ignite/2.10.0-rc2/
https://dist.apache.org/repos/dist/dev/ignite/packages_2.10.0-rc2/
The following staging can be used for testing:
Pavel,
Thank you! I'll prepare a new rc shortly.
On Wed, 10 Mar 2021 at 23:20, Pavel Tupitsyn wrote:
>
> Maxim, thanks!
> I've cherry-picked IGNITE-14293.
>
> On Wed, Mar 10, 2021 at 10:05 PM Maxim Muzafarov wrote:
>
> > Pavel,
> >
> > Sorry, my bad. E
l?
> If we keep it, let's cherry-pick 14250 as well?
>
> On Wed, Mar 10, 2021 at 8:21 PM Maxim Muzafarov wrote:
>
> > Pavel,
> >
> >
> > I think it is better and safe to cherry-pick the `IGNITE-14293 .NET:
> > AffinityKey does not work` only. I will be very happ
ately, the question is - do we want to include 13979 (.NET: Modernize
> examples),
> or not. Thoughts?
>
>
> On Wed, Mar 10, 2021 at 7:45 PM Maxim Muzafarov wrote:
>>
>> Pavel,
>>
>>
>> Can you assist a bit with the cherry-picking process
r 10, 2021 at 10:54 AM Ilya Kasnacheev
> wrote:
>
> > Hello!
> >
> > Unless we do extra checks for Windows environment, I suggest merging
> > IGNITE-14284 <https://issues.apache.org/jira/browse/IGNITE-14284>
> >
> > Regards,
> > --
> > Il
dev list.
>
> And finally, I agree with Denis. This whole situation is
> counter-productive. I'm happy to jump on a Discord or any other voice chat
> to discuss in more detail.
>
> [1]
> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Ignite-3-0-development-a
finish 3.0 looks too huge to me, actually it
> should be finished by the end of the year.
>
> вт, 9 мар. 2021 г. в 19:53, Maxim Muzafarov :
>
> > Pavel,
> >
> > > We have agreed on a direction for 3.0 [1], no need to change it.
> >
> > Thank you for sharing the
-14168 fix description of validate_indexes command (#8798)
https://issues.apache.org/jira/browse/IGNITE-14168
IGNITE-14138 Fixed an issue where historical rebalance can kill
supplier node. Fixes #8769
https://issues.apache.org/jira/browse/IGNITE-14138
On Mon, 1 Mar 2021 at 21:26, Maxim Muzafa
l? I'm working on it.
> https://issues.apache.org/jira/browse/IGNITE-14293
>
> On Mon, Mar 8, 2021 at 9:18 PM Maxim Muzafarov wrote:
>
> > Folks,
> >
> > The vote cancelled. The following issues need to be addressed:
> > https://issues.apache.org/jira/browse/IGNIT
ote:
>
> -1
>
> We have agreed on a direction for 3.0 [1], no need to change it.
>
> [1]
> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Ignite-3-0-development-approach-td49922.html
>
> On Tue, Mar 9, 2021 at 7:42 PM Maxim Muzafarov wrote:
>
> >
Pavel,
> 2) Much later, release what is being worked on in ignite-3 as Ignite 4.0 or
> 5.0
Yes, you're right.
On Tue, 9 Mar 2021 at 19:41, Maxim Muzafarov wrote:
>
> Ilya,
>
> > 0. I am accustomed with major.minor.maintenance schema. Does it mak
't see why there would be implicit PDS compatibility between any
> > X.0.0 and Y.0.0, X != Y.
> > 4. I think this is a sensible approach.
> > 5. Since ignite-3 seems to be a separate repo ATM, I don't see why it is
> > applicable.
> >
> > Regards,
> >
>
/github.com/apache/ignite-3
>
> On Sun, Mar 7, 2021 at 11:04 AM Nikolay Izhikov wrote:
>
> > Hello, Maxim.
> >
> > I’m +1 to follow your proposal.
> >
> > > 5 марта 2021 г., в 22:08, Maxim Muzafarov
> > написал(а):
> > >
> > > Ig
Folks,
The vote cancelled. The following issues need to be addressed:
https://issues.apache.org/jira/browse/IGNITE-14284
https://issues.apache.org/jira/browse/IGNITE-14285
Maxim Muzafarov created IGNITE-14286:
Summary: Fix snapshot check command for client nodes
Key: IGNITE-14286
URL: https://issues.apache.org/jira/browse/IGNITE-14286
Project: Ignite
Issue
Ignites,
I've created the IEP-69 [1] which describes the evolutionary release
process for the Apache Ignite 2.x version. You can find all the
details of my suggestion there, but here you can find the crucial
points:
0. Versioning - grand.major.bug-fix[-rc_number]
1. Prepare the next 3.0
be run as a single job, but in favor of flexibility in
> > configuration (enable / disable checks) it is OK to separate it in 2 steps.
> >
> > Do you have some objections to do it that way?
> >
> > On Wed, Mar 3, 2021 at 8:45 PM Maxim Muzafarov wrote:
> >
> &g
Dear Community,
The release candidate is ready. The rest of the documentation pages
will be completed prior to the release announcement message. Please,
see the links below.
I have uploaded a release candidate to:
https://dist.apache.org/repos/dist/dev/ignite/2.10.0-rc1/
Maxim,
Can you clarify what means '[Sanity Checks] runs in parallel with
[Build]'? AFAIK the checks need the build results to run themselves.
On Wed, 3 Mar 2021 at 18:48, Max Timonin wrote:
>
> Discussed with Petr privately. Proposal is:
>
> 1. The [Build] job runs without any checks.
> 2.
Maxim Muzafarov created IGNITE-14273:
Summary: ignite-extensions: Export data from snapshot to custom
format
Key: IGNITE-14273
URL: https://issues.apache.org/jira/browse/IGNITE-14273
Project
Maxim Muzafarov created IGNITE-14267:
Summary: Cluster snapshot must support encrypted caches
Key: IGNITE-14267
URL: https://issues.apache.org/jira/browse/IGNITE-14267
Project: Ignite
Maxim Muzafarov created IGNITE-14266:
Summary: System views for page statistics must include the bucktes
sizes
Key: IGNITE-14266
URL: https://issues.apache.org/jira/browse/IGNITE-14266
Project
picked:
> 0675e2a7e800730c9c8230332b82809754ddae5a
>
> Sorry for a delay.
>
> Best Regards,
> Igor
>
>
> On Mon, Mar 1, 2021 at 9:06 PM Igor Sapego wrote:
>>
>> Maxim,
>>
>> The issue is fixed and is merged to master now.
>>
>> Best Regards,
&g
Maxim Muzafarov created IGNITE-14261:
Summary: Add references to the new documentation metrics pages
from the legacy page
Key: IGNITE-14261
URL: https://issues.apache.org/jira/browse/IGNITE-14261
org/jira/browse/IGNITE-14206
>
> On Wed, Feb 24, 2021 at 5:47 PM Maxim Muzafarov wrote:
>
> > Anton,
> >
> > Your improvement is very important, for sure, but it's almost 2 months
> > have passed since the initiation of the release branch. I think we
> > should
101 - 200 of 757 matches
Mail list logo
