Browse Source

note irctest_stable in release runbook

tags/v2.6.0
Shivaram Lingamneni 3 years ago
parent
commit
319b9a6c6e
1 changed files with 1 additions and 0 deletions
  1. 1
    0
      DEVELOPING.md

+ 1
- 0
DEVELOPING.md View File

@@ -40,6 +40,7 @@ Develop branches are either used to work out implementation details in preperati
40 40
 1. Publish the release on GitHub (Releases -> "Draft a new release"); use the new tag, post the changelog entries, upload the binaries
41 41
 1. Update the `irctest_stable` branch with the new changes (this may be a force push).
42 42
 1. If it's a production release (as opposed to a release candidate), update the `stable` branch with the new changes. (This may be a force push in the event that stable contained a backport. This is fine because all stable releases and release candidates are tagged.)
43
+1. Similarly, for a production release, update the `irctest_stable` branch (this is the branch used by upstream irctest to integration-test against Oragono).
43 44
 1. Make the appropriate announcements:
44 45
     * For a release candidate:
45 46
         1. the channel topic

Loading…
Cancel
Save