ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitriy Setrakyan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-775) Fix binaries naming.
Date Mon, 27 Apr 2015 19:26:41 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14514767#comment-14514767
] 

Dmitriy Setrakyan commented on IGNITE-775:
------------------------------------------

Cos, I think it makes sense to open another ticket to address the new-version pings.

> Fix binaries naming.
> --------------------
>
>                 Key: IGNITE-775
>                 URL: https://issues.apache.org/jira/browse/IGNITE-775
>             Project: Ignite
>          Issue Type: Bug
>          Components: build
>    Affects Versions: sprint-2
>            Reporter: Nikita Ivanov
>            Assignee: Anton Vinogradov
>             Fix For: sprint-4
>
>
> To summarize:
> - GridGain Enterprise Edition (e.g., gridgain-enterprise-foo-version.zip) is fine;
> - GridGain Community Edition (e.g., gridgain-community-foo-version.zip) is fine;
> - Apache Ignite binaries provided by GridGain (e.g., apache-ignite-foo-version.zip) is
fine, too, as long as the binaries don't go announcing version updates from info published
on the GridGain site (but it's OK to look for info on the Ignite site); and as long as they
either don't contain the LGPL&Co. dependencies, or very explicitly warn users that distribution
rights are not covered by ALv2;
> What's currently published is confusing, i.e., not OK.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message