Robert Osfield wrote:
I don't see much point in having a 2.8.3 that is identical to 2.8.2
save for changes that are only enabled by a CMake change. This is a
special release for a specific feature for a specific client, I would
branch and name the branch according to the nature of your changes
rather than try to try to disguise it as a conventional point release.
I there were other bug fixes to go into the OSG-2.8 branch then I
believe we'd have good justification for a 2.8.3 release, even then
I'm not sure that the changes that you are considering would be
appropriate to be rolled into it.
My goal is to get this out the door with as little work as possible. If
you're going to reject this change in a 2.8.3 release regardless of
whether it's binary compatible or not, then I'll just go with the
branch. I've already spent more time discussing it here in osg-users
than it took me to actually code the fix.
-Paul
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
