>If we are going to back-patch more aggressively, we _have_ to be sure
>that those back-patched releases have the same quality as all our other
I know that I am probably being semantic here but I in know way want to
be more aggressive with back patching. My
thoughts for 98% of things in on bugfixes within the existing tree only.
Although I am sure for some things we can
use (at least as a guide) code being written in 7.4. My whole purpose
in bringing the idea up is to increase the adoption rate.
My thought isn't to be more agressive per say, but more responsible in
our releases. Like I said, I may be, being semantic.
>I know people already know this, but it is worth mentioning specifically
>--- my point is that more agressive backpatching has risks.
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-222-2783 - jd(at)commandprompt(dot)com - http://www.commandprompt.com
Editor-N-Chief - PostgreSQl.Org - http://www.postgresql.org
In response to
pgsql-hackers by date
|Next:||From: Peter Eisentraut||Date: 2003-10-03 23:32:37|
|Subject: Re: 7.4 status|
|Previous:||From: Nigel J. Andrews||Date: 2003-10-03 22:20:55|
|Subject: Re: Thoughts on maintaining 7.3|