Poor v15 to v16 migration documentations

[qu8n]

How can we improve the documentation?

Hey team, I'm excited for all these updates, but the experience of updating to v16 has been challenging.

The current docs is mixing up v15 and v16.

For example, the latest docs page shows v15 and the installation steps lead to users installing v15, yet some example commands are those of v16:

Because v16 is a huge change, what do you think about having separate doc versions for v15 vs v16? Perhaps a navbar dropdown could let users select docs for v15 vs v16?

[Stratus3D]

Strange, somehow the version on the website didn't get updated properly. I will fix this evening.

[thomas-merz]

A better migration docu (and doing NO Breaking Changes in minor version at all) should have prevented #1895

[lachieh]

A better migration docu (and doing NO Breaking Changes in minor version at all) should have prevented #1895

@thomas-merz Anything pre-1.0.0 always has the potential to be a breaking change. This is clearly outlined in the spec. Semantic Versioning Spec, Item #4:

Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.