Hi,
I think folks over interpreted Matt's email. Please
cut him (and us) some slack.
We will do patch releases. We are staffed to do patch
releases. We do need to aggregate up bugs and do them in a thoughtfull fashion
because any fix can break something else. We base what we fix and when we do
such releases on customer feedback--if we need to we might put out one
immediately after a new release or we might go 6 months. It depends on the
issues our customers are facing. But we are indeed staffed and have
resources to be able to do patches and you will see patches for Flex. I
don't have a specific date for you because we haven't finalized everything that
will be in it yet. It doesn't make sense to do a lot of tiny patches
because the overhead of regression testing a release of the software is enormous
so we will do fewer, medium sized patches instead. This is true for
the Player team, the Compiler team, the SDK team, the tool team and the server
team. Each of these teams might do patches on a different cycle of course
depending on need. In general, we are most conservative about changes to
the Player because the risk of "injections" is highest here with software that
quickly goes out to 100s of millions of people. Jack, you suggest we should have
a patch in the first "6-9 months after a release". While we don't have a
final schedule in place, that is a reasonable timeframe from my perspective too.
Please don't jump to conclusions (and jump on Matt)--we
don't need to rethink our strategy here, on the contrary, we seem to be in
agreement.
-David
SVP, Adobe From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Jack Caldwell Sent: Wednesday, August 30, 2006 3:18 PM To: flexcoders@yahoogroups.com Subject: RE: [flexcoders] Flex 2 patch timeline Matt or anyone else at Adobe.
I agree that the quality of Flex Builder 2 is good . . . .
very good . . . . however . . . .
I know nothing will probably change since Adobe is the big
software company, and I am only a single
customer(Flex Builder 2 w/charting), but this position
disturbs me.
It reminds me of the construction industry when a
contractor builds or remodels my house. I have paid
for the work and I find problems but the contractor is off
working on another house and doesn't have the
time or resources to fix the problems in a timely
manner.
To be honest, I could care less about a Mac
version . . . . AND I know those wanting a Mac
version could
care less about a
Windows version. So please no bashing from the Mac
side.
It appears that Adobe has not allocated enough resources to
the development team where they can have
2 groups. As I recall, it was said on this forum,
soon after Flex 2 was released the development team
received new Macs to begin work on a Mac
version.
Why did Adobe not already have a plan and resources in
place. This type of thing is done all the time.
While I do not expect that every single bug be issued a
"release patch", it would be very nice and
customer
friendly to have a bug fix release plan in place and
implement that plan. Especially in the first 6-9 months
of
a major release.
I haven't encountered a bug that I know of. But when
I do, I will probably have spent many hours
or days
thinking I did not write the code right only to find
out later is was a bug. Wasted time . . . . money.
I have said this before, but I would not have a single
customer if I told them I could not fix the software they
purchased because I was working on another
version.
I really do not understand why large software companies
employ this type of bug fix and update plan.
I only hope Adobe will rethink their strategy and
implementation of releasing bug fixes.
My .02 or actually $ 749 for Flex Builder 2
w/charting.
Thanks,
Jack From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Matt Chotin Sent: Wednesday, August 30, 2006 10:21 AM To: flexcoders@yahoogroups.com Subject: RE: [flexcoders] Flex 2 patch timeline
Are there specific bugs
you’re looking to be addressed? Based on direct feedback as well as
observation from the various public forums we’ve been pretty pleased with the
quality of the release so we’ve held off on rushing out an updater while we work
on things like the Mac release of Flex Builder. Doesn’t mean we’re not
fixing bugs, but we’ve decided to try to address more issues in a longer cycle
rather than fewer issues quickly. If there’s a specific
issue that is blocking your work use the wish form (http://www.adobe. Matt From:
Before I
dive headlong into my first full Flex 2 project, can anybody -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
SPONSORED LINKS
YAHOO! GROUPS LINKS
__,_._,___ |
- Re: [flexcoders] Flex 2 patch timeline Martin Wood
- Re: [flexcoders] Flex 2 patch timeline Impudent1
- RE: [flexcoders] Flex 2 patch timeline Louie Penaflor
- Re: [flexcoders] Flex 2 patch timeline Adam Reynolds
- Re: [flexcoders] Flex 2 patch timeline Mike Nimer
- Re: [flexcoders] Flex 2 patch timeline hank williams
- RE: [flexcoders] Flex 2 patch timeline David Mendels