I don’t see the donator desire here. This desire is to give AI consumers more
frequent releases with bug fix and understanding when we, as a community,
will release new, announced features to them.
Now it’s not clear why consumers should fix bugs themselves, if they don’t
have the opportunity to
Hi, Igniters!
I propose to discuss immediately the timing of 2.9.0 and interim releases!
My propose:
~ June 01 - 2.8.1
~ September 01 - 2.8.2
~ November 01 - 2.9.0
Sberbank team, for its part, is ready to take on the work of management
interim releases.
Regards,
Aleksey Chetaev.
--
Sent
Aleksey Chetaev created IGNITE-7594:
---
Summary: Tx performance drop after WAL optimization
Key: IGNITE-7594
URL: https://issues.apache.org/jira/browse/IGNITE-7594
Project: Ignite
Issue
Aleksey Chetaev created IGNITE-7094:
---
Summary: Javadoc warnings in ml module
Key: IGNITE-7094
URL: https://issues.apache.org/jira/browse/IGNITE-7094
Project: Ignite
Issue Type: Bug
Aleksey Chetaev created IGNITE-6822:
---
Summary: IgfsMapReduceExample raise exception in multi nodes run
Key: IGNITE-6822
URL: https://issues.apache.org/jira/browse/IGNITE-6822
Project: Ignite
t able to view new Run configs:
> You do not have enough permissions to access build type with id:
> IgniteRelease_427CheckBuildIgniteFabricOpenJDK8
>
> What should I do to see new builds?
>
> Sincerely,
> Dmitriy Pavlov
>
> ср, 6 сент. 2017 г. в 15:57, Aleksey
FYI:
I founded some issues with build failed in our JIRA:
1. https://issues.apache.org/jira/browse/IGNITE-2149
2. https://issues.apache.org/jira/browse/IGNITE-4721
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Igniters,
In Ignite DEVNOTES we have full instruction how we can build Ignite, but we
have a lot of different options with which Ignite can be builded:
1. Ignite Fabric without Scala modules
2. Ignite Fabric with Scala modules
3. Ignite Fabric LGPL without Scala
4. Ignite Fabric LGPL with
Aleksey Chetaev created IGNITE-6243:
---
Summary: RazorSQL crashed on try edit, describe and another
actions with table.
Key: IGNITE-6243
URL: https://issues.apache.org/jira/browse/IGNITE-6243
Project
Aleksey Chetaev created IGNITE-6189:
---
Summary: Benchmarks for check LFS used disk space
Key: IGNITE-6189
URL: https://issues.apache.org/jira/browse/IGNITE-6189
Project: Ignite
Issue Type
Aleksey Chetaev created IGNITE-6108:
---
Summary: Hangs in streamer when using store
Key: IGNITE-6108
URL: https://issues.apache.org/jira/browse/IGNITE-6108
Project: Ignite
Issue Type: Bug
If anyone can’t sleep at night
If anyone sleep very bad
If you afraid that your password
Can evil hacker steal right now
For they we worked day and night
Don’t slept and worked fully days
And finish with https
Teamcity for, Igniters for.
https://ci.ignite.apache.org
--
View this message in
ead of forcing many people to follow some rules just to make this
> > > report looks sexy, we'd better to have one responsbile enginner, who
> will
> > > spend an hour once in 1-2 months to make release notes correct and
> > > meaningful. We can have a template with , , , tags
> f
Aleksey Chetaev created IGNITE-5920:
---
Summary: CacheClientBinaryQueryExample return different results if
we add non local node
Key: IGNITE-5920
URL: https://issues.apache.org/jira/browse/IGNITE-5920
> > single person interested in reviewing all of them? E.g. we added new
> >> JDBC
> >> > driver. I do not see it in the list of major features, neither I need
> to
> >> > know that this task was split into 20 smaller sub tasks, each of
> which
eporting.
> It is not user-friendly.
>
> Vladimir.
>
> On Wed, Aug 2, 2017 at 4:57 PM, Aleksey Chetaev <[hidden email]
> <http:///user/SendEmail.jtp?type=node=20380=0>>
> wrote:
>
> > Igniters,
> >
> > Started 2.0 we generated manually Jira based relea
for create release notes. In template we
can setup Jira servers with credentials and filters for each release notes
section.
Please see pull request: https://github.com/apache/ignite/pull/2379 may be
we can merge this to Ignite for improve our release process?
Kind regards
Aleksey Chetaev.
--
View
; https://www.globalsign.com/en/repository/globalsign-subscriber-agreement-digital-certificates-and-services.pdf
> [2] https://letsencrypt.org/
> [3]
> https://www.eff.org/deeplinks/2017/06/lets-encrypt-has-issued-100-million-certificates
>
> Thanks,
> Cos
>
> On Wed, Jul
Hi,
A know GlobalSing support open source projects for
free(https://www.globalsign.com/en/ssl/ssl-open-source/).
We can request certificates from them, it will be more easy for me. Any
objection?
Denis Magda-2 wrote
> Hi Cos,
>
> Alexey Chetaev, please join the conversation and share your
Guys,
I removed test binaries. I hope Ilya S. can give more comments about this
issue on Monday.
Best Regards,
Aleksey Chetaev.
--
View this message in context:
http://apache-ignite-developers.2346864.n4.nabble.com/Fwd-ignite-your-dist-artifacts-1-BAD-signature-tp19732p19741.html
Sent from
Aleksey Chetaev created IGNITE-5434:
---
Summary: Yardstick sql benchmarks broken on Ignite-5267 branch
Key: IGNITE-5434
URL: https://issues.apache.org/jira/browse/IGNITE-5434
Project: Ignite
users. Users in this group
can start and stop builds in projects with Ignite tests. (Users add to this
group automaticly on created).
Best Regards,
Aleksey Chetaev.
--
View this message in context:
http://apache-ignite-developers.2346864.n4.nabble.com/CI-Server-permissions-changed-tp18500.html
Sent fro
Aleksey Chetaev created IGNITE-5355:
---
Summary: Create task with release tools
Key: IGNITE-5355
URL: https://issues.apache.org/jira/browse/IGNITE-5355
Project: Ignite
Issue Type: Task
23 matches
Mail list logo
