From 80f1c62aae6621d3da026f200828a8b443548e2d Mon Sep 17 00:00:00 2001
From: Lars Wirzenius <lwirzenius@wikimedia.org>
Date: Mon, 6 May 2019 17:59:55 +0300
Subject: Change: make bullet points into paragraphs

---
 ci-arch.html |  12 +++++-------
 ci-arch.mdwn |  39 +++++++++++++++++++--------------------
 ci-arch.pdf  | Bin 315026 -> 314960 bytes
 3 files changed, 24 insertions(+), 27 deletions(-)

diff --git a/ci-arch.html b/ci-arch.html
index 0985097..e175cbb 100644
--- a/ci-arch.html
+++ b/ci-arch.html
@@ -46,13 +46,11 @@
 </ul>
 </nav>
 <h1 id="introduction">Introduction</h1>
-<ul>
-<li><p>CI WG plans replacement of its current WMF CI system with one of Argo, GitLab CI, Zuul v3. These were selected in the first phase of the CI WG.</p></li>
-<li><p>We aim to do “continuous deployment”, not only “continous integration” or “continuous delivery”. The goal is to deploy changes to production as often and as quickly as possible, without compromising on the safety and security of the production environment.</p></li>
-<li><p>This document goes into more detail of how the new CI system should work, without (yet) discussing which replacement is chosen. A meta-level architecture if you wish.</p></li>
-<li><p>It is assumed as of the writing of this document that future CI will build on and deploy to containers orchestrated by Kubernetes.</p></li>
-<li><p>An important change is that we aim to change things so that as much as possible, all software deployments are to containers orchestrated by Kubernetes</p></li>
-</ul>
+<p>CI WG plans replacement of its current WMF CI system with one of Argo, GitLab CI, Zuul v3. These were selected in the first phase of the CI WG.</p>
+<p>We aim to do “continuous deployment”, not only “continous integration” or “continuous delivery”. The goal is to deploy changes to production as often and as quickly as possible, without compromising on the safety and security of the production environment.</p>
+<p>This document goes into more detail of how the new CI system should work, without (yet) discussing which replacement is chosen. A meta architecture if you wish.</p>
+<p>It is assumed as of the writing of this document that future CI will build on and deploy to containers orchestrated by Kubernetes.</p>
+<p>An important change is that we aim to change things so that as much as possible, all software deployments are to containers orchestrated by Kubernetes</p>
 <h1 id="requirements">Requirements</h1>
 <ul>
 <li><p>This chapter lists the requirements we have for the CI system and which we design the system to fulfil.</p></li>
diff --git a/ci-arch.mdwn b/ci-arch.mdwn
index 4f2b70d..004544e 100644
--- a/ci-arch.mdwn
+++ b/ci-arch.mdwn
@@ -29,26 +29,25 @@ abstract: |
 
 # Introduction
 
-* CI WG plans replacement of its current WMF CI system with one of
-  Argo, GitLab CI, Zuul v3. These were selected in the first phase of
-  the CI WG.
-
-* We aim to do "continuous deployment", not only "continous
-  integration" or "continuous delivery". The goal is to deploy changes
-  to production as often and as quickly as possible, without
-  compromising on the safety and security of the production
-  environment.
-
-* This document goes into more detail of how the new CI system should
-  work, without (yet) discussing which replacement is chosen. A
-  meta-level architecture if you wish.
-
-* It is assumed as of the writing of this document that future CI will
-  build on and deploy to containers orchestrated by Kubernetes.
-
-* An important change is that we aim to change things so that as much
-  as possible, all software deployments are to containers
-  orchestrated by Kubernetes
+CI WG plans replacement of its current WMF CI system with one of Argo,
+GitLab CI, Zuul v3. These were selected in the first phase of the CI
+WG.
+
+We aim to do "continuous deployment", not only "continous integration"
+or "continuous delivery". The goal is to deploy changes to production
+as often and as quickly as possible, without compromising on the
+safety and security of the production environment.
+
+This document goes into more detail of how the new CI system should
+work, without (yet) discussing which replacement is chosen. A meta
+architecture if you wish.
+
+It is assumed as of the writing of this document that future CI will
+build on and deploy to containers orchestrated by Kubernetes.
+
+An important change is that we aim to change things so that as much as
+possible, all software deployments are to containers orchestrated by
+Kubernetes
 
 # Requirements
 
diff --git a/ci-arch.pdf b/ci-arch.pdf
index 473aaf0..e1fd8c9 100644
Binary files a/ci-arch.pdf and b/ci-arch.pdf differ
-- 
cgit v1.2.1