Rules

Secret ingredients to quality software

Edit
Info

Do you use version numbers and well formatted notes to keep track of solution changes?

Last updated by Tiago Araujo on 03 Jul 2020 10:18 pm (11 months ago) See History

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:

  1. New version number
  2. Developer initials
  3. 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.

change log bad
Bad Example: Version 1.0.0.0, No changelog

change log good
Good Example: Solution has up to date versioning with detailed changelog

Adam CoganAdam Cogan
Mehmet OzdemirMehmet Ozdemir

We open source. This page is on GitHub