Upcoming releases

[ml-evs]

After the flurry of activity at the recent workshop, here's my current plan for releases (will probably only affect @eimrek, @d-beltran). The idea is to avoid any major rewrites for ongoing PRs, but also to prevent @eimrek or me needing to worry too much about making breaking changes to things like config (and then forcing them upon @d-beltran).

v1.3.x - any remaining small patches/features like #2308 or otherwise (optional)
v1.4.x - #2310
v2.0 - #2313, plus any restructure I do in e.g. #2299, and any forward-ported changes that e.g., add trajectories from #2310

We can then treat 1.4.x as a supported version for anyone that needs to keep the old approach to config (by backporting e.g., security fixes an otherwise).

I also have no issue releasing v2.0 before v1.4, so we'll see which PRs get done first.

[eimrek]

Fine for me. but in principle #2310 doesn't really break anything (e.g. the current config will be exactly the same, and will be taken from the same sources if you don't provide it via python api).

But in general, fine to be added in 2.0 if you're planning to make that release anyway (esp as it's a fairly big refactor). But the PR is practically ready and tests are passing, so good to merge soon to avoid conflicts etc (maybe before #2299 ?).