-
Notifications
You must be signed in to change notification settings - Fork 339
FIX: update switcher list #1009
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This works for me - though my feeling is that we should only include, say, the latest versions in the last 3 minor series (so latest/
, v0.10.1
, v09.0
, and v0.8.1
). We want to strongly encourage people to keep up with the latest releases.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me - maybe we should wait a day or two to make sure nobody else on the team wants to keep some other version in the list?
My feeling is that 5 versions is a good number to keep in the menu. Can you add to the "how to make a release" docs that when adding the new version to the One option I've heard suggested elsewhere is to have a link "older versions" that goes to an orphan HTML page that lists all the versions. I'm neutral as to whether to do that; I like the completeness but also feel it's rarely going to be useful. |
+1 on last 5 versions from me (though I think we should stick to "the latest patch release within minor releases" |
yes, I was thinking that too (but didn't make it clear) |
I updated the list with the last 5 + dev branch |
#1008
wait for confirmation of the list in the issue