Ewout ter Hoeven

> 1. the future behavior is the desired behavior, so in principle, we don't need to do anything. Great, moved to the _No action needed_-list. > 3 and 4. No...

> So another option is to require 1.4.6 and just move to sobol. I think this is the most future-proof option. Do we needs some sort of validation that it...

@quaquel Was no time in the meeting, could you take a look at this?

@quaquel Awesome! I rewrote the changelog a bit, let me know what you think. The rest looks good! I also added that this is the lastrelease series with Python 3.8...

Furthermore, do you want to do something with #82 and #102 before release?

They should really go straight for 3.11, that's 20%+ compute time saved right there. Note that current versions can still keep running on 3.8, the version bump will only apply...

> I am checking 1.4.6 right now but there sobol is not yet available. It should be in it: https://github.com/SALib/SALib/releases/tag/v1.4.6 But we can fix it in a 2.3.1 if preferred....

Perfect, could you cherry-pick a12c819 to a new PR?

Yes, let's release! I already like that we have [documented this](https://github.com/quaquel/EMAworkbench/blob/master/CONTRIBUTING.md#releases). Do you want to do it?

Yes, that would be awesome! Additionally awesome would it be if you can run all notebooks in your repository, to check for depreciation warnings and such. @yaananth do you think...