I went through the CVS logs to draft release notes, and found that the
list of patches applied to REL7_4_STABLE is a bit skimpy:
http://developer.postgresql.org/pgdocs/postgres/release-7-4-22.html
I'm wondering if we should leave 7.4 out of the current set of update
releases. If I were a DBA conservative enough to still be runnng 7.4.x,
I doubt I'd find anything there compelling enough to justify an upgrade.
So I'm thinking that generating a 7.4.x tarball now would be mostly a
waste of server space, and we should leave these changes for the next
update cycle.
The main counter-argument I can think of is that it's too confusing
to release the same fixes in different branches at different times.
We did that this spring, and it was confusing, at least when it came
time to make the release notes for the next set of updates. But I
dunno if any users noticed particularly.
One thing that ties into this is whether there ever will *be* another
7.4.x release. We haven't formally discussed an EOL date for 7.4,
but its fifth birthday will be 2008-11-17. I imagine we'd want to make
its final update release be after that date. If we do a release now,
the final update might be even skimpier than this one.
Comments?
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
