Book a Demo

Author Topic: Co-Exist EA 13 and 12.1?  (Read 62431 times)

Glassboy

  • EA Practitioner
  • ***
  • Posts: 1367
  • Karma: +112/-75
    • View Profile
Re: Co-Exist EA 13 and 12.1?
« Reply #30 on: September 08, 2016, 07:39:57 am »
To be more precise it won't allow two packages with the same Product Code to coexist.
To be more precise, it won't allow two packages with the same upgrade code to coexist. The product code can change, and best practice says that it should at least every time new files/apis etc are added.

Yes.  I was conflating the two and I mistakenly called PackageCode Version code.  Naughty me, but it has been about six years since I had to build a transform.

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8110
  • Karma: +119/-20
    • View Profile
Re: Co-Exist EA 13 and 12.1?
« Reply #31 on: September 08, 2016, 08:27:51 am »
It might be a good idea to give the beta versions a different upgrade code then, so people can install a beta version alongside their "real" version.

As soon as it's out of beta it can be changed to the original one so it does an upgrade as per usual.

Geert
Considered that, but then installing the released version over the beta is the hard part.

On the other hand, don't we usually say that the beta should not be used on production machines or models? That position would imply it shouldn't matter how the beta behaves with non-beta versions.

Glassboy

  • EA Practitioner
  • ***
  • Posts: 1367
  • Karma: +112/-75
    • View Profile
Re: Co-Exist EA 13 and 12.1?
« Reply #32 on: September 08, 2016, 09:29:35 am »
Considered that, but then installing the released version over the beta is the hard part.
On the other hand, don't we usually say that the beta should not be used on production machines or models? That position would imply it shouldn't matter how the beta behaves with non-beta versions.

The flaw in your logic is that people are just as likely to put the production release and the beta on their dev machine to run side by side comparisons on dev repositories.

(strictly speaking most people's production networks are just slightly better controlled dev networks anyway)
« Last Edit: September 08, 2016, 11:12:38 am by Glassboy »

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: Co-Exist EA 13 and 12.1?
« Reply #33 on: September 08, 2016, 09:47:16 am »
Spot on, Glassboy!

And once you've done your dev checks, you might (as we did) allow a small number of users onto production repositories.

The question is about coexistence of versions, not access to repositories

Paolo.


Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Co-Exist EA 13 and 12.1?
« Reply #34 on: September 08, 2016, 12:56:43 pm »
Indeed, from all the clients in all the years I've been doing consultancy I've only seen one who had an actual test environment for the client pc's the IT team worked on, and that was a bank with 6000 IT staff.
All the others just find a couple of volunteers to test a new version and install it on their "production" machines. Once they're happy the software gets rolled out to the rest of them.

Exceptions are the ones that use some kind of terminal system to deploy their client software (citrix, MS RemoteApps)

Geert

Rich Anderson

  • EA User
  • **
  • Posts: 142
  • Karma: +8/-0
    • View Profile
    • LinkedIn
Re: Co-Exist EA 13 and 12.1?
« Reply #35 on: September 12, 2016, 10:17:06 am »
Go away for a while and lots of stuff happens!   ;)
Rich Anderson
Urgnt Limited