Replies: 1 comment 1 reply
-
It happens that I've just finished to fix bitrotten CI and to close a couple of complex tickets, so the next release is imminent. In general, no, there is no guaranteed release cadence for psycopg. It depends very much on the bugs being fixed and by my personal workload. Since 3.1.18 release we have made a considerable amount of work to prepare 3.2, while in 3.1 there weren't critical bugs open, and still there was a lot of work done there too to get to 3.1.19. At the moment I have paying customers which require attention. Free software pays very little, therefore it can only take a proportional amount of time. This sentence is absolutely false, by the way: it takes my attention and my time much more than what it pays financially. Then you meet people like the dude in #807 which makes me think that giving away any work for free is not a good idea and maintenance should be limited to funded work. If your company requires a defined release cadence you are welcome to fund the project accordingly. |
Beta Was this translation helpful? Give feedback.
-
Is there any information on psycopg's release cadence? The last release was on Febuary 4th, over 3 months ago.
Beta Was this translation helpful? Give feedback.
All reactions