[sldev] Version control repository

[Duffy Langdon]

I agree that getting access to a VCS system, where the stable and head 
branches can be retrieved is a priority, otherwise the code made public will 
quickly grow stale.

Almost all on this list should be able to set up their own sandbox, if they 
want/need it. So if Linden Lab is already using SVN, by all means, continue 
to do so, it will cause less overall confusion.

----- Original Message ----- 
From: "Kitten Lulu" <kitten at ngi.it>
To: <sldev at lists.secondlife.com>
Sent: Wednesday, January 10, 2007 12:37 PM
Subject: Re: [sldev] Version control repository


> Peekay Semyorka ha scritto:
>> 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.
>>
>>
> I think choosing what LL already knows is a good idea and I agree that 
> read-only access to an official/authoritative source code repository is a 
> priority.
>
> I wonder if there is a migration path that would allow to move from (or 
> augment) a Subversion repository to a SVK repository. Is there anyone with 
> significant experience with svk who can comment?
> _______________________________________________
> Click here to unsubscribe or manage your list subscription:
> /index.html
>