> It is indeed possible to create an entirely distinct
> set of pages for each version, where a version would
> be selectable via a dropdown menu. Alternatively, a
> single set can be used where its pages are annotated
> wherever there are version differences.
Thank you for your research.
> Is the development activity high enough to warrant a separate documentation set?
I do not know.
> If it is, then having a guide full of annotations (and possibly screenshots and
> code samples) may not be the way to go. You also need to consider future versions
> as well (or use a combination of these ideas: a "version" that covers, say, 20.04
> and 22.04).
> As an aside, I seem to recall backports not being done to the Server Guide,
> which can mislead readers. Keeping a single set would sidestep that issue.
Update publications of previous LTS Ubuntu Serverguides has been very infrequent.
> If you choose the first option (dropdown menu) I can follow up with
> instructions on how to get that done.
The stakeholders are the Servergguide contributors, which I think is mainly the server team. Myself, I am okay with either solution.
Peter wrote:
> It is indeed possible to create an entirely distinct
> set of pages for each version, where a version would
> be selectable via a dropdown menu. Alternatively, a
> single set can be used where its pages are annotated
> wherever there are version differences.
Thank you for your research.
> Is the development activity high enough to warrant a separate documentation set?
I do not know.
> If it is, then having a guide full of annotations (and possibly screenshots and
> code samples) may not be the way to go. You also need to consider future versions
> as well (or use a combination of these ideas: a "version" that covers, say, 20.04
> and 22.04).
> As an aside, I seem to recall backports not being done to the Server Guide,
> which can mislead readers. Keeping a single set would sidestep that issue.
Update publications of previous LTS Ubuntu Serverguides has been very infrequent.
> If you choose the first option (dropdown menu) I can follow up with
> instructions on how to get that done.
The stakeholders are the Servergguide contributors, which I think is mainly the server team. Myself, I am okay with either solution.