> However, (of course, you were expecting a however), I would like to see a patch that went out and did not cause additional issues.
I agree. My understanding is that there are some internal reviews occurring around the topic of patch quality. I can't really go into details, but it is an issue being talked about. > In a patch, do they release any new functionality, or simply work to fix issues? Under current policy, patches may only contain defect fixes. Sometimes, though, the distinction between a defect and an enhancement can get downright philosophical - so minor changes to, or an extension of, existing functionality may be present in a patch because it may be the only way to address what is advocated as a defect. -David J. Easter Sr. Product Manager, Service Management Business Unit BMC Software, Inc. The opinions, statements, and/or suggested courses of action expressed in this E-mail do not necessarily reflect those of BMC Software, Inc. My voluntary participation in this forum is not intended to convey a role as a spokesperson, liaison or public relations representative for BMC Software, Inc. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Opela, Gary L Contr OC-ALC/ITMA Sent: Friday, March 09, 2007 12:04 PM To: arslist@ARSLIST.ORG Subject: Re: Remedy Supported Products Hey David, I can understand what you're saying, and it makes sense. I mean, whenever they are at 6.3, they don't want to have to make a new patch for each version of 6.X.X.X.X.X that has ever been put out each time they release a new patch for the most recently supported code lines. However, (of course, you were expecting a however), I would like to see a patch that went out and did not cause additional issues. I'm not sure about 19, but in 18, 20, 21 there were numerous things broken. In 18, they broke the STRSTR function, in 20 they broke flashboards, and some other stuff, and in 21, now, I'm seeing more ppl report issues. In a patch, do they release any new functionality, or simply work to fix issues? IF they are only fixing issues, then the testing should not be that hard, should it? I mean, they are fixing a bug, so they know exactly what code was touched, and they should be able to see any other code that references that code and test it. I'm sorry for venting, it just seems that each new patch released is released almost exclusively to fix issues caused by the previous patch. Then they have to release a new patch to fix issues in that patch. I just want a stable patch so I can upgrade my server from 6.3 w/o any patches, but it hardly seems worth it since we are running stable, and each new patch breaks something that we use. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Easter, David Sent: Friday, March 09, 2007 10:41 AM To: arslist@ARSLIST.ORG Subject: Re: Remedy Supported Products As documented in the BMC Software Product Support Policy <http://www.bmc.com/info_center_support/overview/0,,19097_4736154_407375 96,00.html> on Support Central: "For the purpose of this support policy, a maintenance release is considered part of the main version/release. For example, 3.2.05 is supported as part of the 3.2 release." Once a maintenance release is generally available, further patches to the version prior to the maintenance release are not generated by BMC. Patches are generated for only the latest maintenance release code line. In the case of AR System 7.0x, future patches are only generated against the AR System 7.0.01 code line. Patches are still generated for 6.0.1 and 6.03 as per the policy. Support continues to take calls on 7.0.00 even with the release of 7.0.01. However it is correct that an issue or defect would likely need to be duplicated on the 7.0.01 code stream prior to escalation or submission for a patch. -David J. Easter Sr. Product Manager, Service Management Business Unit BMC Software, Inc. The opinions, statements, and/or suggested courses of action expressed in this E-mail do not necessarily reflect those of BMC Software, Inc. My voluntary participation in this forum is not intended to convey a role as a spokesperson, liaison or public relations representative for BMC Software, Inc. ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Ashcraft, Roy W. Sent: Friday, March 09, 2007 7:52 AM To: arslist@ARSLIST.ORG Subject: Remedy Supported Products ** I opened a ticket with BMC yesterday over a problem we are having with Mid-Tier 7.00.00 patch 2. The immediate response, which was expected, was to update to version 7.00.01 patch 1. I responded explaining the business reasons why that is not feasible for our situation. I very quickly received a response indicating that in order for them to escalate this to engineering we would have to upgrade to the latest patch. Is BMC only supported the current patch release now and forswearing all support for past products, no matter how recent? Roy Ashcraft Systems Analyst SAIC [EMAIL PROTECTED] (402) 293-5218 __20060125_______________________This posting was submitted with HTML in it___ ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
