Re: [VOTE] Apche Ignite PMC Chair Election

2016-12-13 Thread Branko Čibej
On 2016-12-10 21:24 (+0100), Dmitriy Setrakyan wrote: > According to the discussion on the dev list [1], the following candidates > were proposed for the Apache Ignite PMC Chair position: > > Vladimir Ozerov > Konstantin Boudnik > Valentin Kulichenko > Denis Magda > Branko Čibej I'm mild

Re: Switching back to review-then-commit process

2016-03-21 Thread Branko Čibej
On 05.03.2016 04:43, Konstantin Boudnik wrote: > It saddens me to see this coming to it ;( Yeah. You guys are introducing red tape that's a barrier for new committers and a bureaucratic trap for everyone else. For example: what happens when a module owner takes off for a couple months? Which is l

Re: Ignite Voting Process

2015-12-31 Thread Branko Čibej
On 31.12.2015 09:58, Branko Čibej wrote: > On 30.12.2015 16:30, Raul Kripalani wrote: >> Hi Anton, >> >> Why don't we publish artifacts for ignite-geospatial, ignite-hibernate and >> ignite-schedule? The lgpl profile is not triggered in these instructions, >>

Re: Ignite Voting Process

2015-12-31 Thread Branko Čibej
On 30.12.2015 16:30, Raul Kripalani wrote: > Hi Anton, > > Why don't we publish artifacts for ignite-geospatial, ignite-hibernate and > ignite-schedule? The lgpl profile is not triggered in these instructions, > and these artifacts cease existing in Maven Central 1.2.0-incubating > onwards. > > I k

Re: EA versioning

2015-12-05 Thread Branko Čibej
It was fun watching this thread. I don't even know what EA means, but I have to wonder ... what's wrong with releasing 1.5.0-beta? Or does the Java world need its own special terminology for yet another well-established process? :) -- Brane

Re: Branch deletion prohibited

2015-11-23 Thread Branko Čibej
On 24.11.2015 05:53, Branko Čibej wrote: > Instead of complaining to me, it'd be far more useful to work with those > other PMCs to produce a set of rules for using Git -- *not* a single > blessed workflow -- that prevent losing important information about the > code base. Ideally

Re: Branch deletion prohibited

2015-11-23 Thread Branko Čibej
On 23.11.2015 20:41, Konstantin Boudnik wrote: > On Mon, Nov 23, 2015 at 09:08AM, Branko Čibej wrote: >> On 23.11.2015 04:13, Konstantin Boudnik wrote: >>> On Sun, Nov 22, 2015 at 02:16PM, Dmitriy Setrakyan wrote: >>>> Cos, >>>> >>>> I beli

Re: Branch deletion prohibited

2015-11-23 Thread Branko Čibej
On 23.11.2015 04:13, Konstantin Boudnik wrote: > On Sun, Nov 22, 2015 at 02:16PM, Dmitriy Setrakyan wrote: >> Cos, >> >> I believe this is the ticket: >> https://issues.apache.org/jira/browse/INFRA-10798 >> >> This policy does seem myopic, would be great if Ignite could get an >> exemption. > Thank

Re: MSDN subscriptions for ASF Committers

2015-11-22 Thread Branko Čibej
On 16.10.2015 09:48, Raul Kripalani wrote: > According to the feedback of other fellow committers, they can take weeks > to approve it (!). When did you apply? Just found this thread ... indeed, it can take weeks or even months. At some point, the subscriptions were bulk-updated every 6 months. :)

Re: Why portable marshaller handle Date and Timestamp in the same way?

2015-10-06 Thread Branko Čibej
On 06.10.2015 12:26, Vladimir Ozerov wrote: > Yakov, this could work in .Net where you have real generics. But it will > not work in Java in general case due to type erasure - you simply cannot > infer the type. > > Let's look closely to this: > Date Java: 10^-3 > Timestamp Java: 10^-9 > DateT

Re: Fwd: Coding Guidelines: zookeeper IP finder and mqtt streamer

2015-10-05 Thread Branko Čibej
On 29.09.2015 00:41, Konstantin Boudnik wrote: > Hmm... > > Negligence, n. : the trait of neglecting responsibilities and lacking concern > syn : omission, oversight "Negligence" usually means continued and repeated (non-)action. In that respect it's an extremely negative label to use; you're effe

