(this is a bit sarcastic, but that's my specialty) - What would make you think that a company that builds a system which is supposed to be based on ITIL best practices would use ITIL best practices in building that system?
----- Original Message ----- From: "Jose Huerta" <[email protected]> To: [email protected] Sent: Wednesday, June 27, 2012 10:59:41 AM Subject: Re: Next ARS version ** In case of other products, version numbering is normally related to licensing. So when you buy a license, the upgrades inside a major version are included (that was the case of windows server 2008 and R2). But when you want to upgrade to another version, you must pay for the upgrade. In Remedy it doesn't make sense, since you are granted all upgrades if you are paying maintenance or none (even patches) if you are not paying maintenance. But I agree that version numbering is a bit confusing. According ITIL Release Management best practices, the version number must have a meaning. In Remedy it hasn't, so you must ignore it. But it would be helpful if it has this meaning. For instance: Major versions means a re-install to upgrade. Minor versions means an upgrade: functional change, but you can upgrade without installing everything again and migrating the data. Third number means a patch. Anyway, I thing that this topic is not enough important to create almost 20 emails.... :) Jose M. Huerta Project Manager Movil: 661 665 088 Telf.: 971 75 03 24 Fax: 971 75 07 94 SM2 Baleares S.A. C/Rita Levi Edificio SM2 Parc Bit 07121 Palma de Mallorca La información contenida en este mensaje de correo electrónico es confidencial. La misma, es enviada con la intención de que únicamente sea leída por la persona(s) a la(s) que va dirigida. El acceso a este mensaje por otras personas no está autorizado, por lo que en tal caso, le rogamos que nos lo comunique por la misma vía, se abstenga de realizar copias del mensaje o remitirlo o entregarlo a otra persona y proceda a borrarlo de inmediato. P Por favor, no imprima este mensaje ni sus documentos adjuntos si no es necesario. On Wed, Jun 27, 2012 at 4:13 PM, Pierson, Shawn < [email protected] > wrote: An example of a Windows version that was a "minor" version update but is actually very different is Windows Server 2008 versus Windows Server 2008 R2 (not to be confused with Windows Server 2008 SP2.) In fact, I think that 2008 was technically Windows NT 6 and 2008 R2 is Windows NT 6.1, but I could be wrong. Thanks, Shawn Pierson Remedy Developer | Energy Transfer -----Original Message----- From: Action Request System discussion list(ARSList) [mailto: [email protected] ] On Behalf Of pritch Sent: Wednesday, June 27, 2012 7:25 AM To: [email protected] Subject: Re: Next ARS version Thanks for the info. Can you give examples of non-BMC software that issues major updates with only bumping the minor (or release) version - ie Has MS Windows released a major update that went to 6.1 rather than 7. I know that's an OS vs an app system, but do any other apps that you know of do that (Crystal, SAP, etc)? ----- Original Message ----- From: "Ben Chernys" < [email protected] > To: [email protected] Sent: Wednesday, June 27, 2012 4:51:20 AM Subject: Re: Next ARS version In any software, the version number is not decided on any logical or code based reason but rather a marketing or arbitrary reason. In the case of Remedy this is not different than say Meta-Update, Windows, etc. or any number of software products that I have worked on. ARS 5.12 was a minor version number change from 5.1 (+.02) but was a major release as new field types were introduced and some field structures were significantly changed. I am still waiting for one of those changes to be implemented in any Admin tool. That is an enum where the integers and labels are the results of queries. I have never tested that such a field is possible but the structures to define such a field have been in place since 5.12. I expect that the code was never implemented given the convolutions ITSM has to simulate such a thing. 7.6.04 was a major release as overlays were introduced. This is only on arserver(d). ITSM also had major changes. 6 to 7 was a minor arserver release mostly to support multi-tenancy but a major ITSM release with a completely different foundation data, help desk, etc, multi-tenancy. 5.0 was not significantly different that 4.x and I would have classified that as a small upgrade. I would have classified 5.12 as a major release. This is based on experience and not version numbers. I also remember a 7.0.1 patch that changed the database structure removing the ability to go back (without a backup). I am not sure that this was documented. Version numbers are always rather arbitrarily chosen. They would perhaps be better as names or labels so as to not build any expectations. On all software releases and upgrades, look at the release notes and not the version number to guess the nature of the release (ie whether minor or major). And it is a guess. Release notes are not always complete and also do not always reflect all the changes that have taken place. I am sure that does not give you or your customers much confidence or much ability to judge efforts required. As always, major or minor, upgrade in a test environment pretty close to your production environment with both the customisations and data quantities. As for ITSM, I would consider any release change including patches as major and requiring significant efforts. Just my 2 cents worth on the subject J Cheers Ben Ben Chernys Senior Software Architect Description: logoSthInc-sm Canada / Deutschland Mobile: +49 171 380 2329 GMT + 1 + [ DST ] Email: <mailto: Ben.Chernys_AT_softwaretoolhouse.com > Ben.Chernys_AT_softwaretoolhouse.com Web: < http://www.softwaretoolhouse.com/ > www.softwaretoolhouse.com Check out Software Tool House's free Diary Editor and out Freebies Section for an ITSM 7.6.04 Forms and Fields spreadsheet. Meta-Update, our premium ARS Data tool, lets you automate your imports, migrations, in no time at all, without programming, without staging forms, without merge workflow. < http://www.softwaretoolhouse.com/ > http://www.softwaretoolhouse.com/ -----Original Message----- From: Action Request System discussion list(ARSList) [mailto: [email protected] ] On Behalf Of pritch Sent: June-26-12 21:36 To: [email protected] Subject: Re: Next ARS version SLA's with clients are based on minor / major release levels - more time to upgrade to major releases from GA. When BMC changes it from 7.6.03 to 7.6.04 the client 9at least mine) wants to know why it's going to take so much effort to upgrade when the version number reflects only an 'incidental' release. ----- Original Message ----- From: "Susan Palmer" < [email protected] > To: [email protected] Sent: Monday, June 25, 2012 9:04:16 PM Subject: Re: Next ARS version ** What does it really matter what the number is?� The content is what matters.� We'll be told when they want us to know.� That's been the mantra since I started using Remedy in 1995, don't bother asking ...we're not telling.� On Mon, Jun 25, 2012 at 2:01 PM, Longwing, LJ CTR MDA/IC < <mailto: [email protected] > [email protected] > wrote: What I remember from that time is that 7.6.3 was supposed to be 8....but they realigned things to internal numbering practices...and was originally supposed to include overlays...but they couldn't get it hardened before GA...so they released 7.6.3 without it....and then 'shortly' later released 7.6.4 which was the 'finished product' that 7.6.3 was supposed to be... -----Original Message----- From: Action Request System discussion list(ARSList) [mailto: [email protected] ] On Behalf Of Joe Martin D'Souza Sent: Monday, June 25, 2012 12:58 PM To: [email protected] Subject: Re: Next ARS version ** That�s weird.. did they call it a maintenance release? No way it wasn�t.. With the introduction of something so foreign to the ARS as the overlays, it can�t be considered a maintenance release.. It was a major release.. In my opinion, any release that changes the structure of the underlying database IS NOT a maintenance release. Changes to the DB structure, should be one of the several other criteria, that determines if a release ought to be qualified as a major release.. If they had already changed the structure of the DB in 7.6.03, and then leveraged that new structure in 7.6.04, then yes, it can be argued as a maintenance release, but I do not think this was the case. The DB structure was altered in 7.6.04 to accommodate the overlays feature, and not in 7.6.03.. Joe From: Tauf Chowdhury <mailto: [email protected] > Sent: Monday, June 25, 2012 10:25 AM Newsgroups: public.remedy.arsystem.general To: <mailto: [email protected] > [email protected] Subject: Re: Next ARS version ** Personally, I think BMC needs to redefine its versioning criteria after seeing what happened with 7.6.03 to 7.6.04. I still can't make sense of how 04 was a "maintenance release." Sent from my iPhone On Jun 24, 2012, at 11:11 AM, praveen kumar < <mailto: [email protected] > [email protected] > wrote: � � � �** � � � �Yes..! next ARS release will be 8.0 confirmed by BMC. Loads of new features and expectations. Fingers crossed for the upcoming release. � � � �Cheers.! � � � �prawin � � � �> � � � �> I think it was to be 7.7, but then BMC decided there are enough new � � � �> feature to call it 8.0. � � � �> � � � �> On 24/06/2012 12:22, Jose Huerta wrote: � � � �> > ** I'm a bit confused about next version. � � � �> > � � � �> > Some people told me that it will be 7.7, but others say 8.0. I'm sure � � � �> > that you'll have the correct answer. � � � �> > � � � �> > Regards, � � � �> > � � � �> > Jose Huerta � � � �> > < http://theremedyforit.com/ > http://theremedyforit.com/ � � � �> > _attend WWRUG12 < http://www.wwrug.com > www.wwrug.com ARSlist: "Where the Answers Are"_ � � � �> � � � �> _______________________________________________________________________________ � � � �> UNSUBSCRIBE or access ARSlist Archives at < http://www.arslist.org > www.arslist.org � � � �> attend wwrug12 < http://www.wwrug12.com > www.wwrug12.com ARSList: "Where the Answers Are" � � � �_attend WWRUG12 < http://www.wwrug.com > www.wwrug.com ARSlist: "Where the Answers Are"_ _attend WWRUG12 < http://www.wwrug.com > www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at < http://www.arslist.org > www.arslist.org attend wwrug12 < http://www.wwrug12.com > www.wwrug12.com ARSList: "Where the Answers Are" _attend WWRUG12 < http://www.wwrug.com > www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at < http://www.arslist.org > www.arslist.org attend wwrug12 < http://www.wwrug12.com > www.wwrug12.com ARSList: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" Private and confidential as detailed here: http://www.sug.com/disclaimers/default.htm#Mail . If you cannot access the link, please e-mail sender. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
