Re: Ignite Release Schedules - a suggestion

I actually think that the structure can be simpler and we should just create a branch per release. Most likely, everything that is currently in master should be released anyway, as we all work very hard on making sure that master branch is always stable. I think it does make sense to have a

Re: Halfway to Ignite 1.6

Cos, I agree that it would be nice to merge IGNITE-1371 . However, if there are more fixes and review comments, I would schedule it for the next release. I guess Alexey, Anton, and Igor and better judges on it. Guys, can you please comment? As it

Re: Ignite Release Schedules - a suggestion

On Tue, May 17, 2016 at 01:09AM, endianignite wrote: > With regard to branch structure, I took some time to think and have a > suggestion. Feel free to pick holes in it. > > Major feature releases would continue to have major version numbers: e.g., > 1.7, 1.8, 2.x and so on. Bug-fix releases

Re: Halfway to Ignite 1.6

You can still talk about the release even if it is in the final stages. What would be unfortunate is to miss some of the good features (like IGNITE-1371) just because of an arbitrary date of an even of some kind, which has no relevance to the project itself. For what it worth, rushing releases

Re: 1.5.0.final is breaking packaging: osgi dependency is non-existent

On Mon, May 16, 2016 at 04:09AM, Andrey Kornev wrote: > I'd love to elaborate, Konstantin, but I can't. I have no experience with > the package management tools, neither yum nor rpm. Understood, and that's ok. I am rather trying to understand where these could possible be coming from. > BTW,

[jira] [Created] (IGNITE-3155) visorcmd: "open -d" doesn't work

Vasilisa Sidorova created IGNITE-3155: -- Summary: visorcmd: "open -d" doesn't work Key: IGNITE-3155 URL: https://issues.apache.org/jira/browse/IGNITE-3155 Project: Ignite Issue Type:

Re: Multiple failover SPI

Vasiliy, You can specify failover SPI to use for a particular task via @ComputeTaskSpis annotation. If there is no annotation, the first SPI in the list will be used. -Val On Tue, May 17, 2016 at 12:02 AM, Vasiliy Sisko wrote: > Hello Igniters. > > > I noticed that a grid

Re: Ignite 1.6 release timelines

First version of Web Console merged to ignite-1.6. On Tue, May 17, 2016 at 9:31 PM, Pavel Tupitsyn wrote: > All done from .NET side as well. > > On Tue, May 17, 2016 at 5:28 PM, Denis Magda wrote: > > > Hi, > > > > Reviewed and merged IGNITE-2394

Re: Contribution merged: IGNITE-2394 Cache loading from storage is called on client nodes

Hi Denis, I want to thank you and all devs for your support. Will try to contribute more. Best regards. 2016-05-17 17:26 GMT+03:00 Denis Magda : > Alper, let me thank you from the community side for the contribution you’ve > done. > > The contribution fixed an unpleasant

[GitHub] ignite pull request: IGNITE-3139 .Net: UTF-16 surrogate symbols ar...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/721 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request: IGNITE-3140: Added test for UTF-8 string form...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/723 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Re: Ignite 1.6 release timelines

All done from .NET side as well. On Tue, May 17, 2016 at 5:28 PM, Denis Magda wrote: > Hi, > > Reviewed and merged IGNITE-2394 (Cache loading from storage is called on > client nodes). > Finalized and merged IGNITE-3098 (UTF-16 surrogate pairs are not properly > serialized

Re: Ignite 1.6 release timelines

Hi, Reviewed and merged IGNITE-2394 (Cache loading from storage is called on client nodes). Finalized and merged IGNITE-3098 (UTF-16 surrogate pairs are not properly serialized by BinaryMarshaller). These are last things from my side for 1.6. — Denis > On May 17, 2016, at 11:09 AM, Pavel

[jira] [Created] (IGNITE-3154) More efficient field lookup in binary protocol.

Vladimir Ozerov created IGNITE-3154: --- Summary: More efficient field lookup in binary protocol. Key: IGNITE-3154 URL: https://issues.apache.org/jira/browse/IGNITE-3154 Project: Ignite Issue

[GitHub] ignite pull request: IGNITE-3004 Added variations tests.

GitHub user ntikhonov opened a pull request: https://github.com/apache/ignite/pull/726 IGNITE-3004 Added variations tests. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3004 Alternatively you can

[jira] [Created] (IGNITE-3153) TcpDiscoveryZookeeperIpFinder doesn't properly handle client reconnections

Valentin Kulichenko created IGNITE-3153: --- Summary: TcpDiscoveryZookeeperIpFinder doesn't properly handle client reconnections Key: IGNITE-3153 URL: https://issues.apache.org/jira/browse/IGNITE-3153

[jira] [Created] (IGNITE-3152) Client node's addresses are registered in IP finder

Valentin Kulichenko created IGNITE-3152: --- Summary: Client node's addresses are registered in IP finder Key: IGNITE-3152 URL: https://issues.apache.org/jira/browse/IGNITE-3152 Project: Ignite

[jira] [Created] (IGNITE-3150) Update C++ documentation on readme.io

Igor Sapego created IGNITE-3150: --- Summary: Update C++ documentation on readme.io Key: IGNITE-3150 URL: https://issues.apache.org/jira/browse/IGNITE-3150 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-3149) IGFS: Simplify default configuration.

Vladimir Ozerov created IGNITE-3149: --- Summary: IGFS: Simplify default configuration. Key: IGNITE-3149 URL: https://issues.apache.org/jira/browse/IGNITE-3149 Project: Ignite Issue Type:

[GitHub] ignite pull request: Ignite tledkov test stabilization

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/725 Ignite tledkov test stabilization You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request: Ignite tledkov test stabilization

Github user tledkov-gridgain closed the pull request at: https://github.com/apache/ignite/pull/724 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

Re: Ignite Release Schedules - a suggestion

With regard to branch structure, I took some time to think and have a suggestion. Feel free to pick holes in it. Major feature releases would continue to have major version numbers: e.g., 1.7, 1.8, 2.x and so on. Bug-fix releases would be minor releases: e.g., 1.7.1, 1.7.2, 1.7.x, etc. Major

[GitHub] ignite pull request: Ignite tledkov test stabilization

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/724 Ignite tledkov test stabilization You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: Ignite 1.6 release timelines

Hi, Please note that documentation tickets do not hold the release (IGNITE-3101 and subtasks). Other than that, in .NET, recently emerged 'IGNITE-3139 UTF surrogates' is expected to be merged today. Pavel. On Tue, May 17, 2016 at 10:20 AM, Semyon Boikov wrote: > In 1.6

[jira] [Created] (IGNITE-3147) Add missing properties to configuration (CollisionSpi and FailoverSpi)

Vasiliy Sisko created IGNITE-3147: - Summary: Add missing properties to configuration (CollisionSpi and FailoverSpi) Key: IGNITE-3147 URL: https://issues.apache.org/jira/browse/IGNITE-3147 Project:

Re: Ignite 1.6 release timelines

In 1.6 we implemented 'late affinity assignment' mode (see https://issues.apache.org/jira/browse/IGNITE-324 and IgniteConfiguration.isLateAffinityAssignment) On Mon, May 16, 2016 at 7:03 PM, Alexey Kuznetsov wrote: > https://issues.apache.org/jira/browse/IGNITE-2832 >

Multiple failover SPI

Hello Igniters. I noticed that a grid configuration contain an array of failover SPIs, but using of several failover SPIs is not described in a documentation. Can anyone provide an example how to configure several falover SPI in one grid? -- Vasiliy Sisko GridGain Systems www.gridgain.com