Re: EOL for 7.4?

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Andreas 'ads' Scherbaum <adsmail(at)wars-nicht(dot)de>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: EOL for 7.4?
Date: 2009-11-12 22:11:09
Message-ID: 1258063869.2538.122.camel@jd-desktop.unknown.charter.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 2009-11-12 at 23:09 +0100, Andreas 'ads' Scherbaum wrote:
> On Thu, 12 Nov 2009 15:23:06 -0500 Andrew Dunstan wrote:
>
> > Andreas 'ads' Scherbaum wrote:
> > > On Tue, 03 Nov 2009 10:32:17 -0800 Josh Berkus wrote:
> > >
> > >
> > >> The same goes for other OSS projects. There's quite a few random OSS
> > >> apps which were created on PG 7.4 and have never offered their users an
> > >> upgrade path (Gnuworld comes to mind). They need an EOL announcement to
> > >> get them motivated to upgrade.
> > >>
> > >
> > > I know several customers who decided to move from 7.3 only after the
> > > EOL was announced. If 7.3 would not has see an EOL, they would never
> > > ever have moved to a newer version.
> > >
> >
> >
> > Nobody that I have seen is arguing against EOLing 7.4.
>
> True. But as Josh pointed out: some people/projects/companies need
> more "motivation" to actually consider an upgrade at all.

We have discussed in the past EOLing 7.4 I thought at the end of this
year. IMO 7.4 and 8.0 both need to be EOL. Can we just set a date and
call it good? March 31st sounds good.

Let's write up a quick announcement, add the letters EOL to the download
pages and call it good.

Joshua D. Drake

--
PostgreSQL.org Major Contributor
Command Prompt, Inc: http://www.commandprompt.com/ - 503.667.4564
Consulting, Training, Support, Custom Development, Engineering
If the world pushes look it in the eye and GRR. Then push back harder. - Salamander

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-11-12 22:31:11 Re: plpgsql GUC variable: custom or built-in?
Previous Message Alvaro Herrera 2009-11-12 22:09:58 Re: plpgsql GUC variable: custom or built-in?