Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to use the the zenodo script #1

Open
jdemel opened this issue Jun 28, 2022 · 4 comments
Open

How to use the the zenodo script #1

jdemel opened this issue Jun 28, 2022 · 4 comments

Comments

@jdemel
Copy link
Collaborator

jdemel commented Jun 28, 2022

@willcode I realized I have push access to this repo. Thus, I added an initial working version here.

This issue would be a good place to continue our discussion from gnuradio/gnuradio#5786 .

Most importantly, you brought up the idea to have separate files for each release line.

A zenodo dir would be a good place for the tools and user map. There could be one zenodo.json for each branch, e.g., zenodo-maint-3.10.json, or separate directories per branch, or ... ??? TBD: procedures to perform at release time.

I'd argue it'd suffice to add this to the latest release for now.

@willcode
Copy link
Member

Sure, we can try it out for the next 3.10 release in September. It should be close enough to main that the contributors are the same. I guess there's no reason to do this with main since it doesn't get formally released.

@jdemel
Copy link
Collaborator Author

jdemel commented Jun 29, 2022

I agree. The tool is not configured to do 2way comparisons. In that case I'd go for a different approach. Anyway, I'd suggest to start with 3.10 releases and later and maybe we can extend this tool to be more sophisticated in the future.

@dkozel
Copy link

dkozel commented Sep 26, 2022

The September release has been done!

@willcode
Copy link
Member

I did a run and copied the json file in the 3.10 branch before release. It might not be right but it's a start.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants