release branch version ahead of next and master

[catilac]

The master and next branches are marked as 3.4.0
The release branch is 3.5.0

Just trying to understand the reason behind it. I'm going to work off of the master branch.
Also wondering if I can help with any of this!

[ruuda]

Just trying to understand the reason behind it.

There is some context in #48 (comment). master is not currently in a state where I would feel confident releasing it, which is something I need to fix, but honestly I feel burned out on it. I made multiple attempts at a larger refactor in the next branch, but I never managed to push through to get it done.

In the meantime, I’ve been backporting smaller changes to the release branch and tagging and releasing from that.

I'm going to work off of the master branch.

If it’s a small change, you can build it on top of the release branch. If it’s a larger change — to be very honest, I can’t promise I will have the energy to review it. The thing that got me into this situation in the first place, was merging contributions that I wasn’t fully satisfied with, thinking “I’ll clean it up myself later,” which now many years later I still didn’t find the motivation to do.

Also wondering if I can help with any of this!

Thank you for the kind offer! More pull requests means more things for me to review, and although everybody is contributing with the best intentions, that takes energy. The thing that would help me the most is to have a co-maintainer, but that would need to be somebody who I trust to use good judgment, and you build that kind of trust by collaborating for a while first, which means more things for me to review … so I’m kind of stuck in this cycle.

[ruuda]

I’ve made release the default branch now to hopefully make things a bit clearer.