Prerequisites for changing Solus versioning scheme

[EbonJaeger]

In meetings, we have discussed a desire to change to a date-based versioning system for Solus releases instead of the traditional numbers we use now. Since we are a curated rolling release distribution, a regular version number like "4.6" is largely meaningless. By moving to a date-based system, for example, "Solus 2025.01", it then becomes very clear when an ISO is from, which may be helpful for troubleshooting later on. Our ISO file names already include the date they were generated.

Before we can switch to a new system, though, we need to do some things in advance to let users know that the change is upcoming. This should be done so that when the time comes, there is less of a chance that users will be blindsided by having the version number jump by over 2000.

Prerequisites

• Mention in the next release's blog post (Solus 4.7)
• Social media posts 1 month ahead of the switch
• Mention in each week's sync notes starting 1 month ahead of the switch
• Mention in OC emailings each week starting 1 month ahead of the switch
• Ensure that the version switch doesn't somehow break our website or tooling