[
https://issues.apache.org/jira/browse/IGNITE-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14512075#comment-14512075
]
Branko Čibej commented on IGNITE-775:
-------------------------------------
I'd love to understand which part of GridGain's release process is related to
the ASF and should therefore be tracked here.
Apart from that, whatever runtime update checking code lands in Ignite should
depend on ASF infrastructure for exactly the same reasons we require our master
repositories to reside on ASF infrastructure: to whit, an external entity could
discontinue the service or just vanish, so if our users are depending on this
kind of service, we should be providing it.
On a side note, doing HTTP requests for update checks is sooo last century and
also expensive. I'd love to see ASF Infra support a DNS-based update
notification service.
> 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)
