[Pkg-postgresql-public] Dropping postgresql 8.3 for squeeze

[Dimitri Fontaine]

Gerfried Fuchs <rhonda at deb.at> writes:
>> If Python version changes, a binNMU is triggered on affected packages,
>> which is damn faster and more efficient than mass filling bug reports.
>> Without a line change to the modules sources.
>> 
>> I do not see why this is not doable for PostgreSQL.
>
>  In this case you have a point. Dimitri though wants every single
> postgres version out there in the pool, which just doesn't scale.

I though I made myself a little more clear than that. What I want is:
 - no edit of extension packages when supported-versions changes
 - find a way to have in debian all upstream maintained versions

Choosing which PostgreSQL major version to install on debian is not our
call. I understand why the current situation is what it is, I'm trying
to find a way to improve it and I'm willing to put efforts towards that
goal.

So, dear debian-release guys, is it possible to consider adapting the
debian stable policy to better handle the PostgreSQL case and better
serve its users?

Regards,
-- 
dim