Hello Denis, Dmitriy
Thank you for your reply. I am thinking when a new repo is created that
will not mean that the project will undergo Incubator process , Is
this correct?
We actually want to just take few of our integrations and release them
separately as part of this new git repository. We
Hi Denis,
any PMC member can create repository here
https://selfserve.apache.org/
We just need to select repo names in advance.
Sincerely,
Dmitriy Pavlov
пт, 25 окт. 2019 г. в 23:57, Denis Magda :
> Saikat, sounds great.
>
> As long as you're already driving this initiative, could you please
Saikat, sounds great.
As long as you're already driving this initiative, could you please check
with ASF Infra how to put this approach in place? Will we be able to create
several additional repositories for extensions and release them as part of
the Ignite project?
-
Denis
On Thu, Oct 24,
I'm in.
В Чт, 24/10/2019 в 11:48 -0700, Denis Magda пишет:
> Igniters,
>
> Below is a list of proposed candidates. Let's give the candidates time
> until Monday to either confirm or reject their candidacy. Those who confirm
> will be sent for the vote. If we don't hear back from someone by that
Hi folks!
At the moment every resources injected by GridResourceProcessor on node
start, also is clearing on node stop, but before the stopping of
executors. That behavior on node stopping sometimes causes NPEs at calls
which performed in threads of StripedExecutor, for example, see [1].
Does
Alexei Scherbakov created IGNITE-12327:
--
Summary: Cross-cache tx is mapped on wrong primary when enlisted
caches have incompatible assignments.
Key: IGNITE-12327
URL:
Denis, thank you for so detailed description. I agree everywhere.
I need to do just one minor note, just to draw the line between OK and Not
OK. Pay check driving-community is perfectly OK when an employer sponsors
developers to contribute particular feature or fix.
The only one sensitive thing
Denis,
If got it right you wish that there will be more active contributors
(both code patches and help on user list) whose daily job is not only
development of Apache Ignite.
In my mind it will happen naturally when Ignite becomes more
frequently used in fields. As we all understand almost
Nikita, please, feel free:
1. To create a ticket to remove `stopProcess` method from the interface.
This improvement looks obvious to me.
Seems we can implement it easily.
2. To make all Discovery messages immutable.
This one more complex.
I think we should discuss every single mutable message
There are at least a couple more mutable messages:
StartRoutineDiscoveryMessage and SchemaProposeDiscoveryMessage.
I agree that here that making all messages immutable are highly
desired (e.g. it will allow implementation of new discovery
protocols). But so far I do not understand why marker
10 matches
Mail list logo
