Planning Release 3.1 and then 3.2

[luss]

Now that Mathieu has added support for pg17 and python 3.13 does it make sense to tag release 3.1?

Later in the fall Python 3.9 and PG13 will be EOL and I think in v3.2 we should drop support for them and add support for pg18.
Make sense?

[mfenniak]

Sounds good to me, both for the 3.1 release and the future plan. 3.1 would be mostly a documentation release for "official" updates to the supported PostgreSQL and Python releases -- #69 is the only functional change.

Mathieu has added support for pg17 and python 3.13

(No functional changes were required, just so that I'm not getting any unfair credit. 😉)

[mfenniak]

@luss I'll hold from merging #77 (PG18 beta support) if you want to tag 3.1 first. It's extremely low-risk for earlier PG versions though, so it could go in before you tag if you're OK with that.