Skip to content

[MISC] Update to Release_Protocol.md#126

Merged
chrisgorgo merged 3 commits intobids-standard:masterfrom
franklin-feingold:master
Jan 14, 2019
Merged

[MISC] Update to Release_Protocol.md#126
chrisgorgo merged 3 commits intobids-standard:masterfrom
franklin-feingold:master

Conversation

@franklin-feingold
Copy link
Copy Markdown
Collaborator

Updated figures and added 'v' in front of the version number

@chrisgorgo
Copy link
Copy Markdown
Contributor

I wonder if it would make more sense if the link pointed to the rendering (for example https://bids-specification.readthedocs.io/en/v.1.1.2/) instead of github. WDYT?

@franklin-feingold
Copy link
Copy Markdown
Collaborator Author

I think for releases that can be good and more useful pointing to the rendering because more than likely the reader will not need to see the github repo in that state, just the specification (if so one may navigate to it on the browser, it does not need to be the default). I have reflected that in my recent commit. (Only the first one has the '.' between v and version, for the future we'll follow github convention, i.e. v1.1.2)

@chrisgorgo chrisgorgo merged commit 78446d7 into bids-standard:master Jan 14, 2019
@sappelhoff sappelhoff changed the title Update to Release_Protocol.md [MISC] Update to Release_Protocol.md Sep 8, 2020
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

Successfully merging this pull request may close these issues.

2 participants