Let me rephrase myself.

   - The code of Android or iOS playground app is never part of Apache
   Release. The release scripts always delete code of the Playground App
   before publishing release candidate.
   - The code of playground and weex_sdk is loosely coupled and the
   playground is mainly for demo purpose, like Google Sample [1]. It should
   *never* go into real product environment.
   - But the playground does provide developers the convenience of
   verifying the API or feature of Weex. They just need write code snippet
   online [2], and scan the QR code, then they get what they write.

[1] https://github.com/googlesamples
[2] http://dotwe.org/vue

Best Regards,
YorkShen

申远


Jan Piotrowski <[email protected]> 于2019年5月24日周五 下午8:14写道:

> A compiled Android or iOS native app is actually an interesting case.
> Is this actually part of the release, or is just the source code of
> the app?
>
> How tightly coupled are weex and the playground app anyway? Right now
> the playground app seems to live in a `playground` subfolder of `ios`
> and `android`. Would it maybe make sense to split that off in its own
> repo and have its own releases? I don't expect actual users of weex to
> really need the `playground` code, or do they?
>
> But yes, it would definitely be better to have this app not be
> published via a different commercial entity - no matter if you define
> the binary app to be part of the release or not. If Apache itself has
> a App Store Connect account I don't know though - best start by asking
> INFRA via a ticket. (Maybe it could also be published via one of the
> committers personal account as a fallback)
>
> -J
>
>
> -J
>
> Am Fr., 24. Mai 2019 um 12:20 Uhr schrieb 申远 <[email protected]>:
> >
> > Dear Community
> >
> > Weex 0.24.0 is released now, one can download source or convenience
> binary
> > through the link in our website [1].
> >
> > And there is a remaining issue for the release. One may notice that there
> > exists a showcase app called Weex Playground[2], which is compiled
> > from incubator-weex, but it is not a part os Apache Release as the
> release
> > script deleted the files of Playground when publishing release candidate.
> > As one need a enterprise certificates to publish an iOS App, we used to
> > borrow the certificates from Taobao(China), LTD.
> >
> > Based on the fact above, I have following concerns:
> >
> >    1. I'd like to know whether it is ok to exclude some file during
> apache
> >    release, like the code for Weex playground
> >    2. I am not sure whether it is suitable that I continue borrow the
> >    enterprise certificates from Taobao(China), LTD and publish the iOS
> App. If
> >    it is not acceptable, is there any iOS enterprise certificates under
> ASF?
> >
> > [1] https://weex.apache.org/download/download.html#latest-release
> > [2] https://itunes.apple.com/cn/app/weex-playground/id1130862662
> >
> > Best Regards,
> > YorkShen
> >
> > 申远
>

Reply via email to