We have a Production Project with following states (Dev, Merge, Test, QA and Production”, when ever development team inform us they are getting ready for the upgrade we create cross-merge project for the parallel development and Go-live we disable the Production Facets and make cross-merges project as active Facets Project.
This time Team asking us to create different solution, they wants to avoid back and forth between parallel development project. They sends us requirement to create additional state “UPGRADE” so developers can move the code which is related to upgrade to UPGRADE state from Merge, and regular development code will move as usual from Dev, Merge, Test, QA and Production.
When Go-live time come they want to promote all the packages from Upgrade state to Test, QA and Production.
I would like to know what difficulties we will have in term of version control ? I think there will be issue during go-live when we will move packages from upgrade state to test, QA and Production if there is already higher version exists in production or any state it will not allow us.
Please if you can review our propose project and let me know any other concerns.
Release : 13.0
Component : CA Harvest Software Change Manager