Juha Kiviluoma

Moving to 0.8 after all in order to avoid merge issues.

Toolbox v0.9 will not bring big structural changes affecting the user. There may be visual changes (so image snapshots may become bit outdated), but I think it's fine to do...

The demand responses can be done, both EV and profile. There could be further methods, but no one has reported any great need for those. So, I'll mark them as...

https://github.com/spine-tools/SpineOpt.jl/issues/677 should be sub-task here. (And Manuel has already done something on that)

It feels to me like this shouldn't be about the min/up down time value set by the user or by the default. The constraint between two consecutive timesteps should be...

I just meant the same thing you said in your previous comment - trying to reply to Jody's question how to select the default. We don't need to worry about...

I like this structure. Seems to be quite close to that diataxis too.

In ines the term is actually `solve_pattern` which is better than just `solve` (I just forgot when writing that). Sometimes one `solve_pattern` defines multiple solves (e.g. rolling window). I wouldn't...

That wouldn't be needed if the IDE would differentiate (in color) between variables and parameters. I haven't really tried to set it up, but at least I don't see difference...

Yes, I fully agree. The temporal and stochastics can be just expressed with one index in stylized equations. Naturally separate part that explains what lies behind that index.