Re: EA versioning

Ok from me, the troublemaker :) Glad that we agreed on a policy. On 1 Dec 2015 19:51, "Yakov Zhdanov" wrote: > Guys, I like the scheme we have come to. > > Will submit apache-ignite-1.5.0-b1-rc1 for vote tomorrow :) > > --Yakov >

Re: EA versioning

Thanks you, Raul, for attracting everyones attention to! :) --Yakov 2015-12-02 0:15 GMT+03:00 Raul Kripalani : > Ok from me, the troublemaker :) > > Glad that we agreed on a policy.

[jira] [Created] (IGNITE-2047) Improvements for Ignite Web Console for 1.6

Pavel Konstantinov created IGNITE-2047: -- Summary: Improvements for Ignite Web Console for 1.6 Key: IGNITE-2047 URL: https://issues.apache.org/jira/browse/IGNITE-2047 Project: Ignite

[jira] [Created] (IGNITE-2048) Secondary file system (SFS) is not mandatory in UGFS settings

Pavel Konstantinov created IGNITE-2048: -- Summary: Secondary file system (SFS) is not mandatory in UGFS settings Key: IGNITE-2048 URL: https://issues.apache.org/jira/browse/IGNITE-2048 Project:

[jira] [Created] (IGNITE-2045) Make message handling by OdbcProcessor synchronous.

Igor Sapego created IGNITE-2045: --- Summary: Make message handling by OdbcProcessor synchronous. Key: IGNITE-2045 URL: https://issues.apache.org/jira/browse/IGNITE-2045 Project: Ignite Issue

Re: EA versioning

Thanks, Raul! I like your synthesis. We have already agreed to use 1.5.0-*b1* format for early access builds, but I did not see any opinions about *final* for releases. Does anyone have objections to use *final *qualifier for release builds to conform both OSGi and Maven versioning? Sergi

[jira] [Created] (IGNITE-2046) CPP: Implement SQLColumns ODBC API function

Igor Sapego created IGNITE-2046: --- Summary: CPP: Implement SQLColumns ODBC API function Key: IGNITE-2046 URL: https://issues.apache.org/jira/browse/IGNITE-2046 Project: Ignite Issue Type:

Re: Disabling patch-validation mechanism on TC

Removed patch-based information from the site. Placed a direct link to wiki that describes how to contribute using pull-requests instead. — Denis > On 1 дек. 2015 г., at 17:56, Denis Magda wrote: > > Fully support this endeavor. > > However, we have to update not only

Re: Website links

I’ve tried to fix this issue today but always getting the following error every time I try to open downloads page on my local server The requested URL /download.cgi was not found on this server. This file is missing in the SVN repository. Who has a local copy of it? — Denis > On 1 дек. 2015

Re: Publishing readme.io site

Dmitriy, https://apacheignite-net.readme.io/ got approved and published under open-source terms. Please remove https://dash.readme.io/project/apache-ignite-net/v1.0/dashboard. Thanks, On Tue, Dec 1, 2015 at 5:36 PM, Pavel Tupitsyn wrote: > Dmitriy, I have changed the

Re: Publishing readme.io site

Wow, very nice! Great job on the .NET documentation! Hopefully C++ is not far behind :) On Tue, Dec 1, 2015 at 11:08 PM, Pavel Tupitsyn wrote: > Dmitriy, https://apacheignite-net.readme.io/ got approved and published > under open-source terms. > Please remove >

[jira] [Created] (IGNITE-2051) First query doesn't opens on notebook page

Pavel Konstantinov created IGNITE-2051: -- Summary: First query doesn't opens on notebook page Key: IGNITE-2051 URL: https://issues.apache.org/jira/browse/IGNITE-2051 Project: Ignite

Re: EA versioning

Guys, We are introduced new version naming strategy, but do not added corresponding tests to GridProductVersionSelfTest. I created issue for this:https://issues.apache.org/jira/browse/IGNITE-2049 Please fix before ignite-1.5 goes final. -- Alexey Kuznetsov GridGain Systems www.gridgain.com

[jira] [Created] (IGNITE-2050) NPE: Failed to reinitialize local partitions (preloading will be stopped)

Pavel Konstantinov created IGNITE-2050: -- Summary: NPE: Failed to reinitialize local partitions (preloading will be stopped) Key: IGNITE-2050 URL: https://issues.apache.org/jira/browse/IGNITE-2050

[jira] [Created] (IGNITE-2049) Add to GridProductVersionSelfTest new tests for new naming strategy

