On 8/15/12 7 :30PM, "Om" <bigosma...@gmail.com> wrote:

>So how does this sound:
>
>
>   - We don't keep the .p12 file in the repo.
>   - We ask developers who want to work with the source code to generate a
>   .p12 file (using FB or similar tools) for themselves
>   - They should not check it in (add *.p12 to svn ignore?)
>   - The release managers would create a .p12 certificate(and a pass code)
>   as the official one.  This will not be checked in.
>   - A release build is created using the source code + .p12 + pass code
>   combination.
>   - Whoever is the current release manager gets the .p12 certificate +
>   pass code from the previous release manager to make a release build.
>   - It is up to the release mangers to keep the .p12 and pass code
>   secure.
>
>Note:  We may need two release managers for every release - one for
>windows
>and one for Mac since air apps for a platform need to built on the same
>platform.

This is not the topic of this thread but I think the release manager has
to be able to produce both packages.

Carol

Reply via email to