Open s-makin opened 1 year ago
Long live Cosmic!
I think the package version names being out of date is fine-ish, as long as the commands and response from commands still match. Otherwise, the package will be out of date each and every cycle.
However, if we make it a goal to always keep the version names up to date that would be a good commit for first-time contributors to re-run the commands with the new versions perhaps?
What about a task to update it - across all the documents? - at the beginning of a cycle?
Could we do it "automagically" with Mark Down? Setting a variable ... mmm , I think we don't automatically generate the UMH
The PackageMerging.md page uses Cosmic and Disco in the examples throughout - at one point it even says "Disco is not available yet at time of writing", which is why I first noticed this. This makes the entire page feel out of date and neglected.
I think that if it's possible, these examples should be made as generic as possible (or at least brought up to date with e.g. Jammy/Focal).