Jeff:
I fully understood what Matt was saying. That's just
it . . . . it is not a top priority.
The issue is that Adobe is fixing the bugs, but not
releasing them.
We as developers have to try to figure it out then call
support, etc. That could take
hours or days of my time. It's wasted time and
money.
I am like you, I don't have a large support staff
either.
My position, for over 27 years, has always been . . .
. find a bug send ALL customers
a fix ASAP. Not waiting for a customer to
call me.
Again, in the first 6-9 months after a major release, I
think there should be a different
release plan in place.
Thanks,
Jack
Jack-
I think you misunderstand what Matt said. He didn't say
they aren't working on fixes, he said it hasnt been their top priority. If
you have an issue, he recommended you contact their support team.
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.
Again, its not an issue of not being able to fix bugs,
many companies have a process in place to allow for handling their customers
needs. In the adobe case, if something isnt working as you would expect,
there is the support channel. drop them an email or give them a call, and
they can help solve the issue you are having. They are the ones who are
best able to determine if you are doing something wrong, or if its a bug in the
code which needs to be fixed. I wouldnt be at all surprised if their were
a number of minor patches available through the support channels. I dont
know that there are, but if I were them, and I had a few fixes to specific bugs
that havent been reported by the community at large, but instead by a few
customers, I would probably give the fixes as needed, rather than make a whole
new big push. Then again, thats just my thought process. Sadly, I
dont have a whole support team working for me, so i need to deal with bugs in my
code as they crop up.
At 03:18 PM 8/30/2006, Jack Caldwell
wrote:
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: [EMAIL PROTECTED]ups.com [
mailto:flexcoders@yahoogroups.com] On Behalf Of Matt
Chotin Sent: Wednesday, August 30, 2006 10:21 AM To:
[EMAIL PROTECTED]ups.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.com/go/wish) to
submit it and indicate so. There are also plenty of official support
options available to help as well (
http://www.adobe.com/support/programs/flex/?tab:plans=1)
Matt
From:
[EMAIL PROTECTED]ups.com [ mailto:flexcoders@yahoogroups.com] On
Behalf Of Adam Reynolds Sent: Wednesday, August 30, 2006 2:44
AM To: [EMAIL PROTECTED]ups.com Subject:
[flexcoders] Flex 2 patch timeline
Before I dive headlong into my first full Flex 2
project, can anybody from Adobe give me an update as to when/if there will
be a patch for Flex 2?
Adam
__._,_.___
--
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
__,_._,___
|