oracle dev and policies towards fixing bugs
- From: Charles Schultz <sacrophyte@xxxxxxxxx>
- To: ORACLE-L <oracle-l@xxxxxxxxxxxxx>
- Date: Sun, 21 Apr 2013 09:27:33 -0500
Good day, all,
I am trying to figure out if my expectations are way too high, or if the
state of development in general has simply gone astray.
While exploring the Provisioning Procedures in 11g Enterprise Manager, I
found a simple typo on one of the screens. Since it is not often that I
find typos in a world-class production product (*tongue in cheek*), I filed
an SR. This morning, I was asked if I can upgrade my 11g Enterprise Manager
to 12c because, apparently, the typo is not in that version.
I was utterly flabbergasted!
On the one hand, I am flummoxed as to why Oracle thinks that upgrading is
the ultimate panacea to all bugs. Really? They expect me to upgrade to 12c
just because of a stupid typo?!?
On the other hand, there seems to be no desire or intention to fix bugs in
the currently supported versions. This is a behavior I have seen prevalent
in the database product as well. Oh for the days when a product was
actually stabilized and supported for "long time", instead of the
never-ending upgrade hell.
Ironically, the title of my SR is "How hard is it to fix typos in EM?" I
guess the answer is "VERY VERY HARD!!"
Let me know if my glass is depressingly half-empty. :) Sometimes a little
perspective goes a long way.
For a dose of "positiveness", I will readily acknowledge that I know many
Devs are working hard to create (and fix) some really awesome things. I do
not mean to imply they are "evil" at all. In fact, perhaps my angst is
better directed at those who make the policies and decisions.
--
Charles Schultz
--
//www.freelists.org/webpage/oracle-l
Other related posts:
