> From: El Koro [mailto:k...@noos.fr] > Sent: 23 January 2012 12:24 > > David, I think there is a misunderstanding here. > As it has been discussed previously, the goal of the first release (4.7 or > 4.8 or 4.2012 or ... ) would be like a practice release for the project, > not a "look world, here is the first Apache Flex release" > So the PR of this release would be minimal, and would mainly consist of > "don't use this release for production work but only if you want to help the > Apache Flex project to test what is already broke from the transfert to Apache".
Surely the original plan was based on the assumption that Adobe would donate everything needed for Apache to recreate the Flex 4.6 release and that plan was for an Apache Flex 4.6 release to be made, which would be both a test of the Apache release process and something for the more experimental members of the community to try out for us? That was my understanding of the original plan. We now know this won't be possible as some aspects of the SDK will not now be released to Apache, so the original plan is defunct and a new plan is needed. If we must do a broken release to test the release process, the podling team mustn't assume they can keep it quiet. Instead it should be clearly explained why it's a broken release and what is going to be done about it. So before making the release, there should be in place a proper plan of how a real release will be made and when it likely will occur. David.
