@@ -10,15 +10,14 @@ assume the base platform includes Linux running on each server and
1010switch, plus Docker, Kubernetes, and Helm, with SD-Fabric controlling
1111the network.
1212
13- While we could take a narrow view of Lifecycle Management, and assume
14- the software we want to roll out has already gone through an off-line
15- integration-and-testing process (this is the traditional model of
16- vendors releasing a new version of their product), we take a more
17- expansive approach that starts with the development process—the creation
18- of new features and capabilities. Including the “innovation” step
19- closes the virtuous cycle depicted in :numref: `Figure %s<fig-cycle> `,
20- which the cloud industry has taught us leads to greater *feature
21- velocity *.
13+ Traditionally, software would go through an offline integration and
14+ testing process before any effort to roll it out in production could
15+ begin. However, the approach taken in most modern cloud environments,
16+ including ours, is more expansive: it starts with the development
17+ process—the creation of new features and capabilities. Including the
18+ “innovation” step closes the virtuous cycle depicted in
19+ :numref: `Figure %s<fig-cycle> `, which the cloud industry has taught us
20+ leads to greater *feature velocity *.
2221
2322.. _fig-cycle :
2423.. figure :: figures/Slide9.png
0 commit comments