[sldev] LLMozLib2 is now exclusively in the public SVN repository

[Mike Monkowski]

My vote would be for creating a branch with the same version number or 
release number as the first viewer that used it.

I'm used to CVS where tags are essentially free, so it makes sense to 
tag every intermediate release there (release candidates and first 
looks) and to make a branch for every full (point) release.

Linden is a little different than most projects I've worked on in that 
they never do bug fixes on a full release.  They only do it in the 
intermediate releases.  So everything could be just tagged if it were 
CVS.  I don't know enough about SVN to know whether it has equivalents 
to tags and branches.

Mike

Callum Prentice wrote:
> Sounds like some discussion here would be useful on how best to organize 
> this going forward then.
> 
> LLMozLib2 shouldn't change very often - hopefully less frequently than 
> our major releases but there will be fixes and changes as we use if for 
> new new features in the client.
> 
> Should there be a new version for each client release anyways so there 
> is always a 1:1 correlation? That sounds a bit excessive but if it made 
> things clearer it might be worth it.
> 
> Suggestions appreciated.