From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
---|---|
To: | Michael Meskes <Michael_Meskes(at)topmail(dot)de> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] v6.4.3 ? |
Date: | 1999-02-08 17:50:12 |
Message-ID: | Pine.BSF.4.05.9902081349170.32828-100000@thelab.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, 8 Feb 1999, Michael Meskes wrote:
> On Sun, Feb 07, 1999 at 10:06:03PM +0100, Jan Wieck wrote:
> > I recall some replies to recent problem reports on v6.3.2
> > where we told "upgrade to v6.4.2" (shame on us). That's
> > easier said than done, if someone has big applications
> > breaking on new features.
>
> Agreed.
>
> > I know that it isn't true, but these "upgrade to another
> > release" answers instead of "install bugfix release vX.X.X"
> > look like we don't care about anyone who really uses
> > Postgres, not only playing around with it just for fun.
> > That's the sound of M$.
>
> And once more I agree.
>
> > Patching against v6.4 takes time. It must be done manually
> > nearly all the time since patches don't apply clean. But it's
> > the only way to give Postgres a real good reputation.
>
> I like this approach. However, when d we stop maintaining the old version? I
> think there are still people using 6.3 who cannot simply upgrade to 6.4. So
> do we create 6.3.3 too? Or are there no open bug reports on 6.3 anymore?
One version back, in my opinion...v6.5's release kills anythingolder then
v6.4, v6.6's release kills anything older then v6.5, etc...
And, no, we aren't "supporting" v6.3 at this time, since this is a new
thing...
Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 1999-02-08 18:12:24 | Re: [HACKERS] trouble with rules |
Previous Message | Thomas G. Lockhart | 1999-02-08 17:35:02 | Re: [HACKERS] VACUUM ANALYZE problem on linux |