RE: [stellation-res] Missing stuff on Stellation Server

["Mark C. Chu-Carroll" <mcc@xxxxxxxxxxxxxx>]

On Sun, 2003-08-03 at 10:01, Jonathan Gossage wrote:
> These problems raise a number of issues. I think we are going to need a very
> well structured process for the next while if we are to keep the master
> repository from becoming a mess. The following points come to mind.
> 
> 1. Which is the master repository?
>    Personally I think it should be the Stellation repository.
> 2. How will the slave repository be maintained?
>    Will it be updated by individual committers?
>    Will it be updated centrally?
>    What is the update freqency for the slave repository?

You're dead on that this is a problem. I've been thinking about
this, as I try to work out the mechanics of this.

My inclination at the moment is to just drop the CVS repository,
and to maintain regular backups in zipfiles on downloads.eclipse.org. 

The reason why is pretty much exactly what you're pointing out:
the two repositories have enough major differences that correctly
maintaining synchronization is going to be *extremely* difficult.

The "synchronize" command was designed to help with this. But,
like so much else in the CLI code, it's basically broken. As
usual for the CLI, it was never really tested. And it works for
some simple cases (the one or two cases that Dave tried, before
declaring it complete). But every time that I've tried to use
it, it fails in a new and novel way. So we can't trust that. 

The only things in the CLI that have been close to adequately
tested are add, remove, checkin, checkout, and merge. I consider
pretty much all of the rest of the commands unreliable.

So maintaining synch between repositories just doesn't seem
feasible. 

So my workaround is as follows:
- Every day that changes are made, I will produce a zip file,
  named according to the branch version that it mirrors.

- Every two weeks, I will prune old versions from the FTP site,
  but keep them on the Stellation server, so that they can
  be reinstated should we need them.

So the backup period will be roughly every 24 hours.

I'll try to fix up the rest of the missing/extra file issues
later today. I'm not sure if I'll have time; if not, I'll
do it first thing tomorrow. (We're having my daughter's 
3rd birthday party this afternoon, so I'm a bit busy today.)

	-Mark




> 
> Regards
> 
> Jonathan Gossage
> 
> 
> _______________________________________________
> stellation-res mailing list
> stellation-res@xxxxxxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/stellation-res
-- 
Mark Craig Chu-Carroll,  IBM T.J. Watson Research Center  
*** The Stellation project: Advanced SCM for Collaboration
***      http://stellation.eclipse.org
*** Work: mcc@xxxxxxxxxxxxxx/Home: markcc@xxxxxxxxxxx