I suggest that we document changes during development and mark important features or bug fixes in production releases. I find {fledge} epic to assist in this process and track the steps done via commit messages, so that they can be incorporated automatically in sections and modified later. This enhances trust of users and facilitates adoption and bug fixing + getting more brains working on reverse engineering Bruker OPUS.
I suggest that we document changes during development and mark important features or bug fixes in production releases. I find {fledge} epic to assist in this process and track the steps done via commit messages, so that they can be incorporated automatically in sections and modified later. This enhances trust of users and facilitates adoption and bug fixing + getting more brains working on reverse engineering Bruker OPUS.