Hi,
> So, what's the step?
>
> 1. Call a normal Apache Vote
> 2. Build the App and upload to App Store with ASF's Apple Developer
> Account using the code in step 1
That sounds right to me, in 1 I assume you are voting on a source release.
Thanks,
Justin
So, what's the step?
1. Call a normal Apache Vote
2. Build the App and upload to App Store with ASF's Apple Developer
Account using the code in step 1
Best Regards,
YorkShen
申远
Greg Stein 于2019年11月8日周五 上午8:57写道：
> We're trying to do better on what services are available, so
We're trying to do better on what services are available, so consider this
"step one" :-)
On Thu, Nov 7, 2019 at 1:19 PM Julian Feinauer
wrote:
> Thanks Greg, I didn't know that!
>
> Julian
>
> Am 07.11.19, 19:24 schrieb "Greg Stein" :
>
>
>
Thanks Greg, I didn't know that!
Julian
Am 07.11.19, 19:24 schrieb "Greg Stein" :
https://cwiki.apache.org/confluence/display/INFRA/Distribution+via+the+Apple+App+Store
On Thu, Nov 7, 2019 at 12:14 PM Greg Stein wrote:
> An app signed by the Foundation is most
https://cwiki.apache.org/confluence/display/INFRA/Distribution+via+the+Apple+App+Store
On Thu, Nov 7, 2019 at 12:14 PM Greg Stein wrote:
> An app signed by the Foundation is most definitely associated with the
> ASF. The Foundation has an Apple Developer Account for exactly this reason.
>
>
>
An app signed by the Foundation is most definitely associated with the ASF.
The Foundation has an Apple Developer Account for exactly this reason.
On Thu, Nov 7, 2019 at 9:17 AM Justin Mclean
wrote:
> Hi,
>
> A binary convenance release needs to be created from released voted on
> code. [1]
>
Hi,
A binary convenance release needs to be created from released voted on code. [1]
However if some 3rd party (not the PPMC) wants to use unreleased code and make
a “release” from it and put that somewhere but it needs to be clear that this
is not in anyway associated with the ASF and it
Hi,
I think this cannot be done as PMC or PPMC as it would be a "binary release"
which we cannot do with the ASF policy.
So I think another entity than the ASF / the PMC would need to put the App in
the store, and then you are also free with regards to releases.
Julian
Am 07.11.19, 14:34
Releasing an Apache project (artifact) requires community oversight.
The released artifact going to an FTP server, Maven central. or other
location is a separate concern.
The website describing the projects, its news, etc is less of an
artifact - more of a living document about the community.
At
I am OK with the normal release procedure if we have to.
But I'd like to know the boundary line here, why we don't need go though
the release procedure for Apache Project Website and why we need it for an
App built from Apache code. What's the difference here?
Best Regards,
YorkShen
申远
Jamie
The App should follow a release process - vetting, vote, signatures,
tag on source repository, etc.
The community should approve its release.
On Thu, Nov 7, 2019 at 9:29 AM 申远 wrote:
>
> Hi, there
>
> I'd like to know whether it's necessary to do an Apache Release if we
> publish an App to
Hi, there
I'd like to know whether it's necessary to do an Apache Release if we
publish an App to Apple Store using the code of Apache Weex [1]. I
understand there is no need to do an Apache Release if we publish projects
website, but what if we publish an App to iOS Apple Store?
[1]
12 matches
Mail list logo
