Update proposed new versioning rules for easier preview build usage (#1682)

* Update proposed new versioning rules for easier preview build usage

* Update documentation/proposals/Proposal - 3.0 & 3.X Software Development Plan.md

Co-authored-by: Dylan Perks <[email protected]>

* Update Proposal - 3.0 & 3.X Software Development Plan.md

* Update documentation/proposals/Proposal - 3.0 & 3.X Software Development Plan.md

Co-authored-by: Dylan Perks <[email protected]>

---------

Co-authored-by: Dylan Perks <[email protected]>

Author: Khitiara

documentation/proposals/Proposal - 3.0 & 3.X Software Development Plan.md

@@ -169,7 +169,8 @@ Any post-3.0, pre-4.0 release will be versioned as follows:
 - The major version will always be 3
 - The minor version will be the number of the monthly update cycle i.e. the first monthly update will be versioned 3.1, the second 3.2, etc...
 - The patch version will always be 0, unless it is an emergency patch in which case it'll be the number of the emergency patch i.e. if an emergency patch is required after the first monthly update the version will be 3.1.1, if another one is required (heaven forbid) in this same cycle it'll be 3.1.2 etc...
-- The revision version will always be 0.
+- The revision version will always be 0 for released builds.
+- The patch version shall be incremented after a release to ensure the working tree and therefore the experimental feed tracks a version higher than the currently released one, with the provision that this version number is not final and the final released version number shall be subject to all of the above rules.
 
 Users are expected to keep all of the versions of all Silk.NET packages they are using in-sync. We could write a Roslyn analyser or MSBuild target to help push users to this.
 
@@ -198,4 +199,4 @@ Individual developers on the team may diverge from this, but they will be respon
 - Approved.
 - Support Eto.Forms?
     - Not really used or requested compared to the others, maybe as a community thing.
-- There were some questions about the bindings libraries and how the generator differences are going to be consolidated.
+- There were some questions about the bindings libraries and how the generator differences are going to be consolidated.