maxmustermann/terminal
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
terminal/custom.props

12 lines
545 B
Plaintext
Raw Normal View History

consolidate PackageES versioning in /custom.props (#3672) This location and name is practically mandated by PackageES. Sorry ☹️. This will ensure that all artifacts that we produce are versioned properly: | thing | version (ex.) | |---------|-----------------| | dll/exe | 0.7.1911.22009 | | nupkg | 0.7.191122009 | | appx | 0.7.3269.0 | For reference, here's the version format: ### EXE, DLL, .NET Assembly 0.7.1911.22009 ^ ^ ^ ^ ^ ^ | | | | | `-Build # on that date | | | | `-Day | | | `-Month | | `-Year | `-Minor `-Major ### NuGet Package 0.7.191122009 ^ ^ ^ ^ ^ ^ | | | | | `-Build # on that date | | | | `-Day | | | `-Month | | `-Year | `-Minor `-Major ### AppX Package 0.7.03269.0 ^ ^ ^ ^^ ^ | | | || `-Contractually always zero (a waste) | | | |`-Build # on that date | | | `-Number of days in [base year] | | `-Number of years since [base year] | `-Minor `-Major [base year] = $(XesBaseYearForStoreVersion) It is expected that the base year is changed every time the version number is changed.
2019-11-25 20:29:40 +01:00
<?xml version="1.0" encoding="utf-8"?>
<Project ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<!-- This file is read by XES, which we use in our Release builds. -->
<PropertyGroup Label="Version">
<XesUseOneStoreVersioning>true</XesUseOneStoreVersioning>
master: bump version to v0.9
2020-01-10 02:44:36 +01:00
<XesBaseYearForStoreVersion>2020</XesBaseYearForStoreVersion>
consolidate PackageES versioning in /custom.props (#3672) This location and name is practically mandated by PackageES. Sorry ☹️. This will ensure that all artifacts that we produce are versioned properly: | thing | version (ex.) | |---------|-----------------| | dll/exe | 0.7.1911.22009 | | nupkg | 0.7.191122009 | | appx | 0.7.3269.0 | For reference, here's the version format: ### EXE, DLL, .NET Assembly 0.7.1911.22009 ^ ^ ^ ^ ^ ^ | | | | | `-Build # on that date | | | | `-Day | | | `-Month | | `-Year | `-Minor `-Major ### NuGet Package 0.7.191122009 ^ ^ ^ ^ ^ ^ | | | | | `-Build # on that date | | | | `-Day | | | `-Month | | `-Year | `-Minor `-Major ### AppX Package 0.7.03269.0 ^ ^ ^ ^^ ^ | | | || `-Contractually always zero (a waste) | | | |`-Build # on that date | | | `-Number of days in [base year] | | `-Number of years since [base year] | `-Minor `-Major [base year] = $(XesBaseYearForStoreVersion) It is expected that the base year is changed every time the version number is changed.
2019-11-25 20:29:40 +01:00
<VersionMajor>0</VersionMajor>
version: bump to 0.11
2020-03-23 18:04:37 +01:00
<VersionMinor>11</VersionMinor>
consolidate PackageES versioning in /custom.props (#3672) This location and name is practically mandated by PackageES. Sorry ☹️. This will ensure that all artifacts that we produce are versioned properly: | thing | version (ex.) | |---------|-----------------| | dll/exe | 0.7.1911.22009 | | nupkg | 0.7.191122009 | | appx | 0.7.3269.0 | For reference, here's the version format: ### EXE, DLL, .NET Assembly 0.7.1911.22009 ^ ^ ^ ^ ^ ^ | | | | | `-Build # on that date | | | | `-Day | | | `-Month | | `-Year | `-Minor `-Major ### NuGet Package 0.7.191122009 ^ ^ ^ ^ ^ ^ | | | | | `-Build # on that date | | | | `-Day | | | `-Month | | `-Year | `-Minor `-Major ### AppX Package 0.7.03269.0 ^ ^ ^ ^^ ^ | | | || `-Contractually always zero (a waste) | | | |`-Build # on that date | | | `-Number of days in [base year] | | `-Number of years since [base year] | `-Minor `-Major [base year] = $(XesBaseYearForStoreVersion) It is expected that the base year is changed every time the version number is changed.
2019-11-25 20:29:40 +01:00
<VersionInfoProductName>Windows Terminal</VersionInfoProductName>
</PropertyGroup>
</Project>
Reference in a new issue Copy permalink