Re: [i18n-drafts] Revert the changes to sitepage.js (#348)

> If we have a new version in the future, we can simply chain link to the latest, if that's what we're looking for.

ie. i'm not proposing that we change all .js files to point to the latest when we create a new version - each will point to the next only.  It's then trivial to find the latest, if that's what we need.  And when i say 'create a new version', i mean something that's not backwards compatible or where the name has changed and that needs to be reflected in new articles/pages.  We, of course, can still update a particular version using commits or PRs for less substantial changes.

GitHub Notification of comment by r12a
Please view or discuss this issue at using your GitHub account

Sent via github-notify-ml as configured in

Received on Monday, 28 February 2022 10:20:10 UTC