@vmarkovtsev Any chance in helping to push this out?
You seem to be one of the last active maintainers apart from @aminalaee 😅

@tomchristie Can we do anything about helping with the maintenance of this project?
I know a lot of people switched to sqlalchemy since they introduced async support, yet the databases library is still quite popular and there are very few active maintainers. I can help with reviews if there is no one else that has time for this.

@collerek - I can add you to @encode/maintainers and walk you through how to perform releases if you'd like?

@collerek - I can add you to @encode/maintainers and walk you through how to perform releases if you'd like?

@tomchristie Sure, happy to help :)

Okay - invite sent.

What needs doing at the moment?

We need to approve this PR and release next version: https://github.com/encode/databases/releases/edit/untagged-d723639e4d24f39254b7

Okay - does someone want to compile the release notes for 0.5.4?
(Even if that's just a comment on this thread, then I can help walk @collerek through the release process.)

Sure, I'll do that.

@tomchristie @collerek I think version 0.6.0 would make more sense here.

@tomchristie @collerek I think version 0.6.0 would make more sense here.

Not sure what is the encode policy here.
Normally when you reach 1.0.0 it's usually {breaking}:{feature}:{patch (bug fix)}.
But before 1.0.0 it's also often (fixed 0):{breaking}:{feature & bug fix}

What @collerek said, yup.
We'd also do a 0.x bump if a feature was big enough to be worth calling out.

Great, that makes sense. If it gets approved we can do the release.

Okay - I'm happy with this.

Right then @collerek you're welcome to merge this now.

Once it's merged done you can go to the draft release - https://github.com/encode/databases/releases/tag/untagged-0d04003928428cecab79 - edit it and hit "Publish".