flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <aha...@adobe.com>
Subject Re: AW: AW: [DISCUSS] Release Flex-Tool-API?
Date Wed, 12 Nov 2014 22:43:06 GMT
OK, finished looking.

Everything looks ok, except I think we need md5 and .asc files for the
source-release.zip file and md5 for the other jars would be helpful.

Some minor/optional stuff:
1) Could/should the package name start with “apache-“?  All of our other
releases do.
2) Our other packages unzip and README is in the root.  In the
flex-tool-api package, the unzip results in a folder with all of the files
in it.

Otherwise, I would be good to go.

On 11/12/14, 2:16 PM, "Christofer Dutz" <christofer.dutz@c-ware.de> wrote:

>During the actual release this all happens automatically.
>As I said ... you should be able to see the results by simply running the
>maven build locally. As soon as I intend on creating an RC all would be
>staged in the staging repository and you could have a look there. Do you
>want me to prepare one?
>Von: Alex Harui <aharui@adobe.com>
>Gesendet: Mittwoch, 12. November 2014 23:11
>An: dev@flex.apache.org
>Betreff: Re: AW: [DISCUSS] Release Flex-Tool-API?
>On 11/12/14, 2:05 PM, "Christofer Dutz" <christofer.dutz@c-ware.de> wrote:
>>I just remember what the problem was that as part of a release each file
>>of a release is signed and as soon as I turn on the apache-release
>>profile it expects credentials for this signing process.
>So is there a way to set an alternative “goal” (is that the right word
>that is equivalent to an Ant target?) that will be more like “build”
>instead of “install” and doesn’t try the signing.  Also, it would be great
>to have MD5 files generated for each download. Is that hard to do?

View raw message