Changelog and branch merging

[jkbhagatio]

Previously, we discussed the idea of, for all 'aeon' repos, adhering to updating the changelog for every merge into 'main', and a squashed-rebased version of this merge into 'prod'. The 'prod' branch serves as a more readable, abridged version of the full history that makes up 'main'.

For 'aeon_experiments' this becomes tricky, given that we've moved away from the standard of having one 'main' branch in this repo, and instead have one 'main' branch per experiment in this repo, where the 'main' branch for an experiment is actually just the experiment name.

One option for this going forward is not to have 'prod' branches in 'aeon_experiments', but simply have auto-generated releases with auto- (+ optional manual-) generated changelog updates for every experiment branch.

Another option is to do this and still keep the notion of 'prod' branches.

[jkbhagatio]

Can you have releases per branch? I.e. releases that reference a branch maybe in the release name/tag?

[jkbhagatio]

We've agreed to:

• Drop version numbers from branch names
• For a given experiment branch, experimenters can choose stringency of checks for "clean" data (that gets copied to ceph) via e.g. Actions
  • E.g. requiring a tagged commit: <expname><SemVer>
  • E.g. changelog update

still considering whether or not to do 'prod' branches for "main" exp branches