Add WARNING directive

src/doc/en/developer/advanced_git.rst

@@ -6,14 +6,16 @@
 Advanced Git
 ============
 
-**Sage development is scheduled to move to GitHub in February 2023.** The exact
-date will be announced in `<https://groups.google.com/g/sage-devel>`_. After
-the transition, some parts of this guide (especially those related with `the
-Sage Trac server <https://trac.sagemath.org>`_) will become obsolete and be
-updated according to the new workflow on GitHub. See our `transition guide from Trac to
-GitHub
-<https://github.com/sagemath/trac-to-github/blob/master/docs/Migration-Trac-to-Github.md>`_
-for the preliminary version of the workflow.
+.. WARNING::
+
+    **Sage development is scheduled to move to GitHub in February 2023.** The exact
+    date will be announced in `<https://groups.google.com/g/sage-devel>`_. After
+    the transition, some parts of this guide (especially those related with `the
+    Sage Trac server <https://trac.sagemath.org>`_) will become obsolete and be
+    updated according to the new workflow on GitHub. See our `transition guide from Trac to
+    GitHub
+    <https://github.com/sagemath/trac-to-github/blob/master/docs/Migration-Trac-to-Github.md>`_
+    for the preliminary version of the workflow.
 
 This chapter covers some advanced uses of git that go beyond what is
 required to work with branches. These features can be used in Sage

src/doc/en/developer/git_trac.rst

@@ -6,14 +6,16 @@
 Optional: Using the Git-Trac Command
 ====================================
 
-**Sage development is scheduled to move to GitHub in February 2023.** The exact
-date will be announced in `<https://groups.google.com/g/sage-devel>`_. After
-the transition, some parts of this guide (especially those related with `the
-Sage Trac server <https://trac.sagemath.org>`_) will become obsolete and be
-updated according to the new workflow on GitHub. See our `transition guide from Trac to
-GitHub
-<https://github.com/sagemath/trac-to-github/blob/master/docs/Migration-Trac-to-Github.md>`_
-for the preliminary version of the workflow.
+.. WARNING::
+
+    **Sage development is scheduled to move to GitHub in February 2023.** The exact
+    date will be announced in `<https://groups.google.com/g/sage-devel>`_. After
+    the transition, some parts of this guide (especially those related with `the
+    Sage Trac server <https://trac.sagemath.org>`_) will become obsolete and be
+    updated according to the new workflow on GitHub. See our `transition guide from Trac to
+    GitHub
+    <https://github.com/sagemath/trac-to-github/blob/master/docs/Migration-Trac-to-Github.md>`_
+    for the preliminary version of the workflow.
 
 Git is a separate project from trac, and the two do not know how to
 talk to each other. To simplify the development, we have a special

src/doc/en/developer/index.rst

@@ -4,14 +4,16 @@
 Welcome to the Sage Developer's Guide!
 ======================================
 
-**Sage development is scheduled to move to GitHub in February 2023.** The exact
-date will be announced in `<https://groups.google.com/g/sage-devel>`_. After
-the transition, some parts of this guide (especially those related with `the
-Sage Trac server <https://trac.sagemath.org>`_) will become obsolete and be
-updated according to the new workflow on GitHub. See our `transition guide from Trac to
-GitHub
-<https://github.com/sagemath/trac-to-github/blob/master/docs/Migration-Trac-to-Github.md>`_
-for the preliminary version of the workflow.
+.. WARNING::
+
+    **Sage development is scheduled to move to GitHub in February 2023.** The exact
+    date will be announced in `<https://groups.google.com/g/sage-devel>`_. After
+    the transition, some parts of this guide (especially those related with `the
+    Sage Trac server <https://trac.sagemath.org>`_) will become obsolete and be
+    updated according to the new workflow on GitHub. See our `transition guide from Trac to
+    GitHub
+    <https://github.com/sagemath/trac-to-github/blob/master/docs/Migration-Trac-to-Github.md>`_
+    for the preliminary version of the workflow.
 
 Everybody who uses Sage is encouraged to contribute something back to Sage at
 some point. You could:

src/doc/en/developer/manual_git.rst

@@ -6,14 +6,16 @@
 Using Git with the Sage Trac Server
 ===================================
 
