Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Merged
merged 4 commits into from
Nov 20, 2023
Merged

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

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
52757a9
Update proposed new versioning rules for easier preview build usage
Khitiara Sep 30, 2023
0c0ee89
Update documentation/proposals/Proposal - 3.0 & 3.X Software Developm…
Khitiara Sep 30, 2023
7d5e75b
Update Proposal - 3.0 & 3.X Software Development Plan.md
Khitiara Nov 19, 2023
a85283f
Update documentation/proposals/Proposal - 3.0 & 3.X Software Developm…
Khitiara Nov 20, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions documentation/proposals/Proposal - 3.0 & 3.X Software Development Plan.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -169,7 +169,7 @@ 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, unless it is a preview build generated from the `develop` branch in which case it'll be 1.
Khitiara marked this conversation as resolved.
Show resolved Hide resolved

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.

Expand Down Expand Up @@ -198,4 +198,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.
Loading