Genesys CTI User Forum

Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: cavagnaro on April 18, 2016, 02:35:24 PM

Title: Genesys Release notes
Post by: cavagnaro on April 18, 2016, 02:35:24 PM
Hey guys,
Since a while ago I find Genesys RN kinda..."funny"
Example on Composer:

8.1.410.14 [02/12/2016] – General X
8.1.400.38 [04/14/2016] – Hot Fix

So version 8.1.410.14 is the last one, right? But was released before the 8.1.400.38...so...which one is the newer? How do we read that?
That correction made on 8.1.400.38 is not for the 410 but for only 8.1.400.xx?

Title: Re: Genesys Release notes
Post by: Adam G on April 18, 2016, 03:58:37 PM
Hi cav,

As you know, a Hot Fix is released usually to address a specific/single issue raised by a customer.  General Release should provide a "roll up" of Hot Fixes and other enhancements.  Seems like your example implies that a Hot Fix took a very long time to be released and, during the time it took to be developed, a General Release was rolled out.  It also sounds like Genesys got their releases mixed up....

The bigger difference is that Hot Fixes are only tested against the environment and issue they resolve - General Releases are more thoroughly tested and benchmarked (allegedly!)  Personally, I would only deploy a Hot Fix if it fixed an issue I know we had - otherwise I would wait for the next GA release.
Title: Re: Genesys Release notes
Post by: cavagnaro on April 18, 2016, 04:18:59 PM
Yeah, I do understand that but it is quite messy...if you see a patch that is going to be later that a GA then apply the patch to the GA...right?
Later you can't apply a GA as you know it may have bugs but new features you want.
Then can impact on compilation of your already active projects, example, you did an upgrade of your projects.

Anyway, just saying Genesys dev team seems more fragmented than before

Enviado de meu E6633 usando Tapatalk

Title: Re: Genesys Release notes
Post by: Kubig on April 19, 2016, 08:58:05 AM
I do not see any mess there, the bug was related to the release branch 8.1.400.xx and not to the release branch 8.1.401.xx,because of the hot fix does not make any sense in 8.1.401.xx.
Title: Re: Genesys Release notes
Post by: Adam G on April 19, 2016, 09:16:21 AM
If that is true Kubig, then perhaps they have changed the way they view GA and HF releases?  The simple view is  that each update should be consecutive along a timeline, so that you'll know if you have the latest release - one of the big "killers" when you raise an Incident is the question "are you on the latest version?".

Taking cav's example, the "latest release" is actually 8.1.400.38 - and not 8.1.410.14.  And that makes no sense to me.  I think you are saying that 8.1.4[b]0[/b]0.xx is not the same release "branch" as 8.1.4[b]1[/b]0.xx, so if you have 8.1.4[b]0[/b]0.xx installed, only look at 8.1.4[b]0[/b]0.[b]xx[/b] to see if you have the latest release for that branch?  That is news to me - and quite confusing when you are trying to manage that aspect.
Title: Re: Genesys Release notes
Post by: Kubig on April 19, 2016, 09:46:23 AM
It depends on how you understand the term latest - from my point of view it does not mean the ordering by release date.
Title: Re: Genesys Release notes
Post by: Adam G on April 19, 2016, 10:38:56 AM
OK - just so that I am clear, then... using cav's example:

8.1.400.xx can have .xx HF releases.
8.1.410.xx can have .xx HF releases.

...but they are not related?
Title: Re: Genesys Release notes
Post by: Kubig on April 19, 2016, 11:17:25 AM
In this case, yes.
Title: Re: Genesys Release notes
Post by: Fra on April 19, 2016, 12:11:25 PM
First time I have seen this logic in maintenance releases of the same stream - in this case 8.1.4xx

Indeed, I have seen changes/fixes applied only to a certain stream, but again not within the same stream (i.e. fix in 8.1.3 but not in 8.1.4).

Fra
Title: Re: Genesys Release notes
Post by: Kubig on April 19, 2016, 01:57:51 PM
Agree, that this approach is not most common for Genesys at all. But, each component is developed by another team, so there can be various (bad) habits. However, it make sense in some cases. for instance you develop a software based on any third-party SW/framework, which has several bugs. So, for future release you decide to use another (stable) SW/framework, i.e. HF for this part of component will be no longer required. So, you will just fix the "older" branch, where the "corrupted" part is implemented.
Title: Re: Genesys Release notes
Post by: cavagnaro on April 19, 2016, 02:06:03 PM
Lets just put that from now on it is no longer safe to assume that if you are in lastest release you have all bugs covered. Actually no way to know if the bug fixed on that HF is or not present on the latest GA... Right? So...

Enviado de meu E6633 usando Tapatalk

Title: Re: Genesys Release notes
Post by: Adam G on April 19, 2016, 03:26:16 PM
I think it may be slightly worse than that; I think you may have to read all of the release notes very carefully from now on, to make sure your own bugs/issues are covered... :/
Title: Re: Genesys Release notes
Post by: cavagnaro on April 19, 2016, 09:16:23 PM
Yeah but there is no way to know which bugs are affecting you :(

Enviado de meu E6633 usando Tapatalk

Title: Re: Genesys Release notes
Post by: Adam G on April 19, 2016, 10:10:52 PM
So.. only install Hot Fixes built specifically for you, otherwise only upgrade to the next GA...

?