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

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: State of support for back PG branches


  • From: Josh Berkus <josh(at)agliodbs(dot)com>
  • To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
  • Cc: "Joshua D. Drake" <jd(at)commandprompt(dot)com>, "Marc G. Fournier" <scrappy(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org
  • Subject: Re: State of support for back PG branches
  • Date: Mon, 26 Sep 2005 20:54:49 -0700
  • Message-id: <4338C289(dot)6040702(at)agliodbs(dot)com>

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



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group