[
https://issues.apache.org/jira/browse/FLEX-33186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13451834#comment-13451834
]
Bertrand Delacretaz commented on FLEX-33186:
--------------------------------------------
I think we need a bit more context as to what signing these releases mean,
what's signed, what does the signature mean and what would happen if the
previous release manager is not available to pass the above credentials on.
If the signed .p12 file is included in a Flex release (source code - the ASF
doesn't release binaries), the Incubator PMC needs to be able to understand
what's going on to approve the release.
If this is only about convenience binaries, it's back to FLEX-33188 which IMO
shows the need for Flex to have an explanation page about binaries at
http://incubator.apache.org/flex/
> Procedure for signing InstallApacheFlex releases
> ------------------------------------------------
>
> Key: FLEX-33186
> URL: https://issues.apache.org/jira/browse/FLEX-33186
> Project: Apache Flex
> Issue Type: Task
> Components: InstallApacheFlex
> Reporter: Erik de Bruin
> Assignee: Erik de Bruin
> Priority: Blocker
> Fix For: InstalApacheFlex 1.0
>
>
> This task describes the procedure for signing the AIR packages used to build
> the Install Apache Flex application:
> 1) obtain the 'installapacheflex_self.p12' and 'installapacheflex.password'
> from the previous release manager
> 2) in 'build.properties' modify the KEYSTORE_DIR and CERT_PASSWORD_DIR
> variables to point to the directory containing the files from 1)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
