[Announce] New committer: Iurii Gerzhedovich

[Dmitriy Pavlov]

Dear Igniters,

The Project Management Committee (PMC) for Apache Ignite
has invited Iurii Gerzhedovich to become a committer and we are pleased
to announce that he has accepted.

Being a committer enables easier contribution to the
project since there is no need to go via the patch
submission process. This should enable better productivity.


Please join me in sincere congratulations to Iurii on his new role!
Iurii, keep the pace!


Sincerely,
Dmitriy Pavlov on behalf of Apache Ignite PMC

New Apache Ignite PMC member: Nikita Amelchev

[Dmitriy Pavlov]

Hello Igniters,

The Project Management Committee (PMC) for Apache Ignite
has invited Nikita Amelchev to become a member of PMC and we are pleased
to announce that he has accepted.

We appreciate his constant efforts in improving Apache Ignite code, as well
as efforts in preparing 2 major releases.

A PMC member helps manage and guide the direction of the project.

Congratulations on your new role! Keep the pace!

Best Regards
Dmitriy Pavlov
on behalf of Apache Ignite PMC

Re: Remove nightly builds for ignite-2.14

[Dmitriy Pavlov]

Hi Zhenya,

Thank you for noticing.

These builds are being triggered from the TC bot. I've asked Vitaly Osipov
to remove 2.14 and 2.15 builds.

Sincerely,
Dmitriy Pavlov

чт, 6 июл. 2023 г. в 09:27, Zhenya Stanilovsky :

>
> I found that nightly builds for 2.14 still active [1] can someone fix it ?
>
> [1]
> https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_RunAllNightly/7245960?hideProblemsFromDependencies=false=false+Inspection=true=true
>
>

Re: Apache Ignite 2.16 RELEASE [Time, Scope, Manager]

[Dmitriy Pavlov]

+1, fully support Nikita to be RM


пн, 23 окт. 2023 г. в 13:29, Pavel Tupitsyn :

> Sounds good, new JDK support seems to be in demand.
>
> On Mon, Oct 23, 2023 at 12:20 PM Anton Vinogradov  wrote:
>
> > +1
> >
> > On Sun, Oct 22, 2023 at 12:29 PM Nikita Amelchev 
> > wrote:
> >
> > > Dear Ignite Community!
> > >
> > > I suggest starting Apache Ignite 2.16 release activities.
> > >
> > > We've accumulated a hundred resolved [1] issues with new features and
> > > bug fixes which are waiting for their release date. For example:
> > >
> > > Calcite engine: added hints, became more stable, covered with
> diagnostic
> > > tools;
> > > Cluster Management API (IEP-81);
> > > Realtime CDC (IEP-104, ready to be merged);
> > > Fixes to support JDK 14-21;
> > > Several critical issues;
> > > etc.
> > >
> > > I want to propose myself to be the release manager of the planning
> > release.
> > >
> > > I propose the following timeline:
> > >
> > > Scope Freeze: November 6, 2023
> > > Code Freeze: November 13, 2022
> > > Voting Date: November 20, 2022
> > > Release Date: November 27, 2022
> > >
> > > WDYT?
> > >
> > > [1]
> > >
> >
> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.16%27))%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
> > >
> >
>

Re: [PROPOSAL] Move Ignite 2.x to JDK11 compilation

[Dmitriy Pavlov]

++1 for testing using JDK11

+0 for switching off support of JDK8 runtimes and class version (unless
compilation using JDK11 is done with -target=1.8 our users won't be able to
run Ignite using Java 8).

I suggest the following next steps: once tests are completely fine on
Teamcity using JDK 11, we start a separate thread named like:
"[VOTE] discontinuing JDK 8 since the 2.16 release"
to make the issue for end users more obvious. Since Nikita volunteers to be
a Release Manager, I suppose that 2.16 will be released quite soon.

I personally prefer to switch to newer Java. Using newer runtime helps us
to provide speed and scale, since JVM is developed all the time. But I
might be unaware of the risks, so let's discuss it later with the entire
dev community.

Sincerely,
Dmitriy Pavlov

ср, 30 авг. 2023 г. в 19:09, Ivan Daschinsky :

> +1, sounds reasonable for the open source project. IMHO, Eclipse Temurin
> JDK is a rule of thumb choice nowadays.
>
> ср, 30 авг. 2023 г. в 18:40, Peter Ivanov :
>
> > Hi, Igniters!
> >
> > As part of this proposal I would also like to discuss the JDK vendors we
> > are using on our CI platforms TeamCIty.
> > Historically, Ignite 2.x is being built under Oracle's edition - mostly
> > because of some features like JFR or similar.
> > However today we have pretty much solid alternative represented by
> OpenJDK
> > and its most popular build Eclipse Temurin, which provides every required
> > version for our needs (and especially LTS versions 1.8, 11 and 17) with
> all
> > necessary updates.
> >
> > So, I suggest we update our build agents for TeamCity accordingly,
> provide
> > OpenJDK framework for those 3 major versions and discontinue Oracle's
> > builds.
> > WDYT?
> >
> > пт, 25 авг. 2023 г. в 12:13, Ivan Daschinsky :
> >
> > > +1. It's time to do it at last.
> > >
> > > пт, 25 авг. 2023 г. в 12:06, Peter Ivanov :
> > >
> > > > Mostly, yes.
> > > >
> > > > In other words - proposal is about starting shipping Apache Ignite
> > > releases
> > > > with JDK11 compiled binaries thus dropping JDK8-10 runtime support.
> > > >
> > > > пт, 25 авг. 2023 г. в 12:03, Anton Vinogradov :
> > > >
> > > > > I looks like you're proposing not migration to 2.11 (because it is
> > > > already
> > > > > supported), but Java 8-9 support dropping.
> > > > >
> > > > > On Fri, Aug 25, 2023 at 11:54 AM Peter Ivanov 
> > > > wrote:
> > > > >
> > > > > > Hi, Igniters!
> > > > > >
> > > > > >
> > > > > > I would like to propose the next, if you don't mind me saying,
> > > > > > revolutionary step forward in our project: moving Ignite 2.x
> > > > compilation
> > > > > to
> > > > > > JDK11 minimum version.
> > > > > > I'd rather not make arguments, pros and cons other that currently
> > > exist
> > > > > in
> > > > > > Java world - you know them better than me. Let's just say that it
> > > seems
> > > > > > that time has come - consider at least that JDK11 as the LTS
> > version
> > > is
> > > > > > already about 4 and a half years on the go, and Ignite 3.x
> started
> > > from
> > > > > > JDK11 right away.
> > > > > >
> > > > > > This change may possibly require from us additional efforts on
> > > > supporting
> > > > > > the last version with JDK8 in terms of releasing additional
> patches
> > > and
> > > > > > hotfixes a bit longer than usual. However, this is up to the
> > > community
> > > > to
> > > > > > decide.
> > > > > >
> > > > > > Currently, Apache Ignite 2.x (with Extensions as well) is already
> > > > > prepared
> > > > > > for being compiled with JDK11 and almost all tests are passing.
> If
> > we
> > > > > come
> > > > > > to an agreement about this proposal and designate the next
> version
> > > that
> > > > > > will become the first to provide JDK11 compiled binaries - I am
> > ready
> > > > to
> > > > > > start the process of updating the TeamCity building project
> > > > accordingly.
> > > > > >
> > > > > >
> > > > > > Please, share your thoughts.
> > > > > >
> > > > >
> > > >
> > >
> > >
> > > --
> > > Sincerely yours, Ivan Daschinskiy
> > >
> >
>
>
> --
> Sincerely yours, Ivan Daschinskiy
>

Re: [VOTE] Release Apache Ignite 2.14.0 RC0

[Dmitriy Pavlov]

+1 Checked checksum, license,notice,
Tested that the TC bot is working using RC V2.14.0, Java Version: 1.8.0_171

чт, 6 окт. 2022 г. в 11:15, Ilya Kasnacheev :

