Arthit Suriyawongkul
Arthit Suriyawongkul
I'm try to rethink and find what more logical is: 1. on every branches, set `canonical_version` to `latest` - `mkdocs.yml`: ```yaml - mike: canonical_version: latest ``` 2. on `development/v3.0` branch,...
- Note: We also need to decide on how to update the copyright information at the footer of the page as well. #930 - It is in the `copyright:` section...
> With this change, we will be advertising 3.0.1 as the latest; if we want to change that, we can do that with a slight change and some manual runs...
Discussed in 2024-07-16 Tech team meeting - ready to merge.
The deployment was [failed](https://github.com/spdx/spdx-spec/actions/runs/9986239266/job/27598397125) because v2.3 still occupied "latest" alias. Need to use `-u` option in `mike deploy` to override that. - To assign alias `latest` to `v3.0`, use this...
TODOs progress: - [x] Terms and definitions - [x] [NamespaceMap](https://github.com/spdx/spdx-3-model/blob/main/model/Core/Classes/NamespaceMap.md) - https://github.com/spdx/spdx-3-model/pull/821 - [x] [Annex B: Getting started writing SPDX 3 (Informative)](https://github.com/spdx/spdx-spec/blob/development/v3.0.1/docs/annexes/getting-started.md?plain=1) - https://github.com/spdx/spdx-spec/issues/975#issuecomment-2199010917 - [x] [Annex C: RDF object...
Confirmed. MkDocs (a tool that use to generate HTML for spec website) does not support strikethrough: https://www.markdownguide.org/tools/mkdocs/ Possible solutions are here: https://github.com/mkdocs/mkdocs/issues/868
Add support of strikethrough text in PR #997
Would be great anyway if we can fix the UI to have the dropdown immediately visible.
Probably can close this. PR #995 (merged) now publishes `development/v3.0.1` branch to https://spdx.github.io/spdx-spec/v3.0.1-draft/