diff options
| author | GeckoEidechse <40122905+GeckoEidechse@users.noreply.github.com> | 2023-12-18 15:13:51 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-12-18 15:13:51 +0100 |
| commit | 3b0d2a70789ed730a29feada1e874e6cbaeee31c (patch) | |
| tree | 962e7d169bedf0612d54687445872ebafcdaa192 | |
| parent | c9abbe318c975ef5feace437ac58d6315b691e4b (diff) | |
| download | NorthstarWiki-3b0d2a70789ed730a29feada1e874e6cbaeee31c.tar.gz NorthstarWiki-3b0d2a70789ed730a29feada1e874e6cbaeee31c.zip | |
Document creating releases for DiscordRPC (#254)
| -rw-r--r-- | docs/development/releases.md | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/docs/development/releases.md b/docs/development/releases.md index e04a9be..4d76be2 100644 --- a/docs/development/releases.md +++ b/docs/development/releases.md @@ -139,3 +139,15 @@ Once `2.0` has been released, expectations for `3.0` tend to be lower as the num - Make at least one release candidate and test it before actual release. - Release should also only ever be latest release candidate but tagged as release to avoid introducing new bugs. + + +## Other repos + +Repos like navmeshes and DiscordRPC get their release unrelated to main Northstar release numbering as they usually only see a few release per year due to + + +### DiscordRPC + +Push new tag which in turn will generate a release. Tags are formatted as `vN` where `N` is an always increasing integer, i.e. `v4`, `v5`, `v6`, etc. + +Once a new DiscordRPC release has been made, the version number needs to be bumped in the [release repo](https://github.com/R2Northstar/Northstar) to pull the new release. |