flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christofer Dutz <christofer.d...@c-ware.de>
Subject AW: AW: AW: [DISCUSS] Release Flex-Tool-API?
Date Wed, 12 Nov 2014 22:41:19 GMT
No harm at all.

Its a staging repo ... that's a really cool concept. You can login to Nexus and inspect its
content. When initiating a RC I would post the url to that staging repo and as soon as the
vote passes I switch the repo to "release" and the artifacts are automatically published.
If the RC is denied, I simply delete the repo and all is gone without leaving a trace.


Von: Alex Harui <aharui@adobe.com>
Gesendet: Mittwoch, 12. November 2014 23:28
An: dev@flex.apache.org
Betreff: Re: AW: AW: [DISCUSS] Release Flex-Tool-API?

I’ve run Maven successfully.  I’m now examining the source-release.zip.

Is there any harm in posting builds to the staging repo?  If not, I guess
you can do it without waiting.  Is there an easy way to have the build.a.o
CI server run builds that create md5 checksum files instead of ASC files?
Then more folks are likely to look at it.


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