Axton, But who is laughing? All I hear is weeping and gnashing of teeth.
I wish that the examples were not as credible or as plentiful. -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. On 3/8/07, Axton <[EMAIL PROTECTED]> wrote:
A few things: - The defect description is informative and to the point - The defect contains a workaround - No login required to see the defect or workaround - A search engine can find the information (aka Google, not an internal kb product) But it doesn't hold a flame next to these: SW00261638 After applying patch 20 we now get errors when starting the AR System. SW00261585 User tool Hangs in ITSM 7.0.1 SW00261470 Malloc (ARERR 300) error and server terminates with signal 11 SW00261458 Need to customize the fields on table. SW00261285 BMC Remedy Email Engine for 7.X - New features or functionality SW00261179 arimportcmd exhibits strange behavior SW00261817 arimportcmd exhibits strange behavior SW00260734 ERROR [300] Malloc failed on server I guess if I had to compare the two, the sun site/format would be the equivelant of a newpaper; and the BMC site would be the resulting slivers after sending that newspaper through a paper shredder. Now the icing on the cake will be if Sun documents this a 'fixed' in the errata/release notes when the next version is released. That is one thing I really don't like about the BMC patch process; I don't know what the hell is fixed until I go a retest everything I had a defect generated for since the last patch. Sorry, Friday humor is coming early this week. Axton Grams On 3/8/07, Warren Baltimore <[EMAIL PROTECTED]> wrote: > ** > Tis truly a thing of beauty... > > *sigh* > > > > On 3/8/07, Lucero, Michelle - IST contractor <[EMAIL PROTECTED]> > wrote: > > Hi, Y'all: > > > > Thank you to Lisa Kemes for sending us the link to the JDK related bug > > id. > > > http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6520670 > > > > Am I the only one who had their tongue hanging out in absolute envy > > after viewing that page? > > > > What we would do for a BMC Remedy Product Defects page like that. Could > > someone on the web design team at BMC please take a look at the page? > > (Yes, I have already submitted an enhancement request several months > > ago) > > > > Here are the things that I believe some of us have been asking for that > > are included on the page. > > > > 1. Detailed description of the bug (that 128 character cut-off summary > > has got to go) > > 2. Workaround (if available) > > 3. Evaluation of the bug including the description of the fix > > 4. Related bugs (with a link) > > 5. Not just a Status, but the actual Fix > > 6. The release in which the bug was/will be fixed! > > 7. Repeat of 6: "The release in which the bug was/will be Fixed!" > > > > Awestruck, > > Michelle > > > > DISCLAIMER: The comments above are my own and do not necessarily > > reflect the opinion of anyone at Mary Kay. > > > > > > -- > Warren R. Baltimore II > Remedy Developer > UW Medicine IT Services > School of Medicine > University of Washington > Box 358220 > 1325 Fourth Ave, Suite 2000 > Seattle, WA 98101 > > The opinions expressed in this e-mail are in no way those of the University > of Washington, or the State of Washington. They are my own.
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
