@RX14 The benefit is, while the bugfixes for 0.23.0 where commited to 0.23.1, other improvements could be still be added into master. Otherwise you'd either have feature commits in 0.23.1 or other pull requests would be stalled until 0.23.1 is released.

We've always just merged everything into master from what I can see, if we want to have stable and bugfix branches, I think that merits further discussion. Mainly just so we can all get on the same page that these branches exist and the details of how they are used.

This went to a different branch because of what @straight-shoota said. In addition, the branch was re-created this week, because the Travis setup needs a branch pointing to a tagged commit to be pushed in order to build and update the docs. We could now delete release/0.23, but I don't think it matters.

As for what we were doing previously - I'm really not sure, haven't been that involved before. I totally agree we should agree on a way, and go with it. I think I (personally) some more time around here to have an informed opinion, anyway :)

:trup: