Add versioning section & changelog #10
|
@ -2,5 +2,34 @@
|
|||
sidebar_position: 12
|
||||
---
|
||||
|
||||
# Changelog
|
||||
<span className="todo">TODO</span>
|
||||
# Versions & changelog
|
||||
|
||||
|
||||
## Versioning
|
||||
|
||||
Our versioning policy follows the [Semantic Versioning specification](https://semver.org/).
|
||||
In our case, given a version `MAJOR.MINOR.PATCH`, we increment the:
|
||||
|
||||
* `MAJOR` version when the data model of the Graph changes
|
||||
* `MINOR` version when the pipeline (e.g., different deduplication method, different implementation for an enrichment process) or major data sources change
|
||||
* `PATCH` version when the graph data are updated
|
||||
|
||||
|
||||
## Changelog
|
||||
|
||||
This section will document all notable changes for each graph version.
|
||||
|
||||
|
||||
|
||||
### v5.0.0
|
||||
|
||||
#### Added
|
||||
|
||||
- [Impact indicators](/data-model/entities/result#indicators) at the level of the Result
|
||||
- [Beginner's kit](/downloads/beginners-kit) in the Downloads section
|
||||
- New relation types. See the [complete set of relationship](/data-model/relationships#relationship-types)
|
||||
-
|
||||
#### Changed
|
||||
|
||||
- FOS and SDGs were removed from the [result subjects](/data-model/entities/result#subjects)
|
||||
- Measures were removed from the [result instance](/data-model/entities/result#instance)
|
||||
|
||||
|
|
Loading…
Reference in New Issue
This section documents notable changes between all subversions of a particular "MAJOR" version of the graph...
I do not know how to say this in a better way but you could find something I think ...
Why only subversions of a particular "MAJOR" version ?
At each time, I think that the changelog should list the changes of all past versions.
So, in each new release, we will only append the changes of the new version at this page and not show only the changes that it introduces.
What do you think abou that @claudio.atzori ?
This website is meant to document the public dump, which is currently published every six months. Hence the documentation website updates should go along with it, therefore it's changelog will grow release after release, i.e. dump after dump.
I would prefer to keep the history, appending new entries on each release, so that the readers will always have a glimpse of the evolution.
The level of detail to describe is going to be the tricky part here. I try to systethise these aspects in the ticket belonging to each content update round (see #8233 for example), but I feel like we could do better.