1
General Board / Managing changes to multiple releases
« on: April 03, 2013, 06:59:37 am »
Hello,
In my company we simultaneously work on multiple releases of our IT landscape. Typically release N is in production, release N+1 is in acceptance test, release N+2 is in detailed design and build phase and release N+3 is in feasibility and high level design phase. Obviously, most design changes are made in release N+2 and N+3, but some fixes in release N and N+1 also have design impact.
Managing the code for these releases is rather straighforward using branches in a version control system. Changes in one release/branch are merged into a later release/branch using 3-way diff and merge tools. What would be the best way to manage design changes in such an environment using EA? Note that I did read the whitepapers on version control and deployment, but they only seem to discuss version management with a single branch; not with multiple branches.
Regards, Frans.
In my company we simultaneously work on multiple releases of our IT landscape. Typically release N is in production, release N+1 is in acceptance test, release N+2 is in detailed design and build phase and release N+3 is in feasibility and high level design phase. Obviously, most design changes are made in release N+2 and N+3, but some fixes in release N and N+1 also have design impact.
Managing the code for these releases is rather straighforward using branches in a version control system. Changes in one release/branch are merged into a later release/branch using 3-way diff and merge tools. What would be the best way to manage design changes in such an environment using EA? Note that I did read the whitepapers on version control and deployment, but they only seem to discuss version management with a single branch; not with multiple branches.
Regards, Frans.