>From a message from Robert: In last few OSG/OP/OT releases I have been forced to coordinates the release of OpenThreads, Producer and OpenSceneGraph all at once. Its a nightmare that I really don't want to relive. With osgProducer moving out of the core OSG part of the dependency chain is resolved, leaving only OpenThreads as the major external dependencies that must be release before the OSG gets released.
============ What are you saying here Robert? I have an existing (relatively large) OSG program that uses osgProducer with Producer. Switching this program to use osgViewer will result in my schedule and cost overruns. By saying that osgProducer/Producer is "not part of the core dependency chain" are you saying that you are no longer supporting osgProducer and therefore will not be testing it before this release? I've already found problems where my existing programs broke when moving to CVS/SVN code because of this de-emphasis on osgProducer. I'm currently spending a significant portion of my time tracking down strange problems with OSG that I do not have the time to do even more testing. I just want to work on making improvements in my program and not trying to hit a moving target of future OSG changes. I will need future releases of OSG for the "bug fixes" but at this time need to holdoff switching to new functionality. What support in the future will there be for osgProducer/Producer for existing OSG programs? ____________________________________________________________________________________ It's here! Your new message! Get new email alerts with the free Yahoo! Toolbar. http://tools.search.yahoo.com/toolbar/features/mail/ _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
