On Thu, Oct 24, 2013 at 3:37 PM, Justin Mclean <jus...@classsoftware.com>wrote:

> Hi,
>
> There's nothing stopping us from releasing 2.7 as it, waiting for any
> feedback, and then voting on and releasing a 2.7.1 with that fix (and
> possibly others) in a few weeks. Not all releases need to have major
> changes. Remember anyone can make a release candidate and it only needs 3
> +1 votes.
>
>
Agreed.  My only concern is that if we include this fix in this release, we
need a new 72 hour voting period - which would delay our announcement of
Flex 4.11.0.
My vote is for a minor release a few days after we announce the release,
etc.

Thanks,
Om


> Thanks,
> Justin

Reply via email to