Question: current maintenance status and release cadence

還沒有人認領這個 Issue。

Hey, first off, thanks for asyncpg. We run it in production and it's
been rock solid.

Just trying to get a read on where the project stands. Last release was
0.31.0 back in November, and there's a decent pile of open PRs that
haven't been looked at in a while. A few issues about 0.31.0 regressions
(#1327, #1334) are also sitting unanswered.

Not a complaint at all, I know this is unpaid work. I just need to know
what to plan around: is asyncpg still something we should build on for
the next few years, or should we start thinking about alternatives?

A couple of questions:

- Is another release likely at some point?
- Are security fixes still happening even if feature work is on pause?
- If review time is the bottleneck, are you open to bringing in more
reviewers or maintainers? There seem to be people around who'd be
interested.

Totally fine if the answer is "maintenance mode only", it would just be
useful to have that written down somewhere so people know what to expect.

Thanks!

先檢視 release 0.31.0 的狀態、開啟的 pull request，以及回歸問題 #1327 和 #1334。完成的條件是需要有一份經 maintainer 確認的聲明，涵蓋 release 計畫、安全性修正、維護模式，以及可能擴充 reviewer 或 maintainer 的安排。

由索引模型根據 Issue 內容生成。