-
Notifications
You must be signed in to change notification settings - Fork 163
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
REL: v1.9.0 #1651
REL: v1.9.0 #1651
Conversation
@@ -1372,13 +1320,13 @@ authors: | |||
- given-names: Xiangrui | |||
family-names: Li | |||
website: https://github.com/xiangruili | |||
affiliation: The Ohio State University, United States of America |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not sure why the country was removed here
email: xiangrui.li@gmail.com | ||
- given-names: Yaroslav O. | ||
family-names: Halchenko | ||
website: http://www.onerussian.com | ||
orcid: https://orcid.org/0000-0003-3456-2493 | ||
affiliation: Dartmouth College, United States of America |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and here
@@ -849,7 +822,7 @@ authors: | |||
family-names: Zehl | |||
website: https://github.com/lzehl | |||
orcid: https://orcid.org/0000-0002-5947-9939 | |||
affiliation: Forschungszentrum Jülich, Jülich, 52428, Germany |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why was this shortened this much?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note for the contributor workflow PR: more changes than needed here
Leaving some comments in the PR that are more related to the contributors update worflow: not important for the release per se. |
This section was a bit unclear:
|
You are right @Remi-Gau it should mention that.
it is automatically "overwritten" by the GitHub Changelog Generator that we are using -- these steps have always been applied, as can be verified by checking the stable changelog: https://bids-specification.readthedocs.io/en/stable/CHANGES.html |
OK we should mention both points in the protocol then. |
cc @sjeung @JuliusWelzel FYI we'll release in around 5 days :-) |
ok. everyone stand back!!! we are merging!!! |
@sappelhoff maybe I missed something in the release protocols but when are the URLs in the changelog reverted to the github version rather than the RTD one? |
Next PR merge will trigger the changelog generator. |
this happens automatically (via the GH changelog generator) once the first PR is merged via a "create merge commit" (so not squash and not rebase) method (because that's what triggers the generator), see: bids-specification/.circleci/config.yml Line 110 in b0e6744
|
ha OK then I messed that up... |
The release protocol said commit to Probably worth fixing that in a separate PR. |
yes, together with the other items of note to change in the release protocol 👍 |
definitely a good thing I did this release then: allowed to clarify a few things |
No description provided.