> 0 (binding)
>
> If the main point of this release is Calcite, maybe we should make effort
> to demonstrate it is queryable without legacy ignite-indexing? But I'm not
> going to force this matter.
> --
> Ilya Kasnacheev
>
>
> пн, 3 окт. 2022 г. в 14:06, Maxim Muzafarov :
>
> > +1 (binding)
> >
> > On Mon, 3 Oct 2022 at 14:05, Ivan Daschinsky 
> wrote:
> > >
> > > +1 (binding)
> > >
> > > Checked C++ module and C++ examples compilation on windows 10 (msvc
> 2017)
> > > and ubuntu 22.04 (gcc 11.2.0).
> > > Checked ODBC on windows 10 and ubuntu 22.04 (unixodbc) by pyodbc and
> > python
> > > script (both H2 and CALCITE query engines).
> > > Checked ODBC pre-built binaries on windows 10
> > >
> > > Despite the fact that separation of H2 and CALCITE has been announced,
> H2
> > > (ignite-indexing) is still required for ODBC and CALCITE queries.
> > > Created issue for it --
> > https://issues.apache.org/jira/browse/IGNITE-17800
> > >
> > >
> > > пн, 3 окт. 2022 г. в 13:42, mwiesenberg :
> > >
> > > > +1
> > > > started a node with calcite, inserted data, ran a sql query.
> > > >
> > > > On Mon, Oct 3, 2022 at 2:46 AM Pavel Tupitsyn 
> > > > wrote:
> > > >
> > > > > +1
> > > > >
> > > > > Started .NET and Java nodes, checked examples, checked NuGet
> > packages.
> > > > >
> > > > > On Fri, Sep 30, 2022 at 4:07 PM Alex Plehanov <
> > plehanov.a...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > > Added new experimental, Apache Calcite based SQL engine
> > > > > > It was added in 2.13, in 2.14 it became ignite-indexing (and H2)
> > > > > > independent.
> > > > > >
> > > > > > +1
> > > > > >
> > > > > > Build from sources, start a cluster of two nodes, try some
> queries
> > on
> > > > > > Calcite SQL engine (with removed ignite-indexing module).
> > > > > >
> > > > > > пт, 30 сент. 2022 г. в 15:02, Zhenya Stanilovsky
> > > > > >  > > > > > >:
> > > > > >
> > > > > > >
> > > > > > >
> > > > > > > I think it`s important to mention that local caches are not
> > supported
> > > > > > > since this version [1].
> > > > > > >
> > > > > > > [1]  https://issues.apache.org/jira/browse/IGNITE-15759
> > > > > > >
> > > > > > >
> > > > > > > >Dear Community,
> > > > > > > >
> > > > > > > >The release candidate is ready.
> > > > > > > >
> > > > > > > >I have uploaded release candidate to
> > > > > > > >https://dist.apache.org/repos/dist/dev/ignite/2.14.0-rc0/
> > > > > > > >
> > https://dist.apache.org/repos/dist/dev/ignite/packages_2.14.0-rc0/
> > > > > > > >
> > > > > > > >The following staging can be used for testing:
> > > > > > > >
> > > > > >
> > > >
> > https://repository.apache.org/content/repositories/orgapacheignite-1552/
> > > > > > > >
> > > > > > > >Tag name is 2.14.0-rc0:
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> >
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=tag;h=refs/tags/2.14.0-rc0
> > > > > > > >
> > > > > > > >2.14.0 most important changes:
> > > > > > > >* Added new experimental, Apache Calcite based SQL engine
> > > > > > > >* Added support of IGNITE_TO_STRING_INCLUDE_SENSITIVE option
> by
> > > > > > > Сonsistency check command
> > > > > > > >* CPP Thin: Implemented asynchronous network events handling
> > > > > > > >* CPP thin: Implemented continuous queries
> > > > > > > >* Deprecated IgniteServices#service(String) and
> > > > > > > IgniteServices#services(String).
> > > > > > > >* Implemented CDC for in-memory caches
> > > > > > > >* Implemented NUMA aware allocator for Ignite durable memory
> > > > > > > >* Implemented Read Repair strategies
> > > > > > > >* Implemented array component type in binary object
> > > > > > > >* Removed the legacy service grid implementation
> > > > > > > >
> > > > > > > >RELEASE NOTES:
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> >
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=ignite-2.14
> > > > > > > >
> > > > > > > >Complete list of resolved issues:
> > > > > > > >https://issues.apache.org/jira/issues/?jql=(project%20%3D%20
> > > > > > >
> > > > > >
> > > > >
> > > >
> >
> 'Ignite'%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20('2.14'))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20('CLOSED'%2C%20'RESOLVED')%20AND%20resolution%20in(Fixed%2C%20Done%2C%20Implemented%2C%20Delivered)%20ORDER%20BY%20priority
> > > > > > > >
> > > > > > > >DEVNOTES
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> >
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=ignite-2.14
> > > > > > > >
> > > > > > > >The vote is formal, see voting guidelines
> > > > > > > https://www.apache.org/foundation/voting.html
> > > > > > > >
> > > > > > > >+1 - to accept Apache Ignite 2.14.0-rc0
> > > > > > > >0 - don't care either way
> > > > > > 

[ANNOUNCE] New PMC member: Ivan Daschinsky

[Dmitriy Pavlov]

Hi Igniters!

The Project Management Committee (PMC) for Apache Ignite has invited
Ivan Daschinsky to become a member of the PMC and we are pleased to
announce that he has accepted.

Ivan contributed the Ignite Python thin client. And he is still maintaining
it.
He is also actively supporting users.

Please join me in congratulating Ivan on his new role.

Best Regards,
Dmitriy Pavlov
on behalf of Apache Ignite PMC

Re: [ANNOUNCE] New PMC member: Vyacheslav Koptilin

[Dmitriy Pavlov]

Congrats, Slava! Keep the pace!

пт, 19 авг. 2022 г. в 12:45, Petr Ivanov :

> Congrats!
> Well deserved!
>
> > On 17 Aug 2022, at 17:34, Kseniya Romanova 
> wrote:
> >
> > Hi Igniters!
> >
> > The Project Management Committee (PMC) for Apache Ignite has invited
> > Vyacheslav Koptilin to become a member of the PMC and we are pleased to
> > announce that he has accepted.
> >
> > Vyacheslav is a veteran committer and contributes a lot to the Ignite
> > storage https://github.com/sk0x50.
> >
> > Please join me in congratulating Vyacheslav on his new role.
> >
> > Best Regards,
> > Kseniya Romanova
> > on behalf of Apache Ignite PMC
>
>

[ANNOUNCE] New PMC member: Taras Ledkov

[Dmitriy Pavlov]

Hi Igniters!

The Project Management Committee (PMC) for Apache Ignite has invited
Taras Ledkov to become a member of the PMC and we are pleased to
announce that he has accepted.

Taras is a veteran committer, and it is needless to say how long
and successfully he is contributing to the Apache Ignite.
Taras is responsible for a solid bulk of SQL and JDBC code.

Please join me in congratulating Taras on his new role.

Best Regards,
Dmitriy Pavlov
on behalf of Apache Ignite PMC

Re: Apache Ignite 2.14 RELEASE [Time, Scope, Manager]

[Dmitriy Pavlov]

+1 from my side. Count on my support if somethings need to be done from PMC

This link works for me (without pre-selected issue in URL JIRA displays
more predictable results):
https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.14%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority

and one more filter with open issues
https://issues.apache.org/jira/issues/?jql=(project%20%3D%20'Ignite'%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20('2.14'))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20not%20in%20('CLOSED'%2C%20'RESOLVED')%20ORDER%20BY%20priority
There are only 40, for now.




пн, 8 авг. 2022 г. в 16:01, Taras Ledkov :

> Dear Ignite Community!
>
> I suggest starting Apache Ignite 2.14 release activities.
>
> We've accumulated a hundred resolved [1] issues with new
> features and bug fixes which are waiting for their release date. For
> example,
> - bunch of Calcite based SQL engine fixes and improvements;
> - thin clients improvements;
> - fixes at the core: update counters, binary meta, etc.
>
> I want to propose myself to be the release manager of the planning release.
>
> I propose the following timeline:
>
> Scope Freeze: August 17, 2022
> Code Freeze: August 24, 2022
> Voting Date: September 7, 2022
> Release Date: September 14, 2022
>
> [1].
> https://issues.apache.org/jira/browse/IGNITE-16958?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.14%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority
>
> --
> With best regards,
> Taras Ledkov
>

Re: 0-day CVE in log4j

[Dmitriy Pavlov]

Hi Igniters,

Preliminary: change of the log4j version does not affect any tests
(Alexander Nikolaev, correct me if I'm wrong).

If you're using embedded Ignite, it's perfectly possible to enforce jog4j2
dependency to be 2.15.0 in your project final pom.xml or build.gradle or
any other build system properties.

https://issues.apache.org/jira/browse/IGNITE-16101 ticket seems to be
a blocker for 2.12. But for now, as a workaround, it's possible to select
the latest version manually.

Sincerely,
Dmitriy Pavlov

сб, 11 дек. 2021 г. в 09:47, Nikita Amelchev :

> Hello.
>
> The issue to update dependency was created:
> https://issues.apache.org/jira/browse/IGNITE-16101
>
> I want to include it to the 2.12 scope.
>
> сб, 11 дек. 2021 г., 09:19 Raymond Wilson :
>
> > All
> >
> > This blew up today: CVE-2021-44228 (
> >
> >
> https://www.bleepingcomputer.com/news/security/new-zero-day-exploit-for-log4j-java-library-is-an-enterprise-nightmare/
> > )
> >
> > Will there be a risk assessment with respect to Ignite for this CVE?
> >
> > Thanks,
> > Raymond.
> >
> > --
> > <http://www.trimble.com/>
> > Raymond Wilson
> > Trimble Distinguished Engineer, Civil Construction Software (CCS)
> > 11 Birmingham Drive | Christchurch, New Zealand
> > raymond_wil...@trimble.com
> >
> > <
> >
> https://worksos.trimble.com/?utm_source=Trimble_medium=emailsign_campaign=Launch
> > >
> >
>

Re: [ANNOUNCE] Welcome Maxim Timonin as a new committer

[Dmitriy Pavlov]

My sincere congrats, Maxim!

пн, 29 нояб. 2021 г., 21:32 Nikita Amelchev :

> Hi Maxim,
>
> My congratulations!
>
> пн, 29 нояб. 2021 г. в 19:57, Zhenya Stanilovsky
> :
> >
> >
> >
> > Big deal, congrats Maxim !
> >
> >
> > >Igniters,
> > >
> > >The Project Management Committee (PMC) for Apache Ignite has invited
> Maxim
> > >Timonin to become a committer and we are pleased to announce that he has
> > >accepted.
> > >
> > >Maxim makes valuable contributions to the Apache Ignite code, helps
> > >actively to applications developers on the user list, and made a good
> start
> > >in Project awareness contributing by presenting at Ignite Summit: Cloud
> > >Edition.
> > >
> > >Being a committer enables easier contribution to the project since
> there is
> > >no need to go via the patch submission process. This should enable
> better
> > >productivity.
> > >
> > >Please join me in welcoming Maxim, and congratulating him on the new
> role
> > >in the Apache Ignite Community!
> > >
> > >Kseniya Romanova
> > >on behalf of Apache Ignite PMC
> >
> >
> >
> >
>
>
>
> --
> Best wishes,
> Amelchev Nikita
>

Re: ASF Board report, Nov 2021

[Dmitriy Pavlov]

Thank you Denis and Kseniya, report has been filed to the Board agenda
https://cwiki.apache.org/confluence/display/IGNITE/ASF+Board+Report+Drafts#ASFBoardReportDrafts-Nov2021

Sincerely,
Dmitriy Pavlov

вт, 2 нояб. 2021 г. в 18:59, Kseniya Romanova :

> Denis and Pavel, probably we also need to mention 3 virtual meetups in July
> [1], [2], and September [3]. Also, we gathered at one offline meetup in
> September in Moscow [4]
>
>
> [1] https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/279417063/
> [2] https://www.meetup.com/Moscow-Apache-Ignite-Meetup/events/279466477/
> [3] https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/280030600/
> [4] https://www.meetup.com/Moscow-Apache-Ignite-Meetup/events/280030657/
>
> вт, 2 нояб. 2021 г. в 18:47, Denis Magda :
>
> > Hi Dmitry, thanks for sharing the draft,
> >
> > I would also add that the community is hosting the next Ignite Summit in
> > November: https://ignite-summit.org
> >
> > @Kseniya Romanova , anything else?
> >
> > -
> > Denis
> >
> >
> > On Tue, Nov 2, 2021 at 11:01 AM Dmitriy Pavlov 
> wrote:
> >
> >> Hi Folks,
> >>
> >> It's time to submit next quarter's report to the board.
> >>
> >> I've prepared a draft at
> >>
> >>
> https://cwiki.apache.org/confluence/display/IGNITE/ASF+Board+Report+Drafts#ASFBoardReportDrafts-Nov2021
> >>
> >> Feel free to suggest any changes, significant activities, and/or
> released
> >> features to be added to Community and Project sections.
> >>
> >> I would finalize the report on 08 Nov. Before that time I'll have
> >> limited access to the Internet.
> >>
> >> Sincerely,
> >> Dmitriy Pavlov
> >>
> >
>

ASF Board report, Nov 2021

[Dmitriy Pavlov]

Hi Folks,

It's time to submit next quarter's report to the board.

I've prepared a draft at
https://cwiki.apache.org/confluence/display/IGNITE/ASF+Board+Report+Drafts#ASFBoardReportDrafts-Nov2021

Feel free to suggest any changes, significant activities, and/or released
features to be added to Community and Project sections.

I would finalize the report on 08 Nov. Before that time I'll have
limited access to the Internet.

Sincerely,
Dmitriy Pavlov

Re: [VOTE] Create separate Jira project and Confluence space for Ignite 3

[Dmitriy Pavlov]

-0 from my side.

That's fine if we have a separate project.
But since the mission and the statement of community is the same, I tend to
see 2&3 as the same project. The only difference is that 3 was started
from scratch (from the code point of view).

ср, 6 окт. 2021 г. в 00:23, Maxim Muzafarov :

> - 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 <
> > > valentin.kuliche...@gmail.com>:
> > >
> > > > Hello Community,
> > > >
> > > > As discussed in [1], I would like to propose the creation of a
> separate
> > > > Jira project and Confluence space for Ignite 3.
> > > >
> > > > Ignite 2 and Ignite 3 are developed in parallel in separate repos,
> so we
> > > > need a clear separation in other tools as well - this will help to
> > > > streamline the development process. Please refer to the discussion
> for
> > > more
> > > > details.
> > > >
> > > > [1]
> > > >
> > > >
> > >
> https://lists.apache.org/thread.html/rdcad3fc64b9f3a848c93089baae2bee1124a97869a94f4a04dd80fdf%40%3Cdev.ignite.apache.org%3E
> > > >
> > > > Voting options:
> > > >
> > > >- +1 - Agree with the suggestion
> > > >- 0 - Don't care much about the suggestion
> > > >- -1 - Disagree with the suggestion
> > > >
> > > > This is a majority vote.
> > > >
> > > > Voting ends in 72 hours, at 5pm PDT on October 7:
> > > >
> > > >
> > >
> https://www.timeanddate.com/counters/fullscreen.html?mode=a=20211007T17=2021=10=7=17=0=0=224
> > > >
> > > > -Val
> > > >
> > >
> > >
> > > --
> > > Живи с улыбкой! :D
> > >
>

Re: [Announcement] Apache Ignite 2.11 Code Freeze started

[Dmitriy Pavlov]

We had a separate discussion with Max and Alex, so I tend to agree that
both issues are blockers.

Sincerely,
Dmitriy Pavlov

пт, 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,
> >
> >
> > I've been faced these issues, which seems to be a blocker for the
> > release. Please, take a look and share your thoughts.
> >
> > The server node fails when the client node with the higher java
> > version connects to it [1].
> > The Apache Ignite build fails with missing dependency [2].
> >
> >
> > [1] https://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/jira/browse/IGNITE-15274
> is a
> > > > blocker.
> > > > Fix is quite easy and straightforward
> > > >
> > > > пн, 2 авг. 2021 г. в 03:11, Igor Sapego :
> > > >
> > > > > Cherry-picked to release branch.
> > > > >
> > > > > Best Regards,
> > > > > Igor
> > > > >
> > > > >
> > > > > On Fri, Jul 30, 2021 at 3:11 PM Alexey Gidaspov <
> olive.c...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Ok, I think we should add [1] to 2.11 release. Can you
> cherry-pick it to
> > > > > > release branch?
> > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14815
> > > > > >
> > > > > > On 2021/07/30 02:25:25, Igor Sapego  wrote:
> > > > > > > I'm fine with any of these two solutions.
> > > > > > >
> > > > > > > Best Regards,
> > > > > > > Igor
> > > > > > >
> > > > > > >
> > > > > > > On Thu, Jul 29, 2021 at 6:36 PM Ilya Kasnacheev <
> > > > > > ilya.kasnach...@gmail.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Hello!
> > > > > > > >
> > > > > > > > I think it does make sense to include changes which will let
> us avoid
> > > > > > > > migration issues in the future.
> > > > > > > >
> > > > > > > > Alternatively, maybe we can revert the incomplete change
> from 2.11 in
> > > > > > order
> > > > > > > > to reintroduce it in 2.12 in full form if Igor agrees and RE
> thinks
> > > > > > this is
> > > > > > > > the best course of action.
> > > > > > > >
> > > > > > > > Regards,
> > > > > > > > --
> > > > > > > > Ilya Kasnacheev
> > > > > > > >
> > > > > > > >
> > > > > > > > чт, 29 июл. 2021 г. в 18:07, Igor Sapego  >:
> > > > > > > >
> > > > > > > > > Alexey,
> > > > > > > > >
> > > > > > > > > It contains changes we could not introduce if we release
> ignite in
> > > > > > its
> > > > > > > > > current state as they are going to be breaking changes.
> > > > > > > > >
> > > > > > > > > Best Regards,
> > > > > > > > > Igor
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Thu, Jul 29, 2021 at 4:13 PM Alexey Gidaspov <
> > > > > > olive.c...@gmail.com>
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Hi, Igor!
> > > > > > > > > >
> > > > > > > > > > Now we are in stabilization phase and accepting only
> blockers. I
> > > > > > may be
> > > > > > > > > > wrong, but this ticket doesn't seem to be of that kind.
> > > > > > > > > >
> > > > > > > > > > On 2021/07/28 21:00:15, Igor Sapego 
> wrote:
> &

Re: [Announcement] Apache Ignite 2.11 Code Freeze started

[Dmitriy Pavlov]

What is the impact of missing artifact on our users?

The higher java version client was never supported so I'm not really sure
we should block 2.11 because of that

пт, 27 авг. 2021 г. в 15:51, Dmitry Pavlov :

> Мах, the vote is about to come.
>
> So is 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 been faced these issues, which seems to be a blocker for the
> > release. Please, take a look and share your thoughts.
> >
> > The server node fails when the client node with the higher java
> > version connects to it [1].
> > The Apache Ignite build fails with missing dependency [2].
> >
> >
> > [1] https://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/jira/browse/IGNITE-15274
> is a
> > > > blocker.
> > > > Fix is quite easy and straightforward
> > > >
> > > > пн, 2 авг. 2021 г. в 03:11, Igor Sapego :
> > > >
> > > > > Cherry-picked to release branch.
> > > > >
> > > > > Best Regards,
> > > > > Igor
> > > > >
> > > > >
> > > > > On Fri, Jul 30, 2021 at 3:11 PM Alexey Gidaspov <
> olive.c...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Ok, I think we should add [1] to 2.11 release. Can you
> cherry-pick it to
> > > > > > release branch?
> > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14815
> > > > > >
> > > > > > On 2021/07/30 02:25:25, Igor Sapego  wrote:
> > > > > > > I'm fine with any of these two solutions.
> > > > > > >
> > > > > > > Best Regards,
> > > > > > > Igor
> > > > > > >
> > > > > > >
> > > > > > > On Thu, Jul 29, 2021 at 6:36 PM Ilya Kasnacheev <
> > > > > > ilya.kasnach...@gmail.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Hello!
> > > > > > > >
> > > > > > > > I think it does make sense to include changes which will let
> us avoid
> > > > > > > > migration issues in the future.
> > > > > > > >
> > > > > > > > Alternatively, maybe we can revert the incomplete change
> from 2.11 in
> > > > > > order
> > > > > > > > to reintroduce it in 2.12 in full form if Igor agrees and RE
> thinks
> > > > > > this is
> > > > > > > > the best course of action.
> > > > > > > >
> > > > > > > > Regards,
> > > > > > > > --
> > > > > > > > Ilya Kasnacheev
> > > > > > > >
> > > > > > > >
> > > > > > > > чт, 29 июл. 2021 г. в 18:07, Igor Sapego  >:
> > > > > > > >
> > > > > > > > > Alexey,
> > > > > > > > >
> > > > > > > > > It contains changes we could not introduce if we release
> ignite in
> > > > > > its
> > > > > > > > > current state as they are going to be breaking changes.
> > > > > > > > >
> > > > > > > > > Best Regards,
> > > > > > > > > Igor
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Thu, Jul 29, 2021 at 4:13 PM Alexey Gidaspov <
> > > > > > olive.c...@gmail.com>
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Hi, Igor!
> > > > > > > > > >
> > > > > > > > > > Now we are in stabilization phase and accepting only
> blockers. I
> > > > > > may be
> > > > > > > > > > wrong, but this ticket doesn't seem to be of that kind.
> > >

Re: Empty test results for Security Test Suite ran against master branch on Team City

[Dmitriy Pavlov]

Up!

Folks, who is owner/expert for this suite?

We have a number of tests not running.

чт, 22 апр. 2021 г., 18:01 Dmitry Pavlov :

> Hi,
>
> I guess it 's not correct since master tests count is 0. No reason to run
> a suite without tests.
>
> Folks, why it could be the case? I've checked SUITE_NAME and suite in the
> code and it seems to be mached.
>
> Sincerely,
> Dmitriy Pavlov
>
> On 2021/04/22 14:29:37, Shishkov Ilya  wrote:
> > Hello, Igniters!
> >
> > As I see, there are no test results for Security Test Suite run against
> > 'master' branch [1], for 'ignite-2.10' Security tests results are present
> > as expected [2].
> > Is this situation correct?
> >
> > 1.
> >
> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Security/5977426?buildTab=log=1878=1579
> > 2.
> >
> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Security/5976111?buildTab=log=67783=1599.68439.68448
> >
>

Re: Stop sending IGNITE Created e-mails to dev@

[Dmitriy Pavlov]

I guess so. It was always not clear for me why do we have 'contributors 1'
role.

It might worth to rename role itself to contibutors with notifications.

Sincerely,
Dmitriy Pavlov

пн, 26 апр. 2021 г., 13:01 Ivan Pavlukhin :

> Hi Ilya,
>
> > I have added you to "Contributors 1" role. Everybody in this role will
> still get those "issue created" e-mail.
>
> Thank you for that!
>
> Should not we mention this tweak with "Contributors 1" role somewhere
> in advanced how-to-contribute page?
>
> 2021-04-26 12:28 GMT+03:00, Ilya Kasnacheev :
> > Hello!
> >
> > I have added you to "Contributors 1" role. Everybody in this role will
> > still get those "issue created" e-mail.
> >
> > Feel free in asking me to enlist.
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
> > чт, 22 апр. 2021 г. в 18:16, Ivan Pavlukhin :
> >
> >> > All issues notifications are also sent to iss...@ignite.apache.org so
> >> one can subscribe to this list in order to track the created tickets.
> >>
> >> Does not sound as useful advice. Issues list [1] looks like real
> >> scrapyard, I doubt that it can be usable for anyone in current flavor.
> >> Can we send only "Created" notifications there?
> >>
> >> [1] https://lists.apache.org/list.html?iss...@ignite.apache.org
> >>
> >> 2021-04-21 18:30 GMT+03:00, Ilya Kasnacheev  >:
> >> > Hello!
> >> >
> >> > INFRA ticket created:
> https://issues.apache.org/jira/browse/INFRA-21762
> >> >
> >> > I have asked to keep sending the created issue notifications for
> >> > "Contributors 1" role, which is empty at present. So if you wish to
> >> > keep
> >> > getting those e-mails, please add yourself to this role or tell me to
> >> > do
> >> so
> >> > for you.
> >> >
> >> > Regards,
> >> > --
> >> > Ilya Kasnacheev
> >> >
> >> >
> >> > ср, 21 апр. 2021 г. в 17:59, Alexey Goncharuk <
> >> alexey.goncha...@gmail.com>:
> >> >
> >> >> I support the idea. All issues notifications are also sent to
> >> >> iss...@ignite.apache.org so one can subscribe to this list in order
> to
> >> >> track the created tickets. The notifications trash the devlist
> archive
> >> UI
> >> >> and make it extremely difficult to navigate.
> >> >>
> >> >> вт, 20 апр. 2021 г. в 18:35, Ilya Kasnacheev
> >> >>  >> >:
> >> >>
> >> >> > Hello, Maxim!
> >> >> >
> >> >> > You are free to revert any commit which has led to any new stable
> >> >> > test
> >> >> > failure, or new flaky test that was non-flaky before.
> >> >> >
> >> >> > Just revert the change and reopen the ticket.
> >> >> >
> >> >> > The problem here is that it's very hard to detect on the spot, most
> >> >> > of
> >> >> > MTCGA e-mails are false positives and even if they are not, it is
> >> >> > not
> >> >> > relevant for most of developers.
> >> >> >
> >> >> > WDYT? I'm also still waiting for more input.
> >> >> >
> >> >> > Regards,
> >> >> > --
> >> >> > Ilya Kasnacheev
> >> >> >
> >> >> >
> >> >> > ср, 14 апр. 2021 г. в 21:26, Maxim Muzafarov :
> >> >> >
> >> >> > > +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 Mekhanikov
> >> >> > > 
> >> >> > > wrote:
> >> >> > > >
> >> >> > > > Huge +1 to this.
> >> >> > > >
> >> >> > > > I've already brought up this topic in the 

Re: Stop sending IGNITE Created e-mails to dev@

[Dmitriy Pavlov]

+1 for issues
-1 for TC bot. For the latter I siggest improving analysis to avoid odd
emails and leave only relevant

чт, 22 апр. 2021 г., 18:16 Ivan Pavlukhin :

> > All issues notifications are also sent to iss...@ignite.apache.org so
> one can subscribe to this list in order to track the created tickets.
>
> Does not sound as useful advice. Issues list [1] looks like real
> scrapyard, I doubt that it can be usable for anyone in current flavor.
> Can we send only "Created" notifications there?
>
> [1] https://lists.apache.org/list.html?iss...@ignite.apache.org
>
> 2021-04-21 18:30 GMT+03:00, Ilya Kasnacheev :
> > Hello!
> >
> > INFRA ticket created: https://issues.apache.org/jira/browse/INFRA-21762
> >
> > I have asked to keep sending the created issue notifications for
> > "Contributors 1" role, which is empty at present. So if you wish to keep
> > getting those e-mails, please add yourself to this role or tell me to do
> so
> > for you.
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
> > ср, 21 апр. 2021 г. в 17:59, Alexey Goncharuk <
> alexey.goncha...@gmail.com>:
> >
> >> I support the idea. All issues notifications are also sent to
> >> iss...@ignite.apache.org so one can subscribe to this list in order to
> >> track the created tickets. The notifications trash the devlist archive
> UI
> >> and make it extremely difficult to navigate.
> >>
> >> вт, 20 апр. 2021 г. в 18:35, Ilya Kasnacheev  >:
> >>
> >> > Hello, Maxim!
> >> >
> >> > You are free to revert any commit which has led to any new stable test
> >> > failure, or new flaky test that was non-flaky before.
> >> >
> >> > Just revert the change and reopen the ticket.
> >> >
> >> > The problem here is that it's very hard to detect on the spot, most of
> >> > MTCGA e-mails are false positives and even if they are not, it is not
> >> > relevant for most of developers.
> >> >
> >> > WDYT? I'm also still waiting for more input.
> >> >
> >> > Regards,
> >> > --
> >> > Ilya Kasnacheev
> >> >
> >> >
> >> > ср, 14 апр. 2021 г. в 21:26, Maxim Muzafarov :
> >> >
> >> > > +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 Mekhanikov
> >> > > 
> >> > > wrote:
> >> > > >
> >> > > > Huge +1 to this.
> >> > > >
> >> > > > I've already brought up this topic in the past:
> >> > > >
> >> > >
> >> >
> >>
> http://apache-ignite-developers.2346864.n4.nabble.com/Bots-on-dev-list-td34406.html
> >> > > > I hope some day newcomers won't need to set up their email filters
> >> when
> >> > > > they come to the developers list.
> >> > > >
> >> > > > Denis
> >> > > >
> >> > > > ср, 14 апр. 2021 г. в 18:07, Atri Sharma :
> >> > > >
> >> > > > > +1 to move issues to the issues list.
> >> > > > >
> >> > > > > For MTCGA, maybe build@?
> >> > > > >
> >> > > > > On Wed, Apr 14, 2021 at 8:35 PM Ilya Kasnacheev
> >> > > > > 
> >> > > wrote:
> >> > > > > >
> >> > > > > > Hello!
> >> > > > > >
> >> > > > > > We have a discussion on how to ensure best engagement in dev@
> >> > list,
> >> > > and
> >> > > > > it
> >> > > > > > seems that Issue Created emails from IGNITE project consume a
> >> > > > > > lot
> >> > of
> >> > > > > screen
> >> > > > > > space, it's hard to spot genuine discussions in
> >> > > > > > https://lists.apache.org/list.html?dev@ignite.apache.org for
> >> > > example.
> >> > > > > >
> >> > > > > > We already have issues@ mailing list. I propose that we stop
> >> > > sending any
> >> > > > > > JIRA emails to dev@. If anyone wishes to get just Created
> >> emails,
> >> > > they
> >> > > > > can
> >> > > > > > subscribe to these messages in their JIRA account settings. I
> >> > imagine
> >> > > > > most
> >> > > > > > of you already filter these messages out, so you may need to
> >> adjust
> >> > > your
> >> > > > > > filters slightly.
> >> > > > > >
> >> > > > > > A distant second is MTCGA messages, which are also
> >> > > > > > autogenerated
> >> > and
> >> > > not
> >> > > > > > informative for most readers of the channel, since they are at
> >> best
> >> > > > > > targeted at a single committer and at worst flaky.
> >> > > > > >
> >> > > > > > Where could we move those? What is your opinion here, on both
> >> > issues?
> >> > > > > >
> >> > > > > > Regards,
> >> > > > >
> >> > > > > --
> >> > > > > Regards,
> >> > > > >
> >> > > > > Atri
> >> > > > > Apache Concerted
> >> > > > >
> >> > >
> >> >
> >>
> >
>
>
> --
>
> Best regards,
> Ivan Pavlukhin
>

Re: [VOTE][EXTENSION] Release Apache Ignite performance-statistics-ext, spring-data-all-ext and spring-tx-ext extensions 1.0.0 RC1

[Dmitriy Pavlov]

My best guess that since PMCs have a binding vote in voting in release, a
PMC member should sign binaries as well. And I suppose that in the past
only PMC members were signing the release.

Meanwhile, https://infra.apache.org/release-signing.html does not contain
any mention of PMC role and only committers are mentioned there. It
might be not an answer, since a lot of projects have PMC=Committer and just
one election.

Sincerely,
Dmitriy Pavlov

чт, 15 апр. 2021 г. в 22:05, Ivan Daschinsky :

> I'm sorry, but is it OK, that artifacts are signed with signature of
> non-PMC?
>
> чт, 15 апр. 2021 г. в 19:26, Nikita Amelchev :
>
> > Dear Ignite Community,
> >
> > I have uploaded a release candidate of the following extension modules:
> >
> > performance-statistics-ext
> > spring-data-ext
> > spring-data-2.0-ext
> > spring-data-2.2-ext
> > spring-data-commons
> > spring-tx-ext
> >
> > The release candidate of the performance-statistics-ext extension:
> >
> >
> https://dist.apache.org/repos/dist/dev/ignite/ignite-performance-statistics-ext/1.0.0-rc1/
> >
> > The following staging can be used for testing:
> > https://repository.apache.org/content/repositories/orgapacheignite-1509
> >
> > Tags were created:
> >
> > ignite-performance-statistics-ext-1.0.0-rc1
> >
> >
> https://gitbox.apache.org/repos/asf?p=ignite-extensions.git;a=commit;h=b992d9758278c38e93b375b08e4052954744a436
> >
> > ignite-spring-data-ext-1.0.0-rc1
> > ignite-spring-data-2.2-ext-1.0.0-rc1
> > ignite-spring-data-2.0-ext-1.0.0-rc1
> > ignite-spring-data-commons-1.0.0-rc1
> > ignite-spring-data-all-ext-1.0.0-rc1
> >
> >
> https://gitbox.apache.org/repos/asf?p=ignite-extensions.git;a=commit;h=277ca95f6472d8bd46d906e70ba1a312d36dadb0
> >
> > ignite-spring-tx-ext-1.0.0-rc1
> >
> >
> https://gitbox.apache.org/repos/asf?p=ignite-extensions.git;a=commit;h=55a3ae9e011ba48796847a33481842f154f0febb
> >
> > RELEASE NOTES:
> >
> >
> https://gitbox.apache.org/repos/asf?p=ignite-extensions.git;a=blob;f=RELEASE_NOTES.txt;h=22f8d665c194ba2dfa6167354d97ad53d5ef206f;hb=c8de80ee14d1fb76d6cbb0b18513bb70b499c3cb
> >
> > DOCUMENTATION:
> > Documentation of listed extensions was updated in the following issues:
> >
> >
> https://issues.apache.org/jira/issues/?filter=-1=key%20in%20(IGNITE-14417%2CIGNITE-14398%2CIGNITE-14397%2CIGNITE-14493)
> >
> > The vote is formal, see voting guidelines
> > https://www.apache.org/foundation/voting.html
> >
> > +1 - to accept all the Apache Ignite performance-statistics-ext,
> > spring-data-all-ext and spring-tx-ext extensions 1.0.0-rc1 listed in
> > the thread
> > 0 - don't care either way
> > -1 - DO NOT accept either of the Apache Ignite
> > performance-statistics-ext, spring-data-all-ext and spring-tx-ext
> > extensions 1.0.0-rc1 (explain why)
> >
> > The vote will hold for 72 hours and will end on April 18 2021 17:00 UTC
> >
> >
> https://www.timeanddate.com/countdown/generic?iso=20210418T17=1440=cursive
> >
> > --
> > Best wishes,
> > Amelchev Nikita
> >
>
>
> --
> Sincerely yours, Ivan Daschinskiy
>

Re: [ANNOUNCE] Welcome Ivan Daschinsky as a new committer

[Dmitriy Pavlov]

Congrats, Ivan!

вт, 13 апр. 2021 г. в 20:02, Ivan Daschinsky :

> Guys, many thanks to all of you!
>
> вт, 13 апр. 2021 г. в 13:19, Alex Plehanov :
>
> > Ivan, congratulations!
> >
> >
> > вт, 13 апр. 2021 г. в 13:02, Andrey Mashenkov <
> andrey.mashen...@gmail.com
> > >:
> >
> > > Ivan, congrats!
> > >
> > > On Tue, Apr 13, 2021 at 11:42 AM Alexei Scherbakov <
> > > alexey.scherbak...@gmail.com> wrote:
> > >
> > > > Ivan, great work.
> > > >
> > > > вт, 13 апр. 2021 г. в 10:53, Ivan Pavlukhin :
> > > >
> > > > > Ivan, congrats!
> > > > >
> > > > > 2021-04-13 9:41 GMT+03:00, Nikolay Izhikov :
> > > > > > Congrats! Well deserved.
> > > > > >
> > > > > >> 13 апр. 2021 г., в 09:34, Zhenya Stanilovsky
> > > >  > > > > >
> > > > > >> написал(а):
> > > > > >>
> > > > > >>
> > > > > >> Big deal ! Ivan, ignite it !)
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >>> The Project Management Committee (PMC) for Apache Ignite has
> > > invited
> > > > > >>> Ivan Daschinsky to become a committer and we are pleased to
> > > announce
> > > > > >>> that
> > > > > >>> he has accepted.
> > > > > >>>
> > > > > >>> Ivan made a lot of contributions to Apache Ignite.
> > > > > >>> He helped a lot to improve our Python Thin Client fixing a lot
> of
> > > > > >>> different
> > > > > >>> bugs and contributing major feature such as asyncio support and
> > > > > >>> C-extension
> > > > > >>> which improved performance significantly for many cases. Thanks
> > to
> > > > Ivan
> > > > > >>> Python
> > > > > >>> Thin client has become much more stable and production-ready.
> He
> > > also
> > > > > >>> introduced the CMake building system for Ignite C++, and has
> > made a
> > > > > >>> number
> > > > > >>> of
> > > > > >>> other important improvements. Besides the code contributions,
> > Ivan
> > > is
> > > > > >>> also
> > > > > >>> an
> > > > > >>> active community member.
> > > > > >>>
> > > > > >>> Being a committer enables easier contribution to the project
> > since
> > > > > there
> > > > > >>> is
> > > > > >>> no need to go via the patch submission process. This should
> > enable
> > > > > >>> better
> > > > > >>> productivity.
> > > > > >>>
> > > > > >>> Please join me in welcoming Ivan, and congratulating him on the
> > new
> > > > > role
> > > > > >>> in
> > > > > >>> the Apache Ignite Community.
> > > > > >>>
> > > > > >>> Best Regards,
> > > > > >>> Igor
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > > Best regards,
> > > > > Ivan Pavlukhin
> > > > >
> > > >
> > > >
> > > > --
> > > >
> > > > Best regards,
> > > > Alexei Scherbakov
> > > >
> > >
> > >
> > > --
> > > Best regards,
> > > Andrey V. Mashenkov
> > >
> >
>
>
> --
> Sincerely yours, Ivan Daschinskiy
>

Re: [DISCUSSION] IEP-69 The evolutionary release process

[Dmitriy Pavlov]

Folks,

let me add my 50 cents. I don't see major issues with this IEP, for now.
And I really looking forward to talking about it. I can't get what causes
misunderstanding.

The only thing that concerns me here is that IEP requires the community to
support solutions for 1 year, 1 quarter, etc.

Apache community is not a commercial company that provides support of any
kind, and I would be reluctant to add these or similar statements to any
public documents. At any point in time, the community and PMC can vote and
introduce any major feature breaking compatibility. We tend to avoid 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 follow :-)
>
> Have you checked the `motivation` [1] topic on the IEP-69 page? Should
> I add more details to it prior to the call? I want to make Ignite
> better and also think that the current 2.x version with all the
> advantages and disadvantages is far from exhausted its capabilities.
> I'm pretty sure the same motivation page exists for 3.0 version
> describing the advantages and disadvantages of developing mentioned
> IEPs. It will be good to share it prior to the cal also.
>
>
> [1]
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-69%3A+The+evolutionary+release+process#IEP69:Theevolutionaryreleaseprocess-Motivation
>
> On Thu, 11 Mar 2021 at 01:21, Valentin Kulichenko
>  wrote:
> >
> > Ksenya, thanks for scheduling this so quickly!
> >
> > Guys, I hope we can make this discussion constructive. Please keep in
> mind
> > that Ignite 3 is an ongoing project supported by multiple contributors,
> > committers, and PMC members. Neglecting 6+ months of effort and
> suggesting
> > that it's just "prototyping some cool features and nothing more" is
> really
> > bizarre, and, quite frankly, sounds disrespectful to fellow developers
> > (although I'm 100% sure it was not intended this way).
> >
> > Maxim, one of the biggest issues I have with your IEP is that I don't
> > understand the motivation behind it. If you don't mind, I would like to
> > suggest that you kick off the meeting with a detailed explanation
> > of exactly that. The first step is to achieve a mutual understanding of
> > each other's goals. Once we do that, I'm sure we will easily find a
> > solution.
> >
> > -Val
> >
> > On Wed, Mar 10, 2021 at 8:55 AM Kseniya Romanova <
> romanova.ks@gmail.com>
> > wrote:
> >
> > > 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 :
> > >
> > > > Folks,
> > > >
> > > >
> > > > Agree, the discussion may be endless without compromises on all
> sides.
> > > > I always think that if there is no consensus (and I see from the
> > > > thread [1] that it's was no found) for such important decisions like
> > > > product future development and releases AFS provides the voting
> > > > procedure. Without fixing the results of the discussion [1] it sounds
> > > > like prototyping some cool features and nothing more.
> > > >
> > > > So, back to Denis suggestion can you share - what would be the best
> > > > time for all of us (considering different time zones) to have a call?
> > > >
> > > > I also think that we should start a vote about the future releases on
> > > > our Apache Ignite web-site and user-list, thus all who are using the
> > > > Apache Ignite may choose the best option they like.
> > > >
> > > >
> > > > [1]
> > > >
> > >
> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Ignite-3-0-development-approach-td49922.html
> > > >
> > > > On Wed, 10 Mar 2021 at 03:57, Valentin Kulichenko
> > > >  wrote:
> > > > >
> > > > > Hi Maxim,
> > > > >
> > > > > I disagree with the suggestions. Several community members have
> already
> > > > > pointed out the discussion about Ignite 3.0 [1]. During that
> > > discussion,
> > > > we
> > > > > did agree on the scope of the changes for 3.0, as well as the
> general
> > > > > direction for the product. The new repo was created not to "develop
> > > from
> > > > > scratch", but to provide an opportunity for the community members
> to
> > > > > actively work on Ignite 3 without killing the Ignite 2.x. No
> > > alternative
> > > > > solution for this was presented, so we went ahead with the process
> -- I
> > > > > consider that to be an example of the silent consensus.
> > > > >
> > > > > I also want to emphasize that Ignite 3 is active and is moving
> forward.
> > > > If
> > > > > you look at the ignite-3 repo, commits and PRs are coming in on
> regular
> > > > > basis. We also had the first alpha release early in the year. I do
> > > agree
> > > > > with you, however, that there is not too much activity on the dev
> list.
> > > > As
> > > > > far as I 

Re: New committer: Mauricio Stekl

[Dmitriy Pavlov]

Congrats, Mauricio!

For me, this election proves the statement, that you can contribute in many
different ways.

чт, 4 мар. 2021 г. в 18:32, Никита Сафонов :

> Congratulations, Mauricio!
>
> Thank you for your hard work.
>
> Regards,
> Nikita
>
> чт, 4 мар. 2021 г. в 17:56, Kseniya Romanova :
>
> > Mauricio, congrats, and many thanks for the help!
> >
> > чт, 4 мар. 2021 г. в 07:31, Denis Magda :
> >
> > > The Project Management Committee (PMC) for Apache Ignite has invited
> > > Mauricio Stekl to become a committer and we are pleased to announce
> > > that he has accepted.
> > >
> > > Mauricio is the contributor who has been maintaining and improving our
> > > website for the last two years. There are countless small and
> > > significant changes he has made throughout that time. He helped to
> > > redesign the website, integrated the website into the documentation
> > > publication process, regularly optimizes the pages to ensure our
> > > project is easily discoverable by search engines.
> > >
> > > Being a committer enables easier contribution to the project since
> > > there is no need to go via the patch submission process. This should
> > > enable better productivity.
> > >
> > > -
> > > Denis
> > >
> >
>

Re: Apache Board Report, Feb 10

[Dmitriy Pavlov]

Ok, I've updated the mission statement.

I guess this section is skipped by approvers since it is auto-generated. It
should be there for the case when a reader is not familiar with Ignite.

Btw, if anyone knows where reporter.a.o takes that data and how to
update it, please let me know.



пн, 8 февр. 2021 г. в 14:28, Ilya Kasnacheev :

> Hello!
>
> The mission of Ignite project is the creation and maintenance of software
> related to high-performance distributed database engine providing in-memory
> and persistent data caching, partitioning, processing, and
> querying components.
>
> WDYT?
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пн, 8 февр. 2021 г. в 14:14, Dmitriy Pavlov :
>
> > Hi Ilya,
> >
> > that's a good point. This decision was mentioned in the previous board
> > report, it was in Nov 2020.
> >
> > How description can be changed?
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > пн, 8 февр. 2021 г. в 12:26, Ilya Kasnacheev  >:
> >
> > > Hello!
> > >
> > > In Nov 2020 we have decided that Ignite is a "distributed database":
> > >
> > >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Define-Apache-Ignite-as-a-Distributed-Database-td50269.html
> > >
> > > I think it is worth mentioning, and also that Description section needs
> > > updating.
> > >
> > > Regards,
> > > --
> > > Ilya Kasnacheev
> > >
> > >
> > > вс, 7 февр. 2021 г. в 22:52, Dmitriy Pavlov :
> > >
> > > > Hi Igniters,
> > > >
> > > > Feb 10 is the due date for submitting the next board report. I would
> > like
> > > > to submit it a bit earlier, by the end of the day on Feb 9.
> > > >
> > > > Here is the first version of the report (at the end of the email).
> > Should
> > > > we add here something important?
> > > >
> > > > What do you think if it worths mentioning/requires board attention:
> > > > schema first discussions? IEP-61? Extensions release? Anything
> related
> > to
> > > > the 3.0 development approach?
> > > >
> > > > Sincerely,
> > > > Dmitriy Pavlov
> > > >
> > > >
> > > > ## Description:
> > > > The mission of Ignite is the creation and maintenance of software
> > related
> > > > to
> > > > High-performance, integrated, and distributed In-Memory Database and
> > > > Caching
> > > > Platform providing in-memory data caching, partitioning, processing,
> > and
> > > > querying components.
> > > >
> > > > ## Issues:
> > > > There are no issues requiring board attention
> > > >
> > > > ## Membership Data:
> > > > Apache Ignite was founded 2015-08-19 (5 years ago)
> > > > There are currently 56 committers and 35 PMC members in this project.
> > > > The Committer-to-PMC ratio is 8:5.
> > > >
> > > > Community changes, past quarter:
> > > > - Alex Plehanov was added to the PMC on 2020-11-18
> > > > - Ivan Bessonov was added as a committer on 2021-01-19
> > > > - Nikita Amelchev was added as a committer on 2021-01-21
> > > >
> > > > ## Project Activity:
> > > > Development
> > > > - Apache Ignite community voted to remove MVCC public API. Test and
> > test
> > > >   suites on the TeamCity are under discussion.
> > > > - 3.0.0-alpha1 was released on 2021-01-11, this release is the very
> > first
> > > >   build made from standalone branch Ignite 3.0, such releases should
> > help
> > > > in
> > > >   early adoption and testing of 3.0
> > > > - 2.9.1 was released on 2020-12-28 (latest stable) - this release
> > patches
> > > >   2.9.0 and mostly contains fixes
> > > > - 2.10.0 release is being prepared
> > > >
> > > > Events and conferences
> > > > - Community members and Ignite users continue to run talks at online
> > > > meetups
> > > >
> > > > ## Community Health:
> > > > - dev@, user@ list traffic, and code contributions are almost the
> same
> > > as
> > > >   in the past quarter
> > > > - Issues, PRs related activity have increased (from +14% to +49%)
> > > >
> > >
> >
>

Re: Apache Board Report, Feb 10

[Dmitriy Pavlov]

Hi Ilya,

that's a good point. This decision was mentioned in the previous board
report, it was in Nov 2020.

How description can be changed?

Sincerely,
Dmitriy Pavlov

пн, 8 февр. 2021 г. в 12:26, Ilya Kasnacheev :

> Hello!
>
> In Nov 2020 we have decided that Ignite is a "distributed database":
>
> http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Define-Apache-Ignite-as-a-Distributed-Database-td50269.html
>
> I think it is worth mentioning, and also that Description section needs
> updating.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> вс, 7 февр. 2021 г. в 22:52, Dmitriy Pavlov :
>
> > Hi Igniters,
> >
> > Feb 10 is the due date for submitting the next board report. I would like
> > to submit it a bit earlier, by the end of the day on Feb 9.
> >
> > Here is the first version of the report (at the end of the email). Should
> > we add here something important?
> >
> > What do you think if it worths mentioning/requires board attention:
> > schema first discussions? IEP-61? Extensions release? Anything related to
> > the 3.0 development approach?
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> >
> > ## Description:
> > The mission of Ignite is the creation and maintenance of software related
> > to
> > High-performance, integrated, and distributed In-Memory Database and
> > Caching
> > Platform providing in-memory data caching, partitioning, processing, and
> > querying components.
> >
> > ## Issues:
> > There are no issues requiring board attention
> >
> > ## Membership Data:
> > Apache Ignite was founded 2015-08-19 (5 years ago)
> > There are currently 56 committers and 35 PMC members in this project.
> > The Committer-to-PMC ratio is 8:5.
> >
> > Community changes, past quarter:
> > - Alex Plehanov was added to the PMC on 2020-11-18
> > - Ivan Bessonov was added as a committer on 2021-01-19
> > - Nikita Amelchev was added as a committer on 2021-01-21
> >
> > ## Project Activity:
> > Development
> > - Apache Ignite community voted to remove MVCC public API. Test and test
> >   suites on the TeamCity are under discussion.
> > - 3.0.0-alpha1 was released on 2021-01-11, this release is the very first
> >   build made from standalone branch Ignite 3.0, such releases should help
> > in
> >   early adoption and testing of 3.0
> > - 2.9.1 was released on 2020-12-28 (latest stable) - this release patches
> >   2.9.0 and mostly contains fixes
> > - 2.10.0 release is being prepared
> >
> > Events and conferences
> > - Community members and Ignite users continue to run talks at online
> > meetups
> >
> > ## Community Health:
> > - dev@, user@ list traffic, and code contributions are almost the same
> as
> >   in the past quarter
> > - Issues, PRs related activity have increased (from +14% to +49%)
> >
>

Apache Board Report, Feb 10

[Dmitriy Pavlov]

Hi Igniters,

Feb 10 is the due date for submitting the next board report. I would like
to submit it a bit earlier, by the end of the day on Feb 9.

Here is the first version of the report (at the end of the email). Should
we add here something important?

What do you think if it worths mentioning/requires board attention:
schema first discussions? IEP-61? Extensions release? Anything related to
the 3.0 development approach?

Sincerely,
Dmitriy Pavlov


## Description:
The mission of Ignite is the creation and maintenance of software related to
High-performance, integrated, and distributed In-Memory Database and Caching
Platform providing in-memory data caching, partitioning, processing, and
querying components.

## Issues:
There are no issues requiring board attention

## Membership Data:
Apache Ignite was founded 2015-08-19 (5 years ago)
There are currently 56 committers and 35 PMC members in this project.
The Committer-to-PMC ratio is 8:5.

Community changes, past quarter:
- Alex Plehanov was added to the PMC on 2020-11-18
- Ivan Bessonov was added as a committer on 2021-01-19
- Nikita Amelchev was added as a committer on 2021-01-21

## Project Activity:
Development
- Apache Ignite community voted to remove MVCC public API. Test and test
  suites on the TeamCity are under discussion.
- 3.0.0-alpha1 was released on 2021-01-11, this release is the very first
  build made from standalone branch Ignite 3.0, such releases should help in
  early adoption and testing of 3.0
- 2.9.1 was released on 2020-12-28 (latest stable) - this release patches
  2.9.0 and mostly contains fixes
- 2.10.0 release is being prepared

Events and conferences
- Community members and Ignite users continue to run talks at online meetups

## Community Health:
- dev@, user@ list traffic, and code contributions are almost the same as
  in the past quarter
- Issues, PRs related activity have increased (from +14% to +49%)

Re: [COMMUNITY] Recognizing those who contribute to user support and project awareness

[Dmitriy Pavlov]

Hi Ksenia, Folks,

Thank you for providing this information, and thank all of you for your
contributions. Speaking about how the community recognizes these efforts,
it's pretty much up to PMC to decide.

There is nothing in Apache policies that says that you should contribute
code to be invited to be Committer/PMC. There are examples when the Apache
Foundation itself invites non-technical folks to be members of the
foundation.

So we have a formal way to recognize it, feel free to start a discussion. I
really looking forward to seeing new statistics for 2021, coz it is still
important to mention, even if a community-champion is already a member of
the PMC.

Sincerely,
Dmitriy Pavlov

вт, 5 янв. 2021 г. в 03:50, Saikat Maitra :

> Hi Kseniya,
>
> Much appreciate it.
>
> Thank you and Happy New Year!
>
> Regards,
> Saikat
>
> On Wed, Dec 30, 2020 at 6:50 AM Ivan Pavlukhin 
> wrote:
>
> > Great news! Thanks and Happy holidays!
> >
> > 2020-12-30 12:10 GMT+03:00, Alexey Zinoviev :
> > > Thanks for recognition! Happy New Year!
> > >
> > > вт, 29 дек. 2020 г. в 21:36, Kseniya Romanova <
> romanova.ks@gmail.com
> > >:
> > >
> > >> Hi, Igniters!
> > >>
> > >>
> > >> ASF welcomes all types of contributions, including responses to user
> > >> questions and promotion of projects. And, the GriGain DelRel team
> knows
> > >> that people spend a lot of their private time on such activities. Our
> > >> code
> > >> and documentation contributors are recognized by being promoted to the
> > >> role
> > >> of " committer." But, unfortunately, we don't have a formal way to
> > >> recognize our user-support and project-promotion contributors.
> > >>
> > >>
> > >> In 2020, more than 40 people contributed their time and experience to
> > >> promote project visibility and encourage adoption by developers:
> > >>
> > >>
> > >>
> > >>-
> > >>
> > >>59 talks to 2400 developers and architects at meetup and conference
> > >>events
> > >>-
> > >>
> > >>60+ blog posts and tutorials
> > >>-
> > >>
> > >>2000+ questions answered on the User list and Stackoverflow
> > >>
> > >>
> > >> Let’s praise some of our most active Ignite supporters in 2020:
> > >>
> > >>
> > >>
> > >>-
> > >>
> > >>In user support, Ilya Kasnacheev is our absolute user support
> > >> champion.
> > >>He alone answered 756 questions on Stackoverflow and the User list.
> > >>-
> > >>
> > >>Val Kulichenko posted 9 articles and presented at 6 meetups.
> > >>-
> > >>
> > >>Denis Magda created 10 demos and 4 tutorials and presented at 14
> > >> meetups
> > >>and 7 conferences.
> > >>-
> > >>
> > >>Alexey Zinoviev wrote 4 articles about Ignite ML and presented at 1
> > >>meetup and 1 conference.
> > >>-
> > >>
> > >>Pavel Tupitsyn created 4 articles and helped Ignite users on the
> > >> mailing
> > >>list and Stackoverflow.
> > >>-
> > >>
> > >>Saikat Maitra presented at 2 conferences.
> > >>-
> > >>
> > >>Ivan Pavlukhin helped many new developers to start contributing to
> > >>Ignite.
> > >>
> > >>
> > >> As a sign of our gratitude for their efforts, these contributors will
> > >> receive special New Year gifts.
> > >>
> > >>
> > >> In 2021, we want to track this type of contribution and ensure that
> the
> > >> contributors are recognized within the community. The Alfa version of
> > our
> > >> tracking system is already functioning inside GridGain, so the next
> step
> > >> is
> > >> to upgrade the current system and start a discussion with PMC members.
> > >> Those who help to attract and retain users are definitely worthy of
> > >> praise
> > >> and promotion, as the value of their contribution matches the value
> that
> > >> is
> > >> provided through code and documentation.
> > >>
> > >>
> > >> Keep being awesome and have a Happy New Year!
> > >>
> > >>
> > >> Kseniya
> > >>
> > >> DevRel at GridGain
> > >>
> > >
> >
> >
> > --
> >
> > Best regards,
> > Ivan Pavlukhin
> >
>

Re: [DISCUSS] Ignite 3.0 development approach

[Dmitriy Pavlov]

Folks, I'm a little bit concerned about the simultaneous
- existence of the repo https://github.com/apache/ignite-3 and PRs for that
repo
- and a couple of downvotes from PMC members.

Is it all fine here? Was there any vote /discussion where it was discussed
and consensus approved? What is the status of the ignite-3 repo?

вт, 15 дек. 2020 г. в 17:30, Carbone, Adam :

> I don't believe Java 7 was LTS, and I hope that others will have upgraded
> long before that. If that is the release timeframe for 3.0, then I suppose
> that would makes sense, I would still doubt that people would be going
> newer than java 11, just my opinion of what I'm seeing.
>
> Regards
> ~adam
>
> Adam Carbone | Director of Innovation – Intelligent Platform Team |
> Bottomline Technologies
> Office: 603-501-6446 | Mobile: 603-570-8418
> www.bottomline.com
>
>
>
> On 12/15/20, 4:25 AM, "Ilya Kasnacheev" 
> wrote:
>
> Hello!
>
> I guess Ignite 3.0 will be ready for production use somewhere in 2022,
> realistically. By that time, Java 8 will be long enough out of support
> so
> that most companies will actually forbid its use, WRT vulnerabilities
> et
> all.
>
> After all we have managed to upgrade from Java 7 to Java 8 and only
> got a
> minor amount of complaints.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пн, 14 дек. 2020 г. в 19:06, Carbone, Adam <
> adam.carb...@bottomline.com>:
>
> > So just one bit to consider... Are there features that you need to
> use in
> > these newer versions of java? Or are we just updating to stay
> current? The
> > reason I ask is that there are still lots of people in an enterprise
> space
> > that are beholden to having to support legacy JAVAEE supported
> applications
> > on Websphere, Weblogic, Redhat, etc... and the organizations that
> use those
> > platforms are slow to move... Most of them are still on Java8
> >
> > So as a platform I think a strong consideration needs to be towards
> having
> > the broadest possible support profile until it becomes an impediment
> to
> > doing things that the platform needs. So far I haven't seen huge
> things in
> > the newer versions of java that are must haves ( a few exceptions are
> > things that would be really nice to take advantage of ).
> >
> > I think that apache commons has taken the right approach by staying
> on
> > java 8 giving the largest possible user base.
> >
> > Even standardizing on java 11 would have to make us reconsider
> Ignite as
> > the platform we are using, we are not so invested in it as of now,
> even
> > though we have big plans to leverage it. Just because we aren't sure
> when
> > we are going to be able to upgrade from java8. It has support
> through 2022,
> > so I imagine that is when we will be discussing that.
> >
> > Regards
> >
> > ~Adam
> >
> > Adam Carbone | Director of Innovation – Intelligent Platform Team |
> > Bottomline Technologies
> > Office: 603-501-6446 | Mobile: 603-570-8418
> > www.bottomline.com
> >
> >
> >
> > On 11/24/20, 7:38 AM, "Alexey Zinoviev" 
> wrote:
> >
> > Java 15 is better, VarHandles, ForeignMemory access and so on.
> >
> > In both cases, I support the Java version 11 and higher for the
> > development!
> >
> > вт, 24 нояб. 2020 г. в 15:21, Andrey Mashenkov <
> > andrey.mashen...@gmail.com>:
> >
> > > Let's add maven plugins  for sanity checks at the early stage.
> > > I've created a ticket for this [1].
> > >
> > > Also, I've found initial pom.xml has a target version Java 8.
> > > Do we intend to move to Java 11 (or may be next LTS) and drop
> Java 8
> > in
> > > Ignite 3.0?
> > >
> > > [1]
> >
> https://urldefense.com/v3/__https://issues.apache.org/jira/browse/IGNITE-13751__;!!O3mv9RujDHg!37ujwREhL1l-B3DmRXix6yaN1dE1KgH1Tx_tSl0eLZe4x1y0NnUlF4MzW5FeKAO2Ejs8$
> > >
> > > On Tue, Nov 24, 2020 at 5:40 AM Valentin Kulichenko <
> > > valentin.kuliche...@gmail.com> wrote:
> > >
> > > > Folks,
> > > >
> > > > I went ahead and created the repository [1]. I also
> configured a
> > TeamCity
> > > > project [2] that runs all available JUnit tests on every PR
> > creation or
> > > > update. It also sends the status update to GitHub so that
> it's
> > reflected
> > > in
> > > > the PR itself so that we can do merges directly from GitHub.
> Basic
> > steps
> > > to
> > > > make a change are described on the Wiki page [3].
> > > >
> > > > Let me know if you have any questions.
> > > >
> > > > [1]
> >
> https://urldefense.com/v3/__https://github.com/apache/ignite-3__;!!O3mv9RujDHg!37ujwREhL1l-B3DmRXix6yaN1dE1KgH1Tx_tSl0eLZe4x1y0NnUlF4MzW5FeKIq24lxF$
> >

Re: Hello

[Dmitriy Pavlov]

Hi Varvara,

Thank you for your interest in Apache Ignite and welcome to the Apache
Ignite Community.

I've added a contributor role to the account, so now you should be able to
assign a ticket.

See also short intro how to contribute
https://github.com/apache/ignite/blob/master/CONTRIBUTING.md#contributing-to-apache-ignite

Sincerely
Dmitriy Pavlov

ср, 16 дек. 2020 г. в 18:14, Varvara Kozhukhova
:

> Hello Ignite Community,
>
> My name is Varvara and I'm a Big Data junior developer with 3 months
> experience. My current knowledge includes Hadoop, Spark, Kafka, Hive.
>
> I would like to take part in the Apache Ignite project and make a
> contribution to it.
>
> I'm thinking to start with some easy fix or bugfix to get more acquainted
> with the code.
>
> Could someone give me access, please, so that I will be able to book a
> ticket.
>
> My Jira Id is saventune.
>
>
>

Re: [MTCGA]: new failures in builds [5780347, 5780334] needs to be handled

[Dmitriy Pavlov]

Does it make sense to increase the Control Utility suite timeout a bit?

Now suite timeout is 30 minutes, and tests require 24 minutes to complete
for a successful run.

ср, 9 дек. 2020 г. в 23:36, :

> Hi Igniters,
>
>  I've detected some new issue on TeamCity to be handled. You are more than
> welcomed to help.
>
>  *New Critical Failure in master Control Utility
> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ControlUtility?branch=%3Cdefault%3E
>  No changes in the build
>
>  *New Critical Failure in master-nightly MVCC Cache 7
> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_MvccCache7?branch=%3Cdefault%3E
>  No changes in the build
>
>  - Here's a reminder of what contributors were agreed to do
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
>  - Should you have any questions please contact
> dev@ignite.apache.org
>
> Best Regards,
> Apache Ignite TeamCity Bot
> https://github.com/apache/ignite-teamcity-bot
> Notification generated at 23:35:59 09-12-2020
>

Re: Join to dev community

[Dmitriy Pavlov]

Sorry, I meant text/plain

пн, 30 нояб. 2020 г. в 20:24, Dmitriy Pavlov :

> Hi Aleksey,
>
> Unfortunately Apache Mailing lists can accept text/html or mixed content
> types in emails. Generally speaking, it is because the formatting of text
> in mailing archives is not supported.
>
> Could you please change your email client settings to provide text or
> mixed messages?
>
> Sincerely
> Dmitriy Pavlov
>
> пн, 30 нояб. 2020 г. в 20:16, Aleksey Rostov :
>
>> Hello!
>> So, I found out that I have created an account in
>> https://cwiki.apache.org/
>> . I thought that confluence and jira share accounts but this was not the
>> case.
>> I have created a jira account - arostov and checked it. My main email
>> address is alekse-ros...@ya.ru but I can't send emails from this
>> account, I
>> catch error every time
>>
>> :
>> ezmlm-reject: fatal: Sorry, I don't accept messages of MIME Content-Type
>> 'text/html' (#5.2.3)
>>
>> Therefore I send from secondary email address arostov.a...@gmail.com
>>
>> пт, 27 нояб. 2020 г. в 21:19, Aleksey Rostov :
>>
>> > Hello everyone!
>> > My name is Aleksey Rostov, I want to contribute to Ignite.NET. I am
>> > currently a senior .net developer in Luxoft company in Saint Petersburg.
>> > Please, help me to start contributing.
>> > I have created a jira account - arostov.
>> >
>>
>

Re: Join to dev community

[Dmitriy Pavlov]

Hi Aleksey,

Unfortunately Apache Mailing lists can accept text/html or mixed content
types in emails. Generally speaking, it is because the formatting of text
in mailing archives is not supported.

Could you please change your email client settings to provide text or
mixed messages?

Sincerely
Dmitriy Pavlov

пн, 30 нояб. 2020 г. в 20:16, Aleksey Rostov :

> Hello!
> So, I found out that I have created an account in
> https://cwiki.apache.org/
> . I thought that confluence and jira share accounts but this was not the
> case.
> I have created a jira account - arostov and checked it. My main email
> address is alekse-ros...@ya.ru but I can't send emails from this account,
> I
> catch error every time
>
> :
> ezmlm-reject: fatal: Sorry, I don't accept messages of MIME Content-Type
> 'text/html' (#5.2.3)
>
> Therefore I send from secondary email address arostov.a...@gmail.com
>
> пт, 27 нояб. 2020 г. в 21:19, Aleksey Rostov :
>
> > Hello everyone!
> > My name is Aleksey Rostov, I want to contribute to Ignite.NET. I am
> > currently a senior .net developer in Luxoft company in Saint Petersburg.
> > Please, help me to start contributing.
> > I have created a jira account - arostov.
> >
>

Re: Why WAL archives enabled by default?

[Dmitriy Pavlov]

In older versions of Apache Ignite, WAL archive could contain valid records
needed for recovery. If something was changed since then, my comment may be
not valid.

We've discussed that before, that naming this directory as 'archive' was
not the best possible option. The archive is often considered by users as
something not needed and sometimes it was deleted.

See also page related to internals and directory structure:
https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Persistent+Store+-+under+the+hood#IgnitePersistentStoreunderthehood-WALstructure

So infinite storage of archive is definitely not necessary for vanilla
open-source version, but archive itself is needed.

Sincerely,
Dmitriy Pavlov

ср, 11 нояб. 2020 г. в 01:21, Raymond Wilson :

> Isn't the discussion here related to the WAL archive? If you disable that
> don't you still have the WAL containing un-checkpointed changes?
>
> On Wed, Nov 11, 2020 at 11:01 AM Dmitriy Pavlov 
> wrote:
>
> > Hi Denis,
> >
> > the short answer here, Apache Ignite guarantees ACID, and for
> D-Durability
> > it is required to save all changes in some WAL/Redo Log to have a safe
> way
> > to recover from any hardware failures/disk outage.
> >
> > Should the user disable WAL, he/she could potentially lose durability.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > вт, 10 нояб. 2020 г. в 09:57, ткаленко кирилл :
> >
> > > Hello guys again!
> > >
> > > Does anyone know why we are doing any calculation here
> > > IgniteUtils#adjustedWalHistorySize at all?
> > > Would it be easier to always take the
> > > DataStorageConfiguration#maxWalArchiveSize? It seems that the user can
> > > easily do this himself by changing the value by 1 byte.
> > >
> > > 06.11.2020, 13:56, "Ivan Daschinsky" :
> > > > Alex, thanks for pointing that out. Shame that I missed it.
> > > >
> > > > пт, 6 нояб. 2020 г. в 13:45, Alex Plehanov  >:
> > > >
> > > >>  Guys,
> > > >>
> > > >>  We already have
> > FileWriteAheadLogManager#maxSegCountWithoutCheckpoint.
> > > >>  Checkpoint triggered if there are too many WAL segments without
> > > checkpoint.
> > > >>  Looks like you are talking about this feature.
> > > >>
> > > >>  пт, 6 нояб. 2020 г. в 13:21, Ivan Daschinsky  >:
> > > >>
> > > >>  > Kirill and I discussed privately proposed approach. As far as I
> > > >>  understand,
> > > >>  > Kirill suggests to implement some
> > > >>  > heuristic to do a force checkpoint in some cases if user by
> mistake
> > > >>  > misconfigured cluster in order to preserve
> > > >>  > requested size of WAL archive.
> > > >>  > Currently, as for me, this approach is questionable, because it
> can
> > > cause
> > > >>  > some performance problems. But as an option,
> > > >>  > it can be used and should be switchable.
> > > >>  >
> > > >>  > пт, 6 нояб. 2020 г. в 12:36, Ivan Daschinsky <
> ivanda...@gmail.com
> > >:
> > > >>  >
> > > >>  > > Kirill, how your approach will help if user tuned a cluster to
> do
> > > >>  > > checkpoints rarely under load?
> > > >>  > > No way.
> > > >>  > >
> > > >>  > > пт, 6 нояб. 2020 г. в 12:19, ткаленко кирилл <
> > tkalkir...@yandex.ru
> > > >:
> > > >>  > >
> > > >>  > >> Ivan, I agree with you that the archive is primarily about
> > > >>  optimization.
> > > >>  > >>
> > > >>  > >> If the size of the archive is critical for the user, we have
> no
> > > >>  > >> protection against this, we can always go beyond this limit.
> > > >>  > >> Thus, the user needs to remember this and configure it in some
> > > way.
> > > >>  > >>
> > > >>  > >> I suggest not to exceed this limit and give the expected
> > behavior
> > > for
> > > >>  > the
> > > >>  > >> user. At the same time, the segments needed for recovery will
> > > remain
> > > >>  and
> > > >>  > >> there will be no data loss.
> > > >>  > >>
> > > >>  > >> 06.11.2020, 11:29, "Ivan Daschinsky" :
> > > &g

Re: Ignite 2.9 Announcement Blog Post

[Dmitriy Pavlov]

ok, I see, I supposed this list is somehow automatically being built or
related to announcements.

ср, 11 нояб. 2020 г. в 01:48, Denis Magda :

> You also need to add a release to the reporter manually just for tracking
> purposes. I used to do this once a quarter when the board was requesting a
> report and I would add all the missing releases into that system while
> preparing the report.
>
> -
> Denis
>
>
> On Tue, Nov 10, 2020 at 1:27 PM Dmitriy Pavlov  wrote:
>
> > Hi Alex,
> >
> > Thank you for driving this release and this post.
> >
> > Was the release announced at announce@ ?
> >
> > Denis, Ignite veterans,
> >
> > The reason I'm asking: this release was not available at
> > https://reporter.apache.org/addrelease.html?ignite ? I've added it now.
> Is
> > it always required to add it there manually?
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > пт, 6 нояб. 2020 г. в 09:38, Alex Plehanov :
> >
> > > Igniters,
> > >
> > > Ignite 2.9 announce blog post is published now: [1]
> > >
> > > [1] : https://blogs.apache.org/ignite/entry/apache-ignite-2-9-released
> > >
> > > пт, 25 сент. 2020 г. в 11:04, Alex Plehanov :
> > >
> > > > Denis,
> > > >
> > > > Ok, I will prepare the text soon.
> > > >
> > > > чт, 24 сент. 2020 г. в 23:36, Denis Magda :
> > > >
> > > >> @Alex Plehanov 
> > > >>
> > > >> Are you interested in writing a blog post that covers the major
> > > >> improvements of the 2.9 release? It will be referenced from the
> > > >> announcement email and distributed through other channels. Examples
> of
> > > >> previous articles: https://blogs.apache.org/ignite/
> > > >>
> > > >> It happened that I was the only one who would write such an article
> > but
> > > >> will step down with pleasure if you can take over this task. Once
> the
> > > >> draft
> > > >> is ready, I'll ask a professional technical editor, who reviews my
> > > texts,
> > > >> to work with you as well.
> > > >>
> > > >> -
> > > >> Denis
> > > >>
> > > >
> > >
> >
>

Re: Why WAL archives enabled by default?

[Dmitriy Pavlov]

Hi Denis,

the short answer here, Apache Ignite guarantees ACID, and for D-Durability
it is required to save all changes in some WAL/Redo Log to have a safe way
to recover from any hardware failures/disk outage.

Should the user disable WAL, he/she could potentially lose durability.

Sincerely,
Dmitriy Pavlov

вт, 10 нояб. 2020 г. в 09:57, ткаленко кирилл :

> Hello guys again!
>
> Does anyone know why we are doing any calculation here
> IgniteUtils#adjustedWalHistorySize at all?
> Would it be easier to always take the
> DataStorageConfiguration#maxWalArchiveSize? It seems that the user can
> easily do this himself by changing the value by 1 byte.
>
> 06.11.2020, 13:56, "Ivan Daschinsky" :
> > Alex, thanks for pointing that out. Shame that I missed it.
> >
> > пт, 6 нояб. 2020 г. в 13:45, Alex Plehanov :
> >
> >>  Guys,
> >>
> >>  We already have FileWriteAheadLogManager#maxSegCountWithoutCheckpoint.
> >>  Checkpoint triggered if there are too many WAL segments without
> checkpoint.
> >>  Looks like you are talking about this feature.
> >>
> >>  пт, 6 нояб. 2020 г. в 13:21, Ivan Daschinsky :
> >>
> >>  > Kirill and I discussed privately proposed approach. As far as I
> >>  understand,
> >>  > Kirill suggests to implement some
> >>  > heuristic to do a force checkpoint in some cases if user by mistake
> >>  > misconfigured cluster in order to preserve
> >>  > requested size of WAL archive.
> >>  > Currently, as for me, this approach is questionable, because it can
> cause
> >>  > some performance problems. But as an option,
> >>  > it can be used and should be switchable.
> >>  >
> >>  > пт, 6 нояб. 2020 г. в 12:36, Ivan Daschinsky :
> >>  >
> >>  > > Kirill, how your approach will help if user tuned a cluster to do
> >>  > > checkpoints rarely under load?
> >>  > > No way.
> >>  > >
> >>  > > пт, 6 нояб. 2020 г. в 12:19, ткаленко кирилл  >:
> >>  > >
> >>  > >> Ivan, I agree with you that the archive is primarily about
> >>  optimization.
> >>  > >>
> >>  > >> If the size of the archive is critical for the user, we have no
> >>  > >> protection against this, we can always go beyond this limit.
> >>  > >> Thus, the user needs to remember this and configure it in some
> way.
> >>  > >>
> >>  > >> I suggest not to exceed this limit and give the expected behavior
> for
> >>  > the
> >>  > >> user. At the same time, the segments needed for recovery will
> remain
> >>  and
> >>  > >> there will be no data loss.
> >>  > >>
> >>  > >> 06.11.2020, 11:29, "Ivan Daschinsky" :
> >>  > >> > Guys, fisrt of all, archiving is not for PITR at all, this is
> >>  > >> optimization.
> >>  > >> > If we disable archiving, every rollover we need to create new
> file.
> >>  If
> >>  > >> we
> >>  > >> > enable archiving, we reserve 10 (by default) segments filled
> with
> >>  > >> zeroes.
> >>  > >> > We use mmap by default, so if we use no-archiver approach:
> >>  > >> > 1. We firstly create new empty file
> >>  > >> > 2. Call on it sun.nio.ch.FileChannelImpl#map, thats under the
> hood
> >>  > >> > a. If file is shorter, than wal segment size, it
> >>  > >> > calls sun.nio.ch.FileDispatcherImpl#truncate0, this is under the
> >>  hood
> >>  > >> just
> >>  > >> > a system call truncate [1]
> >>  > >> > b. Than it calls system call mmap on this
> >>  > >> > file sun.nio.ch.FileChannelImpl#map0, under the hood see [2]
> >>  > >> > These manipulation are not free and cheap. So rollover will be
> much
> >>  > much
> >>  > >> > slower.
> >>  > >> > If archiving is enabled, 10 segments are already preallocated
> at the
> >>  > >> moment
> >>  > >> > of node's start.
> >>  > >> >
> >>  > >> > When archiving is enabled, archiver just copy previous
> preallocated
> >>  > >> segment
> >>  > >> > and move it to archive directory.
> >>  > >> > This archived segment is crucial for

Re: Ignite 2.9 Announcement Blog Post

[Dmitriy Pavlov]

Ok, thanks for sharing the link.

ср, 11 нояб. 2020 г. в 00:35, Alex Plehanov :

> Dmitriy,
>
> Yes, the release was announced at announce@. See [1].
>
> [1] :
>
> https://lists.apache.org/thread.html/r2e3dbf7a055fdbc57f47c1180afea59dd8a335c8dde7a5e53885e861%40%3Cannounce.apache.org%3E
>
>
> ср, 11 нояб. 2020 г. в 00:27, Dmitriy Pavlov :
>
> > Hi Alex,
> >
> > Thank you for driving this release and this post.
> >
> > Was the release announced at announce@ ?
> >
> > Denis, Ignite veterans,
> >
> > The reason I'm asking: this release was not available at
> > https://reporter.apache.org/addrelease.html?ignite ? I've added it now.
> Is
> > it always required to add it there manually?
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > пт, 6 нояб. 2020 г. в 09:38, Alex Plehanov :
> >
> > > Igniters,
> > >
> > > Ignite 2.9 announce blog post is published now: [1]
> > >
> > > [1] : https://blogs.apache.org/ignite/entry/apache-ignite-2-9-released
> > >
> > > пт, 25 сент. 2020 г. в 11:04, Alex Plehanov :
> > >
> > > > Denis,
> > > >
> > > > Ok, I will prepare the text soon.
> > > >
> > > > чт, 24 сент. 2020 г. в 23:36, Denis Magda :
> > > >
> > > >> @Alex Plehanov 
> > > >>
> > > >> Are you interested in writing a blog post that covers the major
> > > >> improvements of the 2.9 release? It will be referenced from the
> > > >> announcement email and distributed through other channels. Examples
> of
> > > >> previous articles: https://blogs.apache.org/ignite/
> > > >>
> > > >> It happened that I was the only one who would write such an article
> > but
> > > >> will step down with pleasure if you can take over this task. Once
> the
> > > >> draft
> > > >> is ready, I'll ask a professional technical editor, who reviews my
> > > texts,
> > > >> to work with you as well.
> > > >>
> > > >> -
> > > >> Denis
> > > >>
> > > >
> > >
> >
>

Apache Ignite Board Report, Nov 11

[Dmitriy Pavlov]

Hi Igniters,

The report for the Board meeting on Nov 18 is due today.

I've appended the current version of the report at the end of the email.
The same report has been filed to the agenda.

If you feel that we can add some crucial points to the report, please let
me know. I guess I still can do some updates.

Sincerely,
Dmitriy Pavlov

## Description:
The mission of Ignite is the creation and maintenance of software related to
High-performance, integrated and distributed In-Memory Database and Caching
Platform providing in-memory data caching, partitioning, processing, and
querying components.

## Issues:
There are no issues requiring board attention.

## Membership Data:
Apache Ignite was founded 2015-08-19 (5 years ago)
There are currently 54 committers and 34 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:5.

Community changes, past quarter:
- No new PMC members. The last addition was Maxim Muzafarov on 2020-04-28.
- Sergey Stronchinskiy was added as a committer on 2020-10-14

## Project Activity:
- Major release 2.9.0 was completed on October
  (https://blogs.apache.org/ignite/entry/apache-ignite-2-9-released)
- Minor release 2.9.1 and next major release 2.10.0 are under discussion
- Community members decided to introduce Apache Ignite as a database (no
  trademark changes are expected, but the project description needs an
  update). During entering to the Incubator Ignite was In-memory data grid
- Community members discuss approaches on how to develop 3.0.0. There are
two
  options - separate repository with development of some modules from
scratch
  preserving only behavior. The alternative is to develop in evolutionary
mode
  using the existing code base changing it several times.

## Community Health:
- dev@ mailing list and amount of GitHub-related notifications are almost
the
  same.
- user@ mailing list and amount of PRs/JIRA tickets has a slight decrease
  -10...-40%
- Community members continue to write posts and run talks at online
  meetups

Re: Ignite 2.9 Announcement Blog Post

[Dmitriy Pavlov]

Hi Alex,

Thank you for driving this release and this post.

Was the release announced at announce@ ?

Denis, Ignite veterans,

The reason I'm asking: this release was not available at
https://reporter.apache.org/addrelease.html?ignite ? I've added it now. Is
it always required to add it there manually?

Sincerely,
Dmitriy Pavlov

пт, 6 нояб. 2020 г. в 09:38, Alex Plehanov :

> Igniters,
>
> Ignite 2.9 announce blog post is published now: [1]
>
> [1] : https://blogs.apache.org/ignite/entry/apache-ignite-2-9-released
>
> пт, 25 сент. 2020 г. в 11:04, Alex Plehanov :
>
> > Denis,
> >
> > Ok, I will prepare the text soon.
> >
> > чт, 24 сент. 2020 г. в 23:36, Denis Magda :
> >
> >> @Alex Plehanov 
> >>
> >> Are you interested in writing a blog post that covers the major
> >> improvements of the 2.9 release? It will be referenced from the
> >> announcement email and distributed through other channels. Examples of
> >> previous articles: https://blogs.apache.org/ignite/
> >>
> >> It happened that I was the only one who would write such an article but
> >> will step down with pleasure if you can take over this task. Once the
> >> draft
> >> is ready, I'll ask a professional technical editor, who reviews my
> texts,
> >> to work with you as well.
> >>
> >> -
> >> Denis
> >>
> >
>

Re: ApacheCon Bug Bash

[Dmitriy Pavlov]

Hi Folks,

Could you please share your vision if we need to scan our code base.

Please consider this thread as a discussion in free form.

Sincerely,
Dmitriy Pavlov

вс, 27 сент. 2020 г. в 08:14, Tom DuBuisson :

> Hello all,
>
> The ApacheCon is just around the corner which means so is the bug bash.  In
> preparations we've heard from the likes of Royale, Zookeeper, Groovy,
> Lucene, Solr, Skywalking.  Haven't heard from anyone on this list though,
> and in some cases we need to commit a CI configuration file.  Is there
> interest in participating?  Setup can be fast, we'd just need a 'yes' to
> get started.
>
> Cheers,
> Tom
>
> On Tue, Sep 22, 2020 at 3:09 PM Tom DuBuisson  wrote:
>
> > Ignite Developers,
> >
> >
> >
> > As part of our sponsorship of ApacheCon, our company MuseDev is doing a
> > Bug Bash for select Apache projects. We'll bring members of the ApacheCon
> > community together to find and fix a range of security and performance
> bugs
> > during the conference, and gameify the experience with teams, a
> > leaderboard, and prizes. The bash is open to everyone whether attending
> the
> > conference or not, and our whole dev team will also be participating to
> > help fix as many bugs as we can.
> >
> >
> >
> > We're seeding the bug list with results from Muse, our code analysis
> > platform, which runs as a Github App and comments on possible bugs as
> part
> > of the pull request workflow.  Here's an example of what it looks like:
> >
> > https://github.com/curl/curl/pull/5971#discussion_r490252196
> > <https://github.com/curl/curl/pull/5971>
> >
> >
> >
> > We explored a number of Apache projects and are reaching out because our
> > analysis through Muse found some interesting bugs that could be fixed
> > during the Bash.
> >
> >
> >
> > We're writing to see if you'd be interested in having your project
> > included in the Bash. Everything is set up on our end, and if you're
> > interested, we would need you to say yes on this listserv, and we’ll work
> > with the Apache Infrastructure team to grant Muse access to your Github
> > mirror. We'll then make sure it's all set-up and ready for the Bash. And
> of
> > course, everyone on the project is most welcome to join the Bash and help
> > us smash some bugs.
> >
> >
> > -Tom
> >
>

"When you should not use Apache Ignite", 8 Sept, Online

[Dmitriy Pavlov]

Dear Apache Ignite community members,

We are all subscribed to this list because we are interested in Apache
Ignite.  I participated in its development, and now I have the honor of
serving as VP, Apache Ignite (PMC chair).

It is quite natural to share only the benefits and strengths of your
solution, avoiding limitations. As a technical guy, I understand that this
is not really possible to create a limitless product that fits every
imaginable case.

And on September 8, 2020, I'll give a talk about cases when Apache Ignite
won't suit your needs, cases in which it is better to take something else.
Join the Apache Ignite Virtual meetup on September 8th, join to get the
zoom link and chat after the talk.

https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/272551117/

Hope to see you soon.
Have an awesome week,
Dmitriy Pavlov

Re: Apache Ignite Board report, August, 2020

[Dmitriy Pavlov]

Hi Saikat, thank you, it definitely makes sense to add.

So, the following version has been filed to the board meeting agenda.

## Description:
Apache Ignite® is a horizontally scalable, fault-tolerant distributed
in-memory computing platform for building real-time applications that can
process terabytes of data with in-memory speed

## Issues:
There are no issues requiring board attention.

## Membership Data:
Apache Ignite was founded 2015-08-19 (5 years ago)
There are currently 53 committers and 34 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:5.

Community changes, past quarter:
- No new PMC members. Last addition was Maxim Muzafarov on 2020-04-28.
- Artem Budnikov was added as committer on 2020-07-14
- Sergey Chugunov was added as committer on 2020-06-12

## Project Activity:
- Apache Ignite community is working on preparing release 2.9
- Release 3.0 discussion has been started again.
- Ignite Extensions project that decouples the core features from
   3rd-party integrations is moving forward rapidly
   https://samaitra.blogspot.com/2020/08/apache-ignite-extensions.html
- New features will be available at 2.9: Persistence cache snapshot,
   Tracing, Java Thin Client cluster discovery & compute
- Ignite documentation is being migrated from the readme.io to the
   Ignite codebase. The first version is planned to be released with Ignite
   2.9 release.

## Community Health:
- There is a decrease in mailing list traffic comparing to the previous
   quarter (-10-20%). Activity related to commits count remains stable.
- Apache Ignite users, developers, and PMC members continued to give
   talks related to the product in the C-19 situation mostly online.
   See also https://ignite.apache.org/events.html
- Community members started the Virtual Apache Ignite Meetup
   https://www.meetup.com/Apache-Ignite-Virtual-Meetup/ group that is
   envisioned as a place to meet and discuss Ignite best practices,
internals,
   use cases, share experiences.
- There is a dedicated track for Apache Ignite available at APACHECON 2020
   @Home on September 29th. https://apachecon.com/acah2020/tracks/


Thanks for feedback,

Sincerely,
Dmitriy Pavlov

вт, 11 авг. 2020 г. в 04:40, Saikat Maitra :

> Hi Dmitriy, Denis
>
> I am thinking if it would be good to add that this year a dedicated track
> for Apache Ignite is available in APACHECON 2020 @Home on September 29th.
>
> https://apachecon.com/acah2020/tracks/
>
> Regards,
> Saikat
>
> On Mon, Aug 10, 2020 at 7:18 PM Denis Magda  wrote:
>
> > >
> > > A little bit off-top: PMCs, would anybody like to be a PMC
> representative
> > > for the new group in addition to Denis M.? It is recommended to have 2
> > > members at least to make sure that an event using the Apache-project
> > brand
> > > follows branding policy and all other Apache guidelines?
> >
> >
> > This should be unnecessary from the branding perspective as long as the
> > meetup group description already follows basic trademark guidelines
> > (see, a Cassandra
> > meetup group <https://www.meetup.com/Apache-Cassandra-Bay-Area/> for
> > comparison). Based on my experience this is the primary rule to follow.
> As
> > for speakers, they are free to talk about Ignite without any approval by
> > the Ignite PMC or ASF Legal. Please let me know if I'm missing anything.
> >
> > In the future, we might need help with event coordination and
> organization
> > and will be happy to see Ignite committers and PMC members among
> > organizers. But as of now, it's premature since the group has just been
> > started.
> >
> > -
> > Denis
> >
> >
> > On Mon, Aug 10, 2020 at 2:45 PM Dmitriy Pavlov 
> wrote:
> >
> > > Hi Denis,
> > >
> > > thank you for your valuable feedback, this makes perfect sense to
> include
> > > all these points.
> > >
> > > A little bit off-top: PMCs, would anybody like to be a PMC
> representative
> > > for the new group in addition to Denis M.? It is recommended to have 2
> > > members at least to make sure that an event using the Apache-project
> > brand
> > > follows branding policy and all other Apache guidelines?
> > >
> > > Anything else to add to the report?
> > >
> > > Sincerely,
> > > Dmitriy Pavlov
> > >
> > > пн, 10 авг. 2020 г. в 23:27, Denis Magda :
> > >
> > > > Hi Dmitry,
> > > >
> > > > Thanks for sending the draft. I would suggest mentioning the
> following
> > in
> > > > the project activity section:
> > > >
> > > >- Ignite Extensions project that decouples the core features from
> > &g

Re: Apache Ignite Board report, August, 2020

[Dmitriy Pavlov]

Hi Denis,

thank you for your valuable feedback, this makes perfect sense to include
all these points.

A little bit off-top: PMCs, would anybody like to be a PMC representative
for the new group in addition to Denis M.? It is recommended to have 2
members at least to make sure that an event using the Apache-project brand
follows branding policy and all other Apache guidelines?

Anything else to add to the report?

Sincerely,
Dmitriy Pavlov

пн, 10 авг. 2020 г. в 23:27, Denis Magda :

> Hi Dmitry,
>
> Thanks for sending the draft. I would suggest mentioning the following in
> the project activity section:
>
>- Ignite Extensions project that decouples the core features from
>3rd-party integrations is being moved forward rapidly
><https://samaitra.blogspot.com/2020/08/apache-ignite-extensions.html>.
>- Community members started the Virtual Apache Ignite Meetup
><https://www.meetup.com/Apache-Ignite-Virtual-Meetup/> group that is
>envisioned as a place to meet and discuss Ignite best practices,
> internals,
>use cases, share experiences.
>- Ignite documentation is being migrated from the readme.io to the
>Ignite codebase. The first version is planned to be released with Ignite
>2.9 release.
>
> Also, I would just put the definition of Ignite from the website in the
> "description" section. That's what usually PMCs of other projects do in
> their reports:
>
> *Apache Ignite® is a horizontally scalable, fault-tolerant distributed
> in-memory computing platform for building real-time applications that can
> process terabytes of data with in-memory speed.*
>
> -
> Denis
>
>
> On Mon, Aug 10, 2020 at 12:14 PM Dmitriy Pavlov 
> wrote:
>
> > Dear Apache Ignite community,
> >
> > PMC should submit the board report, not later than 12 August.
> >
> > Previous board with drafted publicly with sharing with all developers
> > community. Let us try it one more time. Please share your thoughts on
> what
> > might be added to the board meeting agenda.
> >
> > ## Description:
> > The mission of Ignite is the creation and maintenance of software related
> > to
> > High-performance, integrated and distributed in-memory platform for
> > computing
> > and transacting on large-scale data sets in real-time
> >
> > ## Issues:
> > There are no issues requiring board attention. (hopefully)
> >
> > ## Membership Data:
> > Apache Ignite was founded 2015-08-19 (5 years ago)
> > There are currently 53 committers and 34 PMC members in this project.
> > The Committer-to-PMC ratio is roughly 7:5.
> >
> > Community changes, past quarter:
> > - No new PMC members. Last addition was Maxim Muzafarov on 2020-04-28.
> > - Artem Budnikov was added as committer on 2020-07-14
> > - Sergey Chugunov was added as committer on 2020-06-12
> >
> > ## Project Activity:
> > Apache Ignite community is working on preparing release 2.9.0.
> > Release 3.0 discussion has been resurrected.
> > Project documentation migration from readme.io to the code started.
> >
> > ## Community Health:
> > There is a decrease in mailing list traffic comparing to the previous
> > quarter (-10-20%). Activity related to code commits remains stable.
> > The first committer was elected because of merit related to the non-code
> > contribution, but efforts in the documentation.
> > Apache Ignite users, developers, and PMC members continued to give talks
> > related to the product in C-19 situation mostly online. See also
> > https://ignite.apache.org/events.html
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
>

Apache Ignite Board report, August, 2020

[Dmitriy Pavlov]

Dear Apache Ignite community,

PMC should submit the board report, not later than 12 August.

Previous board with drafted publicly with sharing with all developers
community. Let us try it one more time. Please share your thoughts on what
might be added to the board meeting agenda.

## Description:
The mission of Ignite is the creation and maintenance of software related
to
High-performance, integrated and distributed in-memory platform for
computing
and transacting on large-scale data sets in real-time

## Issues:
There are no issues requiring board attention. (hopefully)

## Membership Data:
Apache Ignite was founded 2015-08-19 (5 years ago)
There are currently 53 committers and 34 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:5.

Community changes, past quarter:
- No new PMC members. Last addition was Maxim Muzafarov on 2020-04-28.
- Artem Budnikov was added as committer on 2020-07-14
- Sergey Chugunov was added as committer on 2020-06-12

## Project Activity:
Apache Ignite community is working on preparing release 2.9.0.
Release 3.0 discussion has been resurrected.
Project documentation migration from readme.io to the code started.

## Community Health:
There is a decrease in mailing list traffic comparing to the previous
quarter (-10-20%). Activity related to code commits remains stable.
The first committer was elected because of merit related to the non-code
contribution, but efforts in the documentation.
Apache Ignite users, developers, and PMC members continued to give talks
related to the product in C-19 situation mostly online. See also
https://ignite.apache.org/events.html

Sincerely,
Dmitriy Pavlov

Re: [RESULT][VOTE] Stop Maintenance of Ignite Web Console

[Dmitriy Pavlov]

Hi Alexey,

You can commit to the GitHub mirror as well as to the original repo. The
only thing you should do it to set up a correspondence between GitHub
account and Apache account

You can do it here https://gitbox.apache.org/setup/ Please keep in mind,
additional 2FA should be enabled for the Github login.

Sincerely,
Dmitriy Pavlov

пт, 17 июл. 2020 г. в 15:24, Alexey Kuznetsov :

> Ivan, thanks!
>
> I tried to commit to GitHub mirror.
>
> On Fri, Jul 17, 2020 at 6:43 PM Ivan Pavlukhin 
> wrote:
>
> > Alexey,
> >
> > How exactly are you trying to commit? A have just committed an empty
> > README without any additional configuration. I did it directly from
> > GitHub web UI. Have you tried "real" repository address
> > https://gitbox.apache.org/repos/asf/ignite-web-console.git ?
> >
> > 2020-07-17 14:01 GMT+03:00, Alexey Kuznetsov :
> > > Dmitriy,
> > >
> > > I'm working on moving Web Console to separate repository IGNITE-13038
> > > <https://issues.apache.org/jira/browse/IGNITE-13038>,
> > >  but I can not commit to https://github.com/apache/ignite-web-console
> > >
> > > Do you know how I can be granted with commit rights?
> > >
> > > ---
> > > Alexey Kuznetsov
> > >
> >
> >
> > --
> >
> > Best regards,
> > Ivan Pavlukhin
> >
>
>
> --
> ---
> Alexey Kuznetsov
>

Re: [RESULT][VOTE] Stop Maintenance of Ignite Web Console

[Dmitriy Pavlov]

Hello,

It makes sense, thank you

Sincerely,
Dmitriy Pavlov

ср, 15 июл. 2020 г. в 17:23, Ilya Kasnacheev :

> Hello!
>
> I think that we indeed should version this change, i.e., only remove
> mentions of Web Console in the version where it's already in the attic.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> ср, 15 июл. 2020 г. в 17:17, Denis Magda :
>
> > We should remove the docs and all the mentioning from the website once
> this
> > ticket is complete:
> > https://issues.apache.org/jira/plugins/servlet/mobile#issue/IGNITE-13038
> >
> > Alex Kuznetsov, are you planning to finish the task in Ignite 2.9
> > timeframe?
> >
> > Denis
> >
> > On Wednesday, July 15, 2020, Ilya Kasnacheev 
> > wrote:
> >
> > > Hello!
> > >
> > > Well, why? I think we can keep Web Console docs for now, just add some
> > note
> > > that it is discontinued. We can also put deprecation notice here.
> > >
> > > Regards,
> > > --
> > > Ilya Kasnacheev
> > >
> > >
> > > пн, 13 июл. 2020 г. в 19:46, Dmitriy Pavlov :
> > >
> > > > Hi Folks,
> > > >
> > > > I've just found our doc still point and recommend using it.
> > > >
> > > > I suggest removing the automatic RDBMS import option from Cache-Store
> > > > documentation:
> > > > https://apacheignite.readme.io/docs/3rd-party-store#automatic
> > > >
> > > > Sincerely
> > > > Dmitriy Pavlov
> > > >
> > > > ср, 20 мая 2020 г. в 01:49, Denis Magda :
> > > >
> > > > > Igniters,
> > > > >
> > > > > The vote is over [1] with a decision to phase out Ignite Web
> Console
> > by
> > > > > moving to a separate repository and stopping its
> > > development/maintenance
> > > > > officially. The following PMC members cast +1 binding votes:
> > > > >
> > > > >- Saikat Maitra
> > > > >- Alexey Zinoviev
> > > > >- Nikolay Izhikov
> > > > >
> > > > > There are no -1 votes thus we can proceed with the tool
> > discontinuation
> > > > > procedure [2].
> > > > >
> > > > > [1]
> > > > >
> > > > >
> > > > http://apache-ignite-developers.2346864.n4.nabble.
> > > com/VOTE-Stop-Maintenance-of-Ignite-WebConsole-td47451.html
> > > > > [2] https://issues.apache.org/jira/browse/IGNITE-13038
> > > > >
> > > > > -
> > > > > Denis
> > > > >
> > > >
> > >
> >
> >
> > --
> > -
> > Denis
> >
>

New Committer: Sergey Chugunov

[Dmitriy Pavlov]

Dear Ignite Community,



The Project Management Committee (PMC) for Apache Ignite has invited Sergey
Chugunov to become a committer and we are pleased to announce that he has
accepted.



Sergey has a long story of Ignite contributions. Besides the code
contributions, Sergey has contributed the TCP Discovery Under The Hood wiki
page, posted a blog post about running Apache Ignite on AWS, and also
mentors newcomer contributors.



Being a committer enables easier contribution to the project since there is
no need to go via the patch submission process. This should enable better
productivity.



Sergey, congratulations on a new role in the Apache Ignite Community.



Best Regards,

Dmitriy Pavlov

on behalf of Apache Ignite PMC

P.S. this announce is a little bit overdue, but I guess Sergey's new role
was not announced to the community.

Re: New committer: Artem Budnikov

[Dmitriy Pavlov]

Hi Artem,

Congrats! That's good to know what we've invited committer because of
documentation effort, not just code.

Igniters,

This makes me happy especially because of CoPDoC principle (
https://community.apache.org/contributors/) which describes you may
contribute in different ways and all your efforts are appreciated..

Sincerely,
Dmitriy Pavlov

чт, 16 июл. 2020 г. в 14:19, Ilya Kasnacheev :

> Hello!
>
> The Project Management Committee for Apache Ignite project has invited
> Artem Budnikov to become a committer and we are pleased to announce that he
> has accepted.
>
> He is the person behind a monumental effort to keep Apache Ignite
> documentation neat and tidy, which he does by writing, reviewing and
> versioning most of docs on apacheignite.readme.io.
>
> Being a committer enables easier contribution to the project since it makes
> possible to merge your own, or other contributors', changes after the
> review. This should enable better productivity.
>
> On behalf of Apache Ignite PMC,
>

Re: [RESULT][VOTE] Stop Maintenance of Ignite Web Console

[Dmitriy Pavlov]

Hi Folks,

I've just found our doc still point and recommend using it.

I suggest removing the automatic RDBMS import option from Cache-Store
documentation:
https://apacheignite.readme.io/docs/3rd-party-store#automatic

Sincerely
Dmitriy Pavlov

ср, 20 мая 2020 г. в 01:49, Denis Magda :

> Igniters,
>
> The vote is over [1] with a decision to phase out Ignite Web Console by
> moving to a separate repository and stopping its development/maintenance
> officially. The following PMC members cast +1 binding votes:
>
>- Saikat Maitra
>- Alexey Zinoviev
>- Nikolay Izhikov
>
> There are no -1 votes thus we can proceed with the tool discontinuation
> procedure [2].
>
> [1]
>
> http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Stop-Maintenance-of-Ignite-WebConsole-td47451.html
> [2] https://issues.apache.org/jira/browse/IGNITE-13038
>
> -
> Denis
>

Re: [TeamCity Bot] Dependency problem: [424]: Service https://ci.ignite.apache.org/app/rest/buildQueue returned forbidden error.

[Dmitriy Pavlov]

Hi Sergey,
I've retriggered it and it worked.

Could it be a temporary issue?

Sincerely,
Dmitriy Pavlov

сб, 20 июн. 2020 г. в 14:46, Sergey Antonov :

> Hello, Igniters!
>
> I can't rerun possible blockers from the visa page [2]. I get a
> message " Dependency
> problem: [424]: Service https://ci.ignite.apache.org/app/rest/buildQueue
> returned forbidden error." when I try to rerun blockers.
>
> Can you help me with this problem? I can't use TC Bot for getting a visa.
>
> [1]
>
> https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull/7924/head=Latest
> [2] https://ibb.co/m8rW74L
> --
> BR, Sergey Antonov
>

Re: Apache Ignite 2.9.0 RELEASE [Time, Scope, Manager]

[Dmitriy Pavlov]

++1 for Alexey as a release manager, that's good we are keeping a rotation
of RMs so every committer/PMC knows how to release the code.

0 for dates, actually, it is up to contributors to propose alternatives.
All in all, it is up to the discussion's course.

Sincerely,
Dmitriy Pavlov

ср, 3 июн. 2020 г. в 14:45, Alex Plehanov :

> Hello Igniters,
>
> AI 2.8.1 is finally released and as we discussed here [1] its time to start
> the discussion about 2.9 release.
>
> I want to propose myself to be the release manager of the 2.9 release.
>
> What about release time, I agree with Maxim that we should deliver features
> as frequently as possible. If some feature doesn't fit into release dates
> we should better include it into the next release and schedule the next
> release earlier then postpone the current release.
>
> I propose the following dates for 2.9 release:
>
> Scope Freeze: June 26, 2020
> Code Freeze: July 10, 2020
> Voting Date: July 31, 2020
> Release Date: August 7, 2019
>
> WDYT?
>
> [1] :
>
> http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-Releases-Plan-td47360.html#a47575
>

Re: [DISCUSS] TC bot instructions for open source contributors

[Dmitriy Pavlov]

Hi Ivan, Igniters,

Yeah, our HTC is kind of a mile long. One try I've done to get a shorter
version is GitHub's Contributing.MD
https://github.com/apache/ignite/blob/master/CONTRIBUTING.md#contributing-to-apache-ignite


I used to share both versions - short and long to new contributors.

But I noticed we have checklist for GitHub. It is extremely essential to
have such small features, which simplifies understanding of process for
newcomers. Thank you for doing this.

Sincerely,
Dmitriy Pavlov

вт, 12 мая 2020 г. в 17:16, Ivan Pavlukhin :

> What worries me is that the page [1] is quite large. I would love to
> see a short (and sufficient enough) version for new contributors.
>
> [1] https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
>
> Best regards,
> Ivan Pavlukhin
>
> вт, 12 мая 2020 г. в 16:41, Dmitriy Pavlov :
> >
> > +1 for linking it from How to contribute  -
> > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> > to instructions related to the bot.
> >
> > May be eventually I would be able to contribute some automation into the
> > Bot to make this process easier and requiring less contributor
> > intervention.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > вт, 12 мая 2020 г. в 12:42, Ilya Kasnacheev :
> >
> > > Hello!
> > >
> > > I think it should be mentioned in [2] since this is the link we try to
> give
> > > to every new Ignite contributor.
> > >
> > > Regards.
> > > --
> > > Ilya Kasnacheev
> > >
> > >
> > > пн, 11 мая 2020 г. в 11:29, Ivan Pavlukhin :
> > >
> > > > Hi,
> > > >
> > > > Recently I faced problems explaining how a code contribution for
> > > > Ignite should be checked with TC bot. Initially I thought that this
> > > > process is well defined in our beloved contribution guidelines [1,
> 2].
> > > > But as I see neither of them explains the process directly. Finally I
> > > > found better instructions [3].
> > > >
> > > > So, the questions is should not we mention TC bot as earlier as
> > > > possible? Naively I would like to see some words about it in
> > > > CONTRIBUTING.md [1].
> > > >
> > > > Please, share your thoughts on this!
> > > >
> > > > [1] https://github.com/apache/ignite/blob/master/CONTRIBUTING.md
> > > > [2]
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> > > > [3]
> > > >
> > >
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+Teamcity+Bot#ApacheIgniteTeamcityBot-HowtocheckaPRwiththeTCBot
> > > >
> > > > Best regards,
> > > > Ivan Pavlukhin
> > > >
> > >
>

Re: [DISCUSSION] New Ignite settings for IGNITE-12438 and IGNITE-13013

[Dmitriy Pavlov]

Sorry for me being obnoxious here, but still. Mentioning ticket numbers
usually does not make a lot of sense for someone, who is outside of context
of popular/trendy tickets.

At the same time, usually contributors scan emails in the list using
subject. They decide what should go to archive and what should they read.
So, in future it may worth to replace all numbers with tickets' actual
topic/summary. People are still humans and they may be too lazy to open
tickets to decide if they need to read this topic or not.

пт, 22 мая 2020 г. в 02:48, Valentin Kulichenko <
valentin.kuliche...@gmail.com>:

> Ivan,
>
> Have you considered eliminating server to client connections altogether?
> Or, at the very least making the "client to server only" mode the default
> one?
>
> All the suggested names are confusing and not intuitive, and I doubt we
> will be able to find a good one. A server initiating a TCP connection with
> a client is confusing in the first place and creates a usability issue. We
> now want to solve it by introducing an additional configuration
> parameter, and therefore additional complexity. I don't think this is the
> right approach.
>
> What are the drawbacks of permanently switching to client-to-server
> connections? Is there any value provided by the server-to-client option?
>
> As for pair connections, I'm not sure I understand why there is a
> limitation. As far as I know, the idea behind this feature is that we
> maintain two connections between two nodes instead of one, so that every
> connection is used for communication in a single direction only. Why does
> it matter which node initiates the connection? Why can't one of the nodes
> (e.g., a client) initiate both connections, and then use them accordingly?
> Correct me if I'm wrong, but I don't see why we can't do this.
>
> -Val
>
> On Thu, May 21, 2020 at 1:58 PM Denis Magda  wrote:
>
> > Ivan,
> >
> > Considering that the setting controls the way a communication SPI
> > connection is open I would add the new parameter to CommunicationSpi
> > interface naming it as follows:
> >
> > >
> > > CommunicationSpi.connectionInitiationMode
> > > {
> > > BIDIRECTIONAL, //both clients and servers initiate a connection
> > > initiation procedure
> > > CLIENTS_TO_SERVERS //servers cannot open a connection to clients,
> > only
> > > clients can do that
> > > }
> >
> >
> > The problem with the environment type approach is that private networks
> of
> > bare-metal environments usually impose restrictions similar to virtual
> > environments powered by Kubernetes. Thus, environmentType.VIRTUALIZED
> > doesn't cover all the cases and I'm struggling to come up with a
> universal
> > alternative.
> >
> > -
> > Denis
> >
> >
> > On Thu, May 21, 2020 at 5:38 AM Ivan Bessonov 
> > wrote:
> >
> > > Hello Igniters,
> > >
> > > I'd like to discuss with you changes related to [1] and [2]. Both
> issues
> > > are mostly the same so
> > > let's discuss the core idea.
> > >
> > > *Motivation.*
> > >
> > > There are certain environments that don't allow Ignite server nodes to
> > open
> > > TCP connections to
> > > thick clients, e.g. K8S, AWS Lambda or Azure Functions. To operate in
> > such
> > > environments, the
> > > server needs a way to request a client to open an "inverse"
> communication
> > > connection to it.
> > >
> > > I've prepared a PR (still in progress) that introduces new mechanism of
> > > opening connection and
> > > related configuration.
> > >
> > > *Main idea*
> > >
> > > This mechanism is called "communication via discovery" or "inverse
> > > connection", it works as
> > > follows:
> > >  - server that needs to connect to "unreachable" thick client sends a
> > > specific Discovery message
> > >(inverse communication request) to that client;
> > >  - client node upon receiving the request opens communication
> connection
> > to
> > > that server;
> > >  - server sees connection opened by client and proceeds with its task
> > (that
> > > required opening
> > >connection to the client).
> > >
> > > Working name for new configuration parameter for this feature is
> > > environmentType, it is an
> > > enum with two values (again, working names): STANDALONE (default) and
> > > VIRTUALIZED.
> > > It is used as a hint to server to speed-up establishing of connections:
> > > when server sees a client
> > > with VIRTUALIZED environmentType it doesn't try to open connection to
> it
> > > and sends inverse
> > > communication request right away.
> > > If environmentType is STANDALONE then server tries to open a connection
> > in
> > > a regular way
> > > (iterating over all client addresses) and sends request only if all
> > > attempts failed.
> > >
> > > There is a concern about naming of the configuration as it catches only
> > one
> > > use-case: when we
> > > deal with some kind of virtualized environment like K8S.
> > > There are other options I've encountered in private discussion:
> > > - connectionMode - ALWAYS_INITIATE / 

Re: Re[2]: [DISCUSS] Ignite process exit code on node stop by failure handler

[Dmitriy Pavlov]

It seems reasonable to me. Also I would like to propose adding value of
Ignition.KILL_EXIT_CODE into javadoc using @value javadoc tag.

Dev ops/admins/anyone who admins Ignite may want to know it's value without
going to Java code.

чт, 21 мая 2020 г. в 09:39, Zhenya Stanilovsky :

>
> Thank you Sergey, as for me — very useful proposal huge +1 here.
>
>
> >Четверг, 21 мая 2020, 0:51 +03:00 от Sergey Antonov <
> antonovserge...@gmail.com>:
> >
> >I've created the Ignite ticket for this improvement [1].
> >
> >[1]  https://issues.apache.org/jira/browse/IGNITE-13047
> >
> >чт, 21 мая 2020 г. в 00:46, Sergey Antonov < antonovserge...@gmail.com >:
> >
> >> Hello, Igniters!
> >>
> >> I'd like to discuss behaviour of Ignite process exit code if the node
> was
> >> stopped by failure handler [1][2]. At the moment ignite process returns
> >> exit code 0 after the stop in all scenarios, except runtime halt by
> >> StopNodeOrHaltFH [1]. In this case, the exit code will be 130 [3]
> >>
> >> My proposal: always finish Ignite process with code [3], if a node was
> >> stopped by FH. It could be helpful for administration purposes, you can
> >> distinguish normal node stop from node stop by FH on OS level.
> >>
> >> WDYT?
> >>
> >> [1]
> >>
> https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/failure/StopNodeOrHaltFailureHandler.html
> >>
> >> [2]
> >>
> https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/failure/StopNodeFailureHandler.html
> >>
> >> [3]
> >>
> https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/Ignition.html#KILL_EXIT_CODE
> >> --
> >> BR, Sergey Antonov
> >>
> >
> >--
> >BR, Sergey Antonov
> >
>
>
>
>

Re: [DISCUSS] Apache URL for TC bot

[Dmitriy Pavlov]

Thank you, it works perfectly!

чт, 14 мая 2020 г. в 11:09, Ivan Pavlukhin :

> Petr, Ivan,
>
> Good stuff! Thank you!
>
> Best regards,
> Ivan Pavlukhin
>
> чт, 14 мая 2020 г. в 10:59, Petr Ivanov :
> >
> > https://mtcga.ignite.apache.org <https://mtcga.ignite.apache.org/> is
> set.
> >
> >
> > > On 12 May 2020, at 17:12, Ivan Pavlukhin  wrote:
> > >
> > > Yes, it sounds reasonable at the first place to research how much
> > > computing power we can get for free.
> > >
> > > Best regards,
> > > Ivan Pavlukhin
> > >
> > > вт, 12 мая 2020 г. в 16:36, Dmitriy Pavlov :
> > >>
> > >> Hi Igniters,
> > >>
> > >> Open clouds for TC Bot sounds really good, but only concern here if
> there
> > >> will be enough storage space and capabilities to run an Apache Ignite
> > >> instance there.
> > >>
> > >> Currently, TC Bot requires a lot of resources, e.g. its DB size
> >100Gb and
> > >> RAM allocated is approx 32Gb.
> > >>
> > >> Sincerely,
> > >> Dmitriy Pavlov
> > >>
> > >> вт, 12 мая 2020 г. в 15:35, Ivan Rakov :
> > >>
> > >>> Ivan,
> > >>>
> > >>> Agree.
> > >>> Mail notifications can be temporarily turned off in configuration of
> the
> > >>> new bot.
> > >>>
> > >>> On Tue, May 12, 2020 at 3:12 PM Ivan Pavlukhin 
> > >>> wrote:
> > >>>
> > >>>> Having bot deployed in open/free (and reliable) infrastructure
> sounds
> > >>>> great! One precaution which seems important to me though is
> avoidance
> > >>>> of duplicate (or even controversial) notifications from 2 bots at
> the
> > >>>> same time.
> > >>>>
> > >>>> Best regards,
> > >>>> Ivan Pavlukhin
> > >>>>
> > >>>> вт, 12 мая 2020 г. в 15:06, Ivan Rakov :
> > >>>>>
> > >>>>> Hi,
> > >>>>>
> > >>>>> I've created an INFRA ticket [1] for forwarding requests from "
> > >>>>> mtcga.ignite.apache.org" to the server where TC bot is hosted [1].
> > >>>>> Definitely, I wouldn't object if anyone will deploy TC bot to the
> > >>> public
> > >>>>> cloud. We can live with two bots for a while, and then start using
> a
> > >>>> public
> > >>>>> bot after it accumulates enough build history to grant VISAs. If
> anyone
> > >>>> is
> > >>>>> interested, please check TC bot homepage on github with setup guide
> > >>> [2].
> > >>>>> <https://github.com/apache/ignite-teamcity-bot>
> > >>>>>
> > >>>>> [1]: https://issues.apache.org/jira/browse/INFRA-20257
> > >>>>> [2]: https://github.com/apache/ignite-teamcity-bot
> > >>>>>
> > >>>>> --
> > >>>>> Best Regards,
> > >>>>> Ivan Rakov
> > >>>>>
> > >>>>> On Tue, May 12, 2020 at 12:44 PM Ilya Kasnacheev <
> > >>>> ilya.kasnach...@gmail.com>
> > >>>>> wrote:
> > >>>>>
> > >>>>>> Hello!
> > >>>>>>
> > >>>>>> It would be nice if somebody would try to bring up a parallel
> > >>>> deployment of
> > >>>>>> MTCGA bot on Apache domain.
> > >>>>>>
> > >>>>>> This way people will have a choice of using "old" or "new" bot,
> and
> > >>>> they we
> > >>>>>> may decide of sticking to one of them.
> > >>>>>>
> > >>>>>> Regards,
> > >>>>>> --
> > >>>>>> Ilya Kasnacheev
> > >>>>>>
> > >>>>>>
> > >>>>>> пн, 11 мая 2020 г. в 18:37, Maxim Muzafarov :
> > >>>>>>
> > >>>>>>> Ivan,
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> Good idea.
> > >>>>>>> +1 to have the right domain name.
> > >>>>>>>
> > >>>>>>> I can imagine that we can go even further and completely move
> > >>> TC.Bot
> > >>>>>>> to some public cloud storage. For example, Amazon can provide
> > >>>>>>> promotional credits for open source projects [1].
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> [1]
> > >>>>>>>
> > >>>>>>
> > >>>>
> > >>>
> https://aws.amazon.com/blogs/opensource/aws-promotional-credits-open-source-projects/
> > >>>>>>>
> > >>>>>>> On Mon, 11 May 2020 at 11:35, Ivan Pavlukhin <
> vololo...@gmail.com>
> > >>>>>> wrote:
> > >>>>>>>>
> > >>>>>>>> Igniters,
> > >>>>>>>>
> > >>>>>>>> As you might know currently TC bot has a domain name in a
> > >>> GridGain
> > >>>>>>>> domain [1]. What do you think should we assign a name in an
> > >>> Apache
> > >>>>>>>> domain to the bot?
> > >>>>>>>>
> > >>>>>>>> [1] https://mtcga.gridgain.com/
> > >>>>>>>>
> > >>>>>>>> Best regards,
> > >>>>>>>> Ivan Pavlukhin
> > >>>>>>>
> > >>>>>>
> > >>>>
> > >>>
> >
>

Re: [DISCUSSION] ASF Board Report Draft, May 2020

[Dmitriy Pavlov]

Here is filed version of the report:

## Description:
The mission of Ignite is the creation and maintenance of software related
to
is a horizontally scalable, fault-tolerant
distributed in-memory computing platform for building real-time
applications that can process terabytes of data with in-memory speed.

## Issues:
There are no issues requiring board attention.

## Membership Data:
Apache Ignite was founded 2015-08-19 (5 years ago)
There are currently 51 committers and 34 PMC members in this project.
The Committer-to-PMC ratio is 3:2.

Community changes, past quarter:
- Maxim Muzafarov was added to the PMC on 2020-04-28
- Slava Koptilin was added as committer on 2020-02-15
- Taras Ledkov was added as committer on 2020-05-09

## Project Activity:
- Apache Ignite 2.8.0 was released on 2020-03-03.
- Spring Boot extensions 1.0.0 was released on 2020-05-07.
- Apache Ignite 2.8.1 release is under preparation.
- Flume, Flink, and some other extensions have been migrated to the
  extensions repository.
   https://github.com/apache/ignite-extensions/tree/master/modules
- Released a new version of the Apache Ignite website:
   https://ignite.apache.org

## Community Health:
- Community prepared a public roadmap with significant improvements planned
  for the rest of 2020:
  https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+Roadmap
- Activity at development-related mailing lists (dev@, issues@,
  notifications@) increased in comparison to last quater (+30..40%). Commits
  count this quarter is slightly less (-17%)
- Community members gave 19 public online and offline presentations about
the
  project since the beginning of 2020. Around 8 talks are yet to be
presented
  and even more to follow: https://ignite.apache.org/events.html

вт, 12 мая 2020 г. в 16:44, Dmitriy Pavlov :

> Hi Denis,
>
> You are right, sending emails to bo...@apache.org is obsolete since it
> generates huge email traffic on the list. Board encourages to use 'Submit
> report to the board meeting agenda" in reporter.apache.org. Report is
> being filed there without any additional emails.
>
> I'll share final version.
>
> Sincerely,
> Dmitriy Pavlov
>
> вт, 12 мая 2020 г. в 00:16, Denis Magda :
>
>> Dmitry, thanks for taking care of this.
>>
>> Btw, I remember that the report generation UI had a sort of "Send Email"
>> checkmark that allowed us to do both - add the report to the board's
>> agenda
>> and also generate an email template for dev@ignite.apache.org. Do you
>> still
>> see such a checkmark/button? If they removed this capability from the
>> interface, would you mind sending a copy of a final report to @dev?
>>
>> -
>> Denis
>>
>>
>> On Sun, May 10, 2020 at 6:22 AM Dmitriy Pavlov 
>> wrote:
>>
>> > Hi Denis,
>> >
>> > Thank you for your valuable proposals, I appreciate it.
>> >
>> > I've updated the description. Eventually, we need to update it in the
>> ASF
>> > records, I guess at projects.apache.org. Report's description is taken
>> > from
>> > somewhere else and is auto-generated.
>> >
>> > I've added all points to project or community activities sections (e.g.
>> > talks go to the community).
>> >
>> > Since where was Spring Boot Extensions 1.0.0 release announce at the
>> list,
>> > I've added it as well to the report.
>> >
>> > The report is now filed into the board meeting agenda.
>> >
>> > Sincerely,
>> > Dmitriy Pavlov
>> >
>> >
>> > пт, 8 мая 2020 г. в 00:49, Denis Magda :
>> >
>> > > Hi Dmitry, thanks!
>> > >
>> > > Please add the following to the project activity section:
>> > >
>> > >- Released a new version of the Apache Ignite website:
>> > >https://ignite.apache.org
>> > >- Prepared a public roadmap with significant improvements planned
>> for
>> > >the rest of 2020:
>> > >
>> > >
>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+Roadmap
>> > >- Flume, flinks and some other extensions have been migrated to the
>> > >extensions repository:
>> > >https://github.com/apache/ignite-extensions/tree/master/modules
>> > >- Community members gave 19 public online and offline presentations
>> > >about the project since the beginning of 2020. Around 8 talks are
>> yet
>> > > to be
>> > >presented and even more to follow:
>> > > https://ignite.apache.org/events.html
>> > >
>> > > To my knowledge, the Spring Boot extension has been

[ANNOUNCE] New Committer: Taras Ledkov

[Dmitriy Pavlov]

Hello Ignite Community,



The Project Management Committee (PMC) for Apache Ignite has invited Taras
Ledkov to become a committer and we are pleased to announce that he has
accepted.


Taras is an Ignite SQL veteran who knows in detail current Ignite - H2
integration and binary serialization, actively participates in JDBC and
thin client protocol development, he is eager to help users on the user
list within his area of expertise.



Being a committer enables easier contribution to the project since there is
no need to go via the patch submission process. This should enable better
productivity.



Taras, thank you for all your efforts, congratulations and welcome on board!
.



Best Regards,

Dmitriy Pavlov

on behalf of Apache Ignite PMC

Re: [DISCUSSION] ASF Board Report Draft, May 2020

[Dmitriy Pavlov]

Hi Denis,

You are right, sending emails to bo...@apache.org is obsolete since it
generates huge email traffic on the list. Board encourages to use 'Submit
report to the board meeting agenda" in reporter.apache.org. Report is being
filed there without any additional emails.

I'll share final version.

Sincerely,
Dmitriy Pavlov

вт, 12 мая 2020 г. в 00:16, Denis Magda :

> Dmitry, thanks for taking care of this.
>
> Btw, I remember that the report generation UI had a sort of "Send Email"
> checkmark that allowed us to do both - add the report to the board's agenda
> and also generate an email template for dev@ignite.apache.org. Do you
> still
> see such a checkmark/button? If they removed this capability from the
> interface, would you mind sending a copy of a final report to @dev?
>
> -
> Denis
>
>
> On Sun, May 10, 2020 at 6:22 AM Dmitriy Pavlov  wrote:
>
> > Hi Denis,
> >
> > Thank you for your valuable proposals, I appreciate it.
> >
> > I've updated the description. Eventually, we need to update it in the ASF
> > records, I guess at projects.apache.org. Report's description is taken
> > from
> > somewhere else and is auto-generated.
> >
> > I've added all points to project or community activities sections (e.g.
> > talks go to the community).
> >
> > Since where was Spring Boot Extensions 1.0.0 release announce at the
> list,
> > I've added it as well to the report.
> >
> > The report is now filed into the board meeting agenda.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> >
> > пт, 8 мая 2020 г. в 00:49, Denis Magda :
> >
> > > Hi Dmitry, thanks!
> > >
> > > Please add the following to the project activity section:
> > >
> > >- Released a new version of the Apache Ignite website:
> > >https://ignite.apache.org
> > >- Prepared a public roadmap with significant improvements planned
> for
> > >the rest of 2020:
> > >
> > >
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+Roadmap
> > >- Flume, flinks and some other extensions have been migrated to the
> > >extensions repository:
> > >https://github.com/apache/ignite-extensions/tree/master/modules
> > >- Community members gave 19 public online and offline presentations
> > >about the project since the beginning of 2020. Around 8 talks are
> yet
> > > to be
> > >presented and even more to follow:
> > > https://ignite.apache.org/events.html
> > >
> > > To my knowledge, the Spring Boot extension has been already released (
> > > https://apacheignite-mix.readme.io/docs/spring-boot). @Nikolay Izhikov
> > > , is it ready to be announced?
> > >
> > > Also, I would suggest using this as a definition of the project (what
> > > Ignite is) - Apache Ignite® is a horizontally scalable, fault-tolerant
> > > distributed in-memory computing platform for building real-time
> > > applications that can process terabytes of data with in-memory speed.
> > >
> > > -
> > > Denis
> > >
> > >
> > > On Thu, May 7, 2020 at 7:46 AM Dmitriy Pavlov 
> > wrote:
> > >
> > > > Hi Igniters,
> > > >
> > > > To increase involvement of each member of the community and increase
> > > > transparency I'd like to share report draft for ASF board with all
> dev@
> > > > community. Thanks to Ivan P. for this idea.
> > > >
> > > > What would you like to add to this report? Major features, events,
> > > popular
> > > > publications could be mentioned in the report (main manual sections
> are
> > > > community and project activity, and issues - if any). Let's make it
> > more
> > > > representative and useful. I'm going to publish it during weekend.
> > Please
> > > > find report draft below and share your thoughts.
> > > >
> > > > Sincerely,
> > > > Dmitriy Pavlov
> > > >
> > > > ## Description:
> > > > The mission of Ignite is the creation and maintenance of software
> > related
> > > > to
> > > > High-performance, integrated and distributed in-memory platform for
> > > > computing
> > > > and transacting on large-scale data sets in real-time
> > > >
> > > > ## Issues:
> > > > There are no issues requiring board attention.
> > > >
> > > > ## Membership Data:
> > > > Apache Ignite was founded 2015-08-19 (5 years ago)
> > > > There are currently 50 committers and 34 PMC members in this project.
> > > > The Committer-to-PMC ratio is roughly 7:5.
> > > >
> > > > Community changes, past quarter:
> > > > - Maxim Muzafarov was added to the PMC on 2020-04-28
> > > > - Slava Koptilin was added as committer on 2020-02-15
> > > >
> > > > ## Project Activity:
> > > > 2.8.0 was released on 2020-03-03.
> > > > Spring boot starter was voted to be released.
> > > > Apache Ignite 2.8.1  release is under preparation.
> > > >
> > > > ## Community Health:
> > > > Activity at development related mailing lists (dev@, issues@,
> > > > notifications@)
> > > >
> > > > increased in compare to past quarter (+30..40%)
> > > > Commits count this quarter is slightly less (-17%)
> > > >
> > >
> >
>

Re: [DISCUSS] TC bot instructions for open source contributors

[Dmitriy Pavlov]

+1 for linking it from How to contribute  -
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
to instructions related to the bot.

May be eventually I would be able to contribute some automation into the
Bot to make this process easier and requiring less contributor
intervention.

Sincerely,
Dmitriy Pavlov

вт, 12 мая 2020 г. в 12:42, Ilya Kasnacheev :

> Hello!
>
> I think it should be mentioned in [2] since this is the link we try to give
> to every new Ignite contributor.
>
> Regards.
> --
> Ilya Kasnacheev
>
>
> пн, 11 мая 2020 г. в 11:29, Ivan Pavlukhin :
>
> > Hi,
> >
> > Recently I faced problems explaining how a code contribution for
> > Ignite should be checked with TC bot. Initially I thought that this
> > process is well defined in our beloved contribution guidelines [1, 2].
> > But as I see neither of them explains the process directly. Finally I
> > found better instructions [3].
> >
> > So, the questions is should not we mention TC bot as earlier as
> > possible? Naively I would like to see some words about it in
> > CONTRIBUTING.md [1].
> >
> > Please, share your thoughts on this!
> >
> > [1] https://github.com/apache/ignite/blob/master/CONTRIBUTING.md
> > [2] https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> > [3]
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+Teamcity+Bot#ApacheIgniteTeamcityBot-HowtocheckaPRwiththeTCBot
> >
> > Best regards,
> > Ivan Pavlukhin
> >
>

Re: [DISCUSS] Apache URL for TC bot

[Dmitriy Pavlov]

Hi Igniters,

Open clouds for TC Bot sounds really good, but only concern here if there
will be enough storage space and capabilities to run an Apache Ignite
instance there.

Currently, TC Bot requires a lot of resources, e.g. its DB size >100Gb and
RAM allocated is approx 32Gb.

Sincerely,
Dmitriy Pavlov

вт, 12 мая 2020 г. в 15:35, Ivan Rakov :

> Ivan,
>
> Agree.
> Mail notifications can be temporarily turned off in configuration of the
> new bot.
>
> On Tue, May 12, 2020 at 3:12 PM Ivan Pavlukhin 
> wrote:
>
> > Having bot deployed in open/free (and reliable) infrastructure sounds
> > great! One precaution which seems important to me though is avoidance
> > of duplicate (or even controversial) notifications from 2 bots at the
> > same time.
> >
> > Best regards,
> > Ivan Pavlukhin
> >
> > вт, 12 мая 2020 г. в 15:06, Ivan Rakov :
> > >
> > > Hi,
> > >
> > > I've created an INFRA ticket [1] for forwarding requests from "
> > > mtcga.ignite.apache.org" to the server where TC bot is hosted [1].
> > > Definitely, I wouldn't object if anyone will deploy TC bot to the
> public
> > > cloud. We can live with two bots for a while, and then start using a
> > public
> > > bot after it accumulates enough build history to grant VISAs. If anyone
> > is
> > > interested, please check TC bot homepage on github with setup guide
> [2].
> > > <https://github.com/apache/ignite-teamcity-bot>
> > >
> > > [1]: https://issues.apache.org/jira/browse/INFRA-20257
> > > [2]: https://github.com/apache/ignite-teamcity-bot
> > >
> > > --
> > > Best Regards,
> > > Ivan Rakov
> > >
> > > On Tue, May 12, 2020 at 12:44 PM Ilya Kasnacheev <
> > ilya.kasnach...@gmail.com>
> > > wrote:
> > >
> > > > Hello!
> > > >
> > > > It would be nice if somebody would try to bring up a parallel
> > deployment of
> > > > MTCGA bot on Apache domain.
> > > >
> > > > This way people will have a choice of using "old" or "new" bot, and
> > they we
> > > > may decide of sticking to one of them.
> > > >
> > > > Regards,
> > > > --
> > > > Ilya Kasnacheev
> > > >
> > > >
> > > > пн, 11 мая 2020 г. в 18:37, Maxim Muzafarov :
> > > >
> > > > > Ivan,
> > > > >
> > > > >
> > > > > Good idea.
> > > > > +1 to have the right domain name.
> > > > >
> > > > > I can imagine that we can go even further and completely move
> TC.Bot
> > > > > to some public cloud storage. For example, Amazon can provide
> > > > > promotional credits for open source projects [1].
> > > > >
> > > > >
> > > > > [1]
> > > > >
> > > >
> >
> https://aws.amazon.com/blogs/opensource/aws-promotional-credits-open-source-projects/
> > > > >
> > > > > On Mon, 11 May 2020 at 11:35, Ivan Pavlukhin 
> > > > wrote:
> > > > > >
> > > > > > Igniters,
> > > > > >
> > > > > > As you might know currently TC bot has a domain name in a
> GridGain
> > > > > > domain [1]. What do you think should we assign a name in an
> Apache
> > > > > > domain to the bot?
> > > > > >
> > > > > > [1] https://mtcga.gridgain.com/
> > > > > >
> > > > > > Best regards,
> > > > > > Ivan Pavlukhin
> > > > >
> > > >
> >
>

Re: [DISCUSSION] ASF Board Report Draft, May 2020

[Dmitriy Pavlov]

Hi Denis,

Thank you for your valuable proposals, I appreciate it.

I've updated the description. Eventually, we need to update it in the ASF
records, I guess at projects.apache.org. Report's description is taken from
somewhere else and is auto-generated.

I've added all points to project or community activities sections (e.g.
talks go to the community).

Since where was Spring Boot Extensions 1.0.0 release announce at the list,
I've added it as well to the report.

The report is now filed into the board meeting agenda.

Sincerely,
Dmitriy Pavlov


пт, 8 мая 2020 г. в 00:49, Denis Magda :

> Hi Dmitry, thanks!
>
> Please add the following to the project activity section:
>
>- Released a new version of the Apache Ignite website:
>https://ignite.apache.org
>- Prepared a public roadmap with significant improvements planned for
>the rest of 2020:
>
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+Roadmap
>- Flume, flinks and some other extensions have been migrated to the
>extensions repository:
>https://github.com/apache/ignite-extensions/tree/master/modules
>- Community members gave 19 public online and offline presentations
>about the project since the beginning of 2020. Around 8 talks are yet
> to be
>presented and even more to follow:
> https://ignite.apache.org/events.html
>
> To my knowledge, the Spring Boot extension has been already released (
> https://apacheignite-mix.readme.io/docs/spring-boot). @Nikolay Izhikov
> , is it ready to be announced?
>
> Also, I would suggest using this as a definition of the project (what
> Ignite is) - Apache Ignite® is a horizontally scalable, fault-tolerant
> distributed in-memory computing platform for building real-time
> applications that can process terabytes of data with in-memory speed.
>
> -
> Denis
>
>
> On Thu, May 7, 2020 at 7:46 AM Dmitriy Pavlov  wrote:
>
> > Hi Igniters,
> >
> > To increase involvement of each member of the community and increase
> > transparency I'd like to share report draft for ASF board with all dev@
> > community. Thanks to Ivan P. for this idea.
> >
> > What would you like to add to this report? Major features, events,
> popular
> > publications could be mentioned in the report (main manual sections are
> > community and project activity, and issues - if any). Let's make it more
> > representative and useful. I'm going to publish it during weekend. Please
> > find report draft below and share your thoughts.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > ## Description:
> > The mission of Ignite is the creation and maintenance of software related
> > to
> > High-performance, integrated and distributed in-memory platform for
> > computing
> > and transacting on large-scale data sets in real-time
> >
> > ## Issues:
> > There are no issues requiring board attention.
> >
> > ## Membership Data:
> > Apache Ignite was founded 2015-08-19 (5 years ago)
> > There are currently 50 committers and 34 PMC members in this project.
> > The Committer-to-PMC ratio is roughly 7:5.
> >
> > Community changes, past quarter:
> > - Maxim Muzafarov was added to the PMC on 2020-04-28
> > - Slava Koptilin was added as committer on 2020-02-15
> >
> > ## Project Activity:
> > 2.8.0 was released on 2020-03-03.
> > Spring boot starter was voted to be released.
> > Apache Ignite 2.8.1  release is under preparation.
> >
> > ## Community Health:
> > Activity at development related mailing lists (dev@, issues@,
> > notifications@)
> >
> > increased in compare to past quarter (+30..40%)
> > Commits count this quarter is slightly less (-17%)
> >
>

Re: [DISCUSS] Remove TC badge from README.md

[Dmitriy Pavlov]

IMO, we can remove. This badge does not work since GitHub started to
cache images. Now TC's status .SVG does not work properly.

чт, 7 мая 2020 г. в 09:25, Ivan Pavlukhin :

> Folks,
>
> I created a ticket [1] and prepared PR with magic number =).
>
> Please review.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-12987
>
> Best regards,
> Ivan Pavlukhin
>
> пн, 4 мая 2020 г. в 10:01, Ivan Pavlukhin :
> >
> > Hi Igniters,
> >
> > Inspired by a neighbor thread about PR checks [1]. It brought my
> > attention that now we have a neat Travis badge and a strange TC badge
> > which is not very useful from a first glance.
> >
> > What do you think, is it ought to completely remove TC badge from readme?
> >
> > [1]
> https://lists.apache.org/thread.html/r1580e2fb23728e83afbe1bad2b4cf7e9cece0e19a1d305e5755d7dd1%40%3Cdev.ignite.apache.org%3E
> >
> > Best regards,
> > Ivan Pavlukhin
>

[DISCUSSION] ASF Board Report Draft, May 2020

[Dmitriy Pavlov]

Hi Igniters,

To increase involvement of each member of the community and increase
transparency I'd like to share report draft for ASF board with all dev@
community. Thanks to Ivan P. for this idea.

What would you like to add to this report? Major features, events, popular
publications could be mentioned in the report (main manual sections are
community and project activity, and issues - if any). Let's make it more
representative and useful. I'm going to publish it during weekend. Please
find report draft below and share your thoughts.

Sincerely,
Dmitriy Pavlov

## Description:
The mission of Ignite is the creation and maintenance of software related
to
High-performance, integrated and distributed in-memory platform for
computing
and transacting on large-scale data sets in real-time

## Issues:
There are no issues requiring board attention.

## Membership Data:
Apache Ignite was founded 2015-08-19 (5 years ago)
There are currently 50 committers and 34 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:5.

Community changes, past quarter:
- Maxim Muzafarov was added to the PMC on 2020-04-28
- Slava Koptilin was added as committer on 2020-02-15

## Project Activity:
2.8.0 was released on 2020-03-03.
Spring boot starter was voted to be released.
Apache Ignite 2.8.1  release is under preparation.

## Community Health:
Activity at development related mailing lists (dev@, issues@, notifications@)

increased in compare to past quarter (+30..40%)
Commits count this quarter is slightly less (-17%)

Re: [DISCUSSION] Ignite WebConsole Deprecation

[Dmitriy Pavlov]

Hi Igniters,

Only whole project may go to the attic. Main reason of moving project to
the attic is inactive community and less than 3 PMC members voting for new
release.
So attic is more about waiting for new community to resurrect project, and
less about codebase.

I suggest us, as always, create new repo and state that development of the
module was discontinued, for now.

Additionally, discontinuation is essential and really major community-wide
decision, it requires formal vote to be run after this discussion. I'm sure
if we build consensus in advance, here in the discussion, vote would be
just formality, but it is still needed.

Sincerely,
Dmitriy Pavlov


чт, 7 мая 2020 г. в 12:34, Ilya Kasnacheev :

> Hello!
>
> I think we should move it to a separate repository, but not Attic.
>
> I can see the scenario where there would be recurrence of interest to this
> tool and somebody may step in to update it.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> ср, 6 мая 2020 г. в 22:20, Denis Magda :
>
> > Folks,
> >
> > Personally, I like the idea of Apache Attic [1] suggested by Saikat. We
> are
> > not discontinuing Ignite WebConsole because it became useless like it was
> > with Hadoop Accelerator. The tool has good capabilities such as the
> > configuration wizard, and the only problem is that we no longer want to
> > support or maintain this technology (while it has the right to exist).
> >
> > Is anybody interested in figuring out with the ASF-mates if Ignite
> > WebConsole can be accepted to Attic? The Attic's guidelines talk about an
> > ASF project as a whole and not about individual components.
> >
> > [1] https://attic.apache.org
> >
> > -
> > Denis
> >
> >
> > On Wed, May 6, 2020 at 7:20 AM Вячеслав Коптилин <
> slava.kopti...@gmail.com
> > >
> > wrote:
> >
> > > Hello,
> > >
> > > +1 to remove this component or move it to a separate repository if
> > someone
> > > wants to maintain it.
> > > In case the web console provides useful features, we should consider
> how
> > to
> > > add them to our command-line utilities, if possible.
> > >
> > > Thanks,
> > > Slava.
> > >
> > > ср, 6 мая 2020 г. в 16:10, Nikolay Izhikov :
> > >
> > > > Hello.
> > > >
> > > > +1 to remove any graphical utilities from the Ignite core.
> > > > I think we should maintain and support only cmd, JMX, and other
> «core»
> > > > tools.
> > > >
> > > > We shouldn't waste our resources on supporting pretty looking UI
> tools.
> > > >
> > > >
> > > > > 2 мая 2020 г., в 04:05, Saikat Maitra 
> > > > написал(а):
> > > > >
> > > > > Hello Denis,
> > > > >
> > > > > I am thinking if we should move web-console to a separate repo like
> > > > > ignite-web-console. In my opinion the tech stack we have in
> > web-console
> > > > > like npm, nodejs and Mondodb etc are little different and can be
> > hosted
> > > > as
> > > > > a separate project in a git repo.
> > > > >
> > > > > I had used web-console for streamers project and found it helpful
> in
> > > > > creating table schema and execute sql queries and also to do cache
> > > > lookup.
> > > > >
> > > > > https://github.com/samaitra/streamers
> > > > >
> > > > > If we continue to find that usage of ignite-web-console is limited
> > then
> > > > we
> > > > > can plan moving ignite-web-console in Apache Attic
> > > > >
> > > > > https://attic.apache.org/
> > > > >
> > > > > Please let me know your thoughts.
> > > > >
> > > > > Regards,
> > > > > Saikat
> > > > >
> > > > >
> > > > >
> > > > > On Fri, May 1, 2020 at 12:43 PM Denis Magda 
> > wrote:
> > > > >
> > > > >> Igniters,
> > > > >>
> > > > >> I would like to hear your opinion on what we should do with Ignite
> > > > >> WebConsole.
> > > > >>
> > > > >> To my knowledge, we don't have active maintainers of the
> component,
> > > and
> > > > a
> > > > >> list of issues is piling up [1]. Users even report that the docker
> > > > images
> > > > >> have not been updated for more than a year [2].
> > > > >>
> > > > >> Personally, I share the opinion of those who believe the community
> > > > needs to
> > > > >> provide and support all the essential tooling (metrics and tracing
> > > API,
> > > > >> command-line tool) while the UI tools are not our business. There
> > is a
> > > > >> myriad of UI tools Ignite can be monitored and traced with. Users
> > > > already
> > > > >> have plenty of choices.
> > > > >>
> > > > >> What are your thoughts? Probably, some of you want to become
> > > > maintainers of
> > > > >> the component. Otherwise, we should let the tool go.
> > > > >>
> > > > >> [1]
> > > > >>
> > > > >>
> > > >
> > >
> >
> https://issues.apache.org/jira/browse/IGNITE-12923?jql=project%20%3D%20IGNITE%20AND%20text%20~%20%22web%20console%22%20AND%20status%20%3D%20Open%20and%20type%20%3D%20Bug%20ORDER%20BY%20createdDate%20
> > > > >> [2] https://issues.apache.org/jira/browse/IGNITE-12923
> > > > >>
> > > > >> -
> > > > >> Denis
> > > > >>
> > > >
> > > >
> > >
> >
>

[ANNOUNCE] New PMC member: Maxim Muzafarov

[Dmitriy Pavlov]

The Project Management Committee (PMC) for Apache Ignite

has invited Maxim Muzafarov to become new PMC member and we are pleased to
announce that he has accepted.



Maxim is active dev list participant, speaker at meetups, and contributes
to additional checks of the product using travis and started new file
rebalance. Maxim did a fantastic job to make release 2.8 possible



Being a PMC member enables assistance with the management

and to guide the direction of the project.

Maxim, congrats with new role and keep the pace !



Best Regards,

Dmitriy Pavlov

on behalf of Apache Ignite PMC

Re: [MTCGA]: new failures in builds [5251854, 5251851] needs to be handled

[Dmitriy Pavlov]

My best guess it is related to  IGNITE-12853
 : Introduced features
for the thin client protocol

Build details
https://ci.ignite.apache.org/viewLog.html?buildId=5254068=Inspection=IgniteTests24Java8_PlatformNetInspections


says that srvVer is missed in the configuration. And this field is
mentioned in the PR for IGNITE-12853


пт, 24 апр. 2020 г. в 06:08, :

> Hi Igniters,
>
>  I've detected some new issue on TeamCity to be handled. You are more than
> welcomed to help.
>
>  If your changes can lead to this failure(s): We're grateful that you were
> a volunteer to make the contribution to this project, but things change and
> you may no longer be able to finalize your contribution.
>  Could you respond to this email and indicate if you wish to continue and
> fix test failures or step down and some committer may revert you commit.
>
>  *New Critical Failure in master Platform .NET (NuGet)*
> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PlatformNetNuGet?branch=%3Cdefault%3E
>  Changes may lead to failure were done by
>  - igor sapego 
> https://ci.ignite.apache.org/viewModification.html?modId=900989
>  - pavel pereslegin 
> https://ci.ignite.apache.org/viewModification.html?modId=900984
>  - nikita amelchev 
> https://ci.ignite.apache.org/viewModification.html?modId=900986
>
>  *New Critical Failure in master Platform .NET (Inspections)*
> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PlatformNetInspections?branch=%3Cdefault%3E
>  Changes may lead to failure were done by
>  - igor sapego 
> https://ci.ignite.apache.org/viewModification.html?modId=900989
>  - pavel pereslegin 
> https://ci.ignite.apache.org/viewModification.html?modId=900984
>  - nikita amelchev 
> https://ci.ignite.apache.org/viewModification.html?modId=900986
>
>  - Here's a reminder of what contributors were agreed to do
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
>  - Should you have any questions please contact
> dev@ignite.apache.org
>
> Best Regards,
> Apache Ignite TeamCity Bot
> https://github.com/apache/ignite-teamcity-bot
> Notification generated at 06:07:28 24-04-2020
>

Re: [DISCUSSION] Major changes in Ignite in 2020

[Dmitriy Pavlov]

Hi Denis,

Thank you for driving this.

Igniters,

I would suggest to stress that Apache Ignite community does not guarantee
these features to be available.

Can we add some kind of disclaimer that says Ignite Roadmap does not imply
any obligations regarding availability and timeline. A number of
contributions can be done on best efforts principle, it is always tricky to
make a promise.

Sincerely,
Dmitriy Pavlov

чт, 23 апр. 2020 г. в 00:06, Denis Magda :

> Igniters,
>
> Here is a draft of our very first roadmap. I decided to make it damp simple
> but descriptive:
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+Roadmap
>
> What we need to do next is to:
>
>- Fill in the "Readiness Estimated Time" column with your best guess of
>when an improvement is to be ready for a release.
>- Add references to JIRAs or IEPs to the first column.
>- Add the names of those contributors who will be cooperating with you
>during development. Goes to the "Contributors" column.
>
> Once this step is complete, we'll see how many features converge around the
> same date/months and we'll plan through 2.9, 2.10, etc. releases
> accordingly.
>
> Please don't put this aside for a while, let's move on quicker. If the
> roadmap misses any contributions that you are going to add, then edit the
> wiki page.
>
> -
> Denis
>
>
> On Wed, Apr 15, 2020 at 3:35 AM Nikita Amelchev 
> wrote:
>
> > Hello, Igniters.
> >
> > I am going to contribute a new feature - profiling tool and
> > performance report. This is part of IEP-35. [1]
> >
> > The tool will be able to collect performance statistics and create a
> > human-readable report. It will help to analyze workload and to tune
> > configuration and applications.
> >
> > Example of report [2, 3, 4].
> >
> > [1]
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Cluster+performance+profiling+tool
> > [2]
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Cluster+performance+profiling+tool?preview=/145723859/148647581/p1.png
> > [3]
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Cluster+performance+profiling+tool?preview=/145723859/148647582/p2.png
> > [4]
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Cluster+performance+profiling+tool?preview=/145723859/148647583/p3.png
> >
> > сб, 11 апр. 2020 г. в 13:54, Alexei Scherbakov <
> > alexey.scherbak...@gmail.com>:
> > >
> > > Folks,
> > >
> > > I keep working on tasks related to data consistency.
> > >
> > > This includes:
> > >
> > > Lost partitions handling overhaul (almost done) and tombstones support
> > > aforementioned by Ivan Rakov
> > > Atomic protocol overhaul (see [1])
> > >
> > > The ultimate goal of the year is to prepare Ignite for passing Jepsen
> > tests.
> > >
> > > [1]
> > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-12+Make+ATOMIC+Caches+Consistent+Again
> > >
> > >
> > > пт, 10 апр. 2020 г. в 18:49, Denis Magda :
> > >
> > > > Steven,
> > > >
> > > > Please start a dedicated discussion for the Golang support. At the
> > moment,
> > > > I'm not aware if anybody from the community planned to provide
> support
> > > > out-of-the-box. However, that's not a tricky task thanks to Ignite's
> > binary
> > > > protocol that lets enable any programming language support easily.
> > > >
> > > > -
> > > > Denis
> > > >
> > > >
> > > > On Fri, Apr 10, 2020 at 8:43 AM smeadows-abb <
> > steven.mead...@us.abb.com>
> > > > wrote:
> > > >
> > > > > First thanks for your quick response.
> > > > >
> > > > > I looked at  https://github.com/amsokol/ignite-go-client and its
> NOT
> > > > > completed and nothing has been for last 16 months. Initial test
> with
> > > > > package
> > > > > failed, so trying to determine your project roadmap with regards to
> > > > Golang
> > > > > and maybe Rust support.
> > > > >
> > > > > I'm NOT sure of 'AFAIK' ?
> > > > >
> > > > > We may need to implement your Restful API to provide support for
> > Golang
> > > > and
> > > > > Rust, provided it's complete?
> > > > >
> > > > > Thanks,
> > > > >   Steve
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> > > > >
> > > >
> > >
> > >
> > > --
> > >
> > > Best regards,
> > > Alexei Scherbakov
> >
> >
> >
> > --
> > Best wishes,
> > Amelchev Nikita
> >
>

Re: [jira] [Created] (IGNITE-12911) B+Tree Corrupted exception when using a key extracted from a value object --- and SQL enabled.

[Dmitriy Pavlov]

Folks,  could you please take a look at this issue?

It seems quite serious if we can potentially get B+Tree corrupted.

Sincerely,
Dmitriy Pavlov

пт, 17 апр. 2020 г. в 19:25, Alexander Korenshteyn (Jira) :

> Alexander Korenshteyn created IGNITE-12911:
> --
>
>  Summary: B+Tree Corrupted exception when using a key
> extracted from a value object --- and SQL enabled.
>  Key: IGNITE-12911
>  URL: https://issues.apache.org/jira/browse/IGNITE-12911
>  Project: Ignite
>   Issue Type: Bug
>   Components: cache, sql
> Reporter: Alexander Korenshteyn
>  Attachments: Employee.java, EmployeeId.java, ServerNode.java
>
> If a key is part of the value like so:
> class key \{ ... }
>
> class value {
> private Key key
> getKey()
> }
>
> cache = ignite.cache()*.withKeepBinary()*
>
> the following scenario yields a B+ Tree exception:
>
> 1. *Enable SQL via annotations or QueryEntities.*
>
> key1= new Key()
> value1 = new Value(key1)
>
> cache.put(key1, value1)
>
> BinaryObject val2 = cache.get(key1)
> BinaryObject key2 = val2.field("key")
>
> *cache.put(key2, emp1); // CRASH!!! CorruptedTreeException: B+Tree
> iscorrupted ...*
>
> user list:
> [
> http://apache-ignite-users.70518.x6.nabble.com/Ignite-crashes-with-CorruptedTreeException-quot-B-Tree-is-corrupted-quot-on-a-composite-BinaryObjecto-tc32032.html
> ]
>
> *Reproducer – attached*
>
>
>
> Exception:
>
>  [2020-04-17 11:24:33,475][ERROR][main][root] Critical system error
> detected. Will be handled accordingly to configured handler
> [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
> super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
> [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
> failureCtx=FailureContext [type=CRITICAL_ERROR, err=class
> o.a.i.i.processors.cache.persistence.tree.CorruptedTreeException: B+Tree is
> corrupted [pages(groupId, pageId)=[IgniteBiTuple [val1=1258113742,
> val2=844420635164673]], cacheId=1976096430, cacheName=EMPLOYEE,
> indexName=_key_PK, msg=Runtime failure on row: Row@2233cac0[ key:
> model.EmployeeId [idHash=1744523301, hash=674030145,
> employeeNumber=65348765, departmentNumber=123], val: model.Employee
> [idHash=382762227, hash=1627745429, firstName=John, lastName=Smith,
> id=model.EmployeeId [idHash=2021540695, hash=674030145,
> employeeNumber=65348765, departmentNumber=123]] ][ John, Smith 
>
> class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> B+Tree is corrupted [pages(groupId, pageId)=[IgniteBiTuple
> [val1=1258113742, val2=844420635164673]], cacheId=1976096430,
> cacheName=EMPLOYEE, indexName=_key_PK, msg=Runtime failure on row:
> Row@2233cac0[ key: model.EmployeeId [idHash=1744523301, hash=674030145,
> employeeNumber=65348765, departmentNumber=123], val: model.Employee
> [idHash=382762227, hash=1627745429, firstName=John, lastName=Smith,
> id=model.EmployeeId [idHash=2021540695, hash=674030145,
> employeeNumber=65348765, departmentNumber=123]] ][ John, Smith ]]
>
>  at
> org.apache.ignite.internal.processors.query.h2.database.H2Tree.corruptedTreeException(H2Tree.java:836)
>
>  at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2447)
>
>  at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putx(BPlusTree.java:2394)
>
>  at
> org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.putx(H2TreeIndex.java:437)
>
>  at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.update(GridH2Table.java:756)
>
>  at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.store(IgniteH2Indexing.java:363)
>
>  at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.store(GridQueryProcessor.java:2016)
>
>  at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.store(GridCacheQueryManager.java:401)
>
>  at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.finishUpdate(IgniteCacheOffheapManagerImpl.java:2555)
>
>  at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke0(IgniteCacheOffheapManagerImpl.java:1664)
>
>  at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1639)
>
>  at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:436)
>
>  at
> org.apache.ignite.int

Re: Moving python, php and node.js in separate repos and release cycles

[Dmitriy Pavlov]

Hi Folks,

There is nothing wrong with releasing system by it's modules, one-by-one.
Also it is perfectly OK to have each module in a separate git repo. Each of
these module release-candidate is voted separately. At the foundation
level, release cycle of the project/modules is not defined, it is up to the
community to decide. It is just general common sense: often  releases are
preferred.

The only one rule, community should vote on release with 3 +1 votes from
the PMC members. And there can be the only issue if module release would
stall without required number of binding votes.

Sincerely,
Dmitriy Pavlov

ср, 22 апр. 2020 г. в 15:03, Igor Sapego :

> Pavel,
>
> 1. We can conduct separate votes for every client, do you see any issues
> here?
> 2. This is true, but we have backward compatibility in our protocol, so
> everything
> should work just fine.
>
> Best Regards,
> Igor
>
>
> On Tue, Apr 21, 2020 at 9:22 PM Pavel Tupitsyn 
> wrote:
>
> > -1
> >
> > - Ignite is a single Apache project, it follows Apache release
> guidelines,
> > with voting and so on. Not sure how are we going to follow that with a
> > separate repo.
> > - Thin client features are often tied to server-side changes
> >
> > > What about dotnet and cpp thin clients?
> > Those reuse some code with thick counterparts - same way as Java thin
> does.
> >
> >
> > On Tue, Apr 21, 2020 at 4:22 PM Nikolay Izhikov 
> > wrote:
> >
> > > What about dotnet and cpp thin clients?
> > >
> > > > 21 апр. 2020 г., в 16:19, Dmitriy Pavlov 
> > > написал(а):
> > > >
> > > > +1 since
> > > > - Simpler release may allow us to release more often
> > > > - Often releases - users will get updates faster, more chances to
> grow
> > > and
> > > > keep our user base
> > > > - Faster updates and easy to get next update may have positive effect
> > on
> > > > community growth. Since newcomer may want to fix a bug and later use
> > > result
> > > > in his/her production environment.
> > > >
> > > > вт, 21 апр. 2020 г. в 13:27, Alexey Zinoviev  >:
> > > >
> > > >> Agree with these non-JVM languages.
> > > >> Especially for Python:)
> > > >>
> > > >> вт, 21 апр. 2020 г. в 12:58, Igor Sapego :
> > > >>
> > > >>> Guys,
> > > >>>
> > > >>> It was discussed on the dev list a few times that it would be a
> good
> > > >>> idea to move Python, Node.js and PHP thin clients to separate repos
> > > >>> and separate release cycles.
> > > >>>
> > > >>> In short there are several arguments for that:
> > > >>>
> > > >>> 1. There are no dependencies on the core functionality so there is
> > > simply
> > > >>> no need for them to be in the main repo.
> > > >>>
> > > >>> 2. Those thin clients often do not get updates from release to
> > release,
> > > >> but
> > > >>> still
> > > >>> we "release" them, as they are a part of the main release.
> > > >>>
> > > >>> 3. Moving them to a separate release cycle will allow us to release
> > > some
> > > >>> hot
> > > >>> fixes for those clients faster and easier.
> > > >>>
> > > >>> 4. Composer needs a PHP packet that is released to be in a separate
> > > >>> repository.
> > > >>>
> > > >>> Thoughts?
> > > >>>
> > > >>> Best Regards,
> > > >>> Igor
> > > >>>
> > > >>
> > >
> > >
> >
>

Re: Moving python, php and node.js in separate repos and release cycles

[Dmitriy Pavlov]

+1 since
- Simpler release may allow us to release more often
- Often releases - users will get updates faster, more chances to grow and
keep our user base
- Faster updates and easy to get next update may have positive effect on
community growth. Since newcomer may want to fix a bug and later use result
in his/her production environment.

вт, 21 апр. 2020 г. в 13:27, Alexey Zinoviev :

> Agree with these non-JVM languages.
> Especially for Python:)
>
> вт, 21 апр. 2020 г. в 12:58, Igor Sapego :
>
> > Guys,
> >
> > It was discussed on the dev list a few times that it would be a good
> > idea to move Python, Node.js and PHP thin clients to separate repos
> > and separate release cycles.
> >
> > In short there are several arguments for that:
> >
> > 1. There are no dependencies on the core functionality so there is simply
> > no need for them to be in the main repo.
> >
> > 2. Those thin clients often do not get updates from release to release,
> but
> > still
> > we "release" them, as they are a part of the main release.
> >
> > 3. Moving them to a separate release cycle will allow us to release some
> > hot
> > fixes for those clients faster and easier.
> >
> > 4. Composer needs a PHP packet that is released to be in a separate
> > repository.
> >
> > Thoughts?
> >
> > Best Regards,
> > Igor
> >
>

Re: No commits to Ignite website: migration from SVN to Git is in progress

[Dmitriy Pavlov]

Yes, most likely there are 2 separate repos (presumably, gitbox servers
provided by Microsoft - not 100% sure here), but these repositories have
fast 2-way sync now. I remember that Infra fixed something in this sync.

вс, 19 апр. 2020 г. в 02:57, Saikat Maitra :

> Hi Dmitriy,
>
> Thank you for your email. I am fine with Github built-in merge tool.
>
> Since, in ignite repo we were using the apply-pull-request.sh script and
> pushing changes to gitbox (https://gitbox.apache.org/repos/asf/ignite.git)
>
> I noted that it was immediately syncing the changes in github as well.
>
> My understanding is the repo sync is two way and if we merge changes in
> github then also it will be synced back to gitbox repo.
>
> Regards,
> Saikat
>
>
>
> On Sat, Apr 18, 2020 at 6:40 PM Dmitriy Pavlov  wrote:
>
> >  Hi Folks,
> >
> > Thanks, to Denis and Infra
> >
> > Saikat,
> >
> > with a slight risk of starting off-topic discussions about that, I
> > nevertheless would like to suggest using GitHub build-in merge tool for
> PRs
> > in the ignite-website. It always closes PRs, it closes right PR, so I
> find
> > this option less error-prone. Since Infra integrated ASF repos with
> GitHub
> > It is really easy to merge changes.
> >
> > But still, if you find having apply-pr script useful by any means, sure,
> go
> > ahead. There are no restrictions there.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > сб, 18 апр. 2020 г. в 21:43, Saikat Maitra :
> >
> > > Hi Denis,
> > >
> > > Thank you for your email. Yes, the docs looks good.
> > >
> > > I was asking about this script that we use in ignite repo as well for
> > > committing changes.
> > >
> > >
> >
> https://github.com/apache/ignite/blob/master/scripts/apply-pull-request.sh
> > >
> > > Regards,
> > > Saikat
> > >
> > >
> > >
> > > On Mon, Apr 13, 2020 at 11:53 AM Denis Magda 
> wrote:
> > >
> > > > Hello Saikat,
> > > >
> > > > You can find short website development guidelines on this page [1].
> > They
> > > > are elementary and request to use pull-requests, especially, if the
> one
> > > is
> > > > not a committer. Feel free to elaborate on the process.
> > > >
> > > > Btw, what are the scripts referred by you?
> > > >
> > > > [1]
> > > https://cwiki.apache.org/confluence/display/IGNITE/Website+Development
> > > > -
> > > > Denis
> > > >
> > > >
> > > > On Sun, Apr 12, 2020 at 12:26 PM Saikat Maitra <
> > saikat.mai...@gmail.com>
> > > > wrote:
> > > >
> > > > > Hello,
> > > > >
> > > > > Are we following the same contribution flow as we are doing for
> > ignite
> > > > git
> > > > > repo?
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-ClosingaTicket
> > > > >
> > > > > I have observed that github ignite-website is also mirrored at
> > > > > https://gitbox.apache.org/repos/asf?p=ignite-website.git
> > > > >
> > > > > I can add our scripts folder in ignite-website folder if it helps.
> > > > >
> > > > > Regards,
> > > > > Saikat
> > > > >
> > > > > On Tue, Apr 7, 2020 at 12:49 AM Ivan Pavlukhin <
> vololo...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Thank you!
> > > > > >
> > > > > > Best regards,
> > > > > > Ivan Pavlukhin
> > > > > >
> > > > > > вт, 7 апр. 2020 г. в 00:46, Denis Magda :
> > > > > > >
> > > > > > > The website is back to normal and serves the content from the
> Git
> > > > > > > repository's "master" branch:
> > > > > > > https://github.com/apache/ignite-website/blob/master
> > > > > > >
> > > > > > > -
> > > > > > > Denis
> > > > > > >
> > > > > > >
> > > > > > > On Mon, Apr 6, 2020 at 2:19 PM Denis Magda 
> > > > wrote:
> > > > > > >
> > > > > > > > I'm checking with the INFRA. It's down for at least the last
> > > couple
> > > > > of
> > > > > > > > hours.
> > > > > > > >
> > > > > > > > -
> > > > > > > > Denis
> > > > > > > >
> > > > > > > >
> > > > > > > > On Mon, Apr 6, 2020 at 12:44 PM Ivan Pavlukhin <
> > > > vololo...@gmail.com>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > >> Denis,
> > > > > > > >>
> > > > > > > >> Is it expected that main website https://ignite.apache.org/
> > > does
> > > > > not
> > > > > > > >> work now?
> > > > > > > >>
> > > > > > > >> Best regards,
> > > > > > > >> Ivan Pavlukhin
> > > > > > > >>
> > > > > > > >> сб, 4 апр. 2020 г. в 01:15, Denis Magda  >:
> > > > > > > >> >
> > > > > > > >> > Igniters,
> > > > > > > >> >
> > > > > > > >> > Please avoid any commits to the website repository until
> > > further
> > > > > > notice.
> > > > > > > >> > We're in a process of the migration:
> > > > > > > >> > https://issues.apache.org/jira/browse/INFRA-20065
> > > > > > > >> >
> > > > > > > >> > -
> > > > > > > >> > Denis
> > > > > > > >>
> > > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: No commits to Ignite website: migration from SVN to Git is in progress

[Dmitriy Pavlov]

 Hi Folks,

Thanks, to Denis and Infra

Saikat,

with a slight risk of starting off-topic discussions about that, I
nevertheless would like to suggest using GitHub build-in merge tool for PRs
in the ignite-website. It always closes PRs, it closes right PR, so I find
this option less error-prone. Since Infra integrated ASF repos with GitHub
It is really easy to merge changes.

But still, if you find having apply-pr script useful by any means, sure, go
ahead. There are no restrictions there.

Sincerely,
Dmitriy Pavlov

сб, 18 апр. 2020 г. в 21:43, Saikat Maitra :

> Hi Denis,
>
> Thank you for your email. Yes, the docs looks good.
>
> I was asking about this script that we use in ignite repo as well for
> committing changes.
>
> https://github.com/apache/ignite/blob/master/scripts/apply-pull-request.sh
>
> Regards,
> Saikat
>
>
>
> On Mon, Apr 13, 2020 at 11:53 AM Denis Magda  wrote:
>
> > Hello Saikat,
> >
> > You can find short website development guidelines on this page [1]. They
> > are elementary and request to use pull-requests, especially, if the one
> is
> > not a committer. Feel free to elaborate on the process.
> >
> > Btw, what are the scripts referred by you?
> >
> > [1]
> https://cwiki.apache.org/confluence/display/IGNITE/Website+Development
> > -
> > Denis
> >
> >
> > On Sun, Apr 12, 2020 at 12:26 PM Saikat Maitra 
> > wrote:
> >
> > > Hello,
> > >
> > > Are we following the same contribution flow as we are doing for ignite
> > git
> > > repo?
> > >
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-ClosingaTicket
> > >
> > > I have observed that github ignite-website is also mirrored at
> > > https://gitbox.apache.org/repos/asf?p=ignite-website.git
> > >
> > > I can add our scripts folder in ignite-website folder if it helps.
> > >
> > > Regards,
> > > Saikat
> > >
> > > On Tue, Apr 7, 2020 at 12:49 AM Ivan Pavlukhin 
> > > wrote:
> > >
> > > > Thank you!
> > > >
> > > > Best regards,
> > > > Ivan Pavlukhin
> > > >
> > > > вт, 7 апр. 2020 г. в 00:46, Denis Magda :
> > > > >
> > > > > The website is back to normal and serves the content from the Git
> > > > > repository's "master" branch:
> > > > > https://github.com/apache/ignite-website/blob/master
> > > > >
> > > > > -
> > > > > Denis
> > > > >
> > > > >
> > > > > On Mon, Apr 6, 2020 at 2:19 PM Denis Magda 
> > wrote:
> > > > >
> > > > > > I'm checking with the INFRA. It's down for at least the last
> couple
> > > of
> > > > > > hours.
> > > > > >
> > > > > > -
> > > > > > Denis
> > > > > >
> > > > > >
> > > > > > On Mon, Apr 6, 2020 at 12:44 PM Ivan Pavlukhin <
> > vololo...@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > >> Denis,
> > > > > >>
> > > > > >> Is it expected that main website https://ignite.apache.org/
> does
> > > not
> > > > > >> work now?
> > > > > >>
> > > > > >> Best regards,
> > > > > >> Ivan Pavlukhin
> > > > > >>
> > > > > >> сб, 4 апр. 2020 г. в 01:15, Denis Magda :
> > > > > >> >
> > > > > >> > Igniters,
> > > > > >> >
> > > > > >> > Please avoid any commits to the website repository until
> further
> > > > notice.
> > > > > >> > We're in a process of the migration:
> > > > > >> > https://issues.apache.org/jira/browse/INFRA-20065
> > > > > >> >
> > > > > >> > -
> > > > > >> > Denis
> > > > > >>
> > > > > >
> > > >
> > >
> >
>

Re: Get rid of @Nullable and @NotNull

[Dmitriy Pavlov]

+1 for using @Nullable as it is a kind of documentation
+1 for using @NotNull as it protects from
wrong fields/variables assignments if modern IDE is used.

пт, 27 мар. 2020 г. в 14:28, Sergey-A Kosarev :

> Classification: Public
>
> +1 for using @Nullable.
>
> @Nullable is not panacea, but much better than nothing.
>
> It's clear indication that you should check the marked object for null
> before using. There is advantage in using @Nullable than @NotNull - Idea or
> any tool like findbugs shows you potential NPE places - where you forgot to
> check for null  object marked @Nullable, otherwise if you use only @NotNull
> it's much harder to see NPE problems as, I believe, always will be too many
> noise - places where developers just forgot to place annotation.
>
> And another arguable point is statistics, in my experience there are more
> objects that not null by nature than nullable. So if you should mark only
> all @NotNull objects, you will need to place much more annotations than if
> mark only @Nullable objects.
>
> Kind regards,
> Sergey Kosarev
>
>
> -Original Message-
> From: Ivan Pavlukhin [mailto:vololo...@gmail.com]
> Sent: 27 March 2020 13:28
> To: dev 
> Subject: Re: Get rid of @Nullable and @NotNull
>
> Here is my opinion. As we do not have a common practice to use @Nullable
> and @NotNull annotations everywhere I would consider every not annotated
> item as effectively @Nullable. @NotNull seems a useful annotation for me,
> sometimes it is a really good thing to assume that something cannot be null
> instead of doing explicit null check everywhere.
>
> Best regards,
> Ivan Pavlukhin
>
> пт, 27 мар. 2020 г. в 13:05, Denis Garus :
> >
> > Hi!
> > I'm not sure that @Nullable can really fix the NPE problem.
> > Currently, we have @Nullable annotation and NPE simultaneously.
> > The best way to avoid NPE is by using a null object pattern.
> > I agree we shouldn't rely on @Nullable.
> >
> >
> > пт, 27 мар. 2020 г. в 12:58, Sergey Antonov :
> >
> > > I disagree.
> > >
> > > Intellij idea IDE has a static code analysis, which uses that
> > > annotation too. IDE highlights possible problems. It helps to make
> > > our code more stable and bugless.
> > >
> > > пт, 27 мар. 2020 г. в 12:06, Pavel Tupitsyn :
> > >
> > > > I disagree, it would be a step back.
> > > >
> > > > > What's the reason for using it?
> > > > Null was a billion dollar mistake [1].
> > > > NullPointerExceptions happen quite a lot in Ignite, and
> > > > annotations
> > > provide
> > > > some clues to avoid those.
> > > >
> > > > [1]
> > > > https://en.wikipedia.org/wiki/Tony_Hoare#Apologies_and_retractions
> > > >
> > > > On Fri, Mar 27, 2020 at 10:58 AM Anton Vinogradov 
> wrote:
> > > >
> > > > > Folks,
> > > > >
> > > > > Found we still use @Nullable annotation.
> > > > >
> > > > > What's the reason for using it?
> > > > > Everything is Object and Nullable :)
> > > > >
> > > > > How about get rid of @Nullable usages and restrict its usage by
> > > > checkstyle
> > > > > plugin?
> > > > >
> > > > > BTW, We already "do not use @NotNull annotation" (с) Coding
> > > > > Guidelines
> > > > [1]
> > > > > which may have some cense in contrast to @Nullable.
> > > > > But I see a lot of usages at code.
> > > > >
> > > > > How about to get rid of @NotNull too and to add such check to
> > > checkstyle
> > > > > plugin too?
> > > > >
> > > > > [1]
> > > > >
> > > > >
> > > >
> > > https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines
> > > #CodingGuidelines-@Annotations
> > > > >
> > > >
> > >
> > >
> > > --
> > > BR, Sergey Antonov
> > >
>
>
> ---
> This e-mail may contain confidential and/or privileged information. If you
> are not the intended recipient (or have received this e-mail in error)
> please notify the sender immediately and delete this e-mail. Any
> unauthorized copying, disclosure or distribution of the material in this
> e-mail is strictly forbidden.
>
> Please refer to https://www.db.com/disclosures for additional EU
> corporate and regulatory disclosures and to
> http://www.db.com/unitedkingdom/content/privacy.htm for information about
> privacy.
>

Re: Who can update TC Bot version.

[Dmitriy Pavlov]

Hi,

I could potentially update this version in the source code, but I'm not
able to deploy new version to the server (since it is now sponsored by
GrigGain, we need someone who will deploy).

Sincerely,
Dmitriy Pavlov

пн, 23 мар. 2020 г. в 08:59, Zhenya Stanilovsky :

> Igniters, 2.8 version already released, but looks like TC bot [1] [2]
> still using 2.7.6 ver. , who can update it ?
> Thanks !
>
> [1] https://github.com/apache/ignite-teamcity-bot
> [2] https://mtcga.gridgain.com/
>
>
>
>

Re: Apache way webinar

[Dmitriy Pavlov]

Hi Nikolay, Ksenia,

All webinars I remember were conducted using GridGain's GoToMeeting
account. AFAIK, Apache Foundation does not provide some shared account for
running webinars. I don't see any issues if a company will sponsor the
infrastructure for running community - related activity. I hope GridGainers
will confirm if it is possible to set it up.

Typically, announces for webinars are done using dev list and/or user list
(depending on topic). Once I sent a meeting invitation to the dev list.

Sincerely,
Dmitriy Pavlov


чт, 12 мар. 2020 г. в 18:49, Kseniya Romanova :

> Nikolay, I believe we can use Gotowebinar (as GridGain contribution) or as
> well GoToMeeting. I will be happy to help with the announcement and
> scheduling.
> Dmitry, what do you think? ASF slack looks less comfortable for this
> purpose.
>
> чт, 12 мар. 2020 г. в 11:22, Nikolay Izhikov :
>
>> Yes.
>>
>> > 12 марта 2020 г., в 10:59, Maksim Stepachev 
>> написал(а):
>> >
>> > It's the perfect idea. Will it in English?
>> >
>> > чт, 12 мар. 2020 г. в 10:15, Nikolay Izhikov :
>> >
>> >> Hello, Igniters.
>> >>
>> >> I want to organize the webinar for the Apache Ignite community.
>> >> The subject of the webinar - «New monitoring and system view in 2.8»
>> >>
>> >> Is there any Apache guides on how to do it?
>> >>
>> >> What software should be used? How I should announce it? etc...
>>
>>

Re: Ignite Website: New Look

[Dmitriy Pavlov]

Hi Denis,

Unfortunately, I don't know details on how to set it up.

One thing I've noticed in Apache Training (incubating) and in Apache DLab
(incubating) that both projects
1. added site sources to Git repository and
2. created an INFRA ticket for setting up the site.

Let's try it too, and let's hope INFRA will guide us on the required steps.

Sincerely,
Dmitriy Pavlov

сб, 7 мар. 2020 г. в 01:08, Denis Magda :

> Dmitry,
>
> Agree on the Github repository. Let me look into it. If you have any
> pointers or came across any instructions earlier please let me know.
>
> -
> Denis
>
>
> On Fri, Mar 6, 2020 at 8:03 AM Dmitriy Pavlov  wrote:
>
> > Hi Igniters,
> >
> > IMO, new design looks good, but please pay attention
> > - every mention of Apache Ignite is better to be followed by (R) mark
> since
> > it is registered trademark of the ASF in the US and other countries.
> > - download page is not available (as Denis mentioned it should not be an
> > issue).
> >
> > And one more side note: since 1) it is a major change in the site look
> and
> > 2) our site is  still stored in the SVN, could we consider migrating to
> Git
> > repository first?
> >
> > Git benefits are more or less obvious:
> > - It will allow us to make a PRs for contributions to the site.
> > - Git repository is slightly more convenient. It works faster during
> clone,
> > commit, and update.
> > - It should help to recognize contributions from  Mauricio and Ignacio
> and
> > all other members, who updates and maintains the site (we don't have
> > contributors listing page and we use git for listing of the project's
> > developers).
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > BTW, since this is important topic, I suggest every email with proposal
> is
> > marked with [DISCUSSION] to help it to be noticed.
> >
> > пт, 6 мар. 2020 г. в 03:21, Nikita Ivanov :
> >
> > > Denis - looks very nice! I do indeed think we need to work on better
> > > content (home page specifically).
> > > Thanks!
> > > --
> > > Nikita Ivanov
> > >
> > >
> > >
> > > On Thu, Mar 5, 2020 at 3:18 PM Denis Magda  wrote:
> > >
> > > > Folks,
> > > >
> > > > As many of you know, these days I mostly contribute by optimizing our
> > > > website, preparing different content including
> documentation/articles,
> > > and
> > > > presenting the project at various events. One of the continuous
> website
> > > > activities we undertake together with Mauricio and Ignacio is search
> > > engine
> > > > optimization (SEO). It helps our website to be ranked higher by
> search
> > > > engines for user searches falling in categories of in-memory caches,
> > > grids,
> > > > databases, etc. (check this simple guide [1] if you'd like to learn
> the
> > > > internals of SEO).
> > > >
> > > > After checking the results of our recent user questionnaire [2] and
> > > > confirming key capabilities with use cases Ignite is selected for, we
> > > > decided to put more effort into the SEO. And, in addition to the
> > keywords
> > > > optimizations, we invested some time into the structural and UI
> changes
> > > of
> > > > the website trying to make the experience better and, as a result, be
> > > > ranked higher.
> > > >
> > > > So, today we'd like to share our first results and check your
> thoughts.
> > > In
> > > > particular, pay attention to:
> > > >
> > > >- The new UI - instead of a dark and bloody theme, we decided to
> > > >experiment with a more lightweight and contemporary design.
> > > >- A new main page structure with the following blocks - banner,
> use
> > > >cases, features, quicks links + tweeter feed.
> > > >- Updated navigation menu - kept essential or highly-ranked pages.
> > > >
> > > >
> > > > Do NOT pay attention to the following yet (we're ready to carry on
> with
> > > the
> > > > items below once hear your feedback):
> > > >
> > > >- Text on the front page will be massaged and tweaked going
> forward
> > to
> > > >get better SEO. Presently, something might sound off to you.
> > > >- Secondary pages are broken from the UI and structure standpoint
> > > >- Some of the pages of the navigation menu, such as Videos, are
> not
> > > >created yet.
> > > >
> > > >
> > > > Alright, we deployed our branch to this test server. Go and check:
> > > > http://157.245.190.104 (user: ignite, pass: apache2020)
> > > >
> > > >
> > > >
> > > > [1] https://moz.com/beginners-guide-to-seo
> > > > [2]
> > > >
> > > >
> > >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-Evolution-Direction-short-questionary-td44577.html
> > > >
> > > > -
> > > > Denis
> > > >
> > >
> >
>

Fwd: [NOTICE] Structural changes to Apache downloads

[Dmitriy Pavlov]

Hi Igniters,

I feel it worth sharing with all of you. I don't think there is something
private in this notice. JFYI

Sincerely,
Dmitriy Pavlov
-- Forwarded message -
От: Daniel Gruno 
Date: ср, 4 мар. 2020 г. в 18:04
Subject: [NOTICE] Structural changes to Apache downloads
To: 


Hello, Apache PMCs,

In order to better provide our millions of users with downloads, the
Apache Infrastructure Team has been restructuring the way downloads work
for our main distribution channels in the past few weeks. For users,
this will largely go unnoticed, and for projects likely the same, but we
did want to reach out to projects and inform them of the changes we've
made:

As of March 2020, we are deprecating www.apache.org/dist/ in favor of
https://downloads.apache.org/ for backup downloads as well as signature
and checksum verification. The primary driver has been splitting up web
site visits and downloads to gain better control and offer a better
service for both downloads and web site visits.

As stated, this does not impact end-users, and should have a minimal
impact on projects, as our download selectors as well as visits to
www.apache.org/dist/ have been adjusted to make use of
downloads.apache.org instead. We do however ask that projects, in their
own time-frame, change references on their own web sites from
www.apache.org/dist/ to downloads.apache.org wherever such references
may exist, to complete the switch in full. We will NOT be turning off
www.apache.org/dist/ in the near future, but would greatly appreciate if
projects could help us transition away from the old URLs in their
documentation and on their download pages.

The standard way of uploading releases[1] will STILL apply, however
there may be a short delay (<= 15 minutes) between releasing and
releases showing up on downloads.apache.org for technical reasons.

If you have any questions about this change, please do not hesitate
to reach out to us at us...@infra.apache.org.

With regards,
Daniel on behalf of ASF Infrastructure.

[1] https://www.apache.org/legal/release-policy.html#upload-ci

Re: Ignite Website: New Look

[Dmitriy Pavlov]

Hi Igniters,

IMO, new design looks good, but please pay attention
- every mention of Apache Ignite is better to be followed by (R) mark since
it is registered trademark of the ASF in the US and other countries.
- download page is not available (as Denis mentioned it should not be an
issue).

And one more side note: since 1) it is a major change in the site look and
2) our site is  still stored in the SVN, could we consider migrating to Git
repository first?

Git benefits are more or less obvious:
- It will allow us to make a PRs for contributions to the site.
- Git repository is slightly more convenient. It works faster during clone,
commit, and update.
- It should help to recognize contributions from  Mauricio and Ignacio and
all other members, who updates and maintains the site (we don't have
contributors listing page and we use git for listing of the project's
developers).

Sincerely,
Dmitriy Pavlov

BTW, since this is important topic, I suggest every email with proposal is
marked with [DISCUSSION] to help it to be noticed.

пт, 6 мар. 2020 г. в 03:21, Nikita Ivanov :

> Denis - looks very nice! I do indeed think we need to work on better
> content (home page specifically).
> Thanks!
> --
> Nikita Ivanov
>
>
>
> On Thu, Mar 5, 2020 at 3:18 PM Denis Magda  wrote:
>
> > Folks,
> >
> > As many of you know, these days I mostly contribute by optimizing our
> > website, preparing different content including documentation/articles,
> and
> > presenting the project at various events. One of the continuous website
> > activities we undertake together with Mauricio and Ignacio is search
> engine
> > optimization (SEO). It helps our website to be ranked higher by search
> > engines for user searches falling in categories of in-memory caches,
> grids,
> > databases, etc. (check this simple guide [1] if you'd like to learn the
> > internals of SEO).
> >
> > After checking the results of our recent user questionnaire [2] and
> > confirming key capabilities with use cases Ignite is selected for, we
> > decided to put more effort into the SEO. And, in addition to the keywords
> > optimizations, we invested some time into the structural and UI changes
> of
> > the website trying to make the experience better and, as a result, be
> > ranked higher.
> >
> > So, today we'd like to share our first results and check your thoughts.
> In
> > particular, pay attention to:
> >
> >- The new UI - instead of a dark and bloody theme, we decided to
> >experiment with a more lightweight and contemporary design.
> >- A new main page structure with the following blocks - banner, use
> >cases, features, quicks links + tweeter feed.
> >- Updated navigation menu - kept essential or highly-ranked pages.
> >
> >
> > Do NOT pay attention to the following yet (we're ready to carry on with
> the
> > items below once hear your feedback):
> >
> >- Text on the front page will be massaged and tweaked going forward to
> >get better SEO. Presently, something might sound off to you.
> >- Secondary pages are broken from the UI and structure standpoint
> >- Some of the pages of the navigation menu, such as Videos, are not
> >created yet.
> >
> >
> > Alright, we deployed our branch to this test server. Go and check:
> > http://157.245.190.104 (user: ignite, pass: apache2020)
> >
> >
> >
> > [1] https://moz.com/beginners-guide-to-seo
> > [2]
> >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-Evolution-Direction-short-questionary-td44577.html
> >
> > -
> > Denis
> >
>

Re: [DISCUSSION] Release Apache Ignite 2.8.0 RC1

[Dmitriy Pavlov]

Ilya, let me personally thank you for checking and filing this bug.

I checked timeline for [result] [vote] email and new email describing new
issue. Unfortunately, after closing the vote it is not possible to stop
release from publishing (only if RM will delay publish stage after closing
the vote). In this case publishing already happened, so replacing existing
binary with new one can cause a lot of mess.

What do you think about our future steps to learn from this case? It is
possible to keep vote open longer that 72hours if someone is still checking
things. Would it help if we agree on RM will delay closing the voting
process until all interested participants finish their checks?

Sincerely,
Dmitriy Pavlov

вт, 3 мар. 2020 г. в 20:33, Ilya Kasnacheev :

> Hello!
>
> Can we please hold back publishing AI-2.8.0-rc1 as public Apache Ignite 2.8
> release?
>
> I have just been notified that
>
> org.apache.ignite.internal.processors.cache.distributed.dht.GridCacheColocatedDebugTest#testPutsMultithreadedColocated
>
> org.apache.ignite.internal.processors.cache.distributed.dht.GridCacheColocatedDebugTest#testPutsMultithreadedMixed
> are flaky: they seem to deadlock on putAll sorted keys maps. They used to
> pass solidly on 2.7, but fail on master and ignite-2.8.
>
> (They fail around 1 time out of 10, so just run them 25 times to check)
>
> If there is indeed a deadlock, this would become a blocker to this release,
> in my opinion, but I need some time to check.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> вс, 1 мар. 2020 г. в 11:29, Maxim Muzafarov :
>
> > Ivan,
> >
> >
> > I agree with you that the more members will check the release the
> > better will be. That's why I've shared the release candidate links [1]
> > before starting a vote. The best time for starting a vote is not
> > mentioned at our release wiki page [2] (should we?) and I've also
> > failed with googling the best practices for it too. So, I've supposed
> > since all of us are working on their own tasks during weekdays the
> > free time on the weekend is the best choice for cheking\voting on the
> > release. Probably this decision was wrong.
> >
> > [1]
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-8-RELEASE-Time-Scope-Manager-tp43616p46117.html
> > [2] https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
> >
> > On Sun, 1 Mar 2020 at 00:37, Ivan Pavlukhin  wrote:
> > >
> > > Also I have a comment regarding to voting. Voting for 72 hour spanning
> > > a weekend sounds a little bit odd to me. In a particular case the more
> > > people check the release the better. And I suppose there is more time
> > > for it on weekdays for the majority.
> > >
> > > Best regards,
> > > Ivan Pavlukhin
> > >
> > > вс, 1 мар. 2020 г. в 00:33, Ivan Pavlukhin :
> > > >
> > > > > As I remember, that Pavlov suggested to discuss threats on a
> private
> > PMC list
> > > > Cannot understand why it should be discussed on a private list. What
> > > > is the clue?
> > > >
> > > > Best regards,
> > > > Ivan Pavlukhin
> > > >
> > > > сб, 29 февр. 2020 г. в 16:00, Alexey Zinoviev <
> zaleslaw@gmail.com
> > >:
> > > > >
> > > > > As I remember, that Pavlov suggested to discuss threats on a
> private
> > PMC
> > > > > list
> > > > >
> > > > > сб, 29 февр. 2020 г., 15:12 Ilya Kasnacheev <
> > ilya.kasnach...@gmail.com>:
> > > > >
> > > > > > Hello!
> > > > > >
> > > > > > As far as my understanding goes, ignite-zookeeper is listed for
> > removal
> > > > > > because it brings a lot of dependencies, some of which may have
> > known
> > > > > > vulnerabilities, which will make the distribution also considered
> > > > > > vulnerable by some scanners.
> > > > > >
> > > > > > Regards,
> > > > > > --
> > > > > > Ilya Kasnacheev
> > > > > >
> > > > > >
> > > > > > сб, 29 февр. 2020 г. в 14:18, Alexey Zinoviev <
> > zaleslaw@gmail.com>:
> > > > > >
> > > > > > > Ok, lets move to this thread. Also, the slim release could be
> > form by
> > > > > > > voting on user-list
> > > > > > >
> > > > > > > сб, 29 февр. 2020 г., 9:55 Alexey Goncharuk <
> > alexey.goncha...@

Re: [DISCUSSION] Release Apache Ignite 2.8.0 RC1

[Dmitriy Pavlov]

Hi Folks,

Unfortunately https://dist.apache.org/repos/dist/release/ignite/2.8.0/ is
already there, so release was happened. I'm not sure it is a good idea to
substitute binaries later.  Was it announced to announce@ ?

IMO, 2.8.1 is ok for that case.

Sincerely,
Dmitriy Pavlov

ср, 4 мар. 2020 г. в 11:29, Nikolay Izhikov :

> Pavel, ++1.
>
> > 4 марта 2020 г., в 11:20, Pavel Tupitsyn 
> написал(а):
> >
> > Igniters,
> >
> > The release has already happened.
> > It is on our website [1], it is on Maven [2].
> > People are using it, so I don't think we can do anything at this point.
> >
> > Bugs happen, we can't delay the release forever because of them. Let's
> fix
> > things in 2.8.1.
> >
> > [1] https://ignite.apache.org/download.cgi
> > [2] https://mvnrepository.com/artifact/org.apache.ignite
> >
> >
> > On Wed, Mar 4, 2020 at 10:06 AM Nikolay Izhikov 
> wrote:
> >
> >> Hello, Igniters.
> >>
> >> Do we have a person who can fix this issue in the nearest time?
> >> Right now IGNITE-12746 is Open and Unassigned.
> >>
> >>> 3 марта 2020 г., в 23:54, Denis Magda  написал(а):
> >>>
> >>> Ilya,
> >>>
> >>> Thanks for catching that and sharing. I wonder if there are any other
> >>> blockers that were pushed to 2.8.x version. If there are a few then we
> >> can
> >>> produce 2.8.1 shortly, otherwise, it sounds reasonable to me to fix the
> >>> issue with putAll, update the binaries and finish the process.
> >>>
> >>> -
> >>> Denis
> >>>
> >>>
> >>> On Tue, Mar 3, 2020 at 2:34 PM Ilya Kasnacheev <
> >> ilya.kasnach...@gmail.com>
> >>> wrote:
> >>>
> >>>> Hello!
> >>>>
> >>>> I have filed an issue
> >> https://issues.apache.org/jira/browse/IGNITE-12746
> >>>>
> >>>> I think this is potentially a game breaker and makes me recommend
> >> avoiding
> >>>> 2.8, if we release it without fix (for now).
> >>>>
> >>>> If you are using any partitioned caches, anyway.
> >>>>
> >>>> So I suggest we withhold 2.8.
> >>>>
> >>>> Regards,
> >>>> --
> >>>> Ilya Kasnacheev
> >>>>
> >>>>
> >>>> вт, 3 мар. 2020 г. в 20:53, Maxim Muzafarov :
> >>>>
> >>>>> Ilya,
> >>>>>
> >>>>> I do not want to force the release no matter what happens, but I
> think
> >>>>> we should release what we have to get feedback not just from the
> >>>>> developer community but from our users too.
> >>>>>
> >>>>> And fix all these issues in 2.8.1.
> >>>>>
> >>>>> On Tue, 3 Mar 2020 at 20:33, Ilya Kasnacheev <
> >> ilya.kasnach...@gmail.com>
> >>>>> wrote:
> >>>>>>
> >>>>>> Hello!
> >>>>>>
> >>>>>> Can we please hold back publishing AI-2.8.0-rc1 as public Apache
> >> Ignite
> >>>>> 2.8
> >>>>>> release?
> >>>>>>
> >>>>>> I have just been notified that
> >>>>>>
> >>>>>
> >>>>
> >>
> org.apache.ignite.internal.processors.cache.distributed.dht.GridCacheColocatedDebugTest#testPutsMultithreadedColocated
> >>>>>>
> >>>>>
> >>>>
> >>
> org.apache.ignite.internal.processors.cache.distributed.dht.GridCacheColocatedDebugTest#testPutsMultithreadedMixed
> >>>>>> are flaky: they seem to deadlock on putAll sorted keys maps. They
> used
> >>>> to
> >>>>>> pass solidly on 2.7, but fail on master and ignite-2.8.
> >>>>>>
> >>>>>> (They fail around 1 time out of 10, so just run them 25 times to
> >> check)
> >>>>>>
> >>>>>> If there is indeed a deadlock, this would become a blocker to this
> >>>>> release,
> >>>>>> in my opinion, but I need some time to check.
> >>>>>>
> >>>>>> Regards,
> >>>>>> --
> >>>>>> Ilya Kasnacheev
> >>>>>>
> >>>>>>
> >>>>>> вс, 1 мар. 2020 г. в 11:29, Maxim Muzafa

[ANNOUNCE] New committer: Vyacheslav Koptilin

[Dmitriy Pavlov]

Hello Ignite Community,

The Project Management Committee (PMC) for Apache Ignite has invited
Vyacheslav Koptilin to become a committer and we are pleased to announce
that he has accepted.

Vyacheslav investigated and fixed a number of non-trivial issues in the
Ignite Native persistent store, was a reviewer of Read Repair (ex.
Consistency Check).

Being a committer enables easier contribution to the project since there is
no need to go via the patch submission process. This should enable better
productivity.

Vyacheslav, thanks for supporting the community and keep the pace!

Best Regards,
Dmitriy Pavlov
on behalf of Apache Ignite PMC

Re: Is ML module @IgniteExperimental?

[Dmitriy Pavlov]

Folks,

>  Do we have plans to fix it?
It is not how community works. It depends on contributors and their
interests  in maintaining and fixing particular bug/feature/module. If
someone would like to help, he/she is always welcomed.

Don't ask others to do stuff for you, in other words.

>CVE
CVEs  are not to be discussed at dev@ use security@ or private@. see
https://www.apache.org/security/committers.html

 > Should we mark it with the @IgniteExperimental
it may be agreed by the community during separate discussion/vote. I
personally not sure I agree.

Since Alexey has interest in maintaining, I support his idea on how module
should be developed. Apache motto is: "Let those who do the job make a
decisions".

Sincerely,
Dmitriy Pavlov


пн, 17 февр. 2020 г. в 13:49, Alexey Zinoviev :

> Hello, Igniters, and you, Nikolay.
>
> First of all, if you have real interest to the ML module and its state, I
> could make call with you and explain this.
>
>
> *As far as I know, for now, we have only 1 active contributor to this area
> -Alexey Zinoviev.*
> Currently, we have 2 active contributors, me and Ravil Galeeyev, a few
> newbies, another guys who started tensorflow and another modules and
> submodules don't visit the community for many months.
>
> *Is ML module production ready?*
> This release will be the first release, than ML is production ready and it
> totally my work.
>
>
> *Can someone related to the ML, please, give some examples of the CVE
> orissues that can be fixed only with removing a bunch of modules?*
> CVE is not the main reason to remove the "bunch of modules", but part of
> the story.
> The main reason, the modules are not work proper way, were experimental,
> never released as a production-ready, support old, outdated version, the
> external frameworks, like Tensorflow, move integration with ignite to the
> special repos, they are not finished, the code there is broken and couldn't
> be fixed, because and I have no power/C++ skills/permission to commit
> something to them and time to support this broken modules.
>
> Also broken TF module blocks the removal of IGFS.
>
> Found CVE were related to the dependencies related to hadoop/tf/parquet and
> so on.
>
> *Should we mark it with the @IgniteExperimental? *
> I don't know, we have no this RAW annotation a few weeks ago and I don't
> know how we should use it.
> It could be, if you finish the discussion about this annotation and the
> write docs about it and share it with me.
>
>
> * As far as I know, the ML module has no documentation. Is it correct? Dowe
> have plans to fix it?*
> The ML docs are here, on our Ignite documentation
> https://apacheignite.readme.io/docs/machine-learning
> of course, something could be wrong, 1.5 year we are not released Ignite
> Yes, I have plan to fix. Of course, after fixing all bugs in release branch
>
> *Should we move it to the ignite-extensions?*
> No we shouldn't, I don't want this, and have a lot of arguments and
> currently is not the time for discussion about this (they are too young and
> have now real infrastructure and release-cycle)
>
> P.S. Community, I understand that the removal of module looks strange, but
> we could understand that ML was a strange experiment without roadmap and
> this situation is finished.
> Now, I have roadmap (will be published later), newbie tickets, the ability
> to prepare correct docs, the understanding what could be used by clients
> and first of all, production-ready ML (it could be run on Ignite-cluster,
> really, it works.)
>
> If you, Igniters, believe, that I could be a good maintainer for ML module,
> please support me here in this thread
> If you think, that I do something wrong, OK, please write it too, I'll read
> carefully.
>
> I spent a few months to fix bugs in components, which were abandoned by
> their creators.
>
> My goal: Ignite should have light-weight, easy-integrated ML without
> strange and unfinished experiments which could be not maintained. It's a
> part of common movement in Ignite (removal of modules or moving them to the
> separate repos).
>
>
> пн, 17 февр. 2020 г. в 12:10, Nikolay Izhikov :
>
> > Hello, Igniters.
> >
> > Can someone bring some light on the state of the ML module in Ignite?
> > As far as I know, for now, we have only 1 active contributor to this
> area -
> > Alexey Zinoviev.
> > I see how whole modules come and go from the module - [1]
> >
> > Please, also note this quote:
> >
> > > Also as a result of good testing from both side (from me and Stepan) we
> > > found a lot of bugs and CVEs in hadoop related components that should
> be
> > > removed in release br

Re: Launched Ignite meetups and redesigned events pages

[Dmitriy Pavlov]

Hi Denis,

yes, sorry for late reply, I just did double check that I can access
answers. Additionally, Ksenia R. have access to proposals.

Anyone from PMC who would like to volunteer and being PMC Representative
for Apache Ignite Local meetups are always welcomed (according
https://www.apache.org/foundation/marks/events  - The ASF events branding
policy).

Moreover, not-yet-PMC volunteers, who would help with talks preparation are
also welcomed. I strongly believe we should not be too formal here.

Sincerely,
Dmitriy Pavlov



чт, 9 янв. 2020 г. в 23:47, Denis Magda :

> Dmitry,
>
> We've also added the reference to the form on the event's webpage. Btw,
> could you remind me who will be receiving the proposals - you, I and some
> other folks or all @dev list?
>
> -
> Denis
>
>
> On Thu, Jan 9, 2020 at 1:53 AM Dmitriy Pavlov  wrote:
>
>> Hi Igniters, Mauricio, Ignacio, and Denis,
>>
>> Thank you all for updating these pages.
>>
>> I would like to stress just one thing:
>> should you have in mind some topic you can run talk about, please feel
>> absolutely free to fill submission proposal.
>>
>> To submit proposal you need to fill in this form
>>
>> https://docs.google.com/forms/d/e/1FAIpQLSdiY7movHKvyWg3gOVedHgukJJnNiaejSO_X838vBseL9VmiQ/viewform
>> .
>>
>> Sincerely,
>> Dmitriy Pavlov
>>
>> вт, 7 янв. 2020 г. в 02:48, Denis Magda :
>>
>> > Igniters,
>> >
>> > I've just merged changes contributed by Mauricio and Ignacio, who helped
>> > us to prepare professional webpages for Ignite meetup groups around the
>> > world [1] and for Ignite events [2]. Now you can easily enroll in a
>> meetup
>> > group nearby or sign up for an upcoming event to be hosted one of our
>> > experts.
>> >
>> > Please check them out and share your feedback. In the meantime, three of
>> > us are going to carry on with optimizations and changes making the
>> website
>> > more useful for developers as well as more searchable/discoverable from
>> > various search engines.
>> >
>> > [1] https://ignite.apache.org/meetup-groups.html
>> > [2] https://ignite.apache.org/events.html
>> >
>> > -
>> > Denis
>> >
>>
>

Re: [DISCUSS] Merge PR via GitHub web UI

[Dmitriy Pavlov]

I always merge PRs from GitHub when possible. By doing it I can keep my
Git's local state unmodified.

So I suggest using squash and merge.

пн, 27 янв. 2020 г. в 14:59, Maxim Muzafarov :

> +1 to keep only "squash" merge option
>
> On Mon, 27 Jan 2020 at 14:39, Pavel Tupitsyn  wrote:
> >
> > Merging from GitHub is very convenient indeed, much faster and safer than
> > anything else.
> >
> > And yes, GitHub provides a way to disable Merge and Rebase, leaving only
> > Squash option:
> >
> https://help.github.com/en/github/administering-a-repository/configuring-commit-squashing-for-pull-requests
> >
> >
> > However, I don't have access to the settings.
> > Peter, can you please change this setting for us?
> >
> > On Mon, Jan 27, 2020 at 2:38 PM Petr Ivanov  wrote:
> >
> > > Iliya,
> > >
> > > How well does this script work under non-linux operations systems?
> > >
> > >
> > > > On 27 Jan 2020, at 14:24, Ilya Kasnacheev  >
> > > wrote:
> > > >
> > > > Hello!
> > > >
> > > > I implore everybody to use scripts/apply-pull-request.sh, I never
> had any
> > > > problems with it. The only downside is that cherry-peek needs to be
> > > clean.
> > > >
> > > > Regards,
> > > > --
> > > > Ilya Kasnacheev
> > > >
> > > >
> > > > пн, 27 янв. 2020 г. в 14:22, Ivan Pavlukhin :
> > > >
> > > >> Today I opened for myself a possibility to merge PR via GitHub. And
> > > >> GitHub allows 3 usual options to do a merge (merge commit, rebase,
> > > >> squash). And "merge commit" is a default option but an illegal one
> > > >> according to Apache Ignite usual practices.
> > > >>
> > > >> So, I wonder is it somehow possible to configure it to keep only
> > > >> "squash" merge option?
> > > >>
> > > >> --
> > > >> Best regards,
> > > >> Ivan Pavlukhin
> > > >>
> > >
> > >
>

Re: Apache Ignite contribution

[Dmitriy Pavlov]

Hi Igniters,

I would name dev list as the only one official channel. Other options are
supplementary channels just for convenience (Slack for voice calls & chats,
Russian local resources for easier communication without foreign language
barrier). But still, I hope we're on the same page that
_If it didn't happen on the list, it didn't happen._

Sincerely,
Dmitriy Pavlov

пн, 27 янв. 2020 г. в 12:24, Alexey Zinoviev :

> And dont forget asf slack with a few channel about Apache ignite
>
> пн, 27 янв. 2020 г., 12:20 Ivan Pavlukhin :
>
> > Maksim, folks,
> >
> > Actually I am curious what kind of communication channel is mentioned
> > telegram channel? Should we add a link to it on official "community
> > resources" page?
> >
> > пн, 27 янв. 2020 г. в 11:40, Maksim Stepachev <
> maksim.stepac...@gmail.com
> > >:
> > >
> > > Hello!
> > >
> > > If you have the telegram, join to Russian channel:
> > https://t.me/RU_Ignite
> > >
> > > чт, 23 янв. 2020 г. в 16:07, Ilya Kasnacheev <
> ilya.kasnach...@gmail.com
> > >:
> > >
> > > > Hello!
> > > >
> > > > I have added you to Contributors of our project, you can now assign
> > issues
> > > > to yourself.
> > > >
> > > > Please read
> > > > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> > > >
> > > > Regards,
> > > > --
> > > > Ilya Kasnacheev
> > > >
> > > >
> > > > чт, 23 янв. 2020 г. в 15:31, Лев Киселев  >:
> > > >
> > > > > Hello,
> > > > > I want to take part in the development of Apache Ignite.
> > > > > Primary skills: Java SE, Java 8, Spring framework, SQL.
> > > > > Also: Multithreading (incl. FJP), Design Patterns, Algorithms and
> > Data
> > > > > Structures.
> > > > >
> > > > > My JIRA ID: l4ndsc4pe
> > > > >
> > > > > Thanks.
> > > > >
> > > >
> >
> >
> >
> > --
> > Best regards,
> > Ivan Pavlukhin
> >
>

Re: [ANNOUNCE] New Apache Ignite PMC member: Igor Sapego

[Dmitriy Pavlov]

Hi Igor,

congrats with new role.

Sincerely,
Dmitriy Pavlov

пн, 27 янв. 2020 г. в 12:51, Petr Ivanov :

> Congratulations, Igor.
>
> Well deserved!
>
>
> > On 27 Jan 2020, at 08:57, Ivan Pavlukhin  wrote:
> >
> > Hello Ignite Community,
> >
> > The Project Management Committee (PMC) for Apache Ignite has invited
> > Igor Sapego to join the PMC as a new member and we are pleased to
> > announce that he has accepted.
> >
> > Igor is an active Community member for a long time. He made a
> > worthless contribution in Ignite C++ development and continues to do
> > it today. Moreover he drives thin clients development for other
> > programming languages. Additionally, always helpful on users mailing
> > list. Wrote blog posts and spoke publicly about Ignite.
> >
> > Being a PMC member enables assistance with the management and to guide
> > the direction of the project.
> >
> > Please join me in congratulating Igor!
> >
> > Best regards,
> > Ivan Pavlukhin
> > on behalf of Apache Ignite PMC
>
>

[ANNOUNCE] New Apache Ignite PMC member: Saikat Maitra

[Dmitriy Pavlov]

Hello Ignite Community,



The Project Management Committee (PMC) for Apache Ignite has invited Saikat
Maitra to join the PMC as a new member and we are pleased to announce that
he has accepted.



Saikat joined the community a long time ago and earned the role of a
committer by integrating Ignite with various streaming technologies. Since
those times Saikat keeps maintaining his contributions and helps newcomers
with their first tasks and reviews. Also, he is involved in a much larger
modularization initiative and does his first public presentations about
Apache Ignite.



Being a PMC member enables assistance with the management and to guide the
direction of the project.



Best Regards,

Dmitriy Pavlov

on behalf of Apache Ignite PMC

Re: Launched Ignite meetups and redesigned events pages

[Dmitriy Pavlov]

Hi Igniters, Mauricio, Ignacio, and Denis,

Thank you all for updating these pages.

I would like to stress just one thing:
should you have in mind some topic you can run talk about, please feel
absolutely free to fill submission proposal.

To submit proposal you need to fill in this form
https://docs.google.com/forms/d/e/1FAIpQLSdiY7movHKvyWg3gOVedHgukJJnNiaejSO_X838vBseL9VmiQ/viewform
.

Sincerely,
Dmitriy Pavlov

вт, 7 янв. 2020 г. в 02:48, Denis Magda :

> Igniters,
>
> I've just merged changes contributed by Mauricio and Ignacio, who helped
> us to prepare professional webpages for Ignite meetup groups around the
> world [1] and for Ignite events [2]. Now you can easily enroll in a meetup
> group nearby or sign up for an upcoming event to be hosted one of our
> experts.
>
> Please check them out and share your feedback. In the meantime, three of
> us are going to carry on with optimizations and changes making the website
> more useful for developers as well as more searchable/discoverable from
> various search engines.
>
> [1] https://ignite.apache.org/meetup-groups.html
> [2] https://ignite.apache.org/events.html
>
> -
> Denis
>

Re: Warning from user/dev lists mailing program

[Dmitriy Pavlov]

Hi Ivan,

I also receive such emails recurrently, but this program didn't reject my
subscription. So I just ignore it.

Sincerely,
Dmitriy Pavlov

пн, 23 дек. 2019 г. в 18:25, Ivan Pavlukhin :

> What is also interesting here is it specific to gmail or other email
> providers are affected as well?
>
> And what bothers me is that some messages seems to be undelivered to
> my inbox. I even followed ezmlm instructions to request "bouncing"
> messages and it worked fine. But it is inconvenient =(
>
> пн, 23 дек. 2019 г. в 16:33, Alexey Goncharuk  >:
> >
> > Hi Ivan,
> >
> > I receive such emails from time to time and I did not manage to
> > understand the conditions when this happens. From a quick search it
> looked
> > like it was related to the number of messages being received per certain
> > time interval, but I could not confirm this based on the number of
> messages
> > on our lists.
> >
> > I also would be curios to know is someone solved this.
> >
> > пн, 23 дек. 2019 г. в 14:45, Ivan Pavlukhin :
> >
> > > Hi,
> > >
> > > From time to time I receive a following warning message (see quoted
> > > below) from a program managing Ignite mailing lists. My guess is that
> > > it is somehow related to gmail (spam) filtering. Does anyone
> > > experience the same? Does anyone know how to fix it?
> > >
> > > Quoted message
> > > Hi! This is the ezmlm program. I'm managing the
> > > u...@ignite.apache.org mailing list.
> > >
> > >
> > > Messages to you from the user mailing list seem to
> > > have been bouncing. I've attached a copy of the first bounce
> > > message I received.
> > >
> > > If this message bounces too, I will send you a probe. If the probe
> bounces,
> > > I will remove your address from the user mailing list,
> > > without further notice.
> > >
> > > --
> > > Best regards,
> > > Ivan Pavlukhin
> > >
>
>
>
> --
> Best regards,
> Ivan Pavlukhin
>

Re: Cache 6 suite is broken

[Dmitriy Pavlov]

Hi Ivan, Igniters,

My proposal is to apply PR and take a look to wider statistics in the
master branch. WDYT?

Sincerely,
Dmitriy Pavlov

ср, 18 дек. 2019 г. в 09:36, Ivan Pavlukhin :

> Igniters,
>
> I run tests several times for my PR [1] and results [2] looks somehow
> better than in master [3]. But the problematic test seems too flaky.
> So, I cannot decide between 2 options:
> 1. Apply PR [1].
> 2. Ignore the problematic test.
> (Unfortunately do not have a chance to investigate and fix)
>
> Someone's opinion would be helpful here.
>
> [1] https://github.com/apache/ignite/pull/7142
> [2]
> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Cache6?branch=pull%2F7142%2Fhead=overview
> [3]
> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Cache6?branch=%3Cdefault%3E=overview
>
> пн, 16 дек. 2019 г. в 13:38, Ivan Pavlukhin :
> >
> > An update. After increasing NetworkTimeout [1] the test passes rarely
> [2].
> >
> > [1] https://github.com/apache/ignite/pull/7142/files
> > [2]
> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Cache6?branch=pull%2F7142%2Fhead=overview
> >
> > пн, 16 дек. 2019 г. в 09:07, Ivan Pavlukhin :
> > >
> > > Hi,
> > >
> > > I noticied that Cache 6 suite finishes badly (exit code 137) almost
> > > everytime [1] on master. It started recently. A problematic test
> > > inside is IgniteCache150ClientsTest. I made some attempts to fix the
> > > test (including reverting recent commits), but had no luck. And a hard
> > > part here is that I do not know whether the issue was caused by code
> > > changes or it is infrastructural one. My best attempt was increasing
> > > NetworkTimeout in test IgniteConfiguration [2]. After that the suite
> > > was able to finish, but IgniteCache150ClientsTest failed. Also, the
> > > problematic test seems so flaky, there are many failures in history.
> > >
> > > Do not have any really good solution in my mind. I see following
> options:
> > > 1. Use workaround in PR [2].
> > > 2. Ignore test and dig deeper in scope of a separate ticket.
> > >
> > > What do you think?
> > >
> > > [1]
> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Cache6?branch=%3Cdefault%3E=overview
> > > [2] https://github.com/apache/ignite/pull/7142/files
> > > --
> > > Best regards,
> > > Ivan Pavlukhin
> >
> >
> >
> > --
> > Best regards,
> > Ivan Pavlukhin
>
>
>
> --
> Best regards,
> Ivan Pavlukhin
>

Re: joining

[Dmitriy Pavlov]

Hi Prashant,

Thank you for your interest in Apache Ignite. And I hope the Ignite
community would be glad to work with new contributors.

Just one note: A company can not contribute to an Apache project, but your
employee(s) can contribute as an individual. Similar is true for
management, an employee can be a member of PMC, but the project is managed
not by companies but only by the project management committee.

Sincerely,
Dmitriy Pavlov

сб, 14 дек. 2019 г. в 05:27, Prashant Rahulkar :

> Hello Everyone,
> I have started software firm in India, with complete motivation to focus on
> open source technologies, so as a part of company policy we will star to
> contribute in this project with our company name.
>
>
> Thanks,
> PrashantR.
>

[ANNOUNCE] New committer: Aleksei Scherbakov

[Dmitriy Pavlov]

Hello Ignite Community,

The Project Management Committee (PMC) for Apache Ignite has invited
Aleksei Scherbakov to become a committer and we are pleased to announce
that he has accepted.

Aleksei investigated and fixed a lot of critical issues. Seems, everybody's
familiar with "partitions counters" fix
https://issues.apache.org/jira/browse/IGNITE-10078 solved huge
data loss issue. On top of that, Aleksei recently finished Data Consistency
wiki: https://cwiki.apache.org/confluence/display/IGNITE/Data+consistency
It will definitely help newcomers in better understanding of product
internals.

Being a committer enables easier contribution to the project since there is
no need to go via the patch submission process. This should enable better
productivity.

Aleksei, thank you!

Best Regards,
Dmitriy Pavlov
on behalf of Apache Ignite PMC

[ANNOUNCE] New Apache Ignite PMC member: Ivan Pavlukhin

[Dmitriy Pavlov]

Hello Ignite Community,



The Project Management Committee (PMC) for Apache Ignite has invited Ivan
Pavlukhin to become a PMC member and we are pleased to announce that he has
accepted.



We appreciate Ivan’s efforts in supporting newcomers. Also, Ivan
contributed MVCC deadlock detector. He is very active dev-list member, he
contributes ideas and does review,- all these things are essential for
community building.



Being a PMC member enables assistance with the management and to guide the
direction of the project.



Please join me in welcoming Ivan’s in his new role in the Apache Ignite
community. Ivan, keep the pace!



Best Regards,

Dmitriy Pavlov

on behalf of Apache Ignite PMC

[ANNOUNCE] New Apache Ignite PMC member: Alexey Zinoviev

[Dmitriy Pavlov]

Hello Ignite Community,



The Project Management Committee (PMC) for Apache Ignite has invited Alexey
Zinoviev (zaleslaw) to become a PMC member and we are pleased to announce
that he has accepted.



Alexey is doing a great work by spreading the word about Apache Ignite, he
contributes to new integrations with other platforms, and he is de facto
maintainer of ML component.



Being a PMC member enables assistance with the management and to guide the
direction of the project.



Please join me in welcoming Alexey in his new role!



Best Regards,

Dmitriy Pavlov

on behalf of Apache Ignite PMC

Launch of the 2020 ASF Community Survey

[Dmitriy Pavlov]

Hello Ignite Users, Enthusiasts and Contributors,

If you have an apache.org email, you should have received an email with an
invitation to take the 2020 ASF Community Survey. Please take 15 minutes to
complete it.

If you do not have an apache.org email address or you didn’t receive a
link, please follow this link to the survey:
https://communitysurvey.limequery.org/454363

This survey is important because it will provide us with scientific
information about our community, and shed some light on how we can
collaborate better and become more diverse. Our last survey of this kind
was implemented in 2016, which means that our existing data about Apache
communities is outdated. The deadline to complete the survey is January
4th, 2020. You can find information about privacy on the survey’s
Confluence page [1].

Your participation is paramount to the success of the Apache Ignite
project! Please consider filling out the survey, and share this news with
your fellow Apache contributors. As individuals form the Apache community,
your opinion matters: we want to hear your voice.

If you have any questions about the survey or otherwise, please reach out
to us!

Kindly,
ASF Diversity & Inclusion
https://diversity.apache.org/


[1]
https://cwiki.apache.org/confluence/display/EDI/Launch+Plan+-+The+2020+ASF+Community+Survey

Re: [DISCUSS] Links to commercial version resources in community wiki

[Dmitriy Pavlov]

I agree that 'TODO: please, fix me GG-X' Should be definitely avoided
in the code in all cases. A number of community members don't have access
to these tickets.

This is the same as linking to GG's private documentation or internal
network servers. It doesn't make sense.

ср, 4 дек. 2019 г. в 14:53, Ivan Pavlukhin :

> Maxim,
>
> References to GG tickets have definitely no meaning for community. But
> references to documentation on the other hand can be very useful,
> actually it is very similar to references to Wikipedia or
> aforementioned Oracle resources.
>
> ср, 4 дек. 2019 г. в 14:40, Maxim Muzafarov :
> >
> > Folks,
> >
> > In general case, 3rd party resource links look for me absolutely
> > normal e.g. we could have some links on Oracle's documentation pages.
> >
> > But let's add a little accuracy. We are talking about links to
> > GridGain documentation pages. For me, it's the same as comments `TODO:
> > please, fix me GG-X` in the source code (e.g. like this one [1]).
> > Looks a bit strange :-)
> >
> >
> > [1]
> https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/PartitionUpdateCounter.java#L43
> >
> > On Tue, 3 Dec 2019 at 20:13, Dmitriy Pavlov  wrote:
> > >
> > > Hi Igniters,
> > >
> > > It is not good if we'll made a tradition of linking to company websites
> > > from the community website / wiki / lists. But if it makes sense to
> mention
> > > something useful for users, why not.
> > >
> > > And in this particular case it may be ok, if it is relevant. Just
> remember,
> > > community resources are not Nascar cars.
> > >
> > > See also https://www.apache.org/foundation/marks/linking
> > >
> > > Sincerely,
> > > Dmitriy Pavlov
> > >
> > > вт, 3 дек. 2019 г. в 19:50, Denis Magda :
> > >
> > > > Hi Ivan,
> > > >
> > > > If an author of an article believes that there is a 3rd party
> resource that
> > > > is handy and helpful for his/her work then there is nothing wrong to
> refer
> > > > to it. Based on Alexey's response in another thread, that GridGain
> page
> > > > brings more clarity to the topic, thus, don't see any issue with
> that.
> > > >
> > > >
> > > > -
> > > > Denis
> > > >
> > > >
> > > > On Tue, Dec 3, 2019 at 6:41 AM Ivan Pavlukhin 
> wrote:
> > > >
> > > > > Folks,
> > > > >
> > > > > In a thread about a document describing data consistency [1] in
> Ignite
> > > > > it was identified that there is a link to GridGain documentation.
> > > > >
> > > > > I do not have strong arguments against having such links in
> community
> > > > > wiki. But it interesting to me to discuss the subject with
> community.
> > > > > Might be there is some common practice in ASF communities about the
> > > > > subject.
> > > > >
> > > > > Please, share your thoughts.
> > > > >
> > > > > [1]
> https://cwiki.apache.org/confluence/display/IGNITE/Data+consistency
> > > > > --
> > > > > Best regards,
> > > > > Ivan Pavlukhin
> > > > >
> > > >
>
>
>
> --
> Best regards,
> Ivan Pavlukhin
>

Re: [DISCUSS] Links to commercial version resources in community wiki

[Dmitriy Pavlov]

Hi Igniters,

It is not good if we'll made a tradition of linking to company websites
from the community website / wiki / lists. But if it makes sense to mention
something useful for users, why not.

And in this particular case it may be ok, if it is relevant. Just remember,
community resources are not Nascar cars.

See also https://www.apache.org/foundation/marks/linking

Sincerely,
Dmitriy Pavlov

вт, 3 дек. 2019 г. в 19:50, Denis Magda :

> Hi Ivan,
>
> If an author of an article believes that there is a 3rd party resource that
> is handy and helpful for his/her work then there is nothing wrong to refer
> to it. Based on Alexey's response in another thread, that GridGain page
> brings more clarity to the topic, thus, don't see any issue with that.
>
>
> -
> Denis
>
>
> On Tue, Dec 3, 2019 at 6:41 AM Ivan Pavlukhin  wrote:
>
> > Folks,
> >
> > In a thread about a document describing data consistency [1] in Ignite
> > it was identified that there is a link to GridGain documentation.
> >
> > I do not have strong arguments against having such links in community
> > wiki. But it interesting to me to discuss the subject with community.
> > Might be there is some common practice in ASF communities about the
> > subject.
> >
> > Please, share your thoughts.
> >
> > [1] https://cwiki.apache.org/confluence/display/IGNITE/Data+consistency
> > --
> > Best regards,
> > Ivan Pavlukhin
> >
>

Apache Ignite trademark registration and related updates

[Dmitriy Pavlov]

Dear Igniters,



I’m happy to announce that Apache Ignite trademark is registered in the US.



Our website was updated to use "Apache Ignite®" instead of "Apache
Ignite™". Similar updates were applied to some groups in social networks,
and to Russian Local meetups groups at meetup.com. If you notice ™ usage,
please feel free to update.



Note that it is only the full name "Apache Ignite" that is registered so
you can't use "Ignite®". And, as always, I encourage everybody to name the
product as Apache Ignite rather than Ignite.



Our website footer was updated to say "... are either registered trademarks
or trademarks of ..."



So, Apache Ignite is registered trademark both in US and EU.



Sincerely,

Dmitriy Pavlov


P.S. see also  https://www.apache.org/foundation/marks/

Re: [RESULT] Ignite PMC Chair Vote

[Dmitriy Pavlov]

Hi Igniters,

Thanks to everyone for all of the congratulations!

I’m very honored to serve in PMC Chair role.

Sincerely,
Dmitriy Pavlov

пт, 22 нояб. 2019 г. в 09:00, Ivan Pavlukhin :

> Hooray!
>
> пт, 22 нояб. 2019 г. в 05:13, Saikat Maitra :
> >
> > Congrats, Dmitry!
> >
> > Regards,
> > Saikat
> >
> > On Thu, Nov 21, 2019 at 3:05 PM Denis Magda  wrote:
> >
> > > Igniters,
> > >
> > > The board has officially approved and appointed Dmitry for the role of
> > > Ignite PMC Chair.
> > >
> > > Congrats, Dmitry! Well deserved! Let's move on, there are many things
> for
> > > all of us to do together ;)
> > >
> > > -
> > > Denis
> > >
> > >
> > > On Thu, Nov 7, 2019 at 1:39 PM Dmitriy Pavlov 
> wrote:
> > >
> > > > Hi Folks,
> > > >
> > > > Thank you, it would be a great honor for me to serve in this role.
> And I
> > > > really surprised by this community decision (other PMC members have a
> > > huge
> > > > contribution to the project in different aspects and they
> > > > all deserve recognition).
> > > >
> > > > But it is a little bit early for congrats since the ASF Board
> appoints
> > > new
> > > > Chair. It is an advisory decision of project PMC who will be the next
> > > > Chair.
> > > >
> > > > AFAIK next Board meeting is scheduled for November 20. Let's wait for
> > > their
> > > > decision first.
> > > >
> > > > Sincerely,
> > > > Dmitriy Pavlov
> > > >
> > > > чт, 7 нояб. 2019 г. в 13:44, Alexey Zinoviev  >:
> > > >
> > > > > Dmitry,  congrats, we will wait the Community roadmap from you and
> will
> > > > be
> > > > > happy to start discussion about that In asf slack or on dev-list!
> > > > >
> > > > > чт, 7 нояб. 2019 г., 12:27 Petr Ivanov :
> > > > >
> > > > > > Dmitriy, congratulations!
> > > > > >
> > > > > >
> > > > > > > On 7 Nov 2019, at 12:06, Николай Кулагин <
> zzzadruga@gmail.com>
> > > > > > wrote:
> > > > > > >
> > > > > > > Dmitry, my congratulations!
> > > > > > >
> > > > > > > This is a clear sign that you are moving in the right
> direction.
> > > > > > > Good luck!
> > > > > > >
> > > > > > > чт, 7 нояб. 2019 г. в 11:12, Вячеслав Коптилин <
> > > > > slava.kopti...@gmail.com
> > > > > > >:
> > > > > > >
> > > > > > >> Hello Igniters, Dmitriy,
> > > > > > >>
> > > > > > >> Congrats, Dmitriy!
> > > > > > >> I hope that a board's approval is just a formal step :)
> > > > > > >>
> > > > > > >> Thanks,
> > > > > > >> S.
> > > > > > >>
> > > > > > >> чт, 7 нояб. 2019 г. в 10:52, Ivan Pavlukhin <
> vololo...@gmail.com
> > > >:
> > > > > > >>
> > > > > > >>> Great news!
> > > > > > >>>
> > > > > > >>> Dmitriy my congratulations! I really believe that it is the
> > > proper
> > > > > > >>> decision today and will make a great positive impact on
> Ignite
> > > > > > >>> Community.
> > > > > > >>>
> > > > > > >>> Hooray!
> > > > > > >>>
> > > > > > >>> ср, 6 нояб. 2019 г. в 22:28, Denis Magda  >:
> > > > > > >>>>
> > > > > > >>>> Igniters,
> > > > > > >>>>
> > > > > > >>>> As early head-ups for you. Ignite PMCs came to a consensus
> and
> > > > > > selected
> > > > > > >>>> Dmitry Pavlov as the next Chair. Next, we need to get a
> board's
> > > > > > >> approval.
> > > > > > >>>> Our request will be reviewed during the next board meeting
> that
> > > > > takes
> > > > > > >>> place
> > > > > > >>>> this month: https://www.apache.org/dev/pmc.html#newchair
> > > > > > >>>>
> > > > > > >>>> -
> > > > > > >>>> Denis
> > > > > > >>>>
> > > > > > >>>>
> > > > > > >>>> On Fri, Nov 1, 2019 at 12:32 PM Denis Magda <
> dma...@apache.org>
> > > > > > wrote:
> > > > > > >>>>
> > > > > > >>>>> Ignite community, the votes were spread this way.
> > > > > > >>>>>
> > > > > > >>>>> Binding (votes of Ignite PMC members):
> > > > > > >>>>> • Alexey Goncharuk - 3
> > > > > > >>>>> • Dmitry Pavlov - 2
> > > > > > >>>>> • Nikolay Izhikov  - 3
> > > > > > >>>>> • Pavel Tupitsyn - 1
> > > > > > >>>>>
> > > > > > >>>>> Non-binding (votes of other community members):
> > > > > > >>>>> • Alexey Goncharuk - 2
> > > > > > >>>>> • Dmitry Pavlov - 11
> > > > > > >>>>> • Nikolay Izhikov - 1
> > > > > > >>>>> • Pavel Tupitsyn - 0
> > > > > > >>>>>
> > > > > > >>>>> As long as only the binding votes can be counted towards
> the
> > > > > > >>>>> election results, we have two candidates who got equal
> votes -
> > > > > Alexey
> > > > > > >>> and
> > > > > > >>>>> Nikolay. Please give Ignite PMC some time to figure out
> how to
> > > > > > >> proceed
> > > > > > >>>>> further.
> > > > > > >>>>>
> > > > > > >>>>>
> > > > > > >>>>> -
> > > > > > >>>>> Denis
> > > > > > >>>>>
> > > > > > >>>
> > > > > > >>>
> > > > > > >>>
> > > > > > >>> --
> > > > > > >>> Best regards,
> > > > > > >>> Ivan Pavlukhin
> > > > > > >>>
> > > > > > >>
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
>
>
>
> --
> Best regards,
> Ivan Pavlukhin
>

Re: Please Authrorize GG's instance of AI TC bot to run backround checks

[Dmitriy Pavlov]

Sure, once one user clicks authorize server,
1) his/her credentials are stored in memory and
2) process of background checks of TC,builds,queue status is started. On
top of that, triggering for new builds is started.

TC Bot doesn't have standalone credentials for TC server(s) configured.
Only host(s) is specified in the conf/properties.


пн, 18 нояб. 2019 г. в 15:08, Ivan Pavlukhin :

> Dmitriy,
>
> Could you please clarify TC Bot needs this "Authorization"? What
> happens inside? Simply would like to understand.
>
> пн, 18 нояб. 2019 г. в 14:57, Dmitriy Pavlov :
> >
> > Hi Ivan,
> >
> > If menu is hidden that means somebody already authorized the server. If
> one
> > can see this menu item, this means none from users authorized it.
> > Authorization is required after restart. If service fails, there is shell
> > script that tries to establish it again. Probably TC Bot instance failed
> > for whatever reason, and script restarted it automatically. Now it is
> > authorized so my request is not relevant.
> >
> > Now it should be up and running as usual. If not, please reply here or on
> > some another topic in the list.
> >
> > Sincerely
> > Dmitriy Pavlov
> >
> > пн, 18 нояб. 2019 г. в 11:19, Ivan Pavlukhin :
> >
> > > Dmitriy,
> > >
> > > Would be glad to do it but cannot find "'Authorize Server' menu item
> > > near the user
> > > name". Where should it be (https://mtcga.gridgain.com/ or somewhere
> else)?
> > >
> > > сб, 16 нояб. 2019 г. в 17:30, Dmitriy Pavlov :
> > > >
> > > > Hi Folks,
> > > >
> > > > Could someone from GG press the 'Authorize Server' menu item near the
> > > user
> > > > name? This will enable the bot to run all background checks.
> > > >
> > > > Technically anyone can authorize the server, but it is better that
> > > > GridGainer will do it.
> > > >
> > > > Sincerely,
> > > > Dmitriy Pavlov
> > >
> > >
> > >
> > > --
> > > Best regards,
> > > Ivan Pavlukhin
> > >
>
>
>
> --
> Best regards,
> Ivan Pavlukhin
>