Re: Let's please fix the mess in Git

2015-10-01 Thread Branko Čibej
Stop. Right. There. If you're going to start pointing fingers at people you can just shut down the project because you're going down the road of petty bickering. That's a great way to dissolve the community into chaos. On the topic of git usage: * Raul is absolutely right about commit message

Re: what is "communication encryption"?

2015-09-30 Thread Branko Čibej
On 30.09.2015 11:18, Nikolay Tikhonov wrote: > SslContextFactory allows to set different encryption protocols (by default > TLS). I think that just "ssl" confuses users. Might be "ssl\tls=off" more > acceptable? SSL is one (rather old) specification of Transport Layer Security (TLS). These days, y

Re: LGPL in 1.4 examples

2015-09-30 Thread Branko Čibej
On 30.09.2015 10:30, Dmitriy Setrakyan wrote: > On Wed, Sep 30, 2015 at 9:45 AM, Branko Čibej wrote: > >> On 30.09.2015 09:29, Dmitriy Setrakyan wrote: >>> On Wed, Sep 30, 2015 at 8:25 AM, Sergey Kozlov >> wrote: >>>> I filed the ticket: >>>&g

Re: LGPL in 1.4 examples

2015-09-30 Thread Branko Čibej
On 30.09.2015 10:33, Dmitriy Setrakyan wrote: > On Wed, Sep 30, 2015 at 10:30 AM, Branko Čibej wrote: > >> On 30.09.2015 10:28, Sergey Kozlov wrote: >>> Could we build these modules during building example project? It seems a >>> bit excessively from user standpoint.

Re: LGPL in 1.4 examples

2015-09-30 Thread Branko Čibej
On 30.09.2015 10:28, Sergey Kozlov wrote: > Could we build these modules during building example project? It seems a > bit excessively from user standpoint. Why do you think users are dumb and lazy and can't issue two build commands instead of one? > On Wed, Sep 30, 2015 at 10

Re: Introducing "compatibility level" concept.

2015-09-30 Thread Branko Čibej
sk using A-protocol; > 4) Cluster shuts down. > 5) Several new B-nodes appear, but have no clue that something was > persisted using A-protocol. They decide to use B-protocol. > 6) Node A restarts and meets unknown B-protocol. > > On Wed, Sep 30, 2015 at 11:01 AM, Branko Čibej wrote:

Re: Introducing "compatibility level" concept.

2015-09-30 Thread Branko Čibej
On 30.09.2015 09:51, Vladimir Ozerov wrote: > Igniters, > > Normally we are trying to maintain backward compatibility with previous > versions. But it is not always possible. > > E.g. we are about to release portable protocol. There are lots suggestions > how to optimize it, but all of them are rel

Re: LGPL in 1.4 examples

2015-09-30 Thread Branko Čibej
On 30.09.2015 09:29, Dmitriy Setrakyan wrote: > On Wed, Sep 30, 2015 at 8:25 AM, Sergey Kozlov wrote: > >> I filed the ticket: >> Build examples failed from binary fabric package >> >> > > I think the reason is that we do not upload Ignite LGPL i

Re: Nodes starts in tests

2015-09-20 Thread Branko Čibej
On 20.09.2015 10:11, Yakov Zhdanov wrote: > Very cool idea! However this will not be working in 100% cases since > sometimes we need custom grid configurations, SPIs, etc, but for > significant number of tests this will work. This is actually, IMO, a very bad idea. One of the most important princi

Re: Apache 2.0 license with JetBrains copyright in Ignite repository.

