It took me a while to read the related JIRA issuse, emails and policies, and I
think the following is allowed in legal and Apache brand management opinions:
Publish binary artifacts through npm, cocoapods and jcenter(maven), which are
basically industry standard binary downstream/distribution channel for JS, iOS
and Android developers.
The following is under consideration:
Now, one of Weex PPMC members build binary artifacts and publish to the above
distribution channels using the same source code as the formal Apache release.
But this binary distribution is not voted as the corresponding source code is
voted yet. Do we need to vote the binary artifacts? If a vote is needed, what
and how the PPMC members check the binary artifacts?
The following is FORBIDDEN:
Publish unreleased codes/artifacts in any binary channel even if it is called
alpha/beta release under the name of Apache Weex/Weex PPMC members. It looks
like we need to cancel the weex weekly publishing permanently as it is against
the Apache rules.
> 在 2019年1月9日，11:06，Willem Jiang 写道：
>
> Hi Team，
>
> I'm not sure if you are aware the official release and unreleased code
> in Apache Incubator.
> Please take some time read through the code and let me know what you think.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
>
> -- Forwarded message -
> From: Justin Mclean
> Date: Sun, Jan 6, 2019 at 7:21 AM
> Subject: Official releases vs unreleased code
> To:
>
>
> Hi,
>
> Over the last few months I’ve run into 1/2 dozen podlings who are
> making and promoting releases to the wider community that contain
> unreleased code, and I’m a little surprised that they were unaware
> that this is not allowed. This also has come up in feedback received
> from the exit questionnaire.
>
> In the release policy [3] it clearly states:
> "Projects MUST direct outsiders towards official releases rather than
> raw source repositories, nightly builds, snapshots, release
> candidates, or any other similar packages.”
>
> This has been discussed many times but these two legal JIRAs [1][2]
> spell it out quite clearly. And while these tickets refer to docker
> the same applies to any distribution mechanism.
>
> In short “It is appropriate to distribute official releases through
> downstream channels, but inappropriate to distribute unreleased
> materials through them.”
>
> So if your projects is using docker, PiPY, GitHub releases, npm or any
> other ways of distribution please make sure that the wider community
> is only pointed at official release and the best way to do this is not
> to publish unreleased code on those platforms. Ask yourself is someone
> outside of the project likely to use this and if the answer is yes
> then reconsider how you are using that distribution channel and make
> sure it only contains official releases.
>
> Thanks,
> Justin
>
> 1. https://issues.apache.org/jira/browse/LEGAL-270
> 2. https://issues.apache.org/jira/browse/LEGAL-427
> 3. http://www.apache.org/legal/release-policy.html#publication
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
