On 6/29/14 8:27 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote:
>> >> the community. We need to make this process simpler and faster. We're >> going to have six releases once we start shipping BlazeDS. >> > >What are the pros and cons of having one monolithic "Apache Flex All" >release 4 times a year. All subprojects depend on one another anyway, why >not aim for including all of them in a predictable, albeit humongous, >release? For me, the con is, for something like FlexJS, we hope to see its capabilities change more quickly than every 3 months. I'd hate to lose early adopters because it takes too long for them to get satisfaction on something that's missing. We are not allowed to use nightly builds as a rapid release mechanism. Also, when we do miss something in a release and want to cut a 4.12.1 sort of thing, we don't want to wait 3 months for that. And if we ever have a security hole to patch, we need to get that out quickly as well. The release process should be simple and fast. There are discussions on other Apache lists on how to make releasing simpler and faster. In theory it is supposed to encourage more participation as well as potential committers and patchers see their work released sooner. -Alex
