[sldev] Why so many maintenance branches?
Soft
soft at lindenlab.com
Fri Mar 7 09:19:57 PST 2008
I got asked why we have so many maintenance branches.
Maintenance branches are for bug fixes and small, incremental changes
only. Basically, anything that doesn't get its own branch falls into
maintenance.
When Lindens are behaving, the maintenance scheme is:
If it's a bug new to this release [candidate]: Branch_x-x-x-Viewer
else if there's a server dependency: maintenance
else if there's a rendering issue: maint-render
else if there's a ui issue:maint-ui
else: maint-viewer
The reason for the partitioning, at least in part, is that QA is
pretty different for each of these. There's a lot of iterative back
and forth with the rx team on UI issues, and there's great paranoia
and triple-checking on platform issues with rendering changes. If
everything fell into maintenance, it would slow down "release" (trunk)
merges even further.
More information about the SLDev
mailing list