And, in addition to that, a more infrequent use of "one-off" exceptions to the intent of the numbering system. For instance, wasn't one of the 7.0.2 installs the same as the 7.0.1, only with a better installer? That seems a bit misleading, since no functionality was added. Same thing happened with one of the CMDB patches, I think. Just my opinion, but in those instances, it would be good to do what I suggested Support do years ago - track who's downloaded what, and if a problem with the installer or some non-application portion of it occurs, proactively contact the customers about replacing the obsolete server/patch - with one using the same version #. If that won't work, at least pull the bad server version from the drop-downs on the download site. Rick _____
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of strauss Sent: Monday, January 08, 2007 7:29 AM To: arslist@ARSLIST.ORG Subject: Re: AR System version numbers ** What we _REALLY_ need is a crosswalk between the version numbers and the patches... i.e., if you have installed ITSM application x 7.02 then is that equal to application x 7.01 Patch 003 ??? It appears that the incremental application releases are only useful for new installs, especially since you are tied to patch installs _only_ once you have invested any time whatsoever in configuring the application(s). Since there is no way to snapshot your configuration data and restore it to a newer application version installation, the only thing you can do after configuring is patch. We will need a clear understanding of what application version level we are up to after each patch, since there seems to be a disconnect between current application releases and patch releases. Christopher Strauss, Ph.D. Remedy Database Administrator University of North Texas Computing Center http://remedy.unt.edu/helpdesk/ _____ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Easter, David Sent: Monday, December 18, 2006 10:55 AM To: arslist@ARSLIST.ORG Subject: AR System version numbers ** Hi All, I've noticed a distinct difference in the way some folks on the list refer to the version number of AR System versus the way BMC refers to the versions. I thought it best to quickly post how BMC refers to versioning around AR System to avoid confusion. Format: VV.RR.MMM Patch PPP V=Version R=Release M=Maintenance Release P=Patch An example would be 3.2.02 Patch 003. Typically, if the digit for V, R or M is less than 10, the first '0' (zero) is not used (in other words, you would not see 03.02.002). Thus, the current release of AR System is 7.0.01. When the first patch for AR System 7.0.01 becomes generally available, it will be known as AR System 7.0.01 Patch 001. Hope this helps folks better understand responses that include version or patch information. Thanks, -David J. Easter Sr. Product Manager, Service Management Business Unit BMC Software, Inc. __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"
