1) Cannot upgrade to Flex 4.x
As you stated somewhere and I've seen by myself migrating a big app to 4.8,
it's better to stay in flex3 for big existing apps and use flex4 for new
ones.
2) Can switch from Adobe Flex to Apache Flex
The only reason I can see right now (there are probably some others) for
people to not switching would be because the maven plugin migration wouldn't
be straightforward, it would imply to mavenize the SDK and use it with FM6
3) Need a bug fixed in 3.x SDK that cannot be practically resolved via
workaround or monkey-patch.
Until now at work, they've been able to survive with that.
What does it mean, IMO, big projects curently under Flex3 won't migrate to
Flex4 and can survive with the last Flex3.
-Fred
-----Message d'origine-----
From: Alex Harui
Sent: Tuesday, January 22, 2013 6:50 AM
To: dev@flex.apache.org
Subject: Re: Adobe BlazeDS and 3.X SDK branch donation
On 1/21/13 9:35 PM, "Justin Mclean" <jus...@classsoftware.com> wrote:
Hi,
Maybe with google trends
http://www.google.fr/trends/explore#q=flex%203%2C%20flex%204%2C%20as3&cmpt=q
It shows interest in flex 3 at around 90% of that of flex 4 each month
over
the last 12 months. You get slightly different results if you use "flex 3"
and
"flex 4" so I'd say it's only rough indication but better than guessing.
I'm not sure I understand. To me, the question isn't whether a lot of folks
are using Flex 3. The question is: are there bugs in Flex 3 that they want
fixed and if we fixed them they would/could use Apache Flex?
IOW, you have to meet all of the following criteria:
1) Cannot upgrade to Flex 4.x
2) Can switch from Adobe Flex to Apache Flex
3) Need a bug fixed in 3.x SDK that cannot be practically resolved via
workaround or monkey-patch.
Otherwise, we'll spend all of this time on release candidates for 3.x
without a significant payoff.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
