Skip to content

Latest commit

 

History

History
42 lines (30 loc) · 1.96 KB

MAINTAINERSHIP.md

File metadata and controls

42 lines (30 loc) · 1.96 KB

XAML-Math Maintainership

Publish a New Version

  1. Update the copyright year in the license file, if required.
  2. Prepare a corresponding entry in the changelog (usually by renaming the "Unreleased" section).
  3. Set <Version> in the Directory.Build.props file.
  4. Update the copyright year in Directory.Build.props, if required.
  5. Merge the aforementioned changes via a pull request.
  6. Push a tag in form of v<VERSION>, e.g. v0.0.1. GitHub Actions will do the rest (push a NuGet package).

Prepare NuGet Package Locally

$ dotnet pack XamlMath.All.sln --configuration Release

(Use XamlMath.Portable.sln on Unix-like operating systems; note you won't be able to build and pack the WPF-specific part of the code, though.)

Push a NuGet Package Manually

$ dotnet nuget push ./src/WpfMath/bin/Release/WpfMath.<VERSION>.nupkg --source https://api.nuget.org/v3/index.json --api-key <YOUR_API_KEY>
$ dotnet nuget push ./src/AvaloniaMath/bin/Release/AvaloniaMath.<VERSION>.nupkg --source https://api.nuget.org/v3/index.json --api-key <YOUR_API_KEY>

Runtime Support Policy

Generally, XAML-Math supports the .NET runtime (.NET Framework or modern .NET) versions that are supported by Microsoft (both basic and extended support are considered), provided that the support cost for the very old versions is reasonable. We will stop support for the currently supported runtime version either after it gets unsupported, or when we consider support cost unreasonable.

Removing .NET runtime version from the list of compatible versions is a breaking change (as far as semantic versioning is concerned).

For reference, see the .NET support dates list.