You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As it is difficult to explain for me, so I'm setting up a test website here for illustration.
(The test website is marked with "DRAFT (TEST-WEBSITE)" at the top and the bottom to avoid confusion)
(Once we have 3.0.2, all of above will redirect instead to 3.0.2.
Once we have 3.1, "latest" will redirect to 3.1; but "v3.0*" will still redirect to the latest 3.0.x)
Only the latest patch versions for each minor version will be displayed on the dropdown list.
Is this something we imagine?
Or do we also need v3.0 (v3.0.0) in the dropdown as well?
(for v2, we only have v2.3 and v2.2.2)
Feel free to suggest something else. Comments will inform changes to PR #1015. Thank you.
Note: Since, from the above settings, "v3.0" will be use as an alias, if we still like to get access to the original v3.0 (v3.0.0) content, we can apply PR #994 to republish v3.0 as v3.0.0.
As it is difficult to explain for me, so I'm setting up a test website here for illustration.
(The test website is marked with "DRAFT (TEST-WEBSITE)" at the top and the bottom to avoid confusion)
We will use the URL of the test spec website https://bact.github.io/spdx-spec/
in place of
https://spdx.github.io/spdx-spec/ here for the purpose of discussion/demonstration.
Once 3.0.1 released, PR #1015 will made these following redirections:
1) Default redirection
If the user doesn't specify a version in the URL, we will bring them to the latest version:
https://bact.github.io/spdx-spec/ --> https://bact.github.io/spdx-spec/v3.0.1/
Do we like to have it like this?
(you can try clicking on these URLs)
https://spdx.github.io/spdx-spec/ currently redirects to https://spdx.github.io/spdx-spec/v3.0/
2) Alias
These following URLs will redirect to https://bact.github.io/spdx-spec/v3.0.1/ :
(Once we have 3.0.2, all of above will redirect instead to 3.0.2.
Once we have 3.1, "latest" will redirect to 3.1; but "v3.0*" will still redirect to the latest 3.0.x)
Do we like to have those URLs behave like that?
3) Versions available to choose from the UI
Only the latest patch versions for each minor version will be displayed on the dropdown list.
Is this something we imagine?
Or do we also need v3.0 (v3.0.0) in the dropdown as well?
(for v2, we only have v2.3 and v2.2.2)
Feel free to suggest something else. Comments will inform changes to PR #1015. Thank you.
Note: Since, from the above settings, "v3.0" will be use as an alias, if we still like to get access to the original v3.0 (v3.0.0) content, we can apply PR #994 to republish v3.0 as v3.0.0.
Additional requirements
The text was updated successfully, but these errors were encountered: