Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
If your changes can lead to this failure(s): We're grateful that you were a
volunteer to make the contribution to this project, but things change and you
may no longer be able to
Alexey Goncharuk created IGNITE-14002:
-
Summary: Formalize coding guidelines for platforms (C++, Python,
Node)
Key: IGNITE-14002
URL: https://issues.apache.org/jira/browse/IGNITE-14002
Project:
Hi Maxim et al,
I’d like to share my interim status on Ignite 2.10 documentation work.
- The following PR’s *[list #1]* are reviewed and, when the changes are
accepted, ready to be merged, including 4 important features.
- I’m pretty sure that I’ll collect and put together
Alexey Goncharuk created IGNITE-14001:
-
Summary: Minor code style fixes for configuration and runner
modules
Key: IGNITE-14001
URL: https://issues.apache.org/jira/browse/IGNITE-14001
Project:
Alexey Goncharuk created IGNITE-14000:
-
Summary: Ignite 3.0: Fix codestyle for cli and cli-common packages
Key: IGNITE-14000
URL: https://issues.apache.org/jira/browse/IGNITE-14000
Project: Ignite
I will take it over.
> On 15 Jan 2021, at 12:37, Andrey Mashenkov wrote:
>
> I've created a ticket for the issue [1].
> Someone who fully understands the release process may pick it up.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-13999
>
> On Fri, Jan 15, 2021 at 12:01 AM Andrey
Andrey Mashenkov created IGNITE-13999:
-
Summary: Switch to SHA-512 for jar checksum calculation.
Key: IGNITE-13999
URL: https://issues.apache.org/jira/browse/IGNITE-13999
Project: Ignite
