input will mean that something (or
> somebody) wrong is trying to connect, possibly using a wrong port or hoping
> that SSL is disabled.
>
> Maybe we need a simple warning. I guess we already have it, actually. Don't
> we?
>
> Regards,
> --
> Ilya Kasnacheev
>
>
>
Hello igniters! I wonder if we can add a new event for a failed ssl
connection? Considering security hazards it can be quite helpful to get
notifications in case someone unauthorized is trying to connect to the
cluster. I've created a small pull-request to illustrate a possible
solution.
https://gi
Hello, Igniters!
Recently we added the possibility of sending user defined attributes from
clients, and check those attributes in a custom authenticator
implementation[1]. However in some cases it's not working well for
GridClient because currently the attributes are only added to TOPOLOGY
message
Oleg Ostanin created IGNITE-12891:
-
Summary: Add userAttributes map to all GridClient messages
Key: IGNITE-12891
URL: https://issues.apache.org/jira/browse/IGNITE-12891
Project: Ignite
Issue
I'm currently working on ticket
https://issues.apache.org/jira/browse/IGNITE-12832
It's not exactly what had been suggested but it will allow to pass some
custom properties to the client configuration and to pass parameters without
length limitations using .properties file.
--
Sent from: http:/
Hello Ignite Community!
My name is Oleg. I want to contribute to Apache Ignite and want to
start with this issue - IGNITE-12832, my JIRA username oleg-a-ostanin.
Any help on this will be appreciated.
Thanks!
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/5498
IGNITE-10403 added parent guava dependency in pom.xml
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10403
Oleg Ostanin created IGNITE-10403:
-
Summary: Yardstick does not work without Guava 20 in the classpath
Key: IGNITE-10403
URL: https://issues.apache.org/jira/browse/IGNITE-10403
Project: Ignite
Github user oleg-ostanin closed the pull request at:
https://github.com/apache/ignite/pull/4812
---
Oleg Ostanin created IGNITE-10346:
-
Summary: Improve TcpDiscoveryVmIpFinder usability in Yardstick
Key: IGNITE-10346
URL: https://issues.apache.org/jira/browse/IGNITE-10346
Project: Ignite
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/4877
IGNITE-5534 added method to activate cluster
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5534
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/4824
IGNITE-9682 changed updatePartitionFullMap() method to update map in â¦
â¦parallel
You can merge this pull request into a Git repository by running:
$ git pull https://github.com
Oleg Ostanin created IGNITE-9682:
Summary: Update full partition map in parallel
Key: IGNITE-9682
URL: https://issues.apache.org/jira/browse/IGNITE-9682
Project: Ignite
Issue Type
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/4812
IGNITE-9309 added runLocal
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9309-b
Alternatively you can
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/4811
Ignite 9492 qaoo
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9492-qaoo
Alternatively you can review
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/4783
Ignite 9309 a
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9309-a
Alternatively you can review and
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/4548
IGNITE-9234 fixed javadocs
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9234
Alternatively you can
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/4323
Ignite 8322 fix
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8322-fix
Alternatively you can review and
Oleg Ostanin created IGNITE-8861:
Summary: Wrong method call in IgniteServise documentation snippet
Key: IGNITE-8861
URL: https://issues.apache.org/jira/browse/IGNITE-8861
Project: Ignite
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/4210
IGNITE-8322 changed default value for preloading option to 'false'
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apa
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/3942
Ignite 8337
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8337
Alternatively you can review and apply
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/3884
Ignite 8322
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8322
Alternatively you can review and apply
Oleg Ostanin created IGNITE-8322:
Summary: Yardstick benchmark preloading option
Key: IGNITE-8322
URL: https://issues.apache.org/jira/browse/IGNITE-8322
Project: Ignite
Issue Type
Oleg Ostanin created IGNITE-8319:
Summary: Examples do not launch from Intellij Idea because ML
module is configured incorrectly.
Key: IGNITE-8319
URL: https://issues.apache.org/jira/browse/IGNITE-8319
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/3825
IGNITE-8274 Changed invoking java in sqlline.sh
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8274
Oleg Ostanin created IGNITE-8226:
Summary: Thousands of warning messages per second in log files.
Key: IGNITE-8226
URL: https://issues.apache.org/jira/browse/IGNITE-8226
Project: Ignite
Oleg Ostanin created IGNITE-8177:
Summary: Reduce weight of error messages like "Failed completing
transaction" in log files.
Key: IGNITE-8177
URL: https://issues.apache.org/jira/browse/I
Oleg Ostanin created IGNITE-7981:
Summary: Thread hangs on ignite.cluster().active(false) method call
Key: IGNITE-7981
URL: https://issues.apache.org/jira/browse/IGNITE-7981
Project: Ignite
Oleg Ostanin created IGNITE-7943:
Summary: Node hangs on start after failing during checkpoint.
Key: IGNITE-7943
URL: https://issues.apache.org/jira/browse/IGNITE-7943
Project: Ignite
Issue
Oleg Ostanin created IGNITE-7344:
Summary: Fix yardstick devnotes
Key: IGNITE-7344
URL: https://issues.apache.org/jira/browse/IGNITE-7344
Project: Ignite
Issue Type: Improvement
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/3142
IGNITW-7093 added plugin to build test.jar to ignite-compatibility poâ¦
â¦m.xml
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain
Oleg Ostanin created IGNITE-7093:
Summary: Ignite compatibility test.jar does not builds
Key: IGNITE-7093
URL: https://issues.apache.org/jira/browse/IGNITE-7093
Project: Ignite
Issue Type
I've just checked master branch (by the way it's 2.4.0-SNAPSHOT now),
everything works fine on java 1.8 and maven 3.5.0. I've also cleaned maven
local repo.
On Mon, Nov 27, 2017 at 4:17 AM, kcmvp wrote:
> I still run into the same issue
>
>
>
> --
> Sent from: http://apache-ignite-developers.234
Oleg Ostanin created IGNITE-6978:
Summary: Failed to move temp file to a regular WAL segment file
Key: IGNITE-6978
URL: https://issues.apache.org/jira/browse/IGNITE-6978
Project: Ignite
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/3058
Ignite 6927
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6927
Alternatively you can review and apply
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/2926
IGNITE-6751 skipped upload ignite-dev-utils module into maven repository
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache
Oleg Ostanin created IGNITE-6751:
Summary: Skip upload ignite-dev-utils module into maven repository
Key: IGNITE-6751
URL: https://issues.apache.org/jira/browse/IGNITE-6751
Project: Ignite
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/2920
IGNITE 6726
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6726
Alternatively you can review and apply
Oleg Ostanin created IGNITE-6726:
Summary: Licenses for Sqlline are missing
Key: IGNITE-6726
URL: https://issues.apache.org/jira/browse/IGNITE-6726
Project: Ignite
Issue Type: Bug
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/2911
IGNITE-6718 skipped upload sqlline and compatibility modules into maâ¦
â¦ven central
You can merge this pull request into a Git repository by running:
$ git pull https://github.com
Oleg Ostanin created IGNITE-6718:
Summary: Skip deploy sqlline and compatibility modules into
repositiry
Key: IGNITE-6718
URL: https://issues.apache.org/jira/browse/IGNITE-6718
Project: Ignite
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/2902
IGNITE-6708 Remove ignite-compatibility from optional directory
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/2901
IGNITE-6706 Remove ignite-sqlline module from optioanl directory
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/2879
IGNITE-6660 fixed Python Redis example (print statements)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/2868
IGNITE 6648
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6648
Alternatively you can review and apply
ood to me. Please consider the notes left in the ticket. I want us
> to prepare a script for Windows, review the language for help notice and
> errors, put together documentation. Prachi will be able to help with the
> editing and documentation.
>
> —
> Denis
>
> > On O
Oleg Ostanin created IGNITE-6648:
Summary: ML javadoc is missing in 2.2 binary release
Key: IGNITE-6648
URL: https://issues.apache.org/jira/browse/IGNITE-6648
Project: Ignite
Issue
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/2861
Ignite 5608
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5608
Alternatively you can review and apply
ave for the ticket resolution.
>
> Denis
>
> On Monday, October 9, 2017, Anton Vinogradov
> wrote:
>
> > Any plans to have ignitesql.bat?
> >
> > On Mon, Oct 9, 2017 at 5:29 PM, Oleg Ostanin > > wrote:
> >
> > > Another build with sqlli
Another build with sqlline included:
https://ci.ignite.apache.org/viewLog.html?buildId=881120&tab=artifacts&buildTypeId=IgniteRelease_XxxFromMirrorIgniteRelease3PrepareVote#!1rrb2,-wpvx2aopzexz,1esn4zrslm4po,-h8h0hn9vvvxp
On Sun, Oct 8, 2017 at 5:11 PM, Denis Magda wrote:
> No more doubts on my
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/2801
removed excluding ML from examples/src
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite remove-ml-excluding
We created the release build procedure on Apache CI server according to
this ticket:
https://issues.apache.org/jira/browse/IGNITE-5249
We also changed the checksum calculation method:
https://issues.apache.org/jira/browse/IGNITE-5817
Oleg
On Thu, Sep 7, 2017 at 9:49 AM, 李玉珏@163 <18624049...@163.c
Great news, thanks a lot!
On Tue, Sep 5, 2017 at 11:47 AM, Pavel Tupitsyn
wrote:
> DocFX takes around 30 seconds on my machine.
>
> > if you already tried that
> Yes, everything is done on my side, see JIRA ticket [4] and preview [5]
> above.
>
> On Tue, Sep 5, 2017 at 11:45 AM, Ilya Suntsov
>
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/2590
IGNITE-5817 Changed checksum calculation methods
(cherry picked from commit 28fb8c8)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com
Github user oleg-ostanin closed the pull request at:
https://github.com/apache/ignite/pull/2585
---
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/2586
IGNITE-6237 created script for signing and uploading artifacts to remâ¦
â¦ote staging.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/2585
Ignite 6237
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6237
Alternatively you can review and apply
Oleg Ostanin created IGNITE-6237:
Summary: Script for signing and uploading artifacts to remote
staging.
Key: IGNITE-6237
URL: https://issues.apache.org/jira/browse/IGNITE-6237
Project: Ignite
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/2539
Ignite 5817 x
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5817-x
Alternatively you can review and
Oleg Ostanin created IGNITE-6209:
Summary: Build Ignite.NET NuGet packages for Apache-Ignite release
on CI
Key: IGNITE-6209
URL: https://issues.apache.org/jira/browse/IGNITE-6209
Project: Ignite
Oleg Ostanin created IGNITE-6192:
Summary: Ignite-ML does not compile
Key: IGNITE-6192
URL: https://issues.apache.org/jira/browse/IGNITE-6192
Project: Ignite
Issue Type: Bug
this email are those of the author,
> and do not necessarily represent the views of any company the author
> might be affiliated with at the moment of writing.
>
>
> On Sun, Aug 6, 2017 at 5:37 AM, Oleg Ostanin
> wrote:
> > Hi,
> >
> > I'd like to start a
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/2498
IGNITE-6155 added new jvm flag for printing gc date stamps
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite
Oleg Ostanin created IGNITE-6155:
Summary: Add GC Date Stamps to yardstick gc log
Key: IGNITE-6155
URL: https://issues.apache.org/jira/browse/IGNITE-6155
Project: Ignite
Issue Type
Hi, Denis
Yes, we have a ticket that already takes this into account:
https://issues.apache.org/jira/browse/IGNITE-5817
I think we can create both sha-256 and sha-512 checksums.
Best regards
Oleg
On Thu, Aug 17, 2017 at 1:51 AM, Denis Magda wrote:
> Igniters, especially the release managers,
>
Hi,
I'd like to start a discussion about Apache Ignite release procedure.
I'm working on ticket Ignite-5249 "The release build procedure should be
placed on the CI/CD server and available to run for the release engineer."
https://issues.apache.org/jira/browse/IGNITE-5249
Currently we have three
Hi,
We need to decide what сhecksum algorythm we should use for signing release
artifacts. Currently we use md5 and sha-1. sha-1 will be replaced by
sha-256 soon. Should we keep md5 or use only sha-256?
Oleg Ostanin created IGNITE-5833:
Summary: Changing maven goal from "install" to "package" for
building from sources
Key: IGNITE-5833
URL: https://issues.apache.org/jira/browse/IGNITE-5833
Oleg Ostanin created IGNITE-5817:
Summary: Changing checksum calculation methods
Key: IGNITE-5817
URL: https://issues.apache.org/jira/browse/IGNITE-5817
Project: Ignite
Issue Type: Bug
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/2338
IGNITE-5807 added new profile to fix artifacts signing, edited DEVNOTâ¦
â¦ES.txt
You can merge this pull request into a Git repository by running:
$ git pull https://github.com
Github user oleg-ostanin closed the pull request at:
https://github.com/apache/ignite/pull/2310
---
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
Oleg Ostanin created IGNITE-5807:
Summary: Fixing signing artifacts
Key: IGNITE-5807
URL: https://issues.apache.org/jira/browse/IGNITE-5807
Project: Ignite
Issue Type: Bug
Hi Vyacheslav
Yes, we changed build procedure, please look in the DEVNOTES.txt.
On Wed, Jul 19, 2017 at 12:53 PM, Vyacheslav Daradur
wrote:
> Hi guys.
> I've downloaded apache-ignite-2.1.0-src.zip, unpack it and execute "mvn
> package -DskipTests"
> result is succes, but the folder "target" in t
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/2310
removed excluding ML sources from assembly file
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
ignite-2.1
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/2308
IGNITE-5762 skipping lgpl and examples deploy
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5762
Oleg Ostanin created IGNITE-5762:
Summary: Skip deploy lgpl modules into repositiry
Key: IGNITE-5762
URL: https://issues.apache.org/jira/browse/IGNITE-5762
Project: Ignite
Issue Type: Bug
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/2286
IGNITE-5740 created new benchmark for load transaction
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5740
Oleg Ostanin created IGNITE-5740:
Summary: Transactional load benchmark
Key: IGNITE-5740
URL: https://issues.apache.org/jira/browse/IGNITE-5740
Project: Ignite
Issue Type: Improvement
Oleg Ostanin created IGNITE-5720:
Summary: Different date format in ResultSet
Key: IGNITE-5720
URL: https://issues.apache.org/jira/browse/IGNITE-5720
Project: Ignite
Issue Type: Bug
Oleg Ostanin created IGNITE-5596:
Summary: Exchange time measurement
Key: IGNITE-5596
URL: https://issues.apache.org/jira/browse/IGNITE-5596
Project: Ignite
Issue Type: Improvement
Oleg Ostanin created IGNITE-5488:
Summary: Build failure: maven-remote-resources-plugin
Key: IGNITE-5488
URL: https://issues.apache.org/jira/browse/IGNITE-5488
Project: Ignite
Issue Type
+1
I have assigned the ticket to myself and I did some preliminary
investigations in this matter. It seems to me the most complicated part
will be configuring tasks in such way that release commiter could use it
without exposing his credentials for Git, SVN and Maven. I suggest we
create an integr
Github user oleg-ostanin closed the pull request at:
https://github.com/apache/ignite/pull/1954
---
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
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/1954
ignite-gg-12199 added new variable CLEAN_WORK_DIR in config files
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Oleg Ostanin created IGNITE-5177:
Summary: Failed javadoc generation for web-agent
Key: IGNITE-5177
URL: https://issues.apache.org/jira/browse/IGNITE-5177
Project: Ignite
Issue Type: Bug
Github user oleg-ostanin closed the pull request at:
https://github.com/apache/ignite/pull/1840
---
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
Github user oleg-ostanin closed the pull request at:
https://github.com/apache/ignite/pull/1838
---
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
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/1889
Ignite 5120
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5120
Alternatively you can review and apply
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/1886
Ignite 2.0 temp for fix hibernate upload
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
ignite-2.0-temp-for-fix
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/1840
Ignite gg 11423 from20
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-gg-11423-from20
Alternatively you
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/1838
Ignite gg 11423 from20
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-gg-11423-from20
Alternatively you
Oleg Ostanin created IGNITE-4894:
Summary: Yardstick-Cassandra
Key: IGNITE-4894
URL: https://issues.apache.org/jira/browse/IGNITE-4894
Project: Ignite
Issue Type: New Feature
Oleg Ostanin created IGNITE-4822:
Summary: Editing default JVM options defined in Ignite-Yardstick
property files.
Key: IGNITE-4822
URL: https://issues.apache.org/jira/browse/IGNITE-4822
Project
t; > > > >>>
> > > > > >>> 2017-02-09 23:58 GMT+03:00 Denis Magda :
> > > > > >>>
> > > > > >>>> Anton,
> > > > > >>>>
> > > > > >>>> You can expect Kubern
I'm sorry, there wasn't any problem with the build, it was local problem on
my machine.
On Fri, Feb 10, 2017 at 11:54 AM, Oleg Ostanin
wrote:
> Hi.
>
> I just discovered that some functionality does not work correctly. I will
> present fixed version later.
>
> On F
Hi.
I just discovered that some functionality does not work correctly. I will
present fixed version later.
On Fri, Feb 10, 2017 at 12:43 AM, Oleg Ostanin
wrote:
> https://drive.google.com/open?id=0B9teTzJ9iIvHckl6eVQ3N0R4a3c
>
> On Fri, Feb 10, 2017 at 12:43 AM, Oleg Ostanin
https://drive.google.com/open?id=0B9teTzJ9iIvHckl6eVQ3N0R4a3c
On Fri, Feb 10, 2017 at 12:43 AM, Oleg Ostanin
wrote:
> I've fixed README.txt and created new DEVNOTES.txt. Also renamed sample
> benchmark configuration file to benchmark-sample.properties.
> Please look for the res
n the build procedures.
>
> —
> Denis
>
> > On Jan 31, 2017, at 3:12 AM, Oleg Ostanin wrote:
> >
> > Hi Denis,
> >
> > Yes, we have included Ignite Yardstick source files with its pom.xml in
> > Ignite binary release. "Building from standalone s
h applied? You
> should be able to use TeamCity for that. Makes sense to see the new project
> structure and walk through final version of the instructions.
>
> —
> Denis
>
> > On Feb 2, 2017, at 2:30 AM, Oleg Ostanin wrote:
> >
> > Denis,
> >
> > Yes
enerated
> >> README.txt. *Anton*, is it feasible to do?
> >>
> >> Finally, when apply the reviews notes please build and share Ignite
> >> binaries with your patch. Want to see the new project structure and
> final
> >> version of the instructions. Present
1 - 100 of 121 matches
Mail list logo
