In one of the past releases, we messed up the core.swc build script and didn't catch it until after release. It seems like we should make sure this is in fact a bug in FB and not some other thing we messed up that is under our control before releasing. So somebody should try a build with a 4.9.9 version number just to be sure. I'll see if I can get another computer going on it.
Clearly we all have different opinions on quality, but a problem in the first thing a newbie tries with FB New Project wouldn't make us look very good and attract more people, especially if we can find a way around it, and shipping with known regressions doesn't help either. Very recently, OpenOffice also voted to release and was in the process of copying their bits to dist when they stopped because an issue was found. Just because you have the votes doesn't mean you have to deploy those bits. -Alex On 7/26/13 7:00 AM, "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
