Fixed #35999 -- Removed #django IRC channel references where appropriate.

Some references are replaced with links to the Django Discord server.

3 files changed, 7 insertions, 11 deletions

diff --git a/docs/internals/contributing/bugs-and-features.txt b/docs/internals/contributing/bugs-and-features.txt
index c59f79e6b8..d95ab96efd 100644
--- a/docs/internals/contributing/bugs-and-features.txt
+++ b/docs/internals/contributing/bugs-and-features.txt
@@ -17,7 +17,7 @@ Otherwise, before reporting a bug or requesting a new feature on the
   `searching`_ or running `custom queries`_ in the ticket tracker.
 
 * Don't use the ticket system to ask support questions. Use the
-  |django-users| list or the `#django`_ IRC channel for that.
+  |django-users| list or the `Django Discord server`_ for that.
 
 * Don't reopen issues that have been marked "wontfix" without finding consensus
   to do so on the `Django Forum`_ or |django-developers| list.
@@ -39,8 +39,8 @@ particular:
 * **Do** read the :doc:`FAQ </faq/index>` to see if your issue might
   be a well-known question.
 
-* **Do** ask on |django-users| or `#django`_ *first* if you're not sure if
-  what you're seeing is a bug.
+* **Do** ask on |django-users| or the `Django Discord server`_ *first* if
+  you're not sure if what you're seeing is a bug.
 
 * **Do** write complete, reproducible, specific bug reports. You must
   include a clear, concise description of the problem, and a set of
@@ -166,5 +166,5 @@ Votes on technical matters should be announced and held in public on the
 
 .. _searching: https://code.djangoproject.com/search
 .. _custom queries: https://code.djangoproject.com/query
-.. _#django: https://web.libera.chat/#django
 .. _Django Forum: https://forum.djangoproject.com/
+.. _Django Discord server: https://discord.gg/xcRH6mN4fa
diff --git a/docs/internals/contributing/index.txt b/docs/internals/contributing/index.txt
index b547e468b7..6ac5e884bd 100644
--- a/docs/internals/contributing/index.txt
+++ b/docs/internals/contributing/index.txt
@@ -31,9 +31,9 @@ a great ecosystem to work in:
   friendly and helpful atmosphere. If you're new to the Django community,
   you should read the `posting guidelines`_.
 
-* Join the `Django Discord server`_ or the `#django IRC channel`_ on
-  Libera.Chat to discuss and answer questions. By explaining Django to other
-  users, you're going to learn a lot about the framework yourself.
+* Join the `Django Discord server`_ to discuss and answer questions. By
+  explaining Django to other users, you're going to learn a lot about the
+  framework yourself.
 
 * Blog about Django. We syndicate all the Django blogs we know about on
   the `community page`_; if you'd like to see your blog on that page you
@@ -45,7 +45,6 @@ a great ecosystem to work in:
   build it!
 
 .. _posting guidelines: https://code.djangoproject.com/wiki/UsingTheMailingList
-.. _#django IRC channel: https://web.libera.chat/#django
 .. _community page: https://www.djangoproject.com/community/
 .. _Django Discord server: https://discord.gg/xcRH6mN4fa
 .. _Django forum: https://forum.djangoproject.com/
diff --git a/docs/internals/howto-release-django.txt b/docs/internals/howto-release-django.txt
index 131c60fec8..bedb1b8822 100644
--- a/docs/internals/howto-release-django.txt
+++ b/docs/internals/howto-release-django.txt
@@ -561,9 +561,6 @@ Now you're ready to actually put the release out there. To do this:
    message body should include the vulnerability details, for example, the
    announcement blog post text. Include a link to the announcement blog post.
 
-#. Add a link to the blog post in the topic of the ``#django`` IRC channel:
-   ``/msg chanserv TOPIC #django new topic goes here``.
-
 Post-release
 ============