Question: current maintenance status and release cadence
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- postgresql, python
- Domain
- documentation, release
Research direction
Start by reviewing the status of release 0.31.0, the open pull requests, and regression issues #1327 and #1334. Done would require a maintainer-confirmed statement covering release plans, security fixes, maintenance mode, and possible reviewer or maintainer expansion.
Written by the indexing model from the issue text.
Description
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!
- Dominant language
- Python
- Stars
- 8.1k
- Forks
- 469
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 9
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MagicStack/asyncpg
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
MagicStack/asyncpg#1357 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
MagicStack/asyncpg#1354 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
MagicStack/asyncpg#1342 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 56/100
MagicStack/asyncpg#1340 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 28/100
MagicStack/asyncpg#1337 ·
All issues in MagicStack/asyncpg
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
learningequality/ricecooker#747 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
BSData/horus-heresy-3rd-edition#3171 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
run-llama/llama_index#23199 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
KhronosGroup/glTF-Blender-IO#2769 ·