My impression is that somewhere in the recent past BMC eliminated too many experienced QA "resources," and now they are paying for it with longer than desirable delays in getting product releases that have completed beta, new patches, or maintenance releases cleared for general access. It is showing up in every BMC Remedy product family that I am concerned about. In addition to longer lag times (from end of beta to general access), we are also seeing more bugs slip though the QA process that _does_ take place, probably because it is under greater "pressure" from multiple product managers. I guess it can happen anywhere, after seeing the reports yesterday of Toyota automotive quality falling...
Christopher Strauss, Ph.D. Remedy Database Administrator University of North Texas Computing Center http://itsm.unt.edu/ _____ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Rick Cook Sent: Friday, October 19, 2007 3:17 PM To: arslist@ARSLIST.ORG Subject: Re: First patch for ARS 7.1 ** Excellent post, Michelle. With all of the "What the <insert expletive>?" problems in recent patches and releases, one has to wonder what passes for QA at BMC these days. What really blows my mind is that they seem to be getting worse, not better. Had they tested the Mid-Tier AT ALL, they would have caught this. Rick _____ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Michelle L Sent: Friday, October 19, 2007 8:34 AM To: arslist@ARSLIST.ORG Subject: Re: First patch for ARS 7.1 ** Good Day To you all (and Mr. Easter) Mid-Tier 7.1.00 (Windows 2003, IIS 6.x, Apache Tomcat 6.0.13, Java Version 1.6.0_01) ARS 6.3 Patch 20 (Windows 2003, SQL Server 2000) I.E. 6 browsers Thank you for providing the defect id, Joe. We are also receiving the message below after upgrading from Mid-Tier 7.0.01 to 7.1.00 when displaying any entry in any form. "Cannot specify a diary field, a character field with unlimited length or maximum length over 255 bytes, or Status-History as a field in a get list description: <field name> (ARERR 241)" The Mid-Tier error message above is definitely a SHOWSTOPPER and will have no choice but to roll back to 7.0.01. Mid-November seems like a long time to wait on something like this. I'm finding it hard to believe that they actually released this Mid-Tier version to the public. Is everyone reporting this to BMC? I guess I will take Carey's advice and hope that there is a one-off private patch to address this. Has anyone received a patch or workaround to address this error? Thanks, Michelle Joseph Kubasek <[EMAIL PROTECTED]> Sent by: "Action Request System discussion list(ARSList)" <arslist@ARSLIST.ORG> 10/18/2007 07:46 AM Please respond to arslist@ARSLIST.ORG To arslist@ARSLIST.ORG cc Subject Re: First patch for ARS 7.1 ** We were given defect id SW00277855. Joe Kubasek On 10/17/07, Axton <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > wrote: Do you have a defect id for this? Axton Grams On 10/17/07, Joseph Kubasek < [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > wrote: > ** An active link retrieving a value from an unlimited length field > generates an arerror 241 in the mid-tier, but not in the WUT. > > Joe Kubasek > > On 10/17/07, LJ LongWing (Head) <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > wrote: > > Carey, > > are there issues with 7.1 Mid-Tier against a 6.3 Patch 21 Server?...I > > haven't read about that yet...if so what are the issues? > > > > -----Original Message----- > > > ________________________________________________________________________ _______ > > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org <http://www.arslist.org/> ARSlist:"Where > the Answers Are" > > > > __20060125_______________________This posting was > submitted with HTML in it___ ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org <http://www.arslist.org/> ARSlist:"Where the Answers Are" __20060125_______________________This posting was submitted with HTML in it___ ====================================================================== Confidentiality Notice: The information contained in and transmitted with this communication is strictly confidential, is intended only for the use of the intended recipient, and is the property of Countrywide Financial Corporation or its affiliates and subsidiaries. If you are not the intended recipient, you are hereby notified that any use of the information contained in or transmitted with the communication or dissemination, distribution, or copying of this communication is strictly prohibited by law. If you have received this communication in error, please immediately return this communication to the sender and delete the original message and any copy of it in your possession. ====================================================================== __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
