develop
master
Supertext.Base contains a collection of useful utilities and helpers.
*.Test projects should contain Unit Tests only which are fast and dependencies mocked *.Specs projects should contain Integration tests whose execution time us probably longer
Each commit at the develp branch will trigger a CI pipeline build. The build runs all unit tests. After the successful pass of build and test, a Nuget package will be packed and released. These Nuget packages are available as Prerelease packages and can be tried by loading them via the feed https://supertext.pkgs.visualstudio.com/_packaging/internal/nuget/v3/index.json Consideration: Prerelease references should not be checked in any consuming project.
The Supertext.Base are versioned after the Semantic Verioning principle (see SemVer).
Given a version number MAJOR.MINOR.PATCH, increment the:
- MAJOR version when you make incompatible API changes,
- MINOR version when you add functionality in a backwards-compatible manner, and
- PATCH version when you make backwards-compatible bug fixes. Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.
With Supertext.Base GitVersion is a helper to increments versions automatically according to the existing version and available tags. Further infos under GitVersion.
Steps in order to release the Supertext.Base libraries:
- Initiate the release with a pull request from develop to master
- After the pull request has been approved, it needs to be merged into the master branch.
- Discuss and coordinate an upcoming release with your team mates.
- Set a new Tag at the master branch according to the SemVer principle. You can do this via https://github.com/Supertext/Supertext.Base/releases/new. Write also something regarding the release.
- Queue a new build with the Supertext.Base release pipeline. The package will be released with the before tagged number as package version. It will be available under the same feed.
Feedback and suggestions are always welcome :-)