Decide which versions/branches we want to update for DITA migration

[aneta-petrova]

The question is: Do we raise PRs that prepare our content for the migration only against master? Or is it expected that we will convert the previous versions as well?

So far, the PRs that have been merged under this milestone targeted master only: https://github.com/theforeman/foreman-documentation/pulls?q=is%3Apr+milestone%3A%22Prepare+for+DITA+migration+%28RH%29%22+is%3Aclosed which means that we're currently preparing only the future version for migration, not the ones that are already published.

[ekohl]

Given it's a moving target I'd only aim at master now and try to set up that continuous conversion pipeline. Once there's automation in place and you feel good about it you can also look at backporting it.

[aneta-petrova]

I'm afraid that experience so far suggests that backporting these changes might not be feasible. The PRs can be quite complex.

With my PRs, I decided to update master and 3.16.

Note that due to the technical solution implemented downstream, this might mean that RH will stop contributing to the earlier versions but I admit I'm not too sure.