Skip to content

Commit 539be97

Browse files
committed
how to contribute
1 parent 4eb339c commit 539be97

File tree

1 file changed

+28
-0
lines changed

1 file changed

+28
-0
lines changed

contributing.md

+28
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
# Contributing
2+
3+
## Making a Release
4+
5+
Git release tags are the single source of truth for release
6+
numbers and release triggers. There is no version information in the
7+
pom file. A default version number is contained in
8+
`.mvn/maven.config`, which should be kept up to date. However, it is
9+
overridden in the CI/CD pipelines by the release tag.
10+
11+
Releases of installable packages will be created with github actions
12+
on tags with a name matching the pattern
13+
`[0-9]+\.[0-9]+\.[0-9]+(-.*)?`,
14+
i.e. `<MAJOR>.<MINOR>.<BUGFIX>[-<SUFFIX>]`. But only tags matching the
15+
pattern `[0-9]+\.[0-9]+\.[0-9]+` will result in an update of the
16+
descriptor file.--So, releases with a suffix are considered kind of
17+
beta and will only occur in the tag's release bundle.
18+
19+
To produce a release:
20+
21+
- first push the branch to be released
22+
- then tag it with the tag name matching the above pattern
23+
24+
This will produce a release on [releases/tag/<TAG_NAME>](releases/tag)
25+
and update the [descriptor
26+
file](https://scdh.github.io/oxbytei/descriptor.xml).
27+
28+
The pattern for release tags is protected.

0 commit comments

Comments
 (0)