March 4, 2015
A strong version management policy will address two of the biggest challenges in IBM Notes development: how to properly manage concurrent development, and how to promote design changes into other environments such as test or production.
In most Notes development environments, concurrent development entails maintaining two or more different iterations of an application design within a single template. As new changes are added, only the elements where the changes have been applied are copied into production through a manual process. If the application is small enough, this may be tenable for the short term, but will quickly become a problem as the application grows in complexity.
Problems like this are easily solved by implementing simple rules that govern how concurrent development should be managed using branches, version numbers, and build processes. Organizational guidelines are also a must in the form of server directory structures so that everyone knows where to work. Proper version management ensures that development efforts are organized and understandable. As people come and go from development or administration teams, it will be much easier to ensure that everyone is working on the correct versions of applications, and they know where to go to find the previous versions.