Flex 3.x SDK?

[Keith Sutton <ke...@spoon.as>]

Alex,

It is great to get Flex 4.6 into community hands and to look into the 
future of Flex but many sites, ISVs and enterprises are hugely invested 
in 3.x . Although the 3.x SDK is 'open code' it would be good to see it 
in the hands of Apache where it could be actively supported by the 
community as well.

Adobe personages before, during and after the Flex Summit stated the 3.x 
SDK could/would be donated. Given the current workload and progress on 
4.6 code migration what would be a feasible/reasonable timeline for 3.x ?

Re: Flex 3.x SDK?

[James Ong <ya...@gmail.com>]

Not to be confuse why 3.x is consider legacy codebase, Flex 3 are
still important for users with legacy Flash player 9 but that is a
minor issue since everything will still be done in actionscript.
Compare to Microsoft convince .Net (although little slower) is richer
in functionality than C++, I can see, most companies has already
invested in C++.


On Thu, Jan 19, 2012 at 8:07 AM, Andrew Morgan <am...@gmail.com> wrote:
> I will add to the chorus that 3.x is very important.  Enterprises are
> already at a crossroads with what to do with their large investment Flex,
> and much of that is on the 3.x codebase.
>
> Migrating to 4 is an expensive proposition with unclear benefits, and given
> the uncertainty around Flex/Flash, I can't see how to
> convince steak-holders to move to 4 right now.
>
> Not migrating Flex 3.x to apache would be a really bad blow to Flex.  Many
> of the existing 3.x projects will move to other technologies if this
> happens.
>
>
>
>
>
> On Wed, Jan 18, 2012 at 1:18 PM, Raju Bitter <ra...@googlemail.com>wrote:
>
>> Sounds like - from an enterprise perspective - the 3.x SDK is more
>> important to the community. And those are probably some of the largest
>> Flex applications in use. Does Adobe have any numbers on how many
>> people are using 3.x vs 4.x?
>>

Re: Flex 3.x SDK?

[Andrew Morgan <am...@gmail.com>]

I will add to the chorus that 3.x is very important.  Enterprises are
already at a crossroads with what to do with their large investment Flex,
and much of that is on the 3.x codebase.

Migrating to 4 is an expensive proposition with unclear benefits, and given
the uncertainty around Flex/Flash, I can't see how to
convince steak-holders to move to 4 right now.

Not migrating Flex 3.x to apache would be a really bad blow to Flex.  Many
of the existing 3.x projects will move to other technologies if this
happens.





On Wed, Jan 18, 2012 at 1:18 PM, Raju Bitter <ra...@googlemail.com>wrote:

> Sounds like - from an enterprise perspective - the 3.x SDK is more
> important to the community. And those are probably some of the largest
> Flex applications in use. Does Adobe have any numbers on how many
> people are using 3.x vs 4.x?
>

Re: Flex 3.x SDK?

[Raju Bitter <ra...@googlemail.com>]

Sounds like - from an enterprise perspective - the 3.x SDK is more
important to the community. And those are probably some of the largest
Flex applications in use. Does Adobe have any numbers on how many
people are using 3.x vs 4.x?

Re: Flex 3.x SDK?

[Deirdre Holub <de...@rrd.com>]

I want to stress this point. If the 3.x SDK does not make it in to Apache
Flex, then all current code written in 3.x immediately becomes legacy code
with no obvious path forward. Once that happens, it becomes much harder to
argue in favor of giving Apache Flex a chance instead of just switching now
to html/js/etc, because the risks of rewriting an app in one or the other
is perceived to be equal.

On Wed, Jan 18, 2012 at 9:53 AM, Quentin Le Hénaff <le...@gmail.com> wrote:

> I totally agree, I do not understand why it would not be ; still some
> innovating products are based on Flex 3 and not Flex 4 as the migration had
> some drawbacks and is expensive.
>
> Many projects have their own Flex base code, I've re-done many base
> components  ; this is very important to share them all or so much work will
> be wasted.
>
> On Wed, Jan 18, 2012 at 6:45 PM, Keith Sutton <ke...@spoon.as> wrote:
>
> > On 1/18/2012 8:21 AM, Doug McCune wrote:
> >
> >> Oh wow, I had no idea the 3.X branch might never make it into the Apache
> >> project. I think that's a really bad idea. As others have mentioned,
> lots
> >> of large enterprises use 3.X (the app I work on included). I always just
> >> assumed that 3.6 would make it into Apache at the same time the latest
> 4.x
> >> branch would too.
> >>
> >>  It was requested repeatedly at the Summit and Deepa and Danny
> definitely
> > said yes it would be. From a enterprise customer perspective it seems
> > unavoidable.
> >
>

