On 13.08.2015 09:09, Yakov Zhdanov wrote:
Why reply-to is dev@ignite.incubator.apache.org? Cos? Brane? Any ideas?
--Yakov
Just how the list is set up. Some people like that, some hate it.
-- Brane
Sergi, why don't you just fix the Wiki?
-- Brane
On 30.07.2015 11:18, Sergi Vladykin wrote:
I meant this wiki page:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
Sergi
2015-07-30 12:17 GMT+03:00 Sergi Vladykin sergi.vlady...@gmail.com:
Also a wiki page should
On 28.07.2015 09:56, Dmitriy Setrakyan wrote:
I want to address the following point made by Brane and Cos:
*if you don't trust a committer to make the changes in the VCSsystem - that
committer shouldn't be having the commit-bit in the first place.*
I don't believe this point
On 28.07.2015 12:15, Pavel Tupitsyn wrote:
Hi, I'm a bit confused, are we talking about merge vs rebase in a feature
(personal) branches?
I hope so, it'd be horrible to do that on master!
-- Brane
On 28.07.2015 12:12, Yakov Zhdanov wrote:
I am for RTC.
Agree with Val, that significant part of the concurrency issues are very
hard to catch with CI. They are caught on review (and some unfortunately
slip through). And Sergi's points seems very valid to me - complex changes
should be
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.
Well, even worst IMO. Why would you want to run an external
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 object model and
working copy semantics are more convoluted
On 27.07.2015 07:38, Atri Sharma wrote:
Folks,
I am doing a shootout of Ignite vs SAP HANA for the Ignite blog.
Does anyone have any interesting points to make? Some specific features,
points, case studies?
DO NOT write articles that compare Ignite with some commercial tool in
the name of
at 11:52 AM, Atri Sharma atri.j...@gmail.com wrote:
By Ignite blog, I meant my personal blog which only reflects my personal
opinion and is not endorsed by ASF or Apache Ignite project in *any* manner.
On Mon, Jul 27, 2015 at 11:50 AM, Branko Čibej br...@apache.org wrote:
On 27.07.2015 07:38
On 27.07.2015 08:45, Dmitriy Setrakyan wrote:
On Sun, Jul 26, 2015 at 11:31 PM, Konstantin Boudnik c...@apache.org wrote:
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
On 27.07.2015 07:47, Dmitriy Setrakyan wrote:
On Sun, Jul 26, 2015 at 10:39 PM, Branko Čibej br...@apache.org wrote:
On 27.07.2015 07:04, Dmitriy Setrakyan wrote:
Igniters,
I believe several very valid points have been made on the general@ list
about our Jira handling, and how we should
consider the consequences of the decision you're about to make.
I was hoping to arrive to a decision as a result of this discussion.
Cos
On July 26, 2015 11:13:40 PM PDT, Branko Čibej br...@apache.org
wrote:
On 27.07.2015 07:47, Dmitriy Setrakyan wrote:
On Sun, Jul 26, 2015 at 10:39 PM, Branko
On 27.07.2015 09:33, Dmitriy Setrakyan wrote:
On Mon, Jul 27, 2015 at 12:26 AM, Branko Čibej br...@apache.org wrote:
Can you describe at which point a master becomes a release branch in
Subversion?
http://subversion.apache.org/docs/community-guide/releasing.html
Also, what happens
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 wrote:
We've all seen problems with bad commits. Bugs happen. If it's
On 27.07.2015 09:12, Dmitriy Setrakyan wrote:
On Sun, Jul 26, 2015 at 11:57 PM, Branko Čibej br...@apache.org wrote:
On 27.07.2015 08:49, Atri Sharma wrote:
I totally agree on this one.
In PostgreSQL, every committer's major changes are normally reviewed by
somebody else before
On 27.07.2015 09:17, Atri Sharma wrote:
On Mon, Jul 27, 2015 at 12:42 PM, Dmitriy Setrakyan dsetrak...@apache.org
wrote:
On Sun, Jul 26, 2015 at 11:57 PM, Branko Čibej br...@apache.org wrote:
On 27.07.2015 08:49, Atri Sharma wrote:
I totally agree on this one.
In PostgreSQL, every
On 27.07.2015 07:04, Dmitriy Setrakyan wrote:
Igniters,
I believe several very valid points have been made on the general@ list
about our Jira handling, and how we should improve our Jira process.
I have tried to outline the Jira Process we should follow on our Wiki:
On 14.07.2015 04:25, Dmitriy Setrakyan wrote:
The vote passed 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.
On 13.07.2015 16:42, Atri Sharma wrote:
Out of curiosity, are we only using MD5 and SHA1 for checksums?
If that is the case, can we try CRC? Much easier to port and easier to
compute
That is complete nonsense.
The point of hashes is to maintain a minimal level of confidence that
the sources
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 that isn't an appropriate way
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 that isn't an appropriate way to address them ;)
I'm more interested in why
On 09.07.2015 10:20, Dmitriy Setrakyan wrote:
The official process of becoming a committer has been documented here:
https://ignite.incubator.apache.org/community/contribute.html#become-committer
Please let me know if you have any comments or suggestions.
Nice.
are suggested /but/ the
On 09.07.2015 10:39, Dmitriy Setrakyan wrote:
* Added 9 committers (including 6 PPMC members).
Aren't all committers also PPMC members? I thought that's what we
decided ...
-- Brane
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
Nickolai Tikhonov
Irina Vasilinets
Anton Vinogradov
Evans Ye
Again, welcome to the Ignite community, even though some of
On 01.07.2015 21:07, Dmitriy Setrakyan wrote:
On Wed, Jul 1, 2015 at 11:56 AM, Konstantin Boudnik c...@apache.org wrote:
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,
With all these transliterated names flying around here, a bit of Texas
slang surely can't hurt. :)
On 30.06.2015 20:33, Konstantin Boudnik wrote:
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
That issue has abslutely nothing to do with my question.
On 30.06.2015 11:38, Anton Vinogradov wrote:
Brane,
I'm working on this issue (IGNITE-1060)
On Mon, Jun 29, 2015 at 8:18 PM, Branko Čibej br...@apache.org wrote:
On 26.06.2015 14:52, Yakov Zhdanov wrote:
Brane, mvn clean package
On 29.06.2015 18:47, Dmitriy Setrakyan wrote:
I saw the vote closed on incubator list, but the download links are not
updated yet.
Yakov, since you are the one handling the vote, can you please push the
release on the website as well?
Please remember that it can take up to 24 hours for the
,
not on some random (possibly infected) developer's laptop.
-- Brane
2015-06-26 9:33 GMT+03:00 Branko Čibej br...@apache.org:
On 22.06.2015 12:20, Yakov Zhdanov wrote:
Guys,
ignite-1.2.0-incubating-rc2 has been accepted with 7 votes (2 binding).
Thanks to those who voted:
- Gianfranco
On 17.06.2015 00:02, Yakov Zhdanov wrote:
Guys,
We have uploaded release candidate to
https://dist.apache.org/repos/dist/dev/incubator/ignite/1.2.0-rc2/
Tag name is
ignite-1.2.0-incubating-rc2
1.2.0 changes:
Added client mode to TCP discovery SPI.
Added memory based evictions.
Added
On Jun 11, 2015 12:03 AM, Branko Čibej br...@apache.org wrote:
On 11.06.2015 01:47, Valentin Kulichenko wrote:
Hmm. I'm not sure I understand. As far as I understand, any vote here
is unanimous, but not majority. I.e., if anyone in community has
objections, vote is declined (already
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 not, that's exactly my point: Consensus is recorded by no
objections being raised on the appropriate
On 07.06.2015 15:50, Dmitriy Setrakyan wrote:
Let's have a vote on the GIT structure proposed by the community (mainly
Brane and Cos).
Stop right there. Voting makes no sense at all. Discuss and reach
consensus instead.
Voting should never be used as a decision-making tool; it's an
indication
result, in this way you'll get a document that keeps
evolving as your needs change. If you voted instead, you'd also have to
vote for any change to the doc ... which is weird, right? :)
-- Brane
On Sun, Jun 7, 2015 at 5:10 PM, Branko Čibej br...@apache.org wrote:
On 07.06.2015 15:50, Dmitriy
On 07.06.2015 08:35, Branko Čibej wrote:
* When you're ready to begin stabilization for a release, create a
release branch (rel-1.2.x for example) from the master branch. Only
bug fixes happen on the release branch. When you're happy with the
stability of the release, just tag
On 06.06.2015 22:17, Vladimir Ozerov wrote:
I think I understand why we do not use schemes proposed above. They are
definitely better than current. But we cannot use them because of two
things:
1) We do not have real stabilization phase. Normally it must include
mainly bugfixes, but we
Hello? Will someone please write the report? This is not a mentors' job.
-- Brane
On 02.06.2015 09:45, Branko Čibej wrote:
Please don't forget that the report is due tomorrow!
On 29.05.2015 00:07, Marvin Humphrey wrote:
Greetings, {podling} developers,
The marvin automated report reminder
On 04.06.2015 18:49, Branko Čibej wrote:
On 04.06.2015 18:42, Atri Sharma wrote:
I like proxy objects although I am wondering if that makes copy by value
any more expensive (I am not sure about deep copying of non native objects)
Note that the only data a proxy object contains is the Java
operators would always create new global references and
the destructor would release the global reference and you'd have almost
Java-like garbage collection semantics.
-- Brane
On Thu, Jun 4, 2015 at 8:23 PM, Branko Čibej br...@apache.org wrote:
On 04.06.2015 15:45, Vladimir Ozerov wrote
have no ides what's
faster, but I suspect that the letting JNI take care of reference
handling is the better option.
-- Brane
On 4 Jun 2015 22:01, Branko Čibej br...@apache.org wrote:
On 04.06.2015 17:10, Atri Sharma wrote:
Something like a smart pointer might be useful here.
I thing that I
On 04.06.2015 15:45, Vladimir Ozerov wrote:
Igniters,
Lots of our features rely on callbacks from Ignite to user code. This is
essential for task execution, cache invokes, cache store, continuous
queries, messaging, etc..
Ideally from user perspective target class should look somewhat like
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 https://github.com/apache/incubator-ignite.git
git checkout -b ignite-788
## Commit the changes
Please don't forget that the report is due tomorrow!
On 29.05.2015 00:07, Marvin Humphrey wrote:
Greetings, {podling} developers,
The marvin automated report reminder script didn't fire for whatever
reason this week, so I'm sending out a bulk reminder manually for the 27
podlings who are
On 01.06.2015 09:58, Vladimir Ozerov wrote:
Igniters,
There is widespread opinion that STL types should not be used in public
(exported) APIs to maximize portability. It means that even such simple
types like std::string or std:vector shouldn't appear in any public
definitions.
Pros:
On 02.06.2015 07:48, Branko Čibej wrote:
If you don't want to use exceptions, you'll still have to write
exception-safe code: depending on the environment, exceptions can be
thrown from standard library methods.
In general, though, I agree that using exceptions for error handling is,
whilst
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 is very stable (comparing
to 2.10).
If we go with
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 through INFRA?
Definitely a new user with very specific
On 02.06.2015 13:07, Atri Sharma wrote:
I am not sure what might be connection issues since I am using my regular
home network for this.
Let me run the build a couple of times and report.
From your reports I gather that this connection problem does not always
happen at the same place. That's
On 28.05.2015 13:43, Yakov Zhdanov wrote:
Hello!
The vote has been finished with 4 +1 votes and 0 0 and 0 -1.
Thanks to all who voted:
1. Cos
2. Brane
3. Jan
4. Roman
Here is the link to the thread:
the long view here.
-- Brane
On Wed, May 27, 2015 at 9:28 AM, Denis Magda dma...@gridgain.com wrote:
On 5/27/2015 12:14 AM, Branko Čibej wrote:
2. Use a C++ parser (e.g., from LLVM) to generate a machine-readable
structure description, and generate the marshalling code from that.
Option 2
Why don't you just use an existing IDL? Something like Thrift or
Protobufs or ... there are quite a few of them out there. Inventing your
own marshalling is a waste of time.
-- Brane
On 26.05.2015 22:12, Vladimir Ozerov wrote:
SFINAE could be a way to perform compile-time introspection:
On 26.05.2015 23:04, Vladimir Ozerov wrote:
Brane,
There are two key features we are planning to address with platforms
integration efforts apart of trivial cache/compue APIs;
1) Portability, so that objects can freely travel between Java, C++, etc..
Also portability is mandatory to support
On 25.05.2015 12:39, Konstantin Boudnik wrote:
Ah, you're right... that's archive, not the dist itself. Hmm... not sure if
write access to it is possible, actually. Looks like it is pulling the content
from elsewhere and keep it in.
Brane, could you chime in, if you posses any secret
On 25.05.2015 17:52, Dmitriy Setrakyan wrote:
Cos,
Which mailing list did this discussion take place in?
This one.
http://mail-archives.apache.org/mod_mbox/incubator-ignite-dev/201505.mbox/%3CCANx3uAg2J9qvj2mP2MsnsXd1A4F6c1zgpOm4iuQ8WzEzi-Uywg%40mail.gmail.com%3E
-- Brane
On 25.05.2015 20:04, Vladimir Ozerov wrote:
I already raised question about backups several months ago but no
implementation decisions were made.
I am not aware of any architectural problems preventing us form having
backups, but currently backups is prohibited eplicitly, and user will get
On 20.05.2015 22:37, Yakov Zhdanov wrote:
Guys,
We have uploaded release candidate to
https://dist.apache.org/repos/dist/dev/incubator/ignite/1.1.0-rc7/
Tag name is
ignite-1.1.0-incubating-rc7
RC7 changes:
Fixed unexpected LICENSE, NOTICE and DEPENDENCIES files in sources zip.
Fixed
On 21.05.2015 11:35, Dmitriy Setrakyan wrote:
Are we saying that non-contributors can attach patches?
Slow down. Anyone who sends a patch is, by definition, a contributor.
Whether or not you decide to use the patch is a different matter. You
don't want to invent any extremely paranoid access
On 21.05.2015 12:00, Dmitriy Setrakyan wrote:
On Thu, May 21, 2015 at 2:48 AM, Branko Čibej br...@apache.org wrote:
On 21.05.2015 11:35, Dmitriy Setrakyan wrote:
Are we saying that non-contributors can attach patches?
Slow down. Anyone who sends a patch is, by definition, a contributor
On 21.05.2015 21:07, Artiom Shutak wrote:
Hi, Igniters,
Respond to this email with your jira username.
I will add your username to approved patchers list and it will enable
auto patch validation mechanism for you.
Sounds good, but ... if someone not on the list attaches a patch to a
new
On 20.05.2015 09:40, Vladimir Ozerov wrote:
This is not about resulting size of our lib. Moreover, we will not
statically link it to Ignite because in this case users will have troubles
when using both Boost and Ignite simultaneously.
The problem is that if we use Boost, we will force users to
On 20.05.2015 09:47, Vladimir Ozerov wrote:
I do not think we will sacrifice anything. C++11 has lots new features such
as smart pointers and lamdas, but I do not see where we can use them on our
public API.
I would definitely recommend using C++03 (or C++98; the only differences
are in the
.
However, given that client will be completely reapproached and should be
less complex I would think whether we need any third party library at all.
--Yakov
2015-05-20 12:27 GMT+03:00 Branko Čibej br...@apache.org:
On 20.05.2015 09:40, Vladimir Ozerov wrote:
This is not about resulting size
On 20.05.2015 21:36, Dmitriy Setrakyan wrote:
On Wed, May 20, 2015 at 6:26 AM, Yakov Zhdanov yzhda...@gridgain.com
wrote:
I still insist that this should be implemented with great care.
I tend to agree with Cos here. Let's implement this feature. If we get some
malicious contributor
Please use the subject tag [RESULT][VOTE] for votes that are complete,
regardless of the vote result; and [CANCELLED][VOTE] for votes that are
cancelled for any reason. Nobody uses [CLOSED][VOTE] anywhere.
-- Brane
On 12.05.2015 19:55, Yakov Zhdanov wrote:
Guys,
We have uploaded release candidate to
https://dist.apache.org/repos/dist/dev/incubator/ignite/1.1.0-rc5/
By the way, it's a good idea to remove obsolete release candidates from
dist/dev. Right now we have dev-dist/1.1.0-rc3 and
On 09.05.2015 03:22, Konstantin Boudnik wrote:
Nope, all the same. However if I copy the file from the git source tree -
everything starts working. In order to double-check me, please run
unzip -l ignite-1.1.0-incubating-src.zip | grep bin/include
This would not have happened if package
On 05.05.2015 18:26, Artiom Shutak wrote:
Hi, Sergey,
I've found 'which' command cannot be found on public TC agents:
http://204.14.53.152/repository/download/Ignite_IgniteStartNodes/47865:id/ignite-startNodes.zip%21/05-05-2015--08-03-11-237aeb53.log
.
What linux installed on agents? Can we
On 03.05.2015 21:32, Konstantin Boudnik wrote:
On Sun, May 03, 2015 at 04:45AM, Branko Čibej wrote:
On 29.04.2015 12:07, Vladimir Ozerov wrote:
My opinion is that a product created for particular platform (say, Python),
should not smell Java. Spring XML is a nice standard in Java community
On 01.05.2015 13:57, Ognen Duzlevski wrote:
On Fri, May 1, 2015 at 12:59 AM, Andrey Kornev andrewkor...@hotmail.com
wrote:
Dmitriy,
It seems the JCache spec doesn't explicitly require the cache data to be
destroyed by a Cache.close() call. See page 38.
The way I interpret (perhaps
include the tag name, so that people can easily compare the
sources with the repository.
-- Brane
On Thu, Apr 30, 2015 at 1:03 AM, Branko Čibej br...@apache.org wrote:
On 29.04.2015 18:10, Dmitriy Setrakyan wrote:
I think one of the biggest improvements in this release is fully
automated
On 29.04.2015 12:07, Vladimir Ozerov wrote:
My opinion is that a product created for particular platform (say, Python),
should not smell Java. Spring XML is a nice standard in Java community. But
I do not think that regular Node.JS/Python/Ruby/.Net/CPP developer knows
what Spring is.
Oh, we
On 30.04.2015 00:48, Konstantin Boudnik wrote:
These simple rules allow to produce a much cleaner git history, which is
easier to work with, bisect if needed, and in general do any sorts of tracing.
I have to point out that the goal of version control is not to have a
clean git history but to
On 29.04.2015 18:42, Dmitriy Setrakyan wrote:
On Wed, Apr 29, 2015 at 11:38 AM, Markus Wiesenbacher
mailingl...@codefreun.de wrote:
You write on your site that GridGain Community Edition powered by Apache
Ignite will have additional bug fixes ... will this version be free? Why
another
On 29.04.2015 23:13, Dmitriy Setrakyan wrote:
On Wed, Apr 29, 2015 at 3:57 PM, Branko Čibej br...@apache.org wrote:
On 29.04.2015 18:42, Dmitriy Setrakyan wrote:
On Wed, Apr 29, 2015 at 11:38 AM, Markus Wiesenbacher
mailingl...@codefreun.de wrote:
You write on your site that GridGain
On 29.04.2015 18:10, Dmitriy Setrakyan wrote:
I think one of the biggest improvements in this release is fully automated
build process. As Yakov suggested, the instructions to run the build are in
the DEVNOTES.txt in sprint-4 branch:
http://s.apache.org/caf
Brane, Cos, please take a look
On 29.04.2015 23:56, Konstantin Boudnik wrote:
On Wed, Apr 29, 2015 at 04:42PM, Dmitriy Setrakyan wrote:
On Wed, Apr 29, 2015 at 4:23 PM, Branko Čibej br...@apache.org wrote:
On 29.04.2015 23:13, Dmitriy Setrakyan wrote:
On Wed, Apr 29, 2015 at 3:57 PM, Branko Čibej br...@apache.org wrote
On 19.04.2015 00:57, Dmitriy Setrakyan wrote:
On Sat, Apr 18, 2015 at 1:27 PM, Ognen Duzlevski ognen.duzlev...@gmail.com
wrote:
Hello,
I have noticed that with 1.0.0-incubating there is somewhat of a delay with
joining an ignite cluster. I have 6 EC2 instances - I start ignite.sh
On 19.04.2015 17:11, Konstantin Boudnik wrote:
On Sun, Apr 19, 2015 at 09:01AM, Branko Čibej wrote:
On 19.04.2015 00:57, Dmitriy Setrakyan wrote:
On Sat, Apr 18, 2015 at 1:27 PM, Ognen Duzlevski ognen.duzlev...@gmail.com
wrote:
Hello,
I have noticed that with 1.0.0-incubating
On 16.04.2015 19:00, Konstantin Boudnik wrote:
Alexey,
all email exchanges on this list are archived and, in fact, for that very
reason, so people can find the answers lately. I don't think we should be
redirecting ppl to an external forum.
Indeed, I've made that point before.
If you need a
On 13.04.2015 00:34, Dmitriy Setrakyan wrote:
Igniters,
I would like to start preparing spirnt-3 branch for 1.1 release. I may be
sending follow up emails to some of you to find out status of some
currently failing tests on TeamCity.
Please avoid commits to that branch unless absolutely
On 09.04.2015 17:20, Suminda Dharmasena wrote:
Hi,
Is it possible to consider having a Nabble archived for the mailing lists
as it has a better interface.
Markmail.org archives all ASF mailing lists, including dev@ignite.
Also perhaps keep the Issues and Commits posted to the relevant
On 09.04.2015 09:59, Dmitriy Setrakyan wrote:
Guys,
I would like to create another Ignite release this Friday.
I suggest you wait until Monday? Many people will be travelling to
Austin for ApacheCon this week-end and are not likely to have time to
review the release.
-- Brane
On 31.03.2015 02:08, Dmitriy Setrakyan wrote:
Thanks Brane! I will be submitting this release to IPMC for the final vote
today. Also some comments are below.
On Mon, Mar 30, 2015 at 4:54 PM, Branko Čibej br...@apache.org wrote:
On 31.03.2015 00:54, Konstantin Boudnik wrote:
On Mon, Mar 30
On 31.03.2015 01:54, Branko Čibej wrote:
+1 for release but the following problems should be fixed for the next
release:
4. Some of the shell scripts in target/release-package/bin do not have
the execute bit set on unix.
-- Brane
On 31.03.2015 03:15, Branko Čibej wrote:
On 31.03.2015 03:00, Valentin Kulichenko wrote:
On Mon, Mar 30, 2015 at 5:51 PM, Branko Čibej br...@apache.org wrote:
On 31.03.2015 00:27, Valentin Kulichenko wrote:
Igniters,
Note that due to licensing issues all modules that depend on LGPL
the
build? That would certainly help in tracking down issues raised by users.
-- Brane
On Thu, Mar 26, 2015 at 2:42 PM, Branko Čibej br...@apache.org wrote:
If the user cannot build a complete release from source, then the source
release is not functional. It's as simple as that. The ASF releases
On 28.03.2015 01:14, Dmitriy Setrakyan wrote:
Cos,
My comments are below.
However, can we proceed with the vote for this release and resolve it in
the next release? The RC3, which is officially downloadable release from
Ignite website also has this issue, among with some others, which we
On 26.03.2015 08:47, dsetrak...@apache.org wrote:
Author: dsetrakyan
Date: Thu Mar 26 07:47:28 2015
New Revision: 1669287
URL: http://svn.apache.org/r1669287
Well, in my opinion, the source download should be first on the page,
not the binaries. Binaries are not official releases; the
://kafka.apache.org/downloads.html
I would prefer that we take the same approach.
D.
On Thu, Mar 26, 2015 at 7:19 AM, Dmitriy Setrakyan dsetrak...@gridgain.com
wrote:
On Thu, Mar 26, 2015 at 4:28 AM, Branko Čibej br...@apache.org wrote:
On 26.03.2015 08:47, dsetrak...@apache.org wrote:
Author: dsetrakyan
package with DEV version of
ignite.properties, because it is based on specific revision.
I agree.
On Thu, Mar 26, 2015 at 7:19 AM, Dmitriy Setrakyan dsetrak...@gridgain.com
wrote:
On Thu, Mar 26, 2015 at 4:28 AM, Branko Čibej br...@apache.org wrote:
On 26.03.2015 08:47, dsetrak...@apache.org
On 25.03.2015 09:35, Dmitriy Setrakyan wrote:
The first official Apache Ignite release (albeit release candidate) was
uploaded and the download page is updated:
https://ignite.incubator.apache.org/download.html
Well, I have to say I'm confused and just a bit unhappy.
We voted on a source
On 25.03.2015 10:55, Branko Čibej wrote:
There are ways, with a bit of scripting on the site, to get direct
download links instead of bouncing people through the mirrors page;
here's an example:
http://httpd.apache.org/download.cgi
Note that this page keeps the PGP/hash links pointing
On 25.03.2015 20:11, Dmitriy Setrakyan wrote:
On Wed, Mar 25, 2015 at 11:55 AM, Branko Čibej br...@apache.org wrote:
On 25.03.2015 19:07, Dmitriy Setrakyan wrote:
Brane,
The wrong download checksum issue has been addressed (I think). Please
double check me. The reason it happened was that I
On 25.03.2015 20:35, Dmitriy Setrakyan wrote:
On Wed, Mar 25, 2015 at 12:29 PM, Branko Čibej br...@apache.org wrote:
On 25.03.2015 20:11, Dmitriy Setrakyan wrote:
On Wed, Mar 25, 2015 at 11:55 AM, Branko Čibej br...@apache.org wrote:
On 25.03.2015 19:07, Dmitriy Setrakyan wrote:
Brane
On 25.03.2015 21:30, Branko Čibej wrote:
On 25.03.2015 20:35, Dmitriy Setrakyan wrote:
On Wed, Mar 25, 2015 at 12:29 PM, Branko Čibej br...@apache.org wrote:
On 25.03.2015 20:11, Dmitriy Setrakyan wrote:
On Wed, Mar 25, 2015 at 11:55 AM, Branko Čibej br...@apache.org wrote:
On 25.03.2015 19
On 25.03.2015 22:04, Branko Čibej wrote:
On 25.03.2015 21:30, Branko Čibej wrote:
On 25.03.2015 20:35, Dmitriy Setrakyan wrote:
On Wed, Mar 25, 2015 at 12:29 PM, Branko Čibej br...@apache.org wrote:
On 25.03.2015 20:11, Dmitriy Setrakyan wrote:
On Wed, Mar 25, 2015 at 11:55 AM, Branko Čibej
On 21.03.2015 00:49, Dmitriy Setrakyan wrote:
This is kind-of last minute,
Point of order: The community has made no decision on release schedule,
so there can be nothing 'last-minute' to the proposal. Even if there
were a schedule, it would be a matter of internal consensus, not
external
On 20.03.2015 21:01, Dmitriy Setrakyan wrote:
Does Amazon provide any AWS accounts for Apache? I would like to use it for
testing and benchmarking Ignite.
Better to ask this on general@; I don't know.
(If not, then I can ask GridGain to sponsor it)
You can get Infra to set up a VM for this
On 20.03.2015 21:20, Dmitriy Setrakyan wrote:
Is anyone getting updates from issues list? I don't think I am, even
thought I am subscribed to the list.
Did you check your spam folder? If you're using GMail, issue
notifications might have ended up there ... Google's been sporadically
sending
On 20.03.2015 22:28, Konstantin Boudnik wrote:
As far as I know they don't. Also, I think ASF has issues with letting target
donations for the specific projects. But in this particular case I don't think
there's a problem as a 3rd party will simply _let_ a project to use some
external
1 - 100 of 153 matches
Mail list logo
