Hi Paul, On 2/23/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
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.
This is what I have been discussing openly on osg-user for the past four months, osgProducer will be moved out of the core OSG, and be maintained seperately. So rather than worry about cost overruns please keep track of discussions.
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?
osgProducer won't be part of the core OSG. osgProducer will be released seperately and on its own release schedule. Its such as small project that it will likely follow along after OSG releases. It does depend upon Producer releases as well though, and I no longer have any input to Producer so can't comment on Don's release schedules
I've already found problems where my existing programs broke when moving to CVS/SVN code because of this de-emphasis on osgProducer.
Please report them, we can't fix problems we know nothing about.
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.
Well sorry for ever making open source, ever improving it, ever trying to fix bugs, ever trying to get releases out.
What support in the future will there be for osgProducer/Producer for existing OSG programs?
Its open source, you can make any future you wish for it. You have full control over when you upgrade, you have full ability to roll bug fixes made back into your local code. There is no magic wand with software, it involves alot of hard graft. Robert. _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
