From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: State of support for back PG branches |
Date: | 2005-09-27 03:54:49 |
Message-ID: | 4338C289.6040702@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom,
> Or, as you say, we could take the viewpoint that there are commercial
> companies willing to take on the burden of supporting back releases, and
> the development community ought not spend its limited resources on doing
> that. I'm hesitant to push that idea very hard myself, because it would
> look too much like I'm pushing the interests of my employer Red Hat
> ... but certainly there's a reasonable case to be made there.
Well, I think you know my opinion on this. Since there *are* commercial
companies available, I think we should use them to reduce back-patching
effort. I suggest that our policy should be: the community will patch
two old releases, and beyond that if it's convenient, but no promises.
In other words, when 8.1 comes out we'd be telling 7.3 users "We'll be
patching this only where we can apply 7.4 patches. Otherwise, better
get a support contract."
Of course, a lot of this is up to individual initiative; if someone
fixes a patch so it applies back to 7.2, there's no reason not to make
it available. However, there's no reason *you* should make it a priority.
--Josh
From | Date | Subject | |
---|---|---|---|
Next Message | Steve Atkins | 2005-09-27 03:57:39 | Re: State of support for back PG branches |
Previous Message | Joshua D. Drake | 2005-09-27 03:26:25 | Re: State of support for back PG branches |