Alexey Kuznetsov created IGNITE-2049: Summary: Add to GridProductVersionSelfTest new tests for new naming strategy Key: IGNITE-2049 URL: https://issues.apache.org/jira/browse/IGNITE-2049 Project:

Re: EA versioning

On Tue, Dec 1, 2015 at 5:57 PM, Sergi Vladykin wrote: > Thanks, Raul! I like your synthesis. > > We have already agreed to use 1.5.0-*b1* format for early access builds, > but I did not see any opinions about *final* for releases. > Does anyone have objections to use

Re: EntryProcessor execution semantics

On Tue, Dec 1, 2015 at 8:34 AM, Andrey Kornev wrote: > Dmitriy, > > Here, by "stateless" I meant whatever Alexey meant in his previous post in > this thread. But I'm really talking about being able to have EPs with side > effects and therefore the execution semantics

Re: EA versioning

2015-12-01 21:55 GMT+03:00 Dmitriy Setrakyan : > What would the “final” qualifier give us? It gives us correct and consistent versions not only for Maven, but for OSGi as well. Now we will have For Maven 1.5.0 > 1.5.0-b1 For OSGi1.5.0 < 1.5.0-b1 If we will

Re: EA versioning

On Tue, Dec 1, 2015 at 7:12 PM, Dmitriy Setrakyan wrote: > > In that case, if we add “.final” suffix, will it satisfy both, Maven and > OSGI worlds? Yep. In fact, "final" in Maven is equivalent to no qualifier. From Javadoc [1]: strings are checked for well-known

Re: EA versioning

What would the “final” qualifier give us? From what I can see, Maven version comparison will work fine without it. Does maven have special handling for the “final” suffix? On Tue, Dec 1, 2015 at 10:36 AM, Raul Kripalani wrote: > On Tue, Dec 1, 2015 at 5:57 PM, Sergi Vladykin

Re: EA versioning

On Tue, Dec 1, 2015 at 6:55 PM, Dmitriy Setrakyan wrote: > What would the “final” qualifier give us? From what I can see, Maven > version comparison will work fine without it. Does maven have special > handling for the “final” suffix? > Yes it does. And OSGi doesn't, so a

Re: EA versioning

On Tue, Dec 1, 2015 at 11:09 AM, Raul Kripalani wrote: > On Tue, Dec 1, 2015 at 6:55 PM, Dmitriy Setrakyan > wrote: > > > What would the “final” qualifier give us? From what I can see, Maven > > version comparison will work fine without it. Does maven

Re: EA versioning

Thanks Sergi, In that case I don’t think anyone would object to adding “.final” suffix at the end. Raul, as an OSGI expert, do you confirm? D. On Tue, Dec 1, 2015 at 11:13 AM, Sergi Vladykin wrote: > 2015-12-01 21:55 GMT+03:00 Dmitriy Setrakyan

Re: EA versioning

On Tue, Dec 1, 2015 at 7:15 PM, Dmitriy Setrakyan wrote: > Raul, as an OSGI expert, do you confirm? > Yep, it was my proposal only to add "-final". Just to be clear, this is a Maven qualifier. The maven-bundle-plugin will translate the hyphen to a dot, for compatibility

Re: EA versioning

Guys, I like the scheme we have come to. Will submit apache-ignite-1.5.0-b1-rc1 for vote tomorrow :) --Yakov

Re: [VOTE] Apache Ignite 1.5.0-EA

Thank you, Yakov! It's appreciated. On 1 Dec 2015 07:42, "Yakov Zhdanov" wrote: > Guys, let's close this vote thread. I think we will resubmit another build > today evening. I will also send out my vision on EA process and I ask > everyone to respond on that thread. > >

Re: Publishing readme.io site

Pavel, I think we should not publish ignite.NET wiki at separate domain. Better case is to add .Net (c++, etc ... ) section to https://apacheignite.readme.io/ On Tue, Dec 1, 2015 at 11:35 AM, Pavel Tupitsyn wrote: > It was available, and I have just taken it. > Dmitry,

[GitHub] ignite pull request: Tmp PR to run test on TC

GitHub user ashutakGG opened a pull request: https://github.com/apache/ignite/pull/283 Tmp PR to run test on TC You can merge this pull request into a Git repository by running: $ git pull https://github.com/ashutakGG/incubator-ignite ignite-testIterator Alternatively you

EA versioning

Guys, When trying to release Apache Ignite 1.5.0 we came to conclusion that we had to proceed with EA version rather than with final release due to many reasons. I think that everyone understands the purposes of EA versions and the advantages that we gain if we establish this process in a proper

Re: EA versioning

