> The Hermit Hacker <scrappy@hub.org> writes:
>
> > Put them up as "official patches" against v6.3.1, but no
> > v6.3.2...not so close behind v6.3.1 :(
>
> Whatever you choose to do, make sure it's well reasoned out and that
> you will then continue to follow that scheme!
>
Agreed, most of your arguments have been gone over a while ago.
But I disagree VERY strongly with Marc, a new set of patches should
DEFINITELY be 6.3.2. What does it matter that this is so close behind
6.3.1 - that simply shows that the PostgreSQL developers have
responded to and fixed a number of bugs in double-quick time. OK,
so it's a little embarrassing that these weren't spotted before
6.3 was released, but it makes things so much simpler for everyone
to say "I'm running 6.3.2" rather than "I'm running 6.3.1 patched
with patch xyz (which I may or may not have applied correctly...)"
If Marc can come up with one really solid reason why a patched
version should NOT be released as 6.3.2, I might reconsider my
viewpoint :-)
Andrew
----------------------------------------------------------------------------
Dr. Andrew C.R. Martin University College London
EMAIL: (Work) martin@biochem.ucl.ac.uk (Home) andrew@stagleys.demon.co.uk
URL: http://www.biochem.ucl.ac.uk/~martin
Tel: (Work) +44(0)171 419 3890 (Home) +44(0)1372 275775