From dev-return-8976-archive-asf-public=cust-asf.ponee.io@weex.incubator.apache.org Tue May 28 03:31:03 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 0EBB3180638 for ; Tue, 28 May 2019 05:31:02 +0200 (CEST) Received: (qmail 44592 invoked by uid 500); 28 May 2019 03:31:02 -0000 Mailing-List: contact dev-help@weex.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@weex.incubator.apache.org Delivered-To: mailing list dev@weex.incubator.apache.org Received: (qmail 44578 invoked by uid 99); 28 May 2019 03:31:01 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 May 2019 03:31:01 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 314A0C002B for ; Tue, 28 May 2019 03:31:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.199 X-Spam-Level: X-Spam-Status: No, score=-0.199 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 4fWkpvLPv-01 for ; Tue, 28 May 2019 03:30:59 +0000 (UTC) Received: from mail-wm1-f49.google.com (mail-wm1-f49.google.com [209.85.128.49]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id D73E95FBEC for ; Tue, 28 May 2019 03:30:58 +0000 (UTC) Received: by mail-wm1-f49.google.com with SMTP id t5so1127288wmh.3 for ; Mon, 27 May 2019 20:30:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-transfer-encoding; bh=gpf9NXXo3Wa6kHngkjqtY+mp0Asn5yxFts5R05yaJV0=; b=U0KFB3N3eRzQp1WoJURIDiNZd2NzqED9VO0Xf4RemhQ6vk0DOALyzQKmv2Yvmy+a1T ICGD79d5m2TnQZwKUNLBFYXPMEIzamyXgU0kRbNAYVI5kQxsRI+JtxYGlAThw8AivEYM se2py9DKR/+cV5NU8GsHr1Yhn1ecUPib5/xdDoBn8329Z5UZaStlb83pT5IV1YF1EXhq e8PGI7DojbTYncb6spxbHXqNYN3mqj56qGk/E3eq1CNuFx5yAAeJFu0ZmbaL9iCBHxN2 Ah71SxqAwYkiSlV6wq64BjViDLRIgDWDJ093cPK6QVyI0LHSIrlimdUhc1eW9oAogxKB 1Pkg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-transfer-encoding; bh=gpf9NXXo3Wa6kHngkjqtY+mp0Asn5yxFts5R05yaJV0=; b=MfA+9p6o0LeSoejijdgP3fdbF8j9wME+wO16S13EZAmRl3Ow4WuLQ1IyTNN5kD9ITK 8XfOShsS4FFgLt8O96nYGfnlPRQN5GkoLC3K/EMMWPa7/QRBPBNIm4xFJwNrEJ660s9W VisvyrmlZFfSHgyQzcW+IJpXY+PBiGejZzW2zpWmck1Ngdwn9ycVcA+z745XSBHlqiuu PktPf0LTikUsx7bS8i1nn0CwJLGiGP0oyx9mxb+t+LY7DVC050BioPNQOxmFJpFyC42J PGN62VpGmYSwDNFvX4Pa+EVoJnVQT5WdcVFLLdrq7Ei2LtSpikGfrWqkd5+B8pHMDLeB cHUQ== X-Gm-Message-State: APjAAAWbnpLXUu2JFAbK1YRtV4hhsIPSCWkHfdKD+Dn3Ej77KfMVxkeI ZXFlsvonWnzA92Dy8fNo+bs0DQGKVvkykoYXKrHoWUKc X-Google-Smtp-Source: APXvYqwvsRWQPjijWPZGqODt093ugYpRpSPESDtMGaqU31A8xHHQ/2cPiksq4/SHb+z3QS6eR4qEOENb5uAhxCGgoxQ= X-Received: by 2002:a1c:7606:: with SMTP id r6mr1450336wmc.25.1559014258050; Mon, 27 May 2019 20:30:58 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Willem Jiang Date: Tue, 28 May 2019 11:30:46 +0800 Message-ID: Subject: Re: [ANNOUNCEMENT] Weex 0.24.0 Released To: dev Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, May 27, 2019 at 8:04 PM =E7=94=B3=E8=BF=9C w= rote: > > I agree with that. > > Moving playground to another separate repository(also under ASF?) may tak= e > couple of days, I don't think there will be big technical issue. > > But this doesn't solve the issue that Weex Playground is under Apple > Developer Enterprise Program Account of Taobao (China) Software. And ther= e > is a similar situation for Weex Android Playground. > So, it looks like Taobao publish the binary release of Weex Playground. I'm not sure if it is OK for Apache. Maybe we should find a way to let the PMC member to provide the convenience binary. > I could and would mark thing "Stuff that some third party provides for > Apache Weex", but for "Stuff for Weex the Apache Weex team also provides"= , > this is really confusing concept. > > Best Regards, > YorkShen > > =E7=94=B3=E8=BF=9C > > > Jan Piotrowski =E4=BA=8E2019=E5=B9=B45=E6=9C=8827= =E6=97=A5=E5=91=A8=E4=B8=80 =E4=B8=8B=E5=8D=884:32=E5=86=99=E9=81=93=EF=BC= =9A > > > Thanks for the clarification. I understand why the Playground app is > > valuable and awesome for developers. > > > > Would it be an option to move the playground and connected code (e.g. > > for http://dotwe.org/vue) to a separate repository? Or does the > > `playground` code benefit so much from being in the same repository? > > > > For me right now this is one of these cases, where it is totally > > unclear what actually is part of "Apache Weex" (vs. "Stuff for Weex > > the Apache Weex team also provides" vs. "Stuff that some third party > > provides for Apache Weex"). > > > > -J > > > > > > Am Mo., 27. Mai 2019 um 09:01 Uhr schrieb =E7=94=B3=E8=BF=9C : > > > > > > Let me rephrase myself. > > > > > > - The code of Android or iOS playground app is never part of Apach= e > > > 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 > > > > > > =E7=94=B3=E8=BF=9C > > > > > > > > > Jan Piotrowski =E4=BA=8E2019=E5=B9=B45=E6=9C= =8824=E6=97=A5=E5=91=A8=E4=BA=94 =E4=B8=8B=E5=8D=888:14=E5=86=99=E9=81=93= =EF=BC=9A > > > > > > > A compiled Android or iOS native app is actually an interesting cas= e. > > > > 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 n= ow > > > > the playground app seems to live in a `playground` subfolder of `io= s` > > > > and `android`. Would it maybe make sense to split that off in its o= wn > > > > 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 defi= ne > > > > the binary app to be part of the release or not. If Apache itself h= as > > > > a App Store Connect account I don't know though - best start by ask= ing > > > > INFRA via a ticket. (Maybe it could also be published via one of th= e > > > > committers personal account as a fallback) > > > > > > > > -J > > > > > > > > > > > > -J > > > > > > > > Am Fr., 24. Mai 2019 um 12:20 Uhr schrieb =E7=94=B3=E8=BF=9C : > > > > > > > > > > Dear Community > > > > > > > > > > Weex 0.24.0 is released now, one can download source or convenien= ce > > > > binary > > > > > through the link in our website [1]. > > > > > > > > > > And there is a remaining issue for the release. One may notice th= at > > there > > > > > exists a showcase app called Weex Playground[2], which is compile= d > > > > > from incubator-weex, but it is not a part os Apache Release as th= e > > > > release > > > > > script deleted the files of Playground when publishing release > > candidate. > > > > > As one need a enterprise certificates to publish an iOS App, we u= sed > > 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 duri= ng > > > > 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 th= e > > 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 > > > > > > > > > > =E7=94=B3=E8=BF=9C > > > > > >