Looks good for me, but why do we need "-rc1" ??? Maybe if vote failed just increase EA number? Mixing EA and RC in one name - looks (IMHO) confusing for me... On Tue, Dec 1, 2015 at 4:35 PM, Yakov Zhdanov wrote: > Guys, > > When trying to release Apache Ignite 1.5.0 we

[jira] [Created] (IGNITE-2039) Please generate two 'NodeStartup' classes - NodeStartupServer and NodeStartupClient

Pavel Konstantinov created IGNITE-2039: -- Summary: Please generate two 'NodeStartup' classes - NodeStartupServer and NodeStartupClient Key: IGNITE-2039 URL: https://issues.apache.org/jira/browse/IGNITE-2039

[jira] [Created] (IGNITE-2040) Please generate java classes for all metadata linked with caches

Pavel Konstantinov created IGNITE-2040: -- Summary: Please generate java classes for all metadata linked with caches Key: IGNITE-2040 URL: https://issues.apache.org/jira/browse/IGNITE-2040

Re: EA versioning

Alexey. We don't mix RC and EA. RCX just added to package for vote. On Tue, Dec 1, 2015 at 12:41 PM, Alexey Kuznetsov wrote: > Looks good for me, but why do we need "-rc1" ??? > > Maybe if vote failed just increase EA number? > > Mixing EA and RC in one name - looks

Re: EA versioning

This is how voting for releases works. RC designates that build is under vote. --Yakov 2015-12-01 12:41 GMT+03:00 Alexey Kuznetsov : > Looks good for me, but why do we need "-rc1" ??? > > Maybe if vote failed just increase EA number? > > Mixing EA and RC in one name -

Re: EA versioning

Ok, now I see. But just one more question it is possible to add "-vote1" instead "-rc1"? Or I just do not understand what is abbreviated as "-rc1" ? On Tue, Dec 1, 2015 at 4:53 PM, Sergey Kozlov wrote: > Alexey. > > We don't mix RC and EA. RCX just added to package for

Re: Publishing readme.io site

Pavel, Yes, I did not found how how to create 2-level category too. So seems, if it impossible - better to create separate domain. On Tue, Dec 1, 2015 at 12:30 PM, Pavel Tupitsyn wrote: > Anton, how would you do that? > As I understand, our readme.io template is

Re: EA versioning

AFAIK, in maven you can have versions with qualifiers, like 1.5.0-ea1 and standard versions, like 1.5.0. According to this article [1], all the versions with a qualifier, such as “-ea” will be considered older than the versions without qualifiers. This means that 1.5.0-ea1 will be older than

Re: EA versioning

Dmitriy, Yakov just sent maven output which says that *1.5.0 < 1.5.0-EA1* *1.5.0-EA1 > 1.5.0-final* That's exactly what I was talking about. Sergi 2015-12-01 18:12 GMT+03:00 Dmitriy Setrakyan : > AFAIK, in maven you can have versions with qualifiers, like 1.5.0-ea1

Re: EA versioning

The most promising way which should work for both Maven and OSGi is to use *beta* for EA and use *final *for releases. http://versionatorr.appspot.com/?a=1.5.0-final=1.5.0-beta1 http://versionatorr.appspot.com/?a=1.5.0=1.5.0-beta1 Sergi 2015-12-01 18:16 GMT+03:00 Sergi Vladykin

Re: EA versioning

Also it is an interesting subject with respect to OSGi versioning because Maven and OSGi versions are somewhat conflicting as well. See [1] [1] http://versionatorr.appspot.com/?a=1.5.0-final=1.5.0-ea Sergi 2015-12-01 17:56 GMT+03:00 Raul Kripalani : > It is different when the

Re: EA versioning

I have got the following output: $ java -cp maven-core-3.3.9.jar:maven-artifact-3.3.9.jar org.apache.maven.artifact.versioning.ComparableVersion 1.5.0 1.5.0-EA1 1.5.0-final Display parameters as parsed by Maven (in canonical form) and comparison result: 1. 1.5.0 == 1.5 1.5.0 < 1.5.0-EA1 2.

Re: EA versioning

Guys, let's name early access versions as "x.x.x-aN" or "x.x.x-bN". This will give us transparent version comparison. Serj, thanks for a good point! As far as upcoming release I suggest releasing "1.5.0-b1" since in my understanding it is very close to final release and is higher than "betta"

[GitHub] ignite pull request: Tmp PR to run test on TC

Github user ashutakGG closed the pull request at: https://github.com/apache/ignite/pull/283 --- 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: EA versioning

