So, based on that, the current supported versions are
Current (7.6.4) C - 1 (7.5) C - 2 (7.1) ? From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Martinez, Marcelo A Sent: Thursday, February 03, 2011 10:23 AM To: [email protected] Subject: Re: version question ** Hello KP, The only documentation I've found is located on the support site under Review Policies> Product Support Policy. Which states: Release Numbering BMC Software uses a three-place numbering scheme to designate released versions of software. The format is VV.RR.MM, where V indicates the version, R indicates the release level, and MM indicates the maintenance level. An example would be version 3.2.02 (abbreviated 3.2.02). Often in referring to general product versions and releases, the maintenance level is omitted. For example, both 3.2.01 and 3.2.02 may sometimes be referred to as 3.2. Version/Release A version/release is a deliverable of a BMC Software product that is fully functional and is installable on the targeted platform through a standard installation program. A version/release is referenced using the V and R portions of the release number as described above. Maintenance Release 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. I wonder if there is documentation with that announcement. Quote "I was on a webinar with them regarding the new release and they made that announcement." Thanks, Marcelo From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Ars Lister Sent: Thursday, February 03, 2011 11:00 AM To: [email protected] Subject: Re: version question ** Hi Marcelo, Last summer, BMC Remedy was supposed to release version 8 which would have been a new release. However, they decided to change their numbering conventions and released what would have been version 8 as 7.6.03 instead. I was on a webinar with them regarding the new release and they made that announcement. I have the details of what their new numbering convention is supposed to indicate in some notes that I have yet to locate, but as soon as I do, I will share. In the meantime, there are several BMC people on this listserv that may be able to enlighten us all... KP _____ From: "Martinez, Marcelo A" <[email protected]> To: [email protected] Sent: Wed, February 2, 2011 5:14:44 PM Subject: version question In regards to ITSM, what is the difference between a version change, a release change, and a maintenance release change? Assuming that a version change is a major change to the application... but what does it entail? What is considered a release change (i.e. going from 7.5.03 to 7.6.00)? I'm currently trying to convince my management upgrade to version 7.6.0x ....but why? Why go to 7.6.0x instead of 7.5.0x? I may also add that I'm doing an analysis of all the "what's new" documentation.. Hopefully someone can shed some light on how it is decided to change the release numbering instead of the maintenance release number.. Thanks Marcelo Martinez ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org <http://www.arslist.org/> attend wwrug11 www.wwrug.com <http://www.wwrug.com/> ARSList: "Where the Answers Are" _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
