| From: | Hannu Krosing <hannuk(at)google(dot)com> |
|---|---|
| To: | "David E(dot) Wheeler" <david(at)justatheory(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Joe Conway <mail(at)joeconway(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Policy for Abandoned Extensions |
| Date: | 2026-10-10 19:58:41 |
| Message-ID: | CAMT0RQSj6LX40Y82X9oSCVoBPqSLVGVoc6vjY9OSr+4DKyV-Jg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Oct 10, 2026 at 9:55 PM Hannu Krosing <hannuk(at)google(dot)com> wrote:
> Maybe we can add "end-of-life" versions to extensions?
>
> So if we have versions x.y.z-alpha and x.y.z-beta before x.y.z , maybe we
> can also have x.y.z-abandoned and/or x.y.z-unmaintained at the other end?
>
> So anyone installing such will habe better chance to notice.
>
That of course implies that the repository maintainer would be the one to
re-release the latest version with -unmaintained at the end when this
happens.
So when it is picked up again, the maintained version needs to get a
version pump
>
> And we could make them also sort after normal versions in pg_ssemver and
> in postgres_debversion and pg_debver :)
>
> ---
> Hannu
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David E. Wheeler | 2026-10-10 20:04:22 | Re: Policy for Abandoned Extensions |
| Previous Message | Hannu Krosing | 2026-10-10 19:55:54 | Re: Policy for Abandoned Extensions |