lc-power-match-baluns ready to publish

[thePlasm]

I have committed to lc-power-match-baluns, which is now ready for a release. I have merged everything from the draft branch to the main branch (and squashed all of the commits). The draft branch still seems to be the default branch. I am requesting for the main branch to be made the default branch, the draft branch to be deleted, and for the repository to be made public.

Regards,
Rasmus

[zerothi]

I have changed default branch and changed to public, I believe you should be able to delete the draft branch, it would be instructive for me if you could check it works. :)

[thePlasm]

When I published the test repo to the sandbox, it showed me the record status (i.e. if it was processing, failed or published). Would it be possible for you to check if the record has failed in the dtudk Zenodo?

[thePlasm]

Dear Nick, I have made a new release, which has worked. It seems that zenodo did not pick up v1.0.0. I have also published the repo to PyPI.

I have noticed that while the .zenodo.json reflects the collaborators and thesis supervisors accurately, the way that this is presented on the Zenodo record is misleading (incorrect order and duplicate authors). I will confirm with my supervisors regarding how this should appear and adjust the .zenodo.json accordingly. Is it possible to amend the metadata of an existing version, or would I need to create a new release to rectify this? Sorry for this mistake and thanks for your help.

[thePlasm]

Regarding my previous comment, I have confirmed that the supervisors in the Zenodo record should reflect the updated .zenodo.json file (i.e. with the thesis_supervisors field removed and with only Jan and Vitaliy shown (in that order)). Would it be possible for the initial release on Zenodo to be rectified to reflect this or would I need to make a new release to amend the record's metadata?

[zerothi]

Done, take a look.
One should always be able to change metadata, but new/changed files, requires a new release.

[thePlasm]

Thanks for your help. I think that is all for publishing this repo. I will close this issue.