mirror/PowerToys
1
0
Fork 0
mirror of https://github.com/microsoft/PowerToys.git synced 2024-11-24 04:12:32 +08:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

small verbage tweak

Clint Rutkas 2020-09-01 16:54:53 -07:00
parent dac99bcda4
commit 05405bea39
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Versioning.md

@ -33,7 +33,7 @@ Our software includes .NET based softare, we need to adhere to the versioning co
|Build|undefined (-1)|
|Revision|undefined (-1)|
PowerToys will follow the *major*.*minor*[.*build*] format where Major will be 0.
PowerToys will follow the 0.*minor*[.*build*] format currently.
## Setting Versions.prop
@ -51,8 +51,8 @@ We will increase the *build* number for any hot fix that goes into Stable, inclu
### Signed branches
- Stable – This is the branch we release our main release from. We will use tags to inform version number to the public which is what we already do currently.
- Pre-release - This will be the branch where we release pre-release variants of PowerToys. Once we hit stability, this will be how we do share prerelease builds to the public so we have a known stable build for everyone.
- `Stable` – This is the branch we release our main release from. We will use tags to inform version number to the public which is what we already do currently.
- `Pre-release` - This will be the branch where we release pre-release variants of PowerToys. Once we hit stability, this will be how we do share prerelease builds to the public so we have a known stable build for everyone.
- We will do a full minor increase. This means if the current major release is `v0.10.0`, this would be `v0.11.0` and the next major release would be `v0.12.0`
- In GitHub, we'll label these are pre-release software in the release as well so they will not prompt for new versions. Pre-release builds will only prompt for new pre-release builds.