On 7 Mar 00, at 10:42, Gilbert Carl Herschberger II wrote:
> At 08:41 PM 3/7/00 +0800, Hilary Cheng <[EMAIL PROTECTED]> wrote:
> > Could we use sourceforge instead of current CVS Jos one ? Since
> >it seems that JOS one is not so stable.
>
> Our first goal must be to "fix" the CVS we already have. Couldn't someone
> monitor the CVS site, making sure CVS is up-and-running every day? Couldn't
> we create an automatic restart for CVS, starting it whenever it goes down?
> Couldn't we create a HTML link to restart CVS when its down?
This is basically what we're doing now. The CVS server on jos.org
has been having semi-regular problems and is being restarted when
needed. It's flakey nature is prompting the move to SourceForge's
CVS.
> CVS doesn't really need to be running for check-out, only check-in. If
> someone would volunteer to make a snapshot of CVS as an archive, these
> files would be available even when CVS is down.
Well, if you actually want to use _CVS_ check out, you need CVS
running.
As far as making snapshots available, that sounds like a good
idea. Once we move to SourceForge, this process is automated
as we can have it automatically make CVS snap shots available on
a daily basis.
> Isn't it possible for the "old" CVS to be a mirror of SourceForge?
Yes. But to what advantage?
> What about the future? I think moving CVS is a pretty big deal. It is a big
> step. Who is going to do the migration work? Isn't this issue big enough to
> require a vote on the vote mailing list?
It's not actually hard at all. If we do a fresh setup (which most of
the kernel developers favor) someone with commit priviledges in
sourceforge simple checks in the source to start things off. If we
want to save the CVS histories in the jos.org server, we simply tar-
gzip up the CVSROOT and email it to sourceforge. They will install
it within 24 hours.
> If we decide to make the move, we should look forward and set a date.
> Before that date, the "old" CVS would be the official site. After that
> date, the "new" CVS would be the official site. How much time do we need?
Last I heard, we're waiting for the kernel rewrite to get to a stable
state. Then, one of the core developers (Jim? Ryan?) will check in
the sources to get the SourceForge cvs populated.
-iain
_______________________________________________
Kernel maillist - [EMAIL PROTECTED]
http://jos.org/mailman/listinfo/kernel
