You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@polygene.apache.org by "Paul Merlin (JIRA)" <ji...@apache.org> on 2015/07/06 10:54:04 UTC

[jira] [Assigned] (ZEST-25) Project -> Source SDK -> Binary SDK

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

Paul Merlin reassigned ZEST-25:
-------------------------------

    Assignee: Paul Merlin

> 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
>
> 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
>    -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
(v6.3.4#6332)