Best way of going from 9.6.02.02 to 9.6.07.05

Author: knut.ivar.alvestad@logica.com (knutia)

Hi We all know the best ting is to develop, test and run prod on the same version is the best ting. But that is not always possible. So what is the best of this two scenarios:   1. Have developers use 9.6.02.02 for developing and compiling artifacts and have prod run the 9.6.02.02 compiled artifacts whit 9.6.07.05  2. Have developers use 9.6.07.05 for developing and compiling artifacts and have prod run the 9.6.07.05 compiled artifacts whit 9.6.02.02   My assumptions is that scenario 1 is the best of the two but i would like the forums opinion on this.   Knut Ivar 

2 Comments

  1. option 1 is supported.  option 2 is not supported, not tested and scares me. 


    Author: Adrian Gosbell (adrian.gosbell@synapse-i.jp)
  2. We do have different environments for this purpose Say Development           9.6.02.02        "Playground" Testing  (Ver1)        9.6.02.02        Qualitiy tests Deployment(Ver1)    9.6.02.02        Same then customer-site Production(Ver1)      9.6.02.02        customer-site Testing  (Ver2)        9.6.07.05        Qualitiy tests Deployment(Ver2)    9.6.07.05        Same then customer-site Production(Ver2)      9.6.07.05        customer-site Version 1  legacy application Version 2  current application Between this environments we use the export/import tools of UnifAce Development could also be 9.6.07.05 Advantage:     for the current application we can use all feature of UnifAce Disadvantage: One have to use some #if() to avoid compiling errors in version 1 Ingo


    Author: istiller (i2stiller@gmx.de)