search

sdmx-twg / sdmx-im

SDMX Information Model - UML model and functional description, definition of classes, associations and attributes
6 stars 3 forks source link

Create semanticVersioning.md #14

Closed dosse closed 1 year ago

dosse commented 4 years ago

Draft for #13

dosse commented 4 years ago

@stratosn Thanks! To answer your questions:

  1. What are the rules for deleting a version? Does it mean I can re-release the same version with different content?

    --> SemVer doesn't and cannot control such things. SemVer is about a contract between producers and consumers to which both adhere. Producers can freely delete (e.g. old outdated, unused) artefacts and upload new artefacts with new versions. However, a producer who deletes an artefact and then uploads a changed artefact with the same version, breaks the contract. And the clients will be unhappy because their consuming systems might get broken!

  2. We need to document (maybe in the technical notes?) the impact of all Artefact changes to semantic versioning.

--> Yes, we should list the changes that trigger major, minor and patch increases. This work remains to be done. I can start drafting this.

dosse commented 2 years ago

Hello @stratosn @egreising When could this request be merged and released? It was part of SDMX 3.0. Thanks.

dosse commented 2 years ago

Hi @stratosn @egreising, I do not have merge permissions in this repo. Would you be able to merge, please?

dosse commented 1 year ago

Hi @stratosn @egreising @sosna @agent96, I do not have merge permissions in this repo. Would you be able to merge, please?