Git release tags?

[mxmilkiib]

Hi, I'd like to aggregate info about SoundBox on https://libreav.org/updates but the project hasn't used any git tags to note release versions yet. Might this be possible going forward, with changelog data in the message? This would then be available via /releases.atom on GH.

[mbitsnbites]

SoundBox doesn't have releases. It's incremental, continuous delivery without version numbers. While it would be possible to add tags, versions and release notes, it's not something that I have planned (plus it would add overhead that I'd like to avoid).

[vsariola]

I'll chime in and point out that there is hardly any "public API" that would benefit from versioning. The binary file format is mostly for internal use (I've had to parse it elsewhere but that's probably unusual) and SB already maintains backwards compatibility with old binary formats. Most people will be fine with the exported .js; when they get the js, they also grab the latest player. Users will probably optimize the player for a specific song (strip effects etc. remove unused oscillators), so after that point, they are completely detached from Soundbox anyway.

[mxmilkiib]

I thought it could be said of CI/CD that each build is a release, but whatever words or phrasing, it would be for the users and potential users to know what is new or different, though no worries if it's out of scope.