From 5bd2d256a96c92bf7beae22e507221013b689416 Mon Sep 17 00:00:00 2001 From: Kwankyu Lee Date: Thu, 5 Jan 2023 12:32:37 +0900 Subject: [PATCH] Add warning header to more places --- src/doc/en/developer/advanced_git.rst | 9 +++++++++ src/doc/en/developer/git_trac.rst | 11 ++++++++++- src/doc/en/developer/index.rst | 18 +++++++++--------- src/doc/en/developer/reviewer_checklist.rst | 9 +++++++++ src/doc/en/developer/workflows.rst | 9 +++++++++ 5 files changed, 46 insertions(+), 10 deletions(-) diff --git a/src/doc/en/developer/advanced_git.rst b/src/doc/en/developer/advanced_git.rst index cb5422cfb3a..a86504220fc 100644 --- a/src/doc/en/developer/advanced_git.rst +++ b/src/doc/en/developer/advanced_git.rst @@ -6,6 +6,15 @@ Advanced Git ============ +**Sage development is scheduled to move to GitHub in February 2023.** The exact +date will be announced in ``_. After +the transition, some parts of this guide (especially those related with `the +Sage Trac server `_) will become obsolete and be +updated according to the new workflow on GitHub. See our `transition guide from Trac to +GitHub +`_ +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 development, but are not really necessary to contribute to Sage. If diff --git a/src/doc/en/developer/git_trac.rst b/src/doc/en/developer/git_trac.rst index 25977e5ef23..f23ffd52cd3 100644 --- a/src/doc/en/developer/git_trac.rst +++ b/src/doc/en/developer/git_trac.rst @@ -6,6 +6,15 @@ Optional: Using the Git-Trac Command ==================================== +**Sage development is scheduled to move to GitHub in February 2023.** The exact +date will be announced in ``_. After +the transition, some parts of this guide (especially those related with `the +Sage Trac server `_) will become obsolete and be +updated according to the new workflow on GitHub. See our `transition guide from Trac to +GitHub +`_ +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 ``git trac`` subcommand for the git suite. Note that this really is @@ -40,7 +49,7 @@ do this by symlinking:: [user@localhost git-trac-command]$ ln -s `pwd`/git-trac ~/bin/ See the `git-trac README `_ for -more details. At this point you leave ``git-trac-command`` subdirectory, and only go +more details. At this point you leave ``git-trac-command`` subdirectory, and only go there whenever you need to update the ``git-trac`` command. diff --git a/src/doc/en/developer/index.rst b/src/doc/en/developer/index.rst index fecfdf99cce..18e2414d304 100644 --- a/src/doc/en/developer/index.rst +++ b/src/doc/en/developer/index.rst @@ -4,6 +4,15 @@ 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 ``_. After +the transition, some parts of this guide (especially those related with `the +Sage Trac server `_) will become obsolete and be +updated according to the new workflow on GitHub. See our `transition guide from Trac to +GitHub +`_ +for the preliminary version of the workflow. + Everybody who uses Sage is encouraged to contribute something back to Sage at some point. You could: @@ -20,15 +29,6 @@ reporting bugs to modifying and extending Sage and its documentation. We also discuss how to share your new and modified code with other Sage users around the globe. -**Sage development is scheduled to move to GitHub in February 2023.** The exact -date will be announced in ``_. After -the transition, some parts of this guide (especially those related with `the -Sage Trac server `_) will become obsolete and be -updated according to the new workflow on GitHub. See our `transition guide from Trac to -GitHub -`_ -for the preliminary version of the workflow. - Here are brief overviews of each part; for more details, see the extended table of contents below. No matter where you start, good luck and welcome to Sage development! diff --git a/src/doc/en/developer/reviewer_checklist.rst b/src/doc/en/developer/reviewer_checklist.rst index 271290e3dc8..6b3badd5bbf 100644 --- a/src/doc/en/developer/reviewer_checklist.rst +++ b/src/doc/en/developer/reviewer_checklist.rst @@ -6,6 +6,15 @@ The reviewer's check list ========================= +**Sage development is scheduled to move to GitHub in February 2023.** The exact +date will be announced in ``_. After +the transition, some parts of this guide (especially those related with `the +Sage Trac server `_) will become obsolete and be +updated according to the new workflow on GitHub. See our `transition guide from Trac to +GitHub +`_ +for the preliminary version of the workflow. + All code that goes into Sage is peer-reviewed. Two reasons for this are: - Because a developer cannot think of everything at once; diff --git a/src/doc/en/developer/workflows.rst b/src/doc/en/developer/workflows.rst index 1b89ecee1c0..6553b61f3f3 100644 --- a/src/doc/en/developer/workflows.rst +++ b/src/doc/en/developer/workflows.rst @@ -6,6 +6,15 @@ Distributed Development ======================= +**Sage development is scheduled to move to GitHub in February 2023.** The exact +date will be announced in ``_. After +the transition, some parts of this guide (especially those related with `the +Sage Trac server `_) will become obsolete and be +updated according to the new workflow on GitHub. See our `transition guide from Trac to +GitHub +`_ +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 the notion of a central server. The Sage trac server is just one of