We need a proper way for them to *update* that before we do that -
otherwise, nobody would be listing 8.2.
The solutino for this is of course to integrate it with community
logins, just not done yet.
//Magnus
>
> How about also requiring a list of support versions?
>
> - --On Tuesday, December 12, 2006 12:52:54 -0500 Robert Treat
> <xzilla@users.sourceforge.net> wrote:
>
> > On Monday 11 December 2006 07:07, it was written:
> >> You list HOSPES as a hosting provider in Poland that provides PostgreSQL
> >> database for hosting. Do you realise their offer does not cover any of the
> >> current releases and thus they offer only old, outdated and insecure
> >> version from the 7.4.x branch.
> >> I think it's not a worthy hosting.
> >
> > So I am going to invent policy that we'll list anyone who offers hosting on a
> > version we link to from the main postgresql.org web page, which means these
> > guys are ok for now. Any objections?
> >
> > --
> > Robert Treat
> > Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
>
>
>
> - ----
> Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
> Email . scrappy@hub.org MSN . scrappy@hub.org
> Yahoo . yscrappy Skype: hub.org ICQ . 7615664
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (FreeBSD)
>
> iD8DBQFFgi6H4QvfyHIvDvMRAkgbAJ0clyPMYKYpv4qjduHWcM93Ns5xiACgn9IF
> DLUX0+SwJGDwPYO7uAXy4/o=
> =Xh/u
> -----END PGP SIGNATURE-----
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org
