Hei,
I am working on the requirements for a DCAT-AP metadata exported for Dataverse software, and I was looking at the last published release 3.0.0 when I noted that some important files such as ranges.ttl SHACL is not part of that release, but in the master branch, under the folder 3.0.1/
Now, from the outside I cannot understand if 3.0.1 has been already released, and what important changes were introduced (no release notes).
It would be quite helpful and avoid confusion, if the repository offered more consistency and information on that front, Such as releases using github tags, release notes (this seemed to be the case until 3.0.0). Plus, the release and state that is being worked on at the moment.
I see the structure of including releases as folders, a bit unconventional and not taking advantage of git's potential pull releases.
Nothing urgent, but feel it could help to have a more consistent and familiar workflow towards the releases.
Cheers
Hei,
I am working on the requirements for a DCAT-AP metadata exported for Dataverse software, and I was looking at the last published release 3.0.0 when I noted that some important files such as ranges.ttl SHACL is not part of that release, but in the master branch, under the folder 3.0.1/
Now, from the outside I cannot understand if 3.0.1 has been already released, and what important changes were introduced (no release notes).
It would be quite helpful and avoid confusion, if the repository offered more consistency and information on that front, Such as releases using github tags, release notes (this seemed to be the case until 3.0.0). Plus, the release and state that is being worked on at the moment.
I see the structure of including releases as folders, a bit unconventional and not taking advantage of git's potential pull releases.
Nothing urgent, but feel it could help to have a more consistent and familiar workflow towards the releases.
Cheers