polygene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niclas Hedhman (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZEST-16) Ensure compliance with Branding policy
Date Wed, 17 Jun 2015 22:53:00 GMT

    [ https://issues.apache.org/jira/browse/ZEST-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14590782#comment-14590782

Niclas Hedhman commented on ZEST-16:

Shane Curcuru wrote to us;
Please update the Zest download pages, where end users can download the
Qi4J product with a clear notice that those downloads are not an
official Apache project release, rather are releases from the
pre-existing Qi4J project, which is migrating to become the Zest project.

Any "Download" or similar pages at Apache projects need to be clear to
end users if they're getting a formal Apache release - that is, one made
by a TLP's PMC formally voting on it - or some other sort of bits of

Similarly, it would be very helpful to update the Zest homepage to make
the plan clearer.  I.e., isn't the intention that the Qi4J project is
turning into the Zest project going forward, and thus releasing (once
the PMC updates branding, etc.) the software as Apache Zest?

> Ensure compliance with Branding policy
> --------------------------------------
>                 Key: ZEST-16
>                 URL: https://issues.apache.org/jira/browse/ZEST-16
>             Project: Zest
>          Issue Type: Sub-task
>            Reporter: Niclas Hedhman

This message was sent by Atlassian JIRA

View raw message