Hi All, I would like to go for getting OpenSceneGraph-3.0 out the door for the end of June, this gives us four weeks to test, debug and make ready. This gives us a little over four weeks to all we have to do. For a perliminary schedule I would suggest breaking the work down into two halves/phases.
Phase 1: Merging pending submissions, testing and debugging Period : Now till to Friday 17th of June : Dev releases tempo to be upped to two or more a week. I'll merge submissions except where new submissions look like they will be a high risk to the release schedule. New freatures will need to be low risk to be included, and as we move closer to the end of Phase 1 I'll steadily raise the bar for merging new features/feature refinements so that only really low risk submissions will be considered. All submissions considered too risky in this phase will be bumped to after 3.0. Ramping up the use of nightly builds will certainly help convergance so if you have machines available that might be suitable please consider contributing to cdash.openscenegraph.org. Phase 2: Feature freeze and release candidate testing Period: 18th June to end of June This phase will begin with the creation of the OpenSceneGrap-3.0 branch which will mark the feature for the release and will be used as the basis of the series of OpenSceneGraph-3.0.0 release candidates. Straight after making the 3.0 branch I'll tag the 3.0.0-rc1 and will call for build and runtime testing. Ideally binaries will be built and made available for testing through the rc series. Only documentation, build and bug fixes will be merged all new features will be ignored till after the final 3.0.0 release is tagged and out of the door. Final release, spreading the news to online news dev sites and party ;-) Throughout the period end user testing is absolutely and utterly crucial to the end quality of the release. If 3.0.0 goes out the door and doesn't work for your application it will be *your* failure to test and report the problems in a timely manner, so please don't hold back till after the realse, dive in and test svn/trunk, the dev releases and release candidates as much as you can. I will do what I can to help fix bugs over the next month but I will be stretched so won't be able to chase everything up - the community scales far better than I can ever do so the bulk of hunting down bugs and addressing them, we are all part of the commuinity so don't assume just because you've reported a problem that there is someone out there with the skills and time to fix it, we all will be stretched by our own work. If you don't feel able to contribute fixes then testing and providing high quality bug reports that aid others in quickly reproducing and understanding the problem is important so worth the extra effort. If your report a problem and then others have to keep asking your questions about the problem just to be able to reproduce it then there is likely something wrong in the quality of your reporting. See how others report problems and how much information was required to help indentify the problem, learn from the most successful posts. Often even basic stuff like version of the OSG, operating system, hardware used, how the OSG was built etc are completely ignored in reports and right away you'll get asked these questions. Use having to ask questions is consuming both out and your time, this is wasted time that would be better spent actually fixing problems, so poor reporting direclty reduces the of the software. The place to report problems is here on the osg-users mailing list/forum, only actual code submissions should posted to osg-submissions. Also don't post reports of problems directly to particular users, including me, as broacasting the problem to the whole community is how we leverage the power of the community. More inportant than anything else, test, test, test. The earlier your test the OSG before the release the more likely that we'll have the time to fix the issues that you find. Thanks in advance for you help, Robert. _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
