Do you use version numbers and well formatted notes to keep track of solution changes?
4/07/2020 8:18 AM by
Dynamics uses a solution as a logical container to hold all customizations for a given function or sub-function. It is very important to have a versioning strategy around changes and when to increment versions.
Increment the version *every time* a change is made and add a new line at the top of the description field containing:
- New version number
- Developer initials
- Change notes, can changes, removals, additions to the solution
This gives you a quick and easy reference for the changes that have happened in the solution. Following this standard means comparing solutions across environments is a painless process.
- Bad Example: Version 188.8.131.52, No changelog
- Good Example: Solution has up to date versioning with detailed changelog
Do you feel this rule needs an update?