The solution version number is often overlooked as an easy way of keeping backups of your solution separate as you configure CRM.
You can number them according to a strict 4-part version numbering (e.g. 184.108.40.206, 220.127.116.11, etc.) but that’s relatively boring and tough to keep consistent.
The most straight forward and easy to maintain method of versioning for solutions is to utilize a pseudo timestamp as the version number.
Anytime a solution is going to be exported, the version number should be updated by the administrator, and saved before it’s actually exported. For simplicity, use the format of YYYY-MM-DD-##, where ## is the intra-day revision number that is just incremented with each version created on a particular day, e.g. the first update/export of a solution on October 9, 2015 would have a version number of 2015.10.09.01 as shown in the following image. (Before exporting again on the same day, just rev the last 2 digits to 02)
Following this convention means your deployment team is never confused about which iteration to install and you can clearly see in production which solutions is live.