-**Sage development is scheduled to move to GitHub in February 2023.** The exact
-date will be announced in `<https://groups.google.com/g/sage-devel>`_. After
-the transition, some parts of this guide (especially those related with `the
-Sage Trac server <https://trac.sagemath.org>`_) will become obsolete and be
-updated according to the new workflow on GitHub. See our `transition guide from Trac to
-GitHub
-<https://github.com/sagemath/trac-to-github/blob/master/docs/Migration-Trac-to-Github.md>`_
-for the preliminary version of the workflow.
+.. WARNING::
+
+    **Sage development is scheduled to move to GitHub in February 2023.** The exact
+    date will be announced in `<https://groups.google.com/g/sage-devel>`_. After
+    the transition, some parts of this guide (especially those related with `the
+    Sage Trac server <https://trac.sagemath.org>`_) will become obsolete and be
+    updated according to the new workflow on GitHub. See our `transition guide from Trac to
+    GitHub
+    <https://github.com/sagemath/trac-to-github/blob/master/docs/Migration-Trac-to-Github.md>`_
+    for the preliminary version of the workflow.
 
 Now we continue our introduction to git from :ref:`chapter-walkthrough`.
 We discuss how to push your local changes to a remote repository
@@ -163,10 +165,12 @@ repository, use these commands::
     [user@localhost sage]$ git remote add trac https://github.com/sagemath/sagetrac-mirror.git -t master
     [user@localhost sage]$ git remote set-url --push trac [email protected]:sage.git
 
-**Sage development is scheduled to move to GitHub in February 2023.** After the
-move, the Sage trac server [email protected]:sage.git will no longer be
-available, but all branches will be available (in read-only mode) on
-https://github.com/sagemath/sagetrac-mirror.git.
+.. WARNING::
+
+    **Sage development is scheduled to move to GitHub in February 2023.** After the
+    move, the Sage trac server [email protected]:sage.git will no longer be
+    available, but all branches will be available (in read-only mode) on
+    https://github.com/sagemath/sagetrac-mirror.git.
 
 Instead of ``trac`` you can use any other name you want, of course.
 To verify that it is set up correctly::

src/doc/en/developer/reviewer_checklist.rst

@@ -6,14 +6,16 @@
 The reviewer's check list
 =========================
 
-**Sage development is scheduled to move to GitHub in February 2023.** The exact
-date will be announced in `<https://groups.google.com/g/sage-devel>`_. After
-the transition, some parts of this guide (especially those related with `the
-Sage Trac server <https://trac.sagemath.org>`_) will become obsolete and be
-updated according to the new workflow on GitHub. See our `transition guide from Trac to
-GitHub
-<https://github.com/sagemath/trac-to-github/blob/master/docs/Migration-Trac-to-Github.md>`_
-for the preliminary version of the workflow.
+.. WARNING::
+
+    **Sage development is scheduled to move to GitHub in February 2023.** The exact
+    date will be announced in `<https://groups.google.com/g/sage-devel>`_. After
+    the transition, some parts of this guide (especially those related with `the
+    Sage Trac server <https://trac.sagemath.org>`_) will become obsolete and be
+    updated according to the new workflow on GitHub. See our `transition guide from Trac to
+    GitHub
+    <https://github.com/sagemath/trac-to-github/blob/master/docs/Migration-Trac-to-Github.md>`_
+    for the preliminary version of the workflow.
 
 All code that goes into Sage is peer-reviewed. Two reasons for this are:
 

src/doc/en/developer/trac.rst

@@ -6,14 +6,16 @@
 The Sage Trac Server
 ====================
 
-**Sage development is scheduled to move to GitHub in February 2023.** The exact
-date will be announced in `<https://groups.google.com/g/sage-devel>`_. After
-the transition, some parts of this guide (especially those related with `the
-Sage Trac server <https://trac.sagemath.org>`_) will become obsolete and be
-updated according to the new workflow on GitHub. See our `transition guide from Trac to
-GitHub
-<https://github.com/sagemath/trac-to-github/blob/master/docs/Migration-Trac-to-Github.md>`_
-for the preliminary version of the workflow.
+.. WARNING::
+
+    **Sage development is scheduled to move to GitHub in February 2023.** The exact
+    date will be announced in `<https://groups.google.com/g/sage-devel>`_. After
+    the transition, some parts of this guide (especially those related with `the
+    Sage Trac server <https://trac.sagemath.org>`_) will become obsolete and be
+    updated according to the new workflow on GitHub. See our `transition guide from Trac to
+    GitHub
+    <https://github.com/sagemath/trac-to-github/blob/master/docs/Migration-Trac-to-Github.md>`_
+    for the preliminary version of the workflow.
 
 Sometimes you will only want to work on local changes to Sage, for
 your own private needs.  However, typically it is beneficial to
