I must strongly disagree. If you can't even create a new project in FB with the latest SDK release, we are going to have a lot of negative karma send our way. Not to mention the consequences of having less experienced and new users try to run an EMPTY application and fail - and then have to debug it, not having a clue.
That is not the way we should do stuff. The vote passed when the current two 'show stopper' issues were not known. The fact that the letter of the Apache Way was followed doesn't mean that we are not now going very much against the spirit of it. I want to release. I agree that a release is long over due. I think we should, in the future, release earlier and more often. But I also think that quality is key. If we start releasing code that doesn't even compile an empty project template in the most used IDE... I don't know. EdB On Fri, Jul 26, 2013 at 4:00 PM, Justin Mclean <jus...@classsoftware.com> wrote: > Hi, > > And I really have to say this is not exactly a show stopper or critical > issue. This need to put into perspective as there a very simple work around > eg just fix/edit the code yourself. It's an inconvenience at most, nothing to > do with the SDK itself, and not everyone uses Flash Builder. I'm not sure we > can ever fix the issue, without revering the version number to 4.9.2 or > something silly. We should be asking Adobe to fix it not using it as yet > another excuse to not make a release. > > The vote for the release candidates has passed and was successful. As the > release manager I'm willing to give a couple of days grace to see if any > solutions for any "outstanding" issues can be found and consider creating a > new release candidate to put up for another vote, but beyond they can go into > the next point release, anything more than that is really going against > Apache policy. > > Thanks, > Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