2015-09-05 Thread Branko Čibej
On 04.09.2015 10:07, Vladimir Ozerov wrote: > Igniters, > > As a part of continuous intergration process we need to add several > JetBrains .cpp and .h files to our repository. Here is the license header > from these files: > > /* Copyright 2011 JetBrains s.r.o. > > * > * Licensed under the Apach

Re: Ignite Teamcity at Apache side

2015-09-03 Thread Branko Čibej
On 03.09.2015 20:31, Konstantin Boudnik wrote: > On Thu, Sep 03, 2015 at 04:11PM, Anton Vinogradov wrote: >>Hello, >>As you may know we already have Ignite Teamcity server where contributors >>can check it's patches. But, as Cos said before, this test environment >>should be runned

Re: Ignite Teamcity at Apache side

2015-09-03 Thread Branko Čibej
On 03.09.2015 15:11, Anton Vinogradov wrote: > Hello, > > As you may know we already have Ignite Teamcity server where contributors > can check it's patches. But, as Cos said before, this test environment > should be runned under apache hardware. > > Apache test environment based on Jenkins, but it

Re: Update version for master

2015-09-03 Thread Branko Čibej
On 03.09.2015 14:29, Raul Kripalani wrote: > On Thu, Sep 3, 2015 at 1:16 PM, Branko Čibej wrote: > >> There hasn't been a 1.4.0 release package yet, so of course no tag? >> > Well, that would explain it ;-) But why is the POM version for both master > and ignite-

Re: Update version for master

2015-09-03 Thread Branko Čibej
On 03.09.2015 13:47, Raul Kripalani wrote: > If development of the 1.4.x release line will continue in the ignite-1.4 > branch, the master/develop branch should carry 1.5.0-SNAPSHOT (or > 2.0.0-SNAPSHOT, depending on the type of changes expected). > > BTW - it seems the tag for ignite-1.4.0 is miss

Re: SVN changes

2015-09-02 Thread Branko Čibej
On 02.09.2015 21:58, Dmitriy Setrakyan wrote: > On Wed, Sep 2, 2015 at 2:53 AM, Branko Čibej wrote: >> Also, any info about the platform you're using, and what kind of >> authentication store you're using (KWallet? Gnome Keyring? OSX >> Keychain?) would be useful

Re: SVN changes

2015-09-02 Thread Branko Čibej
On 02.09.2015 11:29, Branko Čibej wrote: > On 02.09.2015 09:27, Dmitriy Setrakyan wrote: >> On Tue, Sep 1, 2015 at 8:01 PM, Branko Čibej wrote: >> >>> On 02.09.2015 03:26, Dmitriy Setrakyan wrote: >>>> Brane, >>>> >>>> Since recentl

Re: SVN changes

2015-09-02 Thread Branko Čibej
On 02.09.2015 09:27, Dmitriy Setrakyan wrote: > On Tue, Sep 1, 2015 at 8:01 PM, Branko Čibej wrote: > >> On 02.09.2015 03:26, Dmitriy Setrakyan wrote: >>> Brane, >>> >>> Since recently I am constantly asked to confirm an SVN certificate before >>> u

Re: SVN changes

2015-09-01 Thread Branko Čibej
On 02.09.2015 03:26, Dmitriy Setrakyan wrote: > Brane, > > Since recently I am constantly asked to confirm an SVN certificate before > updating or committing. This is really hurting my productivity :) Yeah, right, one extra keypress, heh. > Any advise on how this can be fixed? You should be able

Re: Download page on the Ignite website

2015-09-01 Thread Branko Čibej
priority is getting the mirror service working again. -- Brane > On Tue, Sep 1, 2015 at 12:36 AM, Branko Čibej wrote: > >> Guys, >> >> I just updated the download page magic because Infra made a major change >> in the way download scripts work last night. >> >&

Re: Ignite 1.4

2015-09-01 Thread Branko Čibej
On 01.09.2015 20:46, Konstantin Boudnik wrote: > On Tue, Sep 01, 2015 at 08:45PM, Sergey Kozlov wrote: >> FYI: We've at least 161 unclosed issues planned to fix in version 1.4 > If there're so many issues to go - perhaps it makes sense not to branch out > this early to avoid extra merges? Or just

Download page on the Ignite website

2015-09-01 Thread Branko Čibej
Guys, I just updated the download page magic because Infra made a major change in the way download scripts work last night. As I was doing this, I noticed that someone ripped out the logic that made the site offer downloads from our closest mirror instead of *straight out of the repository*. How

Re: Ignite 1.4

2015-08-31 Thread Branko Čibej
On 31.08.2015 20:06, Konstantin Boudnik wrote: > Submitting for vote and releasing are two different events. The release date > is when the vote is closed and its tally is counted. Heh, actually, the release date is when the release is announced. :) Which is typically after it's on all the mirrors

Re: Ignite 1.4

2015-08-31 Thread Branko Čibej
On 31.08.2015 08:14, Konstantin Boudnik wrote: > On Mon, Aug 31, 2015 at 01:29AM, Yakov Zhdanov wrote: >> Igniters, >> >> I think we have got to the point to start finalization of 1.4 release. >> >> It contains many important fixes and several new features (e.g. secure >> communication). One more p

Re: API stability.

2015-08-29 Thread Branko Čibej
On 29.08.2015 00:06, Konstantin Boudnik wrote: > On Fri, Aug 28, 2015 at 05:14PM, Vladimir Ozerov wrote: >> Dima, >> >> I'm not suggesting doing this, they are already not stable. For example, >> take a look at IgniteCacheObjectProcessor. This is a component which can be >> injected through plugins

Re: How to fix build failure Check License Headers (by RAT) (Maven

2015-08-27 Thread Branko Čibej
On 27.08.2015 18:13, Ken Cheng wrote: > Summary > --- > Generated at: 2015-08-28T00:09:54+08:00 > Notes: 0 > Binaries: 0 > Archives: 0 > Standards: 41 > > Apache Licensed: 0 > Generated Documents: 0 > > JavaDocs are generated and so license header is optional > Generated files do not required l

Re: How to fix build failure Check License Headers (by RAT) (Maven

2015-08-27 Thread Branko Čibej
On 27.08.2015 17:56, Ken Cheng wrote: > I got below error in the TC, how to fix such issue? > > [12:27:35]Step 4/8: Check License Headers (by RAT) (Maven) (7s) > [12:27:41][Step 4/8] org.apache.ignite:ignite-platform > [12:27:41][org.apache.ignite:ignite-platform] Failed to execute goal > org.apach

Re: Documentation by contributors

2015-08-26 Thread Branko Čibej
On 26.08.2015 21:02, Dmitriy Setrakyan wrote: > On Wed, Aug 26, 2015 at 9:15 PM, Konstantin Boudnik wrote: > >> On Wed, Aug 26, 2015 at 09:07PM, Dmitriy Setrakyan wrote: >>> On Wed, Aug 26, 2015 at 8:44 PM, Konstantin Boudnik >> wrote: Just as a friendly reminder: readme.io hosting still ope

Re: [DiSCUSS] Incompatible changes

2015-08-26 Thread Branko Čibej
compatibility is for Ignite; it's extremely important in Subversion, because it allows independent updates/rollbacks of servers and clients. Or you can avoid the compatibility issue by calling the fixed protocol Ignite 2.0. :) -- Brane On Wed, Aug 26, 2015 at 10:40 AM, Branko Čibej wrote

Re: [DiSCUSS] Incompatible changes

2015-08-26 Thread Branko Čibej
On 26.08.2015 08:54, Alexey Goncharuk wrote: > This particular change does not break the compatibility (a new method is > being added to the public API), however I am +1 for adding these principles > to the dev documentation. Way back when Ignite was still a podling I pointed out this: http:/

Re: Contribution routes to Apache Ignite - updating the website

2015-08-25 Thread Branko Čibej
On 25.08.2015 13:09, Raul Kripalani wrote: > The "Start Contributing" section is somewhat unclear and outdated IMHO. > Unfortunately since this is not Wiki, I cannot modify it (where is the > site's source?). The site is, of course, in Subversion at https://svn.apache.org/repos/asf/ignite/site/tr

Re: Code is ready for bug fix https://issues.apache.org/jira/browse/IGNITE-1226

2015-08-25 Thread Branko Čibej
On 25.08.2015 11:58, Raul Kripalani wrote: > The Github repo of Ignite is read only. It's just a mirror of the Apache > repo. > > You need to fork it into your own Github account. Then you clone the fork > locally and push the branch to it. > > Later, you open a Pull Request to the apache/ignite re

Re: I would like to work on the jira IGNITE-1226

2015-08-24 Thread Branko Čibej
On 24.08.2015 20:54, Ken Cheng wrote: > Hi devs, > > please add my email address kcheng@gmail.com to the dev subscription > list. Why don't you just subscribe? Instructions are here: http://ignite.apache.org/community/resources.html#mail-lists -- Brane