Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: Re: time to move to the new code
Date: Sat, 14 Aug 2004 18:31:51 +0100
Message-ID: 
 <E7F85A1B5FF8D44C8A1AF6885BC9A0E407B3B9@ratbert.vale-housing.co.uk>
Thread-Topic: [pgsql-www] time to move to the new code
Thread-Index: AcSBvH26OiUX5uPNSzqvkoamYM5WxQAaBguV
From: "Dave Page" <dpage@vale-housing.co.uk>
To: "Robert Treat" <xzilla@users.sourceforge.net>, <pgsql-www@postgresql.org>

None that I know of - it just needs the content to be sync'ed, and for some=
one with some spare time to look at it (not me I'm afraid - but I'll be all=
 finished on my DS in November if that helps :-) ).

Regards, Dave


-----Original Message-----
From: pgsql-www-owner@postgresql.org on behalf of Robert Treat
Sent: Sat 8/14/2004 6:06 AM
To: pgsql-www@postgresql.org
Subject: [pgsql-www] time to move to the new code
=20
I think it is time to move to the new code for www. The biggest argument=20
against the idea was the desire some folks had to implement a new design=20
along with the new code.  Well, the design doesn't get done and the code ge=
ts=20
more out of synch as maintainance on the live site rolls on, so I think we=
=20
need to bite the bullet and move to the new code. Once it is in place we=20
should be able to make deisng changes much easier anyway, after all that is=
=20
part of the point of the new code.  Are there any open items that would=20
prevent us from making the switch?

--=20
Robert Treat
Build A Better Lamp :: Linux Apache {middleware} PostgreSQL

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
    (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)