-
-
Notifications
You must be signed in to change notification settings - Fork 50
Release Procedure
Eberhard Beilharz edited this page Mar 25, 2019
·
4 revisions
By default we create pre-release versions of the libpalaso nuget packages.
When a product team gets close to releasing their product, they can create a new release of libpalaso:
- add the new version number to
CHANGELOG.md
- create a git tag with the new version, e.g.
v7.0.0
When these changes are committed and pushed to GitHub, the CI server will pick them up and create appropriate nuget packages and publish them on nuget.org.
- Create a release on GitHub based on the git tag. Paste the text from
CHANGELOG.md
as release notes. - Delete (hide) the pre-release versions on nuget.org (e.g. once version 7.0.0 is released we should hide the pre-release version 7.0.0-pre-whatever to remove clutter).
These cleanup steps could be done by a tool, alas nobody wrote one yet 😃.