It's also surprisingly difficult to do much in the way of testing against all those wonderful changes, when the vast majority of the JIRA's referenced aren't public. Can someone maybe consider the idea that if a change is going to get merged into viewer development, the associated jira's need to be publicly accessible (except in cases of security issues, of course).
On May 17, 2011, at 11:22 AM, Oz Linden (Scott Lawrence) wrote: > > The mesh team development branch has been merged to viewer-development > (with the actual mesh support disabled, but with many rendering and > other fixes active). > > Your next pull of the tip of viewer-development will bring you ~2250 > changesets; pay careful attention to any merges of your local changes. > > Some of the changes may cause problems with using the Debug (and > DebugOS) configurations. If you have problems, please bring them up on > the list. Don't file a jira yet unless you believe you have diagnosed a > specific issue well enough that a fix is possible. If it turns out that > these configurations are not working well, getting them fixed will be a > high priority this week. > > If you would like to update your repository to the latest possible > change _before_ the mesh branch move (and let the rest of us sort out > any problems that arise), then you can pull the tag '2.6.9-start'; the > mesh merge is the next revision after that tag. > > _______________________________________________ > Policies and (un)subscribe information available here: > http://wiki.secondlife.com/wiki/OpenSource-Dev > Please read the policies before posting to keep unmoderated posting privileges _______________________________________________ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the policies before posting to keep unmoderated posting privileges
