Finalise versioning in tags

[muratabur]

We now version the project with tags, so the "v1-dev" folder doesn't make sense, we will just call this schemas to avoid any confusion. A small semantic change, but will have breaking consequences if not handled properly.

Option 1:

• just swap out /v1-dev with /schemas and warn in the release notes

Option 2:

• keep backwards compatibility for a period.
• copy /v1-dev and /schemas and push updates to both for 6months/1year

Option 3:

• keep backwards compatibility but push new updates only to /schemas

I like 3 as it doesn't break things, but also doesn't encourage procrastination like 2 would.

[HubertBos]

HELLo

I want to suggest moving with Option 1. This will be painful at the beginning but later on, will fix itself rather than dragging something to infinity. ( Or option 2 if 1st one is not acceptable )

[muratabur]

Thanks everyone for comments (publicly and privately). It seems we can do all three in stages. Option 2 for 6 months, this will then become Option 3 which will then become Option 1.

To summarize:

1. Until June 2025 /v1-dev and /schemas will be identical, with new updates replicated across both.
2. From June 2025 onwards, /v1-dev will stop receiving new updates so any legacy dependencies will continue working.
3. At the end of 2025, /v1-dev will be deleted to complete the migration and legacy dependencies will stop working.