[INFRA] Update release protocol: PDF upload to Zenodo

[sappelhoff]

• closes Publish list of authors with the PDF of the specifications on Zenodo #1554

cc @Remi-Gau @effigies

[sappelhoff]

After the 1.9 release here and publishing the 1.9.0 GitHub release on https://github.com/bids-standard/bids-specification-pdf-releases, the Zenodo record for that repo will become active.

I will then update CITATION.cff to include a second identifier like this first one, but detailing the PDFs for versions 1.9.0 and higher

[Remi-Gau]

@sappelhoff
Can you locate the release for https://github.com/bids-standard/bids-specification-pdf-releases on zenodo: I made a release but I cannot find it

[sappelhoff]

Mmmh seems like something went wrong, let me check -- I'll let you know!

[Remi-Gau]

Well I cannot see the bids matlab release either so maybe I am just too old to understand how to click buttons in a GUI.

[sappelhoff]

I think this may be on Zenodo 🤔 anyways, I deleted your tag and release and re-did them after resetting all webhooks on zenodo and github --> now it has worked.

[Remi-Gau]

Nice

[Remi-Gau]

by the way: minor detail but our release are vX.Y.Z, no? At least from looking at the github tags on the bids spec repo.

I think the bids spec pdf release does not have the leading "v".

[sappelhoff]

you are right. Why do we prepend a v? that's not really in https://semver.org/, is it?

I think I would prefer dropping the v prefix from now on everywhere

[Remi-Gau]

I have seen this v prefix in a few places that use "semver" but that's not systematic.
Fine with me dropping the v from now on. Most people will get it.

[sappelhoff]

@Remi-Gau you could merge this PR via a "Create a merge commit" method to autofix the changelog (ref #1658):

I actually noticed some items like #1483 missing from the changelog, because "the most recent PR before the release wasn't merged via a Merge commit"

bids-specification/Release_Protocol.md

Lines 11 to 14 in b0e6744

	NOTE: Before you start a release, you have to ensure that the automatically generated changelog is
	**up to date**. See the relevant [section in CONTRIBUTING.md](CONTRIBUTING.md#how-is-the-changelog-generated)
	for further information. In practice this means ensuring that the most recently merged pull request was
	merged into the `master` branch using the "Merge commit" option.

this is obviously just a shortcoming in our release protocol (and the way we trigger the github changelog generator), so please just read this as a note to all of us that we should improve the docs on that (and maybe even the process itself) when we find time.