Tom Lane wrote:
>
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
<snip>
> > I can say pretty reliably that we are long past time in 7.2 where we can
> > add code that will push back a final release date. It is fine to slip
> > stuff in and take the responsibility for it, but we are in beta now and
> > anything that pushes back final is bad, because it pushes back _all_ 7.2
> > features from the general user community.
>
> Yup, exactly. "One more feature" is a siren song that you gotta resist,
> else we'll never get out of beta.
>
> It might be appropriate to point out that we've already missed the
> original target date for 7.2 beta by two months, and that if we can't
> produce a release candidate in another week or so we'll likely not have
> 7.2 final until January. That's a long time to keep the world waiting
> for concurrent VACUUM, survival of transaction ID wraparound, and
> several other absolutely *critical* improvements in 7.2. If it looks
> to me like JDBC MD5 passwords (or any other thing that's not clearly a
> bug fix) are going to slip the schedule another week, I'll vote to pass
> it over until 7.3.
>
> Once we go beta, we have to focus on wrapping up what we have
> and getting it out the door, not on squeezing in stuff that is
> "almost ready". There'll always be another release.
>
> regards, tom lane
Thanks guys. Consider me "better educated" now about our release
priorities.
:)
Regards and best wishes,
Justin Clift
--
"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
- Indira Gandhi
