Re: [HACKERS] Mega-commits to "stable" version

> Is anyone else disturbed by wholesale changes to what is supposed to
> be a stable release?
> I am sure Marc will say these are low-risk changes --- but they're not
> *no* risk, because there is always a chance of propagating part of
> some other change that you didn't want, or failing to propagate all
> of the change you did want.  And how much testing will the modified
> 6.5.x code get before it gets published as a stable version?

I agree, and think we should back off on some of those patches, or at
least back off of applying patches of that nature in the future. I'm
guessing that it wasn't clear to Marc what the range of opinions might
be on these particular patches.

otoh, since it's a done deal, it should encourage us to do a bit more
testing than we would have otherwise, on a wider range of platforms.
And the changes probably got the camel's nose under the tent to move
forward with 64-bit fixes on the stable branch (which would be nice
for our RPM work).

Perhaps the Japanese contingent, who seem to have a remarkable range
of platforms, will be willing and able to regression test when we get
closer to a v6.5.2.
                    - Thomas

-- 
Thomas Lockhart                lockhart@alumni.caltech.edu
South Pasadena, California