FYI, OSGi sorts version qualifiers lexicographically: http://wiki.osgi.org/wiki/Bundle-Version Sergi 2015-12-01 18:55 GMT+03:00 Sergi Vladykin : > Anton, > > Since we are not going to mix *b1 *with *beta1* this should work well. > > Nevertheless It seems that it will

[jira] [Created] (IGNITE-2042) Collocated mode is broken for IgniteSet witn BinaryMarshaller

Semen Boikov created IGNITE-2042: Summary: Collocated mode is broken for IgniteSet witn BinaryMarshaller Key: IGNITE-2042 URL: https://issues.apache.org/jira/browse/IGNITE-2042 Project: Ignite

Re: EA versioning

I asked my question because I never see EA and RC in one name. Only one of them. But seems it is OK to have such name. On Tue, Dec 1, 2015 at 7:11 PM, Anton Vinogradov wrote: > RC means Release Candidate. > After successful vote RC cut from name, and this binary

[GitHub] ignite pull request: TC gradlew.bat

GitHub user ashutakGG opened a pull request: https://github.com/apache/ignite/pull/284 TC gradlew.bat It should fix windows TC agents. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ashutakGG/incubator-ignite tc-gradlew_bat

[jira] [Created] (IGNITE-2041) CacheAutoStoreExample: Failed to find class with given class loader for unmarshalling

Ilya Suntsov created IGNITE-2041: Summary: CacheAutoStoreExample: Failed to find class with given class loader for unmarshalling Key: IGNITE-2041 URL: https://issues.apache.org/jira/browse/IGNITE-2041

Re: Publishing readme.io site

Dmitriy, I have changed the subdomain in original project created by Vladimir, so all my work is now under https://dash.readme.io/project/apacheignite-net/v1.5/dashboard. Also I have applied for open source license. Thanks, On Tue, Dec 1, 2015 at 1:09 PM, Anton Vinogradov

Re: EA versioning

Sergi, very good point! Guys, it seems that EA is not a good choice. However, how many of you have ever used RELEASE as version in maven or version range? --Yakov

Re: EA versioning

It is sad that we are learning from bad examples like hazelcast instead of thinking ourselves and making decisions that fast.. Sergi 2015-12-01 17:41 GMT+03:00 Anton Vinogradov : > Sergi, > > Sounds bad. > I've made decision to use EA looking on Hazelcast's versions (

Re: Disabling patch-validation mechanism on TC

Fully support this endeavor. However, we have to update not only the wiki page after that but the start contributing section as well [2] I'll try to find time and update [2] today. [2] https://ignite.apache.org/community/contribute.html#contribute -- Denis On 12/1/2015 5:39 PM, Artem Shutak

Re: EA versioning

It is different when the keyword is part of the version (1.1.1.RELEASE), like Spring, and when it's a qualifier (1.1.1-RELEASE). Maven treats both cases differently. On 1 Dec 2015 14:52, "Yakov Zhdanov" wrote: > Sergi, very good point! Guys, it seems that EA is not a good

[jira] [Created] (IGNITE-2044) CPP: Fix bugs revealed by the ODBC tests.

Igor Sapego created IGNITE-2044: --- Summary: CPP: Fix bugs revealed by the ODBC tests. Key: IGNITE-2044 URL: https://issues.apache.org/jira/browse/IGNITE-2044 Project: Ignite Issue Type:

Re: EA versioning

Sergi, Sounds bad. I've made decision to use EA looking on Hazelcast's versions ( http://mvnrepository.com/artifact/com.hazelcast/hazelcast). Seems we have to use 'alpha' or use 'ga' at release. Or ignore this case and recomend users to use explicit version. On Tue, Dec 1, 2015 at 5:22 PM,

IGNITE-1864 API

Folks (especially Valentin), I want to fix https://issues.apache.org/jira/browse/IGNITE-1864 (Cannot configure jndiNames for CacheJndiTmLookup). I was going to fix it as Val suggested in comments I think we should deprecate CacheTmLookup interface with its > implementations and

Re: EA versioning

Raul, This is how Maven works, exactly because of that we want to switch to 1.5.0-b1 instead of 1.5.0-ea 1.5.0 > 1.5.0-b1 Sergi 2015-12-01 19:06 GMT+03:00 Raul Kripalani : > On Tue, Dec 1, 2015 at 3:33 PM, Yakov Zhdanov wrote: > > > 1.5.0-ea > 1.5.0 > >

RE: EntryProcessor execution semantics

Dmitriy, Here, by "stateless" I meant whatever Alexey meant in his previous post in this thread. But I'm really talking about being able to have EPs with side effects and therefore the execution semantics should be "exactly-once" by default. Besides, maybe it's just me, but intuitively the