Release/0.15.0

[PGijsbers]

According to new release cycle, as I understand it:

• merge this into develop
• release on GitHub (adding tag to develop commit)
• build and release on PyPI

[eddiebergman]

Nothing that stands out but I would ask more clarification on the release/workflow. Is it the case of develop is the main branch to make branches off of, and then main just exists to hold the currently released version seperate from develop?

[PGijsbers]

then main just exists to hold the currently released version seperate from develop?

That's what used to be the practice (not sure why - it's not like people are working on dev while a release is being prepared on main). But there was some slip up in one of the previous merges which means that now we can't fast-forward merge into main anymore either, so now it wasn't even updated for 0.14.2.

[eddiebergman]

Ran into the same issue with Auto-sklearn. The benefits of the main/develop was being able to do hot-fixes while a bigger feature was being worked on for develop, but I havn't found it super helpful otherwise.