[sldev] Documenting when to use SNOW vs when to use VWR

Mike Monkowski monkowsk at watson.ibm.com
Mon Jul 6 14:42:04 PDT 2009


I read the transcript, but I still don't think I understand.  Let me 
throw a few "for instance"s at you to see if I have this right.

1.  Someone running SnowGlobe reports a bug as a SNOW issue.  It is 
later determined that it is also a problem in the standard viewer.  So a 
VWR issue is cloned and the SNOW issue is marked as a duplicate?

2.  Someone makes a fix to a SnowGlobe-only bug.  It's posted as a patch 
on a SNOW issue.  Correct?

3.  Someone makes a fix to a bug that affects both and has been reported 
as a VWR issue.  The patch gets attached to the VWR issue.  Then it is 
decided to put it in SnowGlobe but not the standard viewer (yet).  A 
SNOW issue is cloned from the VWR issue?  Or if a SNOW issue already 
exists (case 1 above) then reopen the SNOW issue?

4.  Someone makes a fix to a bug that affects both and has been reported 
as a VWR issue and it is decided to put it in both.  Is a SNOW issue 
still cloned or do we just wait for the branches to sync up to catch the 
fix for SnowGlobe?

5.  Someone creates a feature that he wishes would ultimately go into 
the main viewer.  That's a VWR feature.  Then it's decided to pick it up 
in SnowGlobe.  The feature is cloned to SNOW?

So, in summary, a SNOW issue should only be created if the bug only 
affects SnowGlobe or cloned when cherry-picking VWR bug fixes and 
features?  And Linden does the cherry-picking, hence the cloning?

Which means, as far as the developer-in-the-street is concerned, only 
create a SNOW issue if the bug only affects SnowGlobe?  But if he makes 
a mistake and it really does affect the standard viewer, then who does 
the cloning?

Yes?  No?  Maybe so?

Mike

Rob Lanphier wrote:
> Hi folks,
> 
> A couple of weeks ago, we discussed how and when to file issues in the
> SNOW project vs filing them in VWR:
> https://wiki.secondlife.com/wiki/Open_Source_Meeting/2009-06-25
> 
> Is there a volunteer who can write up some guidelines, and post them to
> the wiki, preferably either on the "Snowglobe QA" page, or a page that
> we link to from there?
> https://wiki.secondlife.com/wiki/Snowglobe_QA
> 
> One issue we didn't discuss was the subject of how to put issues in
> doc/contributions.txt.  In cases where there's both a SNOW issue and a
> VWR issue, I'd strongly prefer that the VWR version goes into
> doc/contributions.txt.  Based on what I'm seeing so far, it'll make it
> easier to keep track of what eventually lands in the mainline viewer
> that gets its start in Snowglobe.
> 
> Rob
> 
> _______________________________________________
> Policies and (un)subscribe information available here:
> http://wiki.secondlife.com/wiki/SLDev
> Please read the policies before posting to keep unmoderated posting privileges



More information about the SLDev mailing list