MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
content-class: urn:content-classes:message
Subject: Re: Update on 'portal' changes
Date: Mon, 8 Mar 2004 17:05:27 -0000
Message-ID: <03AF4E498C591348A42FC93DEA9661B889F5D1@mail.vale-housing.co.uk>
Thread-Topic: [pgsql-www] Update on 'portal' changes
Thread-Index: AcQFL0br6R4gAGneSWCYkFHPqLqZYAAACKZA
From: "Dave Page" <dpage@vale-housing.co.uk>
To: "Alexey Borzov" <borz_off@cs.msu.su>
Cc: <pgsql-www@postgresql.org>

=20

> -----Original Message-----
> From: Alexey Borzov [mailto:borz_off@cs.msu.su]=20
> Sent: 08 March 2004 17:03
> To: Dave Page
> Cc: pgsql-www@postgresql.org
> Subject: Re: [pgsql-www] Update on 'portal' changes
>=20
>=20
> Speaking of which, what is the real reason for keeping the=20
> current website and the "next-generation" one in one project?
>=20
> Maybe a better approach would be to register a separate=20
> project for the next-generation website (I think this was=20
> already proposed here)?

Because the project is for all the websites, not just the one you are
working on.

We *have* created a separate CVS module which should be more than enough
segregation.

Regards, Dave.