Changes

Page history
move upgrade process graph to the release-specific page authored by anarcat's avatar anarcat 
The graphic is now really out of date and not really useful anymore:
it shows that we are basically finished, but that we're also dragging
old machines around for quite a while.

We need to build a new dataset for bullseye now, and it doesn't make
much sense to keep all that old data around anyways.
Show whitespace changes
Inline Side-by-side
howto/upgrades.md
View page @ 785edf9a
...@@ -9,17 +9,6 @@ major release. Here are the currently documented ones: ...@@ -9,17 +9,6 @@ major release. Here are the currently documented ones:
* [buster](howto/upgrades/buster) * [buster](howto/upgrades/buster)
<figure>
<img alt="graph showing planned completion date, currently around july 2020" src="/howto/upgrades/predict-stretch.png" />
<figcaption>
The above graphic shows the progress of the migration between major
releases. It can be regenerated with the [predict-os](https://gitlab.com/anarcat/predict-os) script. It
pulls information from [howto/puppet](howto/puppet) to update a [CSV file](data.csv) to
keep track of progress over time.
</figcaption>
</figure>
### Team-specific upgrade policies ### Team-specific upgrade policies
Before we perform a major upgrade, it might be advisable to consult Before we perform a major upgrade, it might be advisable to consult
... ...
......