v3.0 released

[Valentin Lorentz]

Hello everyone,


I just released our long-awaited 3.0 version! You can find the release
notes at: https://github.com/codemeta/codemeta/releases/tag/3.0


Three tasks remain to complete the release:

* Accept https://github.com/codemeta/codemeta.github.io/pull/45 in order
to (hopefully) auto-update the crosswalks on the website. I don't have
push access to that repo so I can't do it
* Agree to a persistent context URL (I'll restart the discussion on this)
* Update documentation on the website


Valentin

[Daniel Garijo]

Thanks a lot!

Three comments: 

- the doi badge in the readme points to codemeta-2.0. Shall we update it to codemeta 3.0? Not sure if we can mint a new one, or maybe replace it with the w3id?

- The codemeta JSON file points to the context in 2.0. Shall we update it to 3.0?

- The Readme indicates that there are only 2 released versions of codemeta. Should we include the third too? Maybe update the citation too? (in this case, maybe we want a canonical citation for all versions)

I will add the redirection in w3id to the 3.0 JSON context.

Best,

Daniel

--
You received this message because you are subscribed to the Google Groups "codemeta-pmc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to codemeta-pmc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/codemeta-pmc/a87907e1-d88c-cd2c-de58-e63e3ca1ba84%40inria.fr.
For more options, visit https://groups.google.com/d/optout.

[jo...@nceas.ucsb.edu]

I you want a new DOI, I can create a new one in the same DOI prefix as the others, and just need a release tag to point it at. And yes, I think we shoiuld update all of those places to update to the 3.0 identifiers.

Matt

[Valentin Lorentz]

DOIs aren't suitable to serve JSON-LD contexts anymore, see:
https://github.com/codemeta/codemeta/issues/278

We could mint a new one to reference Codemeta without using it as
context URL, but it may confuse people.

[Tom Morrell]

Congrats on the release! It looks like something went wrong with the merge from the `develop` to the `master` branch though, as I’m seeing pre-merge content at https://github.com/codemeta/codemeta. Maybe we take this opportunity to switch from ‘master` to `main` as the default branch name?

What should we tag issues with for the next release? v3.1 and v4?

Thanks,

Tom Morrell | Research Data Specialist | Caltech Library

caltech.zoom.us/my/tmorrell | 626-395-3827 | data.caltech.edu

To view this discussion on the web visit https://groups.google.com/d/msgid/codemeta-pmc/e3cae36e-089f-fd0a-797d-1c85cc7fb4b9%40inria.fr.

[Valentin Lorentz]

My bad. Fixed now

On 15/07/2023 01:13, Tom Morrell wrote:
> Congrats on the release! It looks like something went wrong with the merge from the `develop` to the `master` branch though, as I’m seeing pre-merge content at https://github.com/codemeta/codemeta. Maybe we take this opportunity to switch from ‘master` to `main` as the default branch name?
>
> What should we tag issues with for the next release? v3.1 and v4?
>
> Thanks,
>

> Tom Morrell <> | Research Data Specialist | Caltech Library <https://library.caltech.edu/>
> <http://caltech.zoon.us/tmorrell>caltech.zoom.us/my/tmorrell <http://caltech.zoom.us/my/tmorrell> | 626-395-3827 | data.caltech.edu <https://data.caltech.edu/>

>
>> On Jul 13, 2023, at 2:12 PM, Valentin Lorentz <valentin...@inria.fr> wrote:
>>
>> DOIs aren't suitable to serve JSON-LD contexts anymore, see: https://github.com/codemeta/codemeta/issues/278
>>
>> We could mint a new one to reference Codemeta without using it as context URL, but it may confuse people.
>>

[Morane GRUENPETER]

Hello all,

Very exciting to see the v3.0 arrival and the CodeMeta project moving forward. 

Thank you Valentin for the v3.0 release and email to the PMC! Great job.

Thank you  Matt, Daniel and Tom for your vigilance, continue reviewing the v3.0, this is the best way to improve its quality.

We will take the time during August to review the release and attend to the pmc comments. Feel free to tag relevant PRs that support the v3.0 with v3.1.

PRs with additional vocabulary terms should be tagged v4.0. 

We will communicate about the new release only at the beginning of September to take the time to review the comments, review the codemeta-generator and existing documentation. Feel free to open issues or discussions for that. Also feel free to respond here with more administrative subjects;-)

Thank you all for the excellent collaboration.

And again congrats Vlorentz for getting us to the finish line.

Kind regards,

Morane

*From the French Alpes*

To view this discussion on the web visit https://groups.google.com/d/msgid/codemeta-pmc/6a6effeb-b079-1adf-8a42-26817776cb0d%40inria.fr.