Tom Lane <tgl@sss.pgh.pa.us> writes:
> Greg Stark <gsstark@mit.edu> writes:
> > This is the only place where I see hardly any movement on major items the
> > whole development cycle, then a rush of radical changes just before the
> > freeze.
>
> [blink] There's been plenty of stuff done all through this development
> cycle (and previous ones too). Read the CVS logs if you've forgotten.
Sure, but that's parallel to what I'm saying. This is the only place I see
"Please delay the freeze so I can squeeze this major change in just before the
release". In other projects I see "Please hurry up and release so I can start
committing major changes again".
Perhaps it's an artifact of people doing most of their work offline and
submitting patches, rather than using the CVS tree as their development
environment. Or perhaps it's an artifact of ~nobody using the CVS version of
postgres except for testing patches. Or perhaps it's a consequence of the
freeze period being so long.
Or perhaps the serious postgres developers are just so good that they're
justified in being confident applying major changes just before a freeze.
Experience does seem to justify that somewhat; I've been repeatedly impressed
at how such drastic changes seem to just work with hardly any changes.
Fwiw, I do feel that 7.4 is pretty fresh. At least in my case I don't plan on
upgrading to 7.5 immediately because 7.4 meets all our needs. When we upgrade
it'll probably be for PITR, but we don't really need it yet.
--
greg
