Re: [ANNOUNCEMENT] Weex 0.24.0 Released

2019-05-24 Thread Jan Piotrowski
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 申远 :
>
> 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
>
> 申远


[ANNOUNCEMENT] Weex 0.24.0 Released

2019-05-24 Thread 申远
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

申远


Re: [incubator-weex] annotated tag 0.9.1.7 deleted (was 7e9a946)

2019-05-24 Thread York Shen
Ref https://github.com/apache/incubator-weex/pull/2481 
, which explains the reason 
of the bug and provides a fix.

Best Regards,
York Shen

申远

> 在 2019年5月24日,17:56,York Shen  写道:
> 
> Well, there is a bug in weex release script, which caused me pushing about 
> 300 local tag to GitHub yesterday. These 300 tags could cause confusion as 
> most of them are neither official release or release candidate. They are just 
> my local tags indicated daily building.
> 
> So, I just deleted the wrong tag and still remained the tag of official 
> release or release candidate.
> 
> I will fix the bug in the release script later.
> 
> Best Regards,
> York Shen
> 
> 申远
> 
>> 在 2019年5月24日,17:49,Willem Jiang > > 写道:
>> 
>> Can I know why do we remove these tags?
>> It's very danger to change the tags without any notification.
>> 
>> Willem Jiang
>> 
>> Twitter: willemjiang
>> Weibo: 姜宁willem
>> 
>> 
>> -- Forwarded message -
>> From: mailto:ky...@apache.org>>
>> Date: Fri, May 24, 2019 at 5:38 PM
>> Subject: [incubator-weex] annotated tag 0.9.1.7 deleted (was 7e9a946)
>> To: comm...@weex.apache.org  
>> mailto:comm...@weex.apache.org>>
>> 
>> 
>> This is an automated email from the ASF dual-hosted git repository.
>> 
>> kyork pushed a change to annotated tag 0.9.1.7
>> in repository https://gitbox.apache.org/repos/asf/incubator-weex.git 
>> .
>> 
>> 
>> *** WARNING: tag 0.9.1.7 was deleted! ***
>> 
>>   tag was  7e9a946
>> 
>> The revisions that were on this annotated tag are still contained in
>> other references; therefore, this change does not discard any commits
>> from the repository.
> 



Re: [incubator-weex] annotated tag 0.9.1.7 deleted (was 7e9a946)

2019-05-24 Thread York Shen
Well, there is a bug in weex release script, which caused me pushing about 300 
local tag to GitHub yesterday. These 300 tags could cause confusion as most of 
them are neither official release or release candidate. They are just my local 
tags indicated daily building.

So, I just deleted the wrong tag and still remained the tag of official release 
or release candidate.

I will fix the bug in the release script later.

Best Regards,
York Shen

申远

> 在 2019年5月24日,17:49,Willem Jiang  写道:
> 
> Can I know why do we remove these tags?
> It's very danger to change the tags without any notification.
> 
> Willem Jiang
> 
> Twitter: willemjiang
> Weibo: 姜宁willem
> 
> 
> -- Forwarded message -
> From: 
> Date: Fri, May 24, 2019 at 5:38 PM
> Subject: [incubator-weex] annotated tag 0.9.1.7 deleted (was 7e9a946)
> To: comm...@weex.apache.org 
> 
> 
> This is an automated email from the ASF dual-hosted git repository.
> 
> kyork pushed a change to annotated tag 0.9.1.7
> in repository https://gitbox.apache.org/repos/asf/incubator-weex.git.
> 
> 
> *** WARNING: tag 0.9.1.7 was deleted! ***
> 
>   tag was  7e9a946
> 
> The revisions that were on this annotated tag are still contained in
> other references; therefore, this change does not discard any commits
> from the repository.



Still Failing: apache/incubator-weex#5955 (0.25.0 - 340ec4a)

2019-05-24 Thread Travis CI
Build Update for apache/incubator-weex
-

Build: #5955
Status: Still Failing

Duration: 2 mins and 4 secs
Commit: 340ec4a (0.25.0)
Author: YorkShen
Message: Chagne Android Version (#2480)

* Fix android version

* Ignore android version check during Apache release

View the changeset: https://github.com/apache/incubator-weex/compare/0.25.0

View the full build log and details: 
https://travis-ci.org/apache/incubator-weex/builds/536701033?utm_medium=notification_source=email

--

You can unsubscribe from build emails from the apache/incubator-weex repository 
going to 
https://travis-ci.org/account/preferences/unsubscribe?repository=11562877_medium=notification_source=email.
Or unsubscribe from *all* email updating your settings at 
https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notification_source=email.
Or configure specific recipients for build notifications in your .travis.yml 
file. See https://docs.travis-ci.com/user/notifications.



Fwd: [incubator-weex] annotated tag 0.9.1.7 deleted (was 7e9a946)

2019-05-24 Thread Willem Jiang
Can I know why do we remove these tags?
It's very danger to change the tags without any notification.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem


-- Forwarded message -
From: 
Date: Fri, May 24, 2019 at 5:38 PM
Subject: [incubator-weex] annotated tag 0.9.1.7 deleted (was 7e9a946)
To: comm...@weex.apache.org 


This is an automated email from the ASF dual-hosted git repository.

kyork pushed a change to annotated tag 0.9.1.7
in repository https://gitbox.apache.org/repos/asf/incubator-weex.git.


*** WARNING: tag 0.9.1.7 was deleted! ***

   tag was  7e9a946

The revisions that were on this annotated tag are still contained in
other references; therefore, this change does not discard any commits
from the repository.