Do we need a patch release for possible ISO review changes?

[goneall]

Reference conversation in this pull request: #994 (comment)

If we get feedback requiring any changes to the model, we'll need to have some mechanism for a release.

I would suggest we create a milestone 3.0.2 for a patch release. We can base the changes off the support branch.

[bact]

This will mean that in the ISO publication it will be called "SPDX 3.0.2"?

Implication is all the IRIs have to be updated as well, since we have the PATCH version part in the IRI pattern.

[bact]

Or we can have a "3.0.1-iso" milestone?

"3.0.1-iso" name will indicate that this is a spec document that the textual content (for human consumption) is similar to the ISO publication -- but there is no difference in the semantic model from "3.0.1", so we can keep the same IRIs for terms.

This "3.0.1-iso" release will be published to the "3.0.1" spec website https://spdx.github.io/spdx-spec/v3.0.1/ - replacing the current "3.0.1".

Keeping the same IRIs and website will make it less work for updating tools/docs (some of them may hard coded the IRIs).

[bact]

Track changes since 3.0.1, see change log updates in #1001
(items with an asterisk * are changes that may go to support/3.0 branch as well)