Hello,

I’m supporting an implementation of IFS APPS 10 (Release 22) having many types of customizations/changes, these include (but are not limited to) things such as custom fields, customizations of Logical Units (IFS Customization Projects in IFS Developer), custom reports, lobby pages, Information Sources for IFS Analysis Models, events, migration jobs and the list goes on an on…

I have been tasked with creating a consistent Version Control strategy for changes, as we currently use a mishmash of different approaches that are not consistent nor very effective to manage the life of our code and the deployment of our deployments as it travel its way into Production going through different “gates” for development, smoke test, user test, regression test and final implementation (a very typical Dev → Test → Pre-Prod → Production).

My question to the community is this: is there a “best practices” for IFS Source Code Management? or Branch Strategies (such as Feature Branching, Release Branching, etc.) that IFS recommends?

Thanks!