polygene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Merlin (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ZEST-25) Project -> Source SDK -> Binary SDK
Date Fri, 24 Jul 2015 15:03:05 GMT

     [ https://issues.apache.org/jira/browse/ZEST-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Paul Merlin resolved ZEST-25.
    Resolution: Fixed

Following a discussion on dev@ several people checked the source and binary distributions.

> Project -> Source SDK -> Binary SDK
> -----------------------------------
>                 Key: ZEST-25
>                 URL: https://issues.apache.org/jira/browse/ZEST-25
>             Project: Zest
>          Issue Type: Sub-task
>            Reporter: Niclas Hedhman
>            Assignee: Paul Merlin
>             Fix For: 2.1
> Apache Software Foundation releases Source Tarballs only.
> Our build system builds a source tarball, but it had a slightly different purpose, more
like a "reference" than the actual release.
> Any binaries that we ship, are not really ASF releases, but convenience packages, and
secondary in nature to the source release.
> THEREFOR, it is important that 
>    -a. The current src/ directory where the source is built into in the tarball is removed
and moved up to its root level.- See 916cc4c
>    -b. Only what we consider "releasable" will be released in that source form- See 1da62b8
and 858f5ba
>    -c. That building from that distributed source files, accurately builds the binaries-
See ac7d88a, and 4f2a0b0
>    -d. Instructions for downstream packagers on how to build (everyone doesn't know Gradle)-
See ac7d88a
> Once the binaries are built, both with Java 7 and Java, we need to verify that the SDK
functions as expected.

This message was sent by Atlassian JIRA

View raw message