Sylwester Arabas

@pjb7687 Apparently, we have already automation in place at Zenodo for archival of every release, so this is automatically done. The question is which version to reference in the paper?...

Thank you @sjfrasier! Let's create a PR for this change. Could you also supply a test code (and test file) that uses the added logic? Thanks, Sylwester

@sjfrasier to create a PR, you need to point Github to a branch where your modifications are stored: https://github.com/gnudatalanguage/gdl/compare so far, there is no PR from you registered yet

> Also, perhaps the Github Continuous Integration machines have an M1, so we could have also available an M1 version of the .DMG ? IIUC, no M1 support yet: https://github.com/actions/runner-images/issues/2187

the review has concluded long time ago, so closing this one

@a-v, I suggest we close this issue for now. The SUNDIALS and SuiteSparse static linking logic in our CMake files is not compliant with conda policy. Thank you all for...

@pjb7687 this commit is already published on Zenodo as a weekly release - we can just change its metadata: https://zenodo.org/record/6796032

@pjb7687 it's up to you, of course, but I wonder if having two Zenodo archives for the very same commit hash with differing "author lists" is not even more misleading?

Thank you, @pjb7687! I've checked the metadata against the `paper.md` (https://github.com/gnudatalanguage/gdl/blob/master/paper/paper.md) and clicked on all ORCID links - all seems to match. @gkthiruvathukal, please do proceed, thanks!

Thank you @gleb-kun! The notice is very true and valid (thanks @citibeth!), yet I'd say that it is still worth to improve the repo contents in such cases. PR would...