From 67c313b8b81e396a763396a922fe278234e1e445 Mon Sep 17 00:00:00 2001 From: cdecker Date: Tue, 6 Oct 2026 14:21:04 +0000 Subject: [PATCH] docs: remove references to IRC and retired c-lightning mailing list The c-lightning mailing list is being retired in favor of more frequently used communication channels (Discord, Telegram). Changelog-None. --- README.md | 8 +------- doc/contribute-to-core-lightning/release-checklist.md | 3 +-- 2 files changed, 2 insertions(+), 9 deletions(-) diff --git a/README.md b/README.md index c79d548ddf5e..351fe33a1604 100644 --- a/README.md +++ b/README.md @@ -25,7 +25,6 @@ Core Lightning (previously c-lightning) is a lightweight, highly customizable an [![Blockstream][blockstream-badge]][blockstream] [![Telegram][telegram-badge]][telegram] [![Discord][discord-badge]][discord] -[![Irc][IRC-badge]][IRC] This implementation has been in production use on the Bitcoin mainnet since early 2018, with the launch of the [Blockstream Store][blockstream-store-blog]. We recommend getting started by experimenting on `testnet` (`testnet4` or `regtest`), but the implementation is considered stable and can be safely used on mainnet. @@ -33,7 +32,7 @@ We recommend getting started by experimenting on `testnet` (`testnet4` or `regte ## Reach Out to Us Any help testing the implementation, reporting bugs, or helping with outstanding issues is very welcome. -Don't hesitate to reach out to us on the implementation-specific [mailing list][ml1], or on [CLN Discord][discord], or on [CLN Telegram][telegram], or on IRC at [dev][irc1]/[gen][irc2] channel. +Don't hesitate to reach out to us on [CLN Discord][discord], or on [CLN Telegram][telegram]. ## Getting Started @@ -214,15 +213,10 @@ Developers wishing to contribute should start with the developer guide [here](do [std]: https://github.com/lightning/bolts [prs-badge]: https://img.shields.io/badge/PRs-welcome-brightgreen.svg?style=flat [prs]: http://makeapullrequest.com -[ml1]: https://lists.ozlabs.org/listinfo/c-lightning [discord-badge]: https://badgen.net/badge/Discord/chat/blue [discord]: https://discord.gg/mE9s4rc5un [telegram-badge]: https://badgen.net/badge/Telegram/chat/blue [telegram]: https://t.me/lightningd -[IRC-badge]: https://img.shields.io/badge/IRC-chat-blue.svg -[IRC]: https://web.libera.chat/#c-lightning -[irc1]: https://web.libera.chat/#lightning-dev -[irc2]: https://web.libera.chat/#c-lightning [docs-badge]: https://readthedocs.org/projects/lightning/badge/?version=docs [docs]: https://docs.corelightning.org/docs [releases]: https://github.com/ElementsProject/lightning/releases diff --git a/doc/contribute-to-core-lightning/release-checklist.md b/doc/contribute-to-core-lightning/release-checklist.md index 6ea1644f65a6..b669bc67851f 100644 --- a/doc/contribute-to-core-lightning/release-checklist.md +++ b/doc/contribute-to-core-lightning/release-checklist.md @@ -94,8 +94,7 @@ Here's a checklist for the release process. 1. Edit the GitHub draft and include the `SHA256SUMS-v.asc` file. 2. Publish the release as not a draft. 3. Announce the final release on core-lightning's release-chat channel on Discord & Telegram. -4. Send a mail to c-lightning mailing list (`c-lightning@lists.ozlabs.org`), using the same wording as the Release Notes in GitHub. -5. Write release blog, post it on [Blockstream](https://blog.blockstream.com/) and announce the release on Twitter. +4. Write release blog, post it on [Blockstream](https://blog.blockstream.com/) and announce the release on Twitter. ## Post-release