Section links in migration-2.0.md point to PER-CS 3.0 instead of 2.0

[rodrigoprimo]

While working on an upcoming PR suggesting a change to migration-2.0.md, I noticed that the section headings link to the unversioned URL for the spec (https://www.php-fig.org/per/coding-style/). This URL currently serves PER-CS 3.0. I believe they should point to sections in the PER-CS 2.0 spec file (https://github.com/php-fig/per-coding-style/blob/2.0.0/spec.md). Is this correct or am I missing something?

Happy to create a PR to update the links if this is indeed an issue.

[Crell]

I think there's a valid question here: Do we want to link to "what you should be doing" (latest version) to review in total, or to the possibly-outdated "here's the one change?"

Thinking forward into the future where we have 6 different older versions, linking to the specific version could lead someone to try to adopt a now-outdated rule. OTOH, linking to the current version could get really complicated if we ever make more substantial changes to the spec, like reorganizing things or more BC-breaking changes.

I'm not sure here. Open to thoughts from the WG.

[rodrigoprimo]

Thanks for your input. Both concerns are fair, and I'm happy to defer to what you and the rest of the WG prefer.

Thinking forward into the future where we have 6 different older versions, linking to the specific version could lead someone to try to adopt a now-outdated rule.

This is something I hadn't considered. To be honest, I don't see this as a big concern, since I think the migration document itself mitigates the risk. Specifically, migration-2.0.md is scoped to the 1.0 to 2.0 transition, so a reader using it is explicitly looking at that upgrade.

OTOH, linking to the current version could get really complicated if we ever make more substantial changes to the spec, like reorganizing things or more BC-breaking changes.

This is the main concern I had in mind when I opened this issue.