Re: Version mismatch Was: [RESULT] [VOTE] Apache Ignite 1.5.0.final Release (RC3)

2016-01-12 Thread Konstantin Boudnik
And at the risk of repeating myself, I would once again "What's wrong with semver?" Cos On Mon, Jan 11, 2016 at 12:49PM, Anton Vinogradov wrote: > Sergey, > > Correct, thats a backward compatibility fix. > Internal node's version based on maven version but each ".a", ".b" and > ".final"

Re: Version mismatch Was: [RESULT] [VOTE] Apache Ignite 1.5.0.final Release (RC3)

2016-01-12 Thread Konstantin Boudnik
Yes, .final works and I appreciate you guys meeting the downstream community a half-way! My point is different: custom version schemas are always a mess and a headache for all downstreams. Look at the nodejs versioning nightmare, as an example ;) If you don't want to make the developers (and they

Re: Version mismatch Was: [RESULT] [VOTE] Apache Ignite 1.5.0.final Release (RC3)

2016-01-12 Thread Dmitriy Setrakyan
On Tue, Jan 12, 2016 at 12:36 PM, Konstantin Boudnik wrote: > And at the risk of repeating myself, I would once again "What's wrong with > semver?" > Cos, we want “beta” to properly compare with "final" versions in Maven. You have mentioned that you would prefer to avoid the

Re: Version mismatch Was: [RESULT] [VOTE] Apache Ignite 1.5.0.final Release (RC3)

2016-01-11 Thread Anton Vinogradov
Sergey, Correct, thats a backward compatibility fix. Internal node's version based on maven version but each ".a", ".b" and ".final" replaces with corresponding "-". On Wed, Jan 6, 2016 at 7:14 AM, Konstantin Boudnik wrote: > On Tue, Jan 05, 2016 at 08:20PM, Sergey Kozlov

Re: Version mismatch Was: [RESULT] [VOTE] Apache Ignite 1.5.0.final Release (RC3)

2016-01-05 Thread Sergey Kozlov
Hi As I rememeber Ignite node prints out the version with dash due internal requirements. Anton V: could you explain why we made such replacement? On Tue, Jan 5, 2016 at 10:09 AM, Dmitriy Setrakyan wrote: > Cos, this seems to be just a typo. The actual release version

Re: Version mismatch Was: [RESULT] [VOTE] Apache Ignite 1.5.0.final Release (RC3)

2016-01-05 Thread Konstantin Boudnik
On Tue, Jan 05, 2016 at 08:20PM, Sergey Kozlov wrote: > Hi > > As I rememeber Ignite node prints out the version with dash due internal > requirements. > > Anton V: could you explain why we made such replacement? That's a bit confusing, not fatal. And it means that there's either an alternative

Version mismatch Was: [RESULT] [VOTE] Apache Ignite 1.5.0.final Release (RC3)

2016-01-04 Thread Konstantin Boudnik
Running into some issues with Zeppelin integration and have noticed that the version reported by the node in the log isn't the same as the version just released. It says 1.5.0-final instead of 1.5.0.final Cos On Mon, Jan 04, 2016 at 01:12PM, Anton Vinogradov wrote: > Hello! > > Apache

Re: Version mismatch Was: [RESULT] [VOTE] Apache Ignite 1.5.0.final Release (RC3)

2016-01-04 Thread Dmitriy Setrakyan
Cos, this seems to be just a typo. The actual release version in maven is 1.5.0.final. On Mon, Jan 4, 2016 at 8:04 PM, Konstantin Boudnik wrote: > Running into some issues with Zeppelin integration and have noticed that > the > version reported by the node in the log isn't the