Mailing-List: contact users-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@flex.apache.org
Received-SPF: pass (athena.apache.org: domain of omuppi1@gmail.com designates
 209.85.214.181 as permitted sender)
MIME-Version: 1.0
Sender: omuppi1@gmail.com
From: OmPrakash Muppirala <bigosmallm@gmail.com>
Date: Mon, 30 Mar 2015 12:19:21 -0700
Message-ID: 
 <CACK5iZeGg+E4OV_1wfWa4Bce4RN_HMNJXZMb=WMvxzNwVeDmKA@mail.gmail.com>
Subject: [TDF Mobile] Releasing TDF Mobile
To: "dev@flex.apache.org" <dev@flex.apache.org>
Cc: "users@flex.apache.org" <users@flex.apache.org>
Content-Type: multipart/alternative; boundary=001a11c3234cc6ec620512865d23

--001a11c3234cc6ec620512865d23
Content-Type: text/plain; charset=UTF-8

Now that 4.14.1 is out of the way, I want to concentrate on releasing the
new Tour de Flex Mobile app on Google Play and Apple App stores.  I have
rebuilt the iOS and Android apps with the new skins and they do look pretty
good, good enough to release.  I plan to be the release manager for this
release.

Here are a few issues we need to consider:

1. The ASF does not currently have a way to let TLP projects to sign app
store binaries.  Instead of waiting on them, I plan to release it under my
own name, but with enough disclaimers to say that this is an [un]official
release of the Apache Flex project (only the binaries)  We will be
releasing the source under the normal release process, of course.
2.  Does anyone want to suggest a better name than Tour de Flex Mobile?  Or
is this good enough?

3.  Testing the binaries will be an interesting problem.

a.  For the Android platform, I can put up the .apk file on our Apache dist
folder and ask folks to download it from there.
b.  As far as the iOS app goes, I am planning on creating a TestFlight team
and send an invite to users@ and dev@ so that folks can sign up for testing
those apps.

Any suggestions or concerns, please feel free to raise them here.

Thanks,
Om

--001a11c3234cc6ec620512865d23--