about summary refs log tree commit diff
diff options
context:
space:
mode:
authorflip1995 <philipp.krones@embecosm.com>2022-04-17 20:40:09 +0200
committerPhilipp Krones <hello@philkrones.com>2022-06-06 16:17:57 +0200
commitc9cbead65672bd1606e630cddbbcf158d164d3e7 (patch)
tree270ed5c87fcf603597b51ec07f90150c5c250a8d
parentb37d24f7ff281d8887aa253caf4a22b4512efd99 (diff)
downloadrust-c9cbead65672bd1606e630cddbbcf158d164d3e7.tar.gz
rust-c9cbead65672bd1606e630cddbbcf158d164d3e7.zip
Book: Add infrastructure description
-rw-r--r--book/src/development/infrastructure/README.md18
1 files changed, 18 insertions, 0 deletions
diff --git a/book/src/development/infrastructure/README.md b/book/src/development/infrastructure/README.md
index 2b4e5f6a6ef..3b2a2539996 100644
--- a/book/src/development/infrastructure/README.md
+++ b/book/src/development/infrastructure/README.md
@@ -1 +1,19 @@
 # Infrastructure
+
+In order to deploy Clippy over `rustup`, some infrastructure is necessary. This
+chapter describes the different parts of the Clippy infrastructure that need to
+be maintained to make this possible.
+
+The most important part is the sync between the `rust-lang/rust` repository and
+the Clippy repository that takes place every two weeks. This process is
+described in the [Syncing changes between Clippy and `rust-lang/rust`](sync.md)
+section.
+
+A new Clippy release is done together with every Rust release, so every six
+weeks. The release process is described in the [Release a new Clippy
+Version](release.md) section. During a release cycle a changelog entry for the
+next release has to be written. The format of that and how to do that is
+documented in the [Changelog Update](changelog_update.md) section.
+
+> _Note:_ The Clippy CI should also be described in this chapter, but for now is
+> left as a TODO.