flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Frédéric THOMAS <webdoubl...@hotmail.com>
Subject RE: Nighly builds and releases
Date Thu, 05 Sep 2013 01:52:00 GMT
> That could and has caused errors, one of the 4.10.0 RC had to be redone
because of this exact issue.

What was the problem exactly ?

> Making and testing a RC is a lot of effort and I rather make that easier
rather than harder or ending up with an RC missing a build number.

Sure it is a lot of effort and coffees I guess but maybe because I can't see
why attributing a build number only at release time would make it harder and
how it can be missed if it is done that way, I can't see the relation with
the fact it makes it harder.

Thanks,
-Fred

-----Message d'origine-----
De : Justin Mclean [mailto:justin@classsoftware.com] 
Envoyé : jeudi 5 septembre 2013 03:15
À : dev@flex.apache.org
Objet : Re: Nighly builds and releases

Hi,

> I haven't look at how and when the date is added yet but can't we 
> decide to add this date from the release target only as the release 
> target is supposed to be run on a release branch only ?

That could and has caused errors, one of the 4.10.0 RC had to be redone
because of this exact issue.

Making and testing a RC is a lot of effort and I rather make that easier
rather than harder or ending up with an RC missing a build number.

Take a  look at building the release here:
https://cwiki.apache.org/confluence/display/FLEX/Release+Guide+for+the+SDK

"Other ant targets you may want to become familiar with are source-release,
source-package, binary-release, binary-package and rat-check. These are
useful if you modify the files in the kit and you want to short circuit some
of the build process to test your changes."

Thanks,
Justin

Mime
View raw message