Skip to content

Commit a61dce5

Browse files
authored
Merge pull request #143 from ktoso/wip-release
2 parents e16f9ce + fc5d605 commit a61dce5

File tree

1 file changed

+53
-0
lines changed

1 file changed

+53
-0
lines changed

Sources/Prometheus/RELEASE.md

Lines changed: 53 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,53 @@
1+
# Releasing
2+
3+
## Release schedule
4+
5+
Releases of this library are performed on a when-needed basis.
6+
7+
Generally one of the maintainers listed in MAINTAINERS.md will perform a release.
8+
9+
If you would like to request a release since a change or fix has been waiting for a release for some time,
10+
you may open up an issue on github, requesting a release.
11+
12+
## Versioning
13+
14+
As usual with Swift packages, we use [Semantic Versioning](https://semver.org/).
15+
16+
## Make a release
17+
18+
Development and releases are made from the `main` branch directly, therefore the branch should remain in releasable state at any time.
19+
20+
Creating a release involves creating a Git tag and pushing it to the upstream repository.
21+
22+
Tags should follow the simple `MAJOR.MINOR.PATCH` format, without any prefix (e.g. do not include the `v` prefix).
23+
24+
Step 1) Make a release tag.
25+
26+
```bash
27+
tag="MAJOR.MINOR.PATCH"
28+
git tag -s "${tag}" -m "${tag}"
29+
git push origin "${tag}"
30+
```
31+
32+
Step 2) Make the GitHub Release and Release Notes.
33+
34+
> Release notes generation is automated and based on the enforced labelling of pull requests.
35+
> As pull requests are merged, they are required to be tagged with `semver/*` tags (`semver/patch`, `semver/minor`, ...).
36+
37+
Navigate to the [New release](https://github.com/swift-server/swift-prometheus/releases/new) page on github and
38+
select your release tag.
39+
40+
Click **Generate release notes** release notes will automatically be generated.
41+
42+
Take a moment to read over the changes and make sure their assigned patch/minor/major categories are correct and match the release's assigned version.
43+
44+
You may add some additional introduction, thanks or additional information which may be useful for anyone reading the release notes.
45+
46+
Step 3) "There is no Step 3!"
47+
48+
## Swift Versions
49+
50+
Generally this project supports three most recent minor versions of Swift.
51+
52+
For example, at time of writing this document Swift 6.2 is the current release, so this project also supports 6.1 and 6.0.
53+
And this list of versions changes whenever a new minor Swift version is released.

0 commit comments

Comments
 (0)