[opensource-dev] Wiki posting: Open Source Repository Strategy

[Kent Quirk (Q Linden)]

On Mar 22, 2010, at 9:11 AM, Boroondas Gupte wrote:

> Hi Q
> 
> thanks for illustrating the planned process.
> 
> On 03/22/2010 04:38 AM, Kent Quirk (Q Linden) wrote:
>> 
>> Since it's policy we intend to follow, please edit only for clarity. If it needs substantive tweaking, please let us do it.
>>   
> As not everyone who might find that wiki article will be reading this mailing list, you might want to enable stable versioning on it. That will still allow everyone to easily edit the "draft" version while you can review changes before you "verify" them and they go live as the "stable page". The Documentation Team uses that for the KB part of the wiki, so Torley etc. can probably tell you how to do it.
> 

Thanks, I'll look into that.

>> Questions and constructive commentary are encouraged.
>>   
> about K)-N): In cases where none of planned new features require secrecy, can viewer-release be exported to a corresponding external branch, too?
> about M): Also in cases where none of planned new features require secrecy, can private beta be skipped in favor of an earlier public beta?
I imagine that we'll have more external branches than are shown there. The idea is to publish as soon as we can reasonably do so, so I think that will have the effect you're looking for.

> about O): What about the inverse, can the community opt not to merge certain features from upstream (viewer-external) into Snowglobe?
The merge to Snowglobe isn't automatic -- it probably requires intelligent merging. So if that includes leaving things out, so be it. The right way to do it will probably be to undo the changesets so that it doesn't become a fork that requires constant maintenance. 



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.secondlife.com/pipermail/opensource-dev/attachments/20100322/c8f4b8e9/attachment.htm