@@ -42,9 +44,11 @@ trac server. Items on the server are called *tickets*, and anyone may
 search or browse the tickets. For a list of recent changes, just visit
 the :trac:`Sage trac timeline <timeline>`.
 
-**Sage development is scheduled to move to GitHub in February 2023.**
-All functions of our Trac server will be taken over by our main repository,
-https://github.com/sagemath/sage.
+.. WARNING::
+
+    **Sage development is scheduled to move to GitHub in February 2023.**
+    All functions of our Trac server will be taken over by our main repository,
+    https://github.com/sagemath/sage.
 
 
 .. _section-trac-account:
@@ -348,10 +352,12 @@ other tests that run on GitHub Actions.
   look at the log, especially if the patch buildbot did not give you
   the green blob.
 
-  **Sage development is scheduled to move to GitHub in February 2023.**
-  After the move, the patch buildbot will no longer be available; the three
-  workflows above are considered a full replacement. If you miss any features
-  of the patch buildbot, please report this in :trac:`33457`.
+.. WARNING::
+
+    **Sage development is scheduled to move to GitHub in February 2023.**
+    After the move, the patch buildbot will no longer be available; the three
+    workflows above are considered a full replacement. If you miss any features
+    of the patch buildbot, please report this in :trac:`33457`.
 
 The following are some other relevant issues:
 

src/doc/en/developer/walk_through.rst

@@ -6,14 +6,16 @@
 Sage Development Process
 ========================
 
-**Sage development is scheduled to move to GitHub in February 2023.** The exact
-date will be announced in `<https://groups.google.com/g/sage-devel>`_. After
-the transition, some parts of this guide (especially those related with `the
-Sage Trac server <https://trac.sagemath.org>`_) will become obsolete and be
-updated according to the new workflow on GitHub. See our `transition guide from Trac to
-GitHub
-<https://github.com/sagemath/trac-to-github/blob/master/docs/Migration-Trac-to-Github.md>`_
-for the preliminary version of the workflow.
+.. WARNING::
+
+    **Sage development is scheduled to move to GitHub in February 2023.** The exact
+    date will be announced in `<https://groups.google.com/g/sage-devel>`_. After
+    the transition, some parts of this guide (especially those related with `the
+    Sage Trac server <https://trac.sagemath.org>`_) will become obsolete and be
+    updated according to the new workflow on GitHub. See our `transition guide from Trac to
+    GitHub
+    <https://github.com/sagemath/trac-to-github/blob/master/docs/Migration-Trac-to-Github.md>`_
+    for the preliminary version of the workflow.
 
 This section is a concise overview of the Sage development process. In
 it, we will see how to make changes to the Sage source code and record
@@ -120,9 +122,11 @@ For the experts, note that the repository at
 `git.sagemath.org <http://git.sagemath.org>`_ is where development
 actually takes place.
 
-**Sage development is scheduled to move to GitHub in February 2023.**
-After the move, https://github.com/sagemath/sage.git will be the
-primary repository.
+.. WARNING::
+
+    **Sage development is scheduled to move to GitHub in February 2023.**
+    After the move, https://github.com/sagemath/sage.git will be the
+    primary repository.
 
 .. _section-walkthrough-branch:
 

src/doc/en/developer/workflows.rst

@@ -6,14 +6,16 @@
 Distributed Development
 =======================
 
-**Sage development is scheduled to move to GitHub in February 2023.** The exact
-date will be announced in `<https://groups.google.com/g/sage-devel>`_. After
-the transition, some parts of this guide (especially those related with `the
-Sage Trac server <https://trac.sagemath.org>`_) will become obsolete and be
-updated according to the new workflow on GitHub. See our `transition guide from Trac to
-GitHub
-<https://github.com/sagemath/trac-to-github/blob/master/docs/Migration-Trac-to-Github.md>`_
-for the preliminary version of the workflow.
+.. WARNING::
+
+    **Sage development is scheduled to move to GitHub in February 2023.** The exact
+    date will be announced in `<https://groups.google.com/g/sage-devel>`_. After
+    the transition, some parts of this guide (especially those related with `the
+    Sage Trac server <https://trac.sagemath.org>`_) will become obsolete and be
+    updated according to the new workflow on GitHub. See our `transition guide from Trac to
+    GitHub
+    <https://github.com/sagemath/trac-to-github/blob/master/docs/Migration-Trac-to-Github.md>`_
+    for the preliminary version of the workflow.
 
 Git is a tool to exchange commits (organized into branches) with other
 developers. As a distributed revision control system, it does not have