Konstantin Boudnik created IGNITE-1269:
--
Summary: ignite-hadoop assembly needs to include ignite-indexing
Key: IGNITE-1269
URL: https://issues.apache.org/jira/browse/IGNITE-1269
Project: Ignite
additionally an ignite node with ignite.sh and the same config.
Also, let me know how I can improve the documentation about Igntie-Spark
integration - you are one of the first persons trying it by yourself, so
your feedback is priceless :)
2015-08-18 16:42 GMT-07:00 Konstantin Boudnik c
side,
right?
Cos
On Wed, Aug 19, 2015 at 01:01AM, Konstantin Boudnik wrote:
Thanks Alexey - that helped somewhat! and let us to figure out the following.
For the benefit of the others here's what we have discovered during the
skype-debug:
1. server and client node process should be started
On Mon, Aug 17, 2015 at 07:39PM, Dmitriy Setrakyan wrote:
On Mon, Aug 17, 2015 at 6:54 PM, Konstantin Boudnik c...@apache.org wrote:
Guys,
I am looking at https://issues.apache.org/jira/browse/IGNITE-1195 as I am
trying to prep for the webinar this week. It seems that if even this bug
On Tue, Aug 18, 2015 at 09:43AM, Nikolay Tikhonov wrote:
Hi,
Hence, the question: how can I disable the build of ignite-yarn (which I
can not care less for) to
have a working Ignite cluster on top of Hadoop 2.6?
You can disable the build of ignite-yarn using the following maven command:
Unfortunately, it won't work in Bigtop 1.0 as it is using Maven 3.0.+ where's
your suggestion only applies to v 3.2.1 and later. At any rate I hacked around
it by explicitly removing the module from the top-level pom file.
I have opened BIGTOP-1968 to see it through...
Cos
On Tue, Aug 18, 2015
Guys,
I am running a simple example to check the latest Spark acceleration module in
Ignite and am hitting some strange stuff (which musta be my configuration
issue, but I can not figure out what is this).
This is how I run spark-shell in my docker container (spark-master and worker
are started
Konstantin Boudnik created IGNITE-1266:
--
Summary: GridUpdateNotifier needs to be fixed to return correct
update version
Key: IGNITE-1266
URL: https://issues.apache.org/jira/browse/IGNITE-1266
Thanks for the contribution! And for the retrospect - very interesting!
Cos
On Mon, Aug 17, 2015 at 06:42PM, Nikita Ivanov wrote:
I'm already grinning from ear to ear so release should go as planned :-))
Awesome news for sure.
As a side historical note: Dmitriy (Setrakyan) and I worked on
On Tue, Aug 18, 2015 at 12:59AM, Dmitriy Setrakyan wrote:
On Tue, Aug 18, 2015 at 12:45 AM, Konstantin Boudnik c...@apache.org wrote:
On Mon, Aug 17, 2015 at 07:39PM, Dmitriy Setrakyan wrote:
On Mon, Aug 17, 2015 at 6:54 PM, Konstantin Boudnik c...@apache.org
wrote:
Guys
like the new process :)
[1]
https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark
2015-08-13 18:13 GMT-07:00 Konstantin Boudnik c...@apache.org:
On Thu, Aug 13, 2015 at 05:54PM, Dmitriy Setrakyan wrote:
On Thu, Aug 13, 2015 at 5:51 PM, Konstantin Boudnik c
It isn't a graduation related issue ;) This is affecting a number of other
lists as well, unfortunately.
Cos
On Thu, Aug 13, 2015 at 07:44AM, Dmitriy Setrakyan wrote:
Hi,
As many of you have noticed, we are having mailing list problems. Some
emails arrive late, while others don't arrive at
On Thu, Aug 13, 2015 at 05:40PM, Alexey Goncharuk wrote:
Maybe I miss a good piece of information about how Git works, but I always
thought that if a pull request is accepted, it will be merged to the GitHub
mirror of Apache Ignite. How will this change get to the original Apache
git
14, 2015 at 12:56 AM, Konstantin Boudnik c...@apache.org wrote:
It isn't a graduation related issue ;) This is affecting a number of other
lists as well, unfortunately.
Cos
On Thu, Aug 13, 2015 at 07:44AM, Dmitriy Setrakyan wrote:
Hi,
As many of you have noticed, we are having
On Thu, Aug 13, 2015 at 05:54PM, Dmitriy Setrakyan wrote:
On Thu, Aug 13, 2015 at 5:51 PM, Konstantin Boudnik c...@apache.org wrote:
On Thu, Aug 13, 2015 at 05:40PM, Alexey Goncharuk wrote:
Maybe I miss a good piece of information about how Git works, but I
always
thought
On Thu, Aug 13, 2015 at 06:31PM, Dmitriy Setrakyan wrote:
On Thu, Aug 13, 2015 at 6:14 PM, Konstantin Boudnik c...@apache.org wrote:
Yeah, as I said don't worry about it guys: it isn't the first graduation
from
the Incubator, not the last, nor most special. INFRA knows what
wrote:
But, why I can open both http://ignite.apache.org and
https://ignite.incubator.apache.org?
It is a part of graduation?
I believe that after graduation, the incubator link will redirect to
ignite.apache.org URL.
On Fri, Aug 14, 2015 at 12:56 AM, Konstantin Boudnik c
The correct state - PA - is set about 11 minutes ago. May be the check for new
patches happens every 15 minutes or less ?
On August 11, 2015 11:32:04 PM PDT, Valentin Kulichenko
valentin.kuliche...@gmail.com wrote:
Igniters,
Today I fixed couple of tickets and attached patches to them, but TC
On Tue, Aug 11, 2015 at 03:18PM, Pavel Tupitsyn wrote:
+1 for email instead of chats.
Yeah, reviewboard sucks badly.
Does it? I heard that it may be painful to install, but from user point of
view it worked fine for me before. Certainly a lot better than no review
tool at all.
Just my
, but I'd say
it needs to bake-in for a bit longer.
Cos
/vishal
Sent from my iPhone
On Aug 10, 2015, at 9:18 PM, Konstantin Boudnik c...@apache.org wrote:
I encourage everyone here to reflect on this emails http://bit.ly/1IASLEK
from
Niclas Hedhman. He's one of the Apache folks who I am
Should be at least 2.6
I still have my doubts host stable 2.7 line is
Cos
On Mon, Aug 10, 2015 at 10:09AM, Sergey Kozlov wrote:
Hi all.
Currently Ignite Hadoop build based by default on Apache Hadoop 2.4.1
(released in June 2014).
But now 2.7.1 is propagated as stable.
Make sense to
On Mon, Aug 10, 2015 at 01:59PM, Nikita Ivanov wrote:
Slack [+1]
Both IRC and, esp. slack are tends to be a huge nuisance and
I don't have time for either. So I don't care one way or another.
--
Nikita Ivanov
On Mon, Aug 10, 2015 at 1:53 PM, Dmitriy Setrakyan dsetrak...@apache.org
On Mon, Aug 10, 2015 at 02:52PM, Dmitriy Setrakyan wrote:
On Mon, Aug 10, 2015 at 2:35 PM, Raul Kripalani ra...@apache.org wrote:
Hey Dmitriy,
On Mon, Aug 10, 2015 at 9:53 PM, Dmitriy Setrakyan dsetrak...@apache.org
wrote:
Let's decide on Slack vs. IRC. Any preferences?
Could
On Mon, Aug 10, 2015 at 10:20PM, Raul Kripalani wrote:
On Mon, Aug 10, 2015 at 9:37 PM, Konstantin Boudnik c...@apache.org wrote:
That's a good idea. However, decisions made on the chat _have_ to be
recorded in the email.
Actually, I'd like to drill into that.
It's not a matter
On Mon, Aug 10, 2015 at 11:29PM, Raul Kripalani wrote:
On Mon, Aug 10, 2015 at 10:41 PM, Konstantin Boudnik c...@apache.org wrote:
On Mon, Aug 10, 2015 at 10:20PM, Raul Kripalani wrote:
On Mon, Aug 10, 2015 at 9:37 PM, Konstantin Boudnik c...@apache.org
wrote:
That's a good idea
On Mon, Aug 10, 2015 at 11:41PM, Raul Kripalani wrote:
On Mon, Aug 10, 2015 at 10:52 PM, Dmitriy Setrakyan dsetrak...@apache.org
wrote:
Would be ideal
if Slack chats could be sent to the dev list on a daily basis as a safety
net.
I imagine that it will just raise a noise level on the
I encourage everyone here to reflect on this emails http://bit.ly/1IASLEK from
Niclas Hedhman. He's one of the Apache folks who I am listening very
closely whenever he says something.
That another reason why I avoid noisy chatter-channels like IRC, Skype, or
Slack (yes, I am making an effort to
Why not to file the tickets to the correct components and simply label them?
If you keep user ticket in the user request component you'll be confusing
the picture about which tickets are for what part of the system. If you decide
to move the ticket to a correct component you'll lose the info
On Wed, Aug 05, 2015 at 03:22PM, Artem Shutak wrote:
Inline.
On Wed, Aug 5, 2015 at 3:31 AM, Dmitriy Setrakyan dsetrak...@apache.org
wrote:
Huge +1 on pull requests. Would be great if we could make TC work with
that.
On Tue, Aug 4, 2015 at 5:30 PM, Alexey Kuznetsov
, Aug 4, 2015 at 11:41 AM, Sergi Vladykin sergi.vlady...@gmail.com
wrote:
Cos,
I'm a bit out of the loop here lately. I think Ivan Veselovsky will clarify
what happens.
Sergi
2015-08-03 23:58 GMT+03:00 Konstantin Boudnik c...@apache.org:
Guys,
I wonder if someone from
Two more just from the top of my head:
- distributed file system (IGFS) w/ optional caching for HDFS-like file
systems
- in-memory mapreduce and acceleration for Hive and similar applications
Cos
On Tue, Aug 04, 2015 at 01:05PM, Prachi Garg wrote:
Hi,
I've been working on putting some
Someone with admin rights on the space might be able to help you
(unfortunately, I don't have such permissions). If not - try filing the INFRA
ticket as you proposed.
Cos
On Thu, Jul 30, 2015 at 09:52PM, Sergi Vladykin wrote:
Brane,
It appeared that I can't login into the wiki and for some
Guys,
I wonder if someone from this list is still maintaining the Ignite component
in Bigtop. I am a bit busy with 1.0 release, but we have this long standing
issue
https://issues.apache.org/jira/browse/BIGTOP-1809
which needs to be addressed. Mostly, the questions are around the tests -
Guys,
I am curious what these Squashed commit... thing means? Are these about
Squashing commits on master or else... Also, why would you need a special
commit about other commits squashing...? Really confused...
Thanks for the clarification
Cos
On Fri, Jul 31, 2015 at 10:35AM,
, Konstantin Boudnik c...@apache.org wrote:
Guys,
I am curious what these Squashed commit... thing means? Are these about
Squashing commits on master or else... Also, why would you need a special
commit about other commits squashing...? Really confused...
Thanks for the clarification
Yup, just use --author
And perhaps --signedoff (is it right?) to indicate who did the review if so
desired
Cos
On July 29, 2015 4:49:00 AM PDT, Andrey Gura ag...@gridgain.com wrote:
Vladimir,
why do you think that second approach allows to avoid typos in
contributor
names?
Git commit has
On Wed, Jul 29, 2015 at 12:19PM, Dmitriy Setrakyan wrote:
On Wed, Jul 29, 2015 at 10:48 AM, Konstantin Boudnik c...@apache.org wrote:
Alternatively you can archive active sprint releases and all open JIRAs
will
get moved automatically.
Seriously? Are they automatically moved
If there's more than just one talk accepted for the EU event i'd recomment to
think about combining them to a separate track perhaps. We are musing over
such a possibility @bigtop as well.
Cos
On Thu, Jul 30, 2015 at 01:17AM, Atri Sharma wrote:
Hi Dmitriy,
I just wanted to let you know that
Alternatively you can archive active sprint releases and all open JIRAs will
get moved automatically.
On Wed, Jul 29, 2015 at 08:07PM, Yakov Zhdanov wrote:
Guys,
I have created new versions in JIRA - ignite-1.4 and ignite-1.5
Contributors, please move your tickets that are currently on
Could you perhaps look it up and link to the thread ? Thanks!
On July 28, 2015 11:52:13 PM PDT, Atri Sharma atri.j...@gmail.com wrote:
Folks,
We have discussed this earlier as well but the discussion died down
(the
primary node's queue flush issue.) I would like to restart the thread.
Please
On Tue, Jul 28, 2015 at 01:33PM, Pavel Tupitsyn wrote:
I hope so, it'd be horrible to do that on master!
Exactly!
But I do not see much sense in enforcing any kind of policy in personal
branches. Sometimes rebase may be better, sometimes I may want to use merge
so I see when and which
On Tue, Jul 28, 2015 at 06:23AM, Vasilisa Sidorova wrote:
In a perfect world I agree with Brane.
But there is top class from each igniter to trust each others on the 1000%
and always to be ready that something go sideways. This process take time.
Actually, no one is talking about 100%
with all the user-commits
in one uber-commit from that user?
Absolutely no. You never touch objects that are already in the remote.
Cos
I think this is the simplest workflow.
Thanks,
On Tue, Jul 28, 2015 at 8:33 PM, Konstantin Boudnik c...@apache.org
wrote:
On Tue, Jul 28, 2015
On Tue, Jul 28, 2015 at 10:29AM, Dmitriy Setrakyan wrote:
Alexey,
I probably was not clear in my email earlier. I think that
DeploymentProvider is a good abstraction and we should have it. My comment
was that I would like it to be exposed as a URI string vs. new
DeploymentProvider(...).
, as long as an email is sent to
the dev list notifying the rest of the community about the change.
D.
On Mon, Jul 27, 2015 at 4:30 PM, Konstantin Boudnik c...@apache.org wrote:
On Tue, Jul 28, 2015 at 01:09AM, Branko Čibej wrote:
On 27.07.2015 18:29, Sergi Vladykin wrote:
Guys
in Idea, too).
This way there is a single commit with a meaningful message in master, and
it does not matter what happened in the personal branch.
I think this is the simplest workflow.
Thanks,
On Tue, Jul 28, 2015 at 8:33 PM, Konstantin Boudnik c...@apache.org wrote:
On Tue, Jul 28
On Tue, Jul 28, 2015 at 11:31AM, Dmitriy Setrakyan wrote:
On Tue, Jul 28, 2015 at 11:20 AM, Konstantin Boudnik c...@apache.org wrote:
On Tue, Jul 28, 2015 at 10:29AM, Dmitriy Setrakyan wrote:
Alexey,
I probably was not clear in my email earlier. I think that
DeploymentProvider
On Tue, Jul 28, 2015 at 10:16PM, Branko Čibej wrote:
On 28.07.2015 21:36, Dmitriy Setrakyan wrote:
Cos, we are not talking about checking binaries. We are planning to
support
GIT/SVN/etc repositories with a POM file. This way we simply build it
using maven ourselves and deploy it.
predictable development. RTC approach here definitely fits better.
Sergi
2015-07-27 11:01 GMT+03:00 Konstantin Boudnik c...@apache.org:
On July 27, 2015 12:50:19 AM PDT, Branko Čibej br...@apache.org wrote:
On 27.07.2015 09:43, Atri Sharma wrote:
On Mon, Jul 27, 2015 at 1:10 PM
On Tue, Jul 28, 2015 at 01:09AM, Branko Čibej wrote:
On 27.07.2015 18:29, Sergi Vladykin wrote:
Guys,
I would say Ignite is quite a big and quite complex project.
This has absolutely nothing to do with trusting developers. FWIW,
Subversion is also very complex, I'll dare say that its
I second.
It's up to the community to go CTR or RTC but former has a way more flexibility
and way speedier. Esp. considering that Ignite has great and functional CI in
place. We are trying to get CTR running in Bigtop, but getting blocked by
comprehensive CI being not ready yet.
Please
need to file a ticket for INFRA to setup the blog on the
roller. Good idea!
Cos
D.
On Sun, Jul 26, 2015 at 11:25 PM, Konstantin Boudnik c...@apache.org wrote:
Don't do it on Ignite blog, first of all.
You can do it on your personal blog as much as you want to, but it should
be made
Don't do it on Ignite blog, first of all.
You can do it on your personal blog as much as you want to, but it should be
made clear that views expressed there DO NOT represent the Apache project or
community stance.
As Brane said (and been discussed before): the ASF is neutral to the vendors
and
On July 27, 2015 12:50:19 AM PDT, Branko Čibej br...@apache.org wrote:
On 27.07.2015 09:43, Atri Sharma wrote:
On Mon, Jul 27, 2015 at 1:10 PM, Branko Čibej br...@apache.org
wrote:
On 27.07.2015 09:36, Dmitriy Setrakyan wrote:
On Mon, Jul 27, 2015 at 12:30 AM, Branko Čibej br...@apache.org
Better be the latter. Otherwise we can add a release build similar to
https://builds.apache.org/view/All/job/Ignite-artifacts/
Cos
On Fri, Jul 24, 2015 at 05:32PM, Dmitriy Setrakyan wrote:
Igniters,
I have noticed that Docker and Cloud images have not been updated since
6/25. Do they
with 16 +1 votes.
The following community members voted:
1. Konstantin Boudnik (PMC, binding)
2. Branko Cibej (PMC, binding)
I did not vote. You should be more careful when summarizing a vote
thread. Please fix this ASAP.
Sorry Brane, saw your name in the reply and assumed
from
it) ;)
Cos
Thanks!
On Mon, Jul 13, 2015 at 5:06 PM, Konstantin Boudnik
c...@apache.org
wrote:
I think file system is more universally used. However, one can
build
an FS
on
top of a good object storage - just need to provide some metadata
abstraction/concept
13, 2015 at 5:06 PM, Konstantin Boudnik c...@apache.org wrote:
I think file system is more universally used. However, one can build an FS
on
top of a good object storage - just need to provide some metadata
abstraction/concept.
Replacing HDFS w/ Gluster doesn't make much sense to me
Ok, I have fixed the CI on builds.apache.org - now they take master as
default.
Cos
On Thu, Jul 09, 2015 at 01:00PM, Konstantin Boudnik wrote:
Yes, I am aware about this issue. However my account stopped working and I
need to take it to INFRA. Will take care about this in a day or two: thanks
Čibej br...@apache.org:
On 12.07.2015 08:18, Branko Čibej wrote:
On 11.07.2015 02:00, Konstantin Boudnik wrote:
On Sat, Jul 11, 2015 at 01:56AM, Yakov Zhdanov wrote:
Dear Sirs!
If you're trying to please IPMC gramma-busybodies with this -
don't
bother:
they will find a reason why
sure our RH brethren have something to say about Ceph.
Re-post on dev@bigtop?
Thanks,
Roman.
On Wed, Jul 8, 2015 at 3:17 PM, Konstantin Boudnik c...@apache.org
wrote:
Guys,
I was looking at the Hadoop accelerator the other day and been
thinking
On Thu, Jul 09, 2015 at 10:49PM, Atri Sharma wrote:
Folks,
I am beta testing a PRAM model based parallel sorting algorithm and will
integrate it with Ignite soon.
My idea is to be able to use Ignite as an in memory sorting engine.
For my own education: what'd be the use case for such
On Thu, Jul 09, 2015 at 10:02PM, Branko Čibej wrote:
On 09.07.2015 21:57, Konstantin Boudnik wrote:
On Thu, Jul 09, 2015 at 12:48PM, Dmitriy Setrakyan wrote:
On Thu, Jul 9, 2015 at 12:45 PM, Branko Čibej br...@apache.org wrote:
On 09.07.2015 10:39, Dmitriy Setrakyan wrote:
* Added 9
Guys,
I was looking at the Hadoop accelerator the other day and been thinking if
anyone has tried to use IGFS on top of a real distributed file storage. The
case in point is Ceph (ceph.com) - a Linux file system available from any
major Linux distribution as a kernel module.
HDFS has its share
It is just that everyone has its own copy, ya know ;)
On July 7, 2015 9:51:43 PM PDT, Branko Čibej br...@apache.org wrote:
On 08.07.2015 01:05, Dmitriy Setrakyan wrote:
Hi,
We have had quite a few committers join the Ignite community in the
past
month:
Ognen Duzlevski
Gianfranco Murador
Guys,
I was trying to figure out where IGNITE-218 has been fixed and it wasn't easy.
The JIRA has these cryptic 'sprint' releases which are disconnected from
actual release numbers '1.0', '1.1' and so on. I think this needs to be fixed
before the graduation. The good news - it seems to be easy to
-post on dev@bigtop?
Thanks,
Roman.
On Wed, Jul 8, 2015 at 3:17 PM, Konstantin Boudnik c...@apache.org wrote:
Guys,
I was looking at the Hadoop accelerator the other day and been thinking if
anyone has tried to use IGFS on top of a real distributed file storage. The
case in point
+1
My load has dropped _very_ significantly in the last a couple of months (given
that I was on vacation and other mentors were picking up my share of the load
;) But I really think there's not much I can be helping this podling with: you
guys are standing on your own feet now.
I don't see any
Looks good - thanks for putting this together!
Cos
On Mon, Jul 06, 2015 at 06:11PM, Yakov Zhdanov wrote:
Igniters,
As it has been discussed, we are applying an updated Git policy which
should be more flexible and transparent that we have now.
Process is described here:
same (javax.servlet.*) classes under
Apache licence (for example -
https://github.com/apache/tomcat/blob/trunk/java/javax/servlet/AsyncContext.java
).
Is there any chances to use these classes at Ignite?
On Tue, Jun 30, 2015 at 8:24 PM, Konstantin Boudnik c...@apache.org
On Wed, Jul 01, 2015 at 11:42AM, Dmitriy Setrakyan wrote:
On Wed, Jul 1, 2015 at 11:40 AM, Konstantin Boudnik c...@apache.org wrote:
On Wed, Jul 01, 2015 at 10:44AM, Dmitriy Setrakyan wrote:
GridGain community edition is not governed by Apache should have LGPL
turned on.
The LGPL
if these are decent, well-used framework and the effort is so small then we
should, IMO.
On July 1, 2015 5:55:35 AM PDT, Alexey Kuznetsov akuznet...@gridgain.com
wrote:
Igniters,
I googled a little and found that several web frameworks have
integration
with Hazelcast as a cache.
For example:
Anything wrong with that? ;)
On Tue, Jun 30, 2015 at 12:07PM, Ognen Duzlevski wrote:
Yall? Texas slang on the dev list? Seriously? :)
On Tue, Jun 30, 2015 at 12:24 AM, Konstantin Boudnik c...@apache.org wrote:
Guys,
this is great! I am very happy to have yall aboard! Welcome!
Cos
- Semyon
- Konstantin Boudnik (binding)
I will start vote on general list shortly.
By the way, and before we get hammered about this on general@: Where are
the 'convenience binaries' for Ignite releases being built? Even if
they're not official, they should be built on controlled
Shall the DockerFile be checked into the source code tree then?
Cos
On Sun, Jun 28, 2015 at 10:58PM, Dmitriy Setrakyan wrote:
Igniters,
Nick Tikhonov has created a docker container which automatically takes user
code, builds it with maven, and deploys it into an Ignite instance before
Ah, that's great! ;)
On Tue, Jun 30, 2015 at 12:35PM, Ognen Duzlevski wrote:
No just wanted you to know there are people on the list who understand what
you said! ;)
On Tue, Jun 30, 2015 at 12:40 PM, Konstantin Boudnik c...@apache.org wrote:
Anything wrong with that? ;)
On Tue, Jun
Guys,
this is great! I am very happy to have yall aboard! Welcome!
Cos
On June 29, 2015 2:04:50 AM PDT, Dmitriy Setrakyan dsetrak...@apache.org
wrote:
Igniters,
Please welcome the new committers and PPMC members to the Ignite
project:
Ognen Duzlevski
Gianfranco Murador
Nikolai Tikhonov
Ira
Apache mail server doesn't let attachments through. The best way is to attach
to a JIRA or do something of the sort.
Cos
On Fri, Jun 26, 2015 at 08:59PM, moon soo Lee wrote:
I attached a screenshot, but i'm not sure if you're seeing it.
There're small buttons on the right side of notebook
+1 [binding]
(on the source release only)
But please, please, please for the fifth time: make the checksum files to be
compatible with the sha1 and md5 utilities. Checking the checksums is a PITA ;(
The project mentors have explained what it means a few times already.
Cos
On Wed, Jun 17, 2015
On June 11, 2015 10:37:22 AM GMT+03:00, Valentin Kulichenko
valentin.kuliche...@gmail.com wrote:
Actually this silence is my main concern here :)
We're going the change the process. And everyone in the community has
to
move to the new process at the same time. I have nothing against
consensus
, for example) instead of
big bunch of links that lead nowhere.
On Mon, Jun 8, 2015 at 3:59 PM, Konstantin Boudnik c...@apache.org wrote:
Why do you consider them useless?
Cos
On Mon, Jun 08, 2015 at 03:44PM, Alexey Kuznetsov wrote:
Why do we need to add useless comments from
Why do you consider them useless?
Cos
On Mon, Jun 08, 2015 at 03:44PM, Alexey Kuznetsov wrote:
Why do we need to add useless comments from tc_commenter to JIRA issues?
They look like:
tc_commenter added a comment - 2 days ago
There was triggered next test builds for last attached
--
Regards,
Cos
On June 8, 2015 1:20:56 PM GMT+03:00, Branko Čibej br...@apache.org wrote:
On 07.06.2015 18:00, Konstantin Boudnik wrote:
I'm with Brane on this one (unlike git cherry picking ;). Vote is a
tool to
record a consensus reached via a discussion/collaboration.
No, it's
I'm with Brane on this one (unlike git cherry picking ;). Vote is a tool to
record a consensus reached via a discussion/collaboration. Apache isn't a
democracy where majority rules; hence voting isn't a decision-making tool.
Cos
On Sun, Jun 07, 2015 at 04:10PM, Branko Čibej wrote:
On 07.06.2015
Actually, this approach works very well for the situation below. The way to
deal with it is explained here
http://nvie.com/posts/a-successful-git-branching-model/
And has been discussed on this list a couple of times already. 'sprint-N'
branch is not different from a 'development' branch,
On Wed, Jun 03, 2015 at 11:46AM, Branko Čibej wrote:
On 03.06.2015 10:06, Gianfranco Murador wrote:
Hi Artem,
I'm going to run the following commands to create the patch. are these
steps correct ?
## Get the repo
git clone -b ignite-sprint-5
On Tue, Jun 02, 2015 at 05:41PM, Dmitriy Setrakyan wrote:
On Tue, Jun 2, 2015 at 4:09 AM, Konstantin Boudnik c...@apache.org wrote:
On Tue, Jun 02, 2015 at 11:59AM, Branko Čibej wrote:
On 01.06.2015 20:55, Dmitriy Setrakyan wrote:
Hi,
We need to setup readme.io to automatically
On Tue, Jun 02, 2015 at 11:52AM, Branko Čibej wrote:
On 01.06.2015 18:06, Dmitriy Setrakyan wrote:
On Mon, Jun 1, 2015 at 9:01 AM, Nikita Ivanov nivano...@gmail.com wrote:
Generally, I'd vote for 2.11 not because of any language features but
because of stability (and tooling around). 2.11
On Tue, Jun 02, 2015 at 11:59AM, Branko Čibej wrote:
On 01.06.2015 20:55, Dmitriy Setrakyan wrote:
Hi,
We need to setup readme.io to automatically commit to our GIT repo when
documentation is changed. Do we have a GIT user we could reuse for this
purpose or should we setup a new user
In Bigtop we follow this process
https://cwiki.apache.org/confluence/display/BIGTOP/How+to+Contribute
which is quite handy as it turned out.
Cos
On Tue, Jun 02, 2015 at 08:38PM, Atri Sharma wrote:
Folks,
Is git diff patch.patch good enough to be put on JIRA? I tried running
format
All keys I have received and verified are now signed and uploaded back to the
key server. Please feel free to do the same with mine.
Cheers,
Cos
On Wed, May 27, 2015 at 06:16PM, Konstantin Boudnik wrote:
Thanks for exchanging the keys with me, guys! I will do the signing later
today and send
The way of contribution is pretty simple - just make a patch and attach it
here. Once the patch is attached please change JIRA ticket status to Patch
Available which should trigger automatic patch validation process (almost
ready, per my conversation with Artem earlier today).
And yes -
that stuff as well.
Looking forward to meet you all!
cos
On Thu, May 14, 2015 at 02:17PM, Konstantin Boudnik wrote:
Flying in on 25th in the afternoon. Leaving (tentatively) on 30th.
It's a business trip, so time might be right during the daytime, but I am
pretty sure we should be able to find
+1 (binding)
- all checksums and signatures are fine
- RAT is clean
+1 (yet again) on what Brane said about the formats of md5 and sha1 - please
make them to be in the standard format. I am not sure why it hasn't been done
yet. Checking them is the time waste ;( Please be considerate of the
Brane's vote is binding as well.
On Mon, May 25, 2015 at 01:06PM, Yakov Zhdanov wrote:
Apache Ignite 1.1.0 release (RC7) has been accepted with 7 votes for (1
binding vote):
1. Konstantin (binding)
2. Brane
3. Yakov
4. Sergi
5. Alex Kuznetsov
6. Vladimir
7. Valentin
I will start
Guys
I've noticed that
https://archive.apache.org/dist/incubator/ignite/
Has rc3 bits loosely laying around. There's a folder 1.0.0-RC3/ that seems to
contain the bits from a later date. What's the deal with it? It looks
confusing. Shall be the one from the root folder be removed?
Cos
to it?
On Mon, May 25, 2015 at 12:58 PM, Konstantin Boudnik c...@apache.org wrote:
Guys
I've noticed that
https://archive.apache.org/dist/incubator/ignite/
Has rc3 bits loosely laying around. There's a folder 1.0.0-RC3/ that seems
to
contain the bits from a later date. What's
Can anyone comment on this? Seems like an interesting topic, for sure.
Thanks,
Cos
On Sun, May 17, 2015 at 12:49AM, Koert Kuipers wrote:
One of the unique capabilities of Ignite is a file system interface to its
in-memory data called Ignite File System (IGFS). IGFS delivers similar
On Thu, May 21, 2015 at 10:32AM, Dmitriy Setrakyan wrote:
On Thu, May 21, 2015 at 10:27 AM, Konstantin Boudnik c...@apache.org wrote:
Can anyone with project admin rights check the permissions chema and see
if there's a tweak for 'Patch available' for different roles in the
project? i
, Director RD
*GridGain Systems*
www.gridgain.com
2015-05-19 20:53 GMT+03:00 Konstantin Boudnik c...@apache.org:
Here's two reasons why current approach is secure enough (and in fact has
been used for some time on Apache build infrastructure):
- only project contributors can
1 - 100 of 342 matches
Mail list logo
