From: | Arthur Silva <arthurprs(at)gmail(dot)com> |
---|---|
To: | Zenaan Harkness <zen(at)freedbms(dot)net> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: advocating LTS release and feature-train release cycles |
Date: | 2015-06-02 02:11:37 |
Message-ID: | CAO_YK0X2wsRrKOwgqEMTadjeR8vE9oFSsqs+hzcrJeWArb6zRQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sun, May 31, 2015 at 6:44 AM, Zenaan Harkness <zen(at)freedbms(dot)net> wrote:
> My comments advocating a (ubuntu/debian/linux-kernel/firefox) LTS
> release and feature-train release cycle:
> https://lwn.net/Articles/646740/
> https://lwn.net/Articles/646743/
>
> The parent article "PostgreSQL: the good, the bad, and the ugly":
> https://lwn.net/Articles/645020/
>
> My summary (from one of my comments above):
> "For PostgreSQL may be:
> - normal release every 3 or 4 months
> - LTS release every 12, 18 or 24 months
>
> This model provides:
> - higher frequency normal releases to
> a) showcase new features to the public and
> b) reduce pressure on developers wanting to not miss an "infrequent
> annual" release; and
>
> - lower frequency LTS releases to
> a) focus testing, stability and long term support resources
> b) satisfy "conservative/ enterprise" RDBMS admins
> "
>
> Regards,
> Zenaan
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
I'm surprised it got no replies so far.
In my opinion a twice a year schedule would be good.
The LTS would be every 2 or 4 releases. Keeping 2 LTS versions supported at
all moments.
Maybe this should be reposted to the hackers list?
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2015-06-02 02:27:42 | Re: advocating LTS release and feature-train release cycles |
Previous Message | Adrian Klaver | 2015-06-02 00:44:31 | Re: pl/python composite type array as input parameter |