Whatever the solution is, I believe it has to take into account the fact that the Rotor team at MS is still evolving the code base. While this is the case, it makes full sense to avoid branching and to try and keep everybody working off the same images. The last time I brought this up, David Stutz said on this very subject:
"The answer is yes: we are listening, and working on this." http://discuss.develop.com/archives/wa.exe?A2=ind0204b&L=dotnet- rotor&F=&S=&P=1240 My thinking is that the more bugs/fixes we make available here, the more incentive we provide to the Rotor team to accelerate whatever plans they have to host a public central repository. However, based on the activity I've seen recently, that might not be the case too soon. (I'm not trying to take everybody here on a guilt trip, just stating a fact - I know everybody is busy with their day-time jobs - I am most of the time anyway, so no flames please :-) ). Cristian On Wed, 1 May 2002 17:59:44 -0400, Werner Vogels <[EMAIL PROTECTED]> wrote: >> There was a thread on this idea a while back--is there a >> centralized place by which to share these fixes? Has >> Microsoft come up with that yet, or is this list it, for >> the moment? > >We're willing to host this at Cornell. Actually we brought up the server >soon after the previous thread but got totally lost in the quirks of >running a CVS server under .net server. Win32 cvs clients are OK but the >authentication mechanism when running the win32 CVS server are a royal >pain. I'll see whether I can revive the effort. > >In the mean time, it is more important to get some organization going, >if we really want to host and manage updates to the source tree online. >We will need some organizational structure with people responsible for >certain modules, who will run tests, etc. before checking in changes, >etc. Update rules, etc. Anyone wants to take a stab at this? > >-- >Werner
