Thread: CVS Server Changes

Hi Guys,

At some point in the near future I need to move the pgAdmin CVS
repository to a new machine. There are 2 issues to consider:

1) The DNS must be updated and will take time to propagate.

2) The CVSROOT is going to change to
:pserver:user@cvs.pgadmin.org/projects/

I want to try to arrange this work to have minimum impact so would
appreciate if those affected (committers and port maintainers primarily)
could give me an idea of how this may best be scheduled.

Thanks, Dave.

Dave Page wrote:

>Hi Guys,
>
>At some point in the near future I need to move the pgAdmin CVS
>repository to a new machine. There are 2 issues to consider:
>
>1) The DNS must be updated and will take time to propagate.
>
>2) The CVSROOT is going to change to
>:pserver:user@cvs.pgadmin.org/projects/
>
>I want to try to arrange this work to have minimum impact so would
>appreciate if those affected (committers and port maintainers primarily)
>could give me an idea of how this may best be scheduled.
>
>

At the moment, I'm quite busy (non-pgadmin stuff), with no work pending
for commitment. Next thing I'd do would be updating wx to near-current cvs.

Regards,
Andreas

> -----Original Message-----
> From: Andreas Pflug [mailto:pgadmin@pse-consulting.de]
> Sent: 16 December 2003 16:54
> To: Dave Page
> Cc: pgadmin-hackers@postgresql.org
> Subject: Re: [pgadmin-hackers] CVS Server Changes
>
>
> At the moment, I'm quite busy (non-pgadmin stuff), with no
> work pending for commitment. Next thing I'd do would be
> updating wx to near-current cvs.

Righto - you're the one who might be most inconvenienced I would guess,
but if you have no pending checkins then that should be easy.

The best bet for everyone will probably be to simply checkout a fresh
tree...

Unless anyone objects, I'll see if I can do it tomorrow morning...

Regards, Dave.