On 1/21/13 6 :09PM, "Justin Mclean" <jus...@classsoftware.com> wrote:
>Hi, > >> BlazeDS is being donated by a different team and I checked earlier in >> January and they said they have to clear up a legal issue. I don't >>have any >> details and haven't pressed them for it. >Mind asking what the legal issue is? > >> 3.x could be a lot of work and nobody has asked for it recently, >It just come up (indirectly) in a JIRA issue. >https://issues.apache.org/jira/browse/FLEX-14658 > >> There might be slightly easier ways to make it happen >Most of us are external and only have a general idea to is required for >this to happen inside Adobe at this point I think any "shortcuts" are >worth investigating. Personally I think it is a much better use of Alex's time to continue to work on the the JS stuff rather than divert him for potentially a couple of months getting 3.x ready for donation. If Flex was still at Adobe, since Flex 4 has been out for so long now I would guess Flex 3 would be at or near end-of-life. Even if it got to Apache it would mean that it would have to be periodically released which is just as big an undertaking as the current version. I think it would be a better use of our resources to concentrate on releasing Flex 4.next more often. Carol
