Flex Bugs Déjà Vu; Memories of Java's Bug Parade
Will the Flex team will be more responsive than their Java colleagues?
Feb. 7, 2008 06:45 AM
Flex is an open source product, which means that you can fix the bugs on your own. This may fork out the product, but it's another story altogether.
On the other hand, developers can vote for the bugs so the Flex team can fix them.
The Flex bug database is available at this Web site.
But I have a strong feeling that I’m about to enter the same waters again… When the Flex open source announcement was made, one engineer from Flex team has asked me if I had any suggestions in this regard. I told him about the bitter taste that Java’s bug parade has left in my mouse. People were allowed to vote for bugs, but some of the top voted bugs were sitting in the database for 7(!) years. What are the guarantees that it won’t happen again with Flex?
The Flex Bugs FAQ has the following:
"Does my bug report immediately go to the development team?
No, A Bug reports only get reviewed by the development team once it receives support (votes) from others in the community."
I do not like this answer. Been there. Done that. Do not want to do it again. I remain cautiously optimistic that Flex team will be more responsive than their Java colleagues. Time will tell.