Working on #1836 has revealed that our current way to generate the changelog is error prone and suboptimal. The software we've been using has been looking for a new maintainer for some years, and due to an issue for our particular setup, we have furthermore pinned a version that is highly outdated.
Next to these technical issues, the BIDS maintainers believe that a more carefully curated changelog would be beneficial for the BIDS community trying to keep up with changes in BIDS.
Working on #1836 has revealed that our current way to generate the changelog is error prone and suboptimal. The software we've been using has been looking for a new maintainer for some years, and due to an issue for our particular setup, we have furthermore pinned a version that is highly outdated.
Next to these technical issues, the BIDS maintainers believe that a more carefully curated changelog would be beneficial for the BIDS community trying to keep up with changes in BIDS.
Potential options are:
... please chime in if you have ideas and/or concrete suggestions on how we should generate the changelog for the BIDS specification in the future.
Another issue with the current changelog generator is, that our repo is getting so big, that we run into API limitations: