Add new comms channel/process

Address duplicate list prefix
Co-authored-by: xrplf-ai-reviewer[bot] <266832837+xrplf-ai-reviewer[bot]@users.noreply.github.com>
2026-10-11 22:28:02 +00:00 · 2026-08-27 16:48:01 -04:00 · 2026-08-27 16:20:03 -04:00 · 2026-08-27 16:16:43 -04:00 · 2026-08-27 16:15:34 -04:00
1 changed files with 15 additions and 3 deletions
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -656,8 +656,12 @@ Xrpld uses a linear workflow model that can be summarized as:
         are needed), being sure to sign each commit and update the
         commit message to include the PR number. You may be able to use
         a fast-forward merge for the first PR.
-      2. Push your branch.
-      3. Continue to [Making the release](#making-the-release) to update
+      2. Ensure that the release notes are ready:
+         - Create a dedicated section outlining the names of any new amendments.
+         - Credit issue reporters as best as possible.
+         - Share the initial release notes with the docs team.
+      3. Push your branch.
+      4. Continue to [Making the release](#making-the-release) to update
         the version number, etc.

      The workflow may look something like:
@@ -699,7 +703,7 @@ merged to `develop`. Be sure to include the commit ID.
 This includes, betas, and the first release candidate (RC).

 1. If you didn't create one [preparing the `develop`
-   branch](#preparing-the-develop-branch), Ensure there is no old
+   branch](#preparing-the-develop-branch), ensure there is no old
   `release-next` branch hanging around. Then make a `release-next`
   branch that only changes the version number. e.g.

@@ -986,6 +990,14 @@ git push --delete upstream-push master-next
 12. Open a PR to update the [API-CHANGELOG](API-CHANGELOG.md) and `API-VERSION-[n].md` with the changes for this release (if any are missing).
 13. Finally, [reverse merge the release into `develop`](#follow-up-reverse-merge).

+##### Post-Release Communication
+
+Once the release is tagged, published on GitHub, and merged:
+
+1. Coordinate with the docs team to open PRs in [xrpl-dev-portal](https://github.com/XRPLF/xrpl-dev-portal) to update the [XRPL documentation](https://xrpl.org) and publish release notes on the [XRPL Blog](https://xrpl.org/blog).
+2. Coordinate with the XRPLF Director of Communications to send an announcement message to notifications@xrpl.foundation.
+3. Update Altnet (Testnet) and Devnet servers (and deploy to Mainnet servers for stable releases).
+
 #### Special cases: point releases, hotfixes, etc.

 On occasion, a bug or issue is discovered in a version that already
Author	SHA1	Message	Date
rachelflynn	a56c8ccd74	Add new comms channel/process	2026-08-27 16:48:01 -04:00
rachelflynn	c98a472a91	Address duplicate list prefix Co-authored-by: xrplf-ai-reviewer[bot] <266832837+xrplf-ai-reviewer[bot]@users.noreply.github.com>	2026-08-27 16:20:03 -04:00
rachelflynn	87ad86806b	Merge branch 'develop' into rachelflynn-add-contribution-guidelines-from-wiki	2026-08-27 16:16:43 -04:00
rachelflynn	8359345b0b	Update CONTRIBUTING with missing details from the wiki release checklist As part of our rippled wiki migration efforts, the CONTRIBUTING doc has been updated to include any details or information that was included in the rippled Release Checklist (https://github.com/XRPLF/rippled/wiki/rippled-Release-Checklist) wiki page. Once merged, this page can be deleted.	2026-08-27 16:15:34 -04:00