[sldev] Version control repository

[Peekay Semyorka]

Hi Rob,

My own view is that LL should first provide us with read-only access to
the official branches of the client code (-dev branch, -stable branch,
etc.)  Let's call this the "official repository" and contains only Linden
released code and those slated for inclusion in the next official viewer.

Then let the community-at-large decide on its own repositories, for its
own projects. Some may group together and decide to use BitKeeper on a
large collaborative effort. Individual developers may choose to just track
the official repository.  Companies may opt to sync official releases into
their internal Perforce system, or ClearCase, etc.

But the official repository remains distinct, clean, separate and
authoritative.

So my suggestion would be for LL to move all the client-related code from
the internal server into a new subversion-based repository (in a DMZ or
mirrored from an internal server) and give the community read privileges
to it. All commits are done by Lindens, based on a well-defined submission
and review process.

In the near or far future, LL may vet external developers for direct
commit privileges into the official repository.  However, before that can
happen, other topics (like the release process) need to be thoroughly
hashed out. At that point we would need greater visibility into any
planned server-side changes which may impact the client.

I would also suggest periodic automated builds of the official repository,
to make snapshot executables available for the greater SL community.

My $0.02,

-peekay