Re: Flex 3.x SDK?

[Quentin Le Hénaff <le...@gmail.com>]

I totally agree, I do not understand why it would not be ; still some
innovating products are based on Flex 3 and not Flex 4 as the migration had
some drawbacks and is expensive.

Many projects have their own Flex base code, I've re-done many base
components  ; this is very important to share them all or so much work will
be wasted.

On Wed, Jan 18, 2012 at 6:45 PM, Keith Sutton <ke...@spoon.as> wrote:

> On 1/18/2012 8:21 AM, Doug McCune wrote:
>
>> Oh wow, I had no idea the 3.X branch might never make it into the Apache
>> project. I think that's a really bad idea. As others have mentioned, lots
>> of large enterprises use 3.X (the app I work on included). I always just
>> assumed that 3.6 would make it into Apache at the same time the latest 4.x
>> branch would too.
>>
>>  It was requested repeatedly at the Summit and Deepa and Danny definitely
> said yes it would be. From a enterprise customer perspective it seems
> unavoidable.
>

Re: Flex 3.x SDK?

[Keith Sutton <ke...@spoon.as>]

On 1/18/2012 8:21 AM, Doug McCune wrote:
> Oh wow, I had no idea the 3.X branch might never make it into the Apache
> project. I think that's a really bad idea. As others have mentioned, lots
> of large enterprises use 3.X (the app I work on included). I always just
> assumed that 3.6 would make it into Apache at the same time the latest 4.x
> branch would too.
>
It was requested repeatedly at the Summit and Deepa and Danny definitely 
said yes it would be. From a enterprise customer perspective it seems 
unavoidable.

Re: Flex 3.x SDK?

[Doug McCune <do...@dougmccune.com>]

Oh wow, I had no idea the 3.X branch might never make it into the Apache
project. I think that's a really bad idea. As others have mentioned, lots
of large enterprises use 3.X (the app I work on included). I always just
assumed that 3.6 would make it into Apache at the same time the latest 4.x
branch would too.

Re: Flex 3.x SDK?

[Jonathan Campos <jo...@gmail.com>]

On Wed, Jan 18, 2012 at 8:23 AM, Michael A. Labriola <
labriola@digitalprimates.net> wrote:

> Most enterprises are still on 3.x and I already have a number of bug fixes
> I want to apply.


Second that. I was hoping that the Flex source movement included the 3.x
branch right from the start. Anything we can do to move that faster I am up
for.

-- 
Jonathan Campos

RE: Flex 3.x SDK?

["Michael A. Labriola" <la...@digitalprimates.net>]

Alex,

If there is anything I can do to help, let me know.

Most enterprises are still on 3.x and I already have a number of bug fixes I want to apply.

Mike

-----Original Message-----
From: Alex Harui [mailto:aharui@adobe.com]
Sent: Wednesday, January 18, 2012 1:05 AM
To: flex-dev@incubator.apache.org
Subject: Re: Flex 3.x SDK?




On 1/17/12 6:55 PM, "Keith Sutton" <ke...@spoon.as> wrote:

> Alex,
> Adobe personages before, during and after the Flex Summit stated the
> 3.x SDK could/would be donated. Given the current workload and
> progress on
> 4.6 code migration what would be a feasible/reasonable timeline for 3.x ?
Good question.  Right now, I think there will be a window of time in April and May when I was going to make contributions to 4.6. (After that, I'm hoping to start prepare Falcon for Apache).  If we hear enough requests for 3.x vs 4.6 work, I would consider trying to get 3.x donated during that time.  It is pretty much up to the community to decide.

--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Notice: This transmission is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged or confidential. Any dissemination, distribution or copying of this transmission by anyone other than the intended recipient is strictly prohibited. If you have received this transmission in error, please notify the sender immediately by e-mail or telephone and delete the original transmission. Thank you.

Re: Flex 3.x SDK?

[Alex Harui <ah...@adobe.com>]

On 1/17/12 6:55 PM, "Keith Sutton" <ke...@spoon.as> wrote:

> Alex,
> Adobe personages before, during and after the Flex Summit stated the 3.x
> SDK could/would be donated. Given the current workload and progress on
> 4.6 code migration what would be a feasible/reasonable timeline for 3.x ?
Good question.  Right now, I think there will be a window of time in April
and May when I was going to make contributions to 4.6. (After that, I'm
hoping to start prepare Falcon for Apache).  If we hear enough requests for
3.x vs 4.6 work, I would consider trying to get 3.x donated during that
time.  It is pretty much up to the community to decide.

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui