Conversation
|
This would at least need some cooperation from the website to redirect unknown versions to Personally I'd prefer to just leave the linked version explicit in the documentation - that gives more freedom to e.g. skip versions in the docs. IIRC it's also not yet decided whether we'll even continue this convention of having a separate doc page for every old version or whether we'll just use |
Of course, and I would like to point out that AegiSite is inherently much easier than the application itself to implement such workaround should issue arises.
For the same reason, I think that automating this update to an extent is better than adding a checklist item before every release, which tends to be forgotten easily and produce more workload to amend, and confusion among users (Considering how many new issue reports still use old version as comparison, and many didn't even notice the need to update). If the latter is eventually decided upon, we can implement a simple redirect on AegiSite, and all past versions will be on the same page. |
Superficial fix to provide more clear guidance for now with minimum extra components. Various non-canonical build have been considered to the best extend.