Skip site navigation (1) Skip section navigation (2)

Re: [CORE] EOL for 7.4?

From: Scrappy <scrappy(at)hub(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Greg Sabino Mullane <greg(at)turnstep(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "pgsql-core(at)postgresql(dot)org" <pgsql-core(at)postgresql(dot)org>
Subject: Re: [CORE] EOL for 7.4?
Date: 2009-12-01 19:19:20
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
is there a reason why we can't follow a similar  4+3 life cycle?   
packagers r produced for the first 4y after .0 release and only source  
updates for year 5 thru 7?

if we could advertise such on the web, there would be no question as  
to when bug reports are accepted (n+4y) and when only security ... and  
after y7, it's just not supported at all ...

that would kill packager requirements on 8.0, 8.1 (as of last month)  
and totally kill 7.4 as of nov '10

Sent from my iPhone

On 2009-12-01, at 14:33, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> "Marc G. Fournier" <scrappy(at)hub(dot)org> writes:
>> What are RedHats "EOL" dates for the various releases?
> Dave already mentioned a public page for that:
> Based on track record so far, Red Hat isn't going to care about  
> anything
> but high-priority security issues towards the end of the life cycle,
> but theoretically I'm on the hook till 2014 for 8.1.x.
>            regards, tom lane

In response to


pgsql-hackers by date

Next:From: Josh BerkusDate: 2009-12-01 19:19:39
Subject: Re: Block-level CRC checks
Previous:From: Tom LaneDate: 2009-12-01 19:17:52
Subject: Re: Block-level CRC checks

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group