Skip to content
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

add to release protocol #406

Closed
8 tasks done
franklin-feingold opened this issue Feb 7, 2020 · 0 comments
Closed
8 tasks done

add to release protocol #406

franklin-feingold opened this issue Feb 7, 2020 · 0 comments

Comments

@franklin-feingold
Copy link
Collaborator

franklin-feingold commented Feb 7, 2020

We have a release protocol that walks through how to process a BIDS release. As we have worked through this release process we have iterated and finetuned our process. Here are a few enhancements to this process.

The goal is for the release protocol to be a straight forward process.

Adding to a step:

  • Step 2: changing previous version links to their RTD render rather than to GitHub
  • Step 2: remove REL entries from the changelog
  • Merge step 5 into step 2. This will reduce the number of release commits.
  • Step 6: day of release ensure release branch most up to date
  • Step 4: fix get -> git
  • Step 4: prevent merges during release week, except for exceptional cases. These should be crucial to the specification and agreed upon by the BIDS maintainers. The exceptional cases can be expanded on. The initial cases: rendering of the specification is down, a crucial change affecting the entire specification
  • Step 10: upload new pdf to zenodo (cc @effigies for this process)
  • Step 11: sharing news of release on those identified platforms
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

No branches or pull requests

1 participant