Add versioning section & changelog #10
No reviewers
Labels
No Label
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: D-Net/openaire-graph-docs#10
Loading…
Reference in New Issue
No description provided.
Delete Branch "changelog"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Adds versioning scheme and changelog
@claudio.atzori and @thanasis.vergoulis please revise the "Versioning" section.
Also, a template for the changelog is added, but I think that would be the last part to add in the documentation website before release.
@ -5,0 +11,4 @@
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 the data sources change
"or the data sources change"
=>
"or major changes in data sources"
@ -5,2 +18,3 @@
<span className="todo">TODO</span>
This section will document all notable changes for each graph version.
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.
WIP: Add versioning sectionto Add versioning sectionAdd versioning sectionto Add versioning section & changelog@claudio.atzori @miriam.baglioni Can you check the content of this?
Do we already know which are the changes to be introduced in the next update?
Do you feel that we need to add something to the proposed changelog?
@ -7,0 +26,4 @@
- [Impact indicators](/data-model/entities/result#indicators) at the level of the Result
- [Beginner's kit](/downloads/beginners-kit) in the Downloads section
- New [relationship types](/data-model/relationships#relationship-types): `Reviews, IsReviewedBy, IsParentOf, IsChildOf, References, IsReferencedBy, IsNewVersionOf, IsPreviousVersionOf, HasVersion, IsVersionOf, Cites, IsCitedBy, IsVariantFormOf, IsOriginalFormOf, Obsoletes, IsObsoletedBy, IsContinuedBy, Continues, Documents, IsDocumentedBy, IsCompiledBy, Compiles, IsPartOf, HasPart, IsSourceOf, IsDerivedFrom, IsIdenticalTo`
@miriam.baglioni not sure if we want to list all new relationships here in the changelog.
Not sure either if I have included all new (and correct) relations, things may have changed since I wrote this.