You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by "Erik de Bruin (JIRA)" <ji...@apache.org> on 2012/08/31 16:08:07 UTC

[jira] [Created] (FLEX-33186) Procedure for signing InstallApacheFlex releases

Erik de Bruin created FLEX-33186:
------------------------------------

             Summary: Procedure for signing InstallApacheFlex releases
                 Key: FLEX-33186
                 URL: https://issues.apache.org/jira/browse/FLEX-33186
             Project: Apache Flex
          Issue Type: Task
          Components: Installer
            Reporter: Erik de Bruin
            Assignee: Bertrand Delacretaz
            Priority: Blocker


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

[jira] [Commented] (FLEX-33186) Procedure for signing InstallApacheFlex releases

Posted by "Erik de Bruin (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FLEX-33186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13451839#comment-13451839 ] 

Erik de Bruin commented on FLEX-33186:
--------------------------------------

Sorry, my bad. Re-reading the title of this issue, I see how it might cause confusion. This is not about the Apache 'signing', but about the Flex 'signing'. So, in that sense it does only concern the Installer convenience binaries. 

I'm updating https://issues.apache.org/jira/browse/FLEX-33188 as per your suggestion.
                
> 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

[jira] [Commented] (FLEX-33186) Procedure for signing InstallApacheFlex releases

Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
    [ 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

[jira] [Resolved] (FLEX-33186) Procedure for signing InstallApacheFlex releases

Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FLEX-33186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bertrand Delacretaz resolved FLEX-33186.
----------------------------------------

    Resolution: Won't Fix

According to Erik, this signing is only about convenience binaries and has no impact on the InstallApacheFlex source code release. 

The current signing instructions for the convenience binaries are found at http://svn.apache.org/repos/asf/incubator/flex/utilities/trunk/installer/RELEASE_GUIDE

Marking this won't fix for now, nothing needed as far as the source release is concerned.
                
> 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

[jira] [Updated] (FLEX-33186) Procedure for signing InstallApacheFlex releases

Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FLEX-33186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bertrand Delacretaz updated FLEX-33186:
---------------------------------------

    Assignee: Erik de Bruin  (was: Bertrand Delacretaz)
    
> Procedure for signing InstallApacheFlex releases
> ------------------------------------------------
>
>                 Key: FLEX-33186
>                 URL: https://issues.apache.org/jira/browse/FLEX-33186
>             Project: Apache Flex
>          Issue Type: Task
>          Components: Installer
>            Reporter: Erik de Bruin
>            Assignee: Erik de Bruin
>            Priority: Blocker
>
> 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