Hi, On Tue, 2009-03-03 at 19:13 -0600, Allen Bierbaum wrote: > Did anything ever get decided?
unfortunately not really ;-(. > Specifically: > > - What is the status of documentation? Will the IEEE VR tutorial > produce documentation that can be used? What method will be used for > the OpenSG 2.0 documentation (doxygen, trac, other)? In the near term > it would be *very* helpful to have a document describing the new > pointer types. I started to clean up the documentation structure, currently only Base, System hopefully soon so we have the canvas to get it up-to-date. As for the method, I would go for doxygen. Can the doxgen result be integrated into trac easily ? > - Has anyone had any more thoughts related to roadmap? Just to throw > something out there for discussion here is an idea: > > 1) Enter feature freeze ASAP. I'm a little split if I at least should try to finish the high-level Material/Chunk reshuffle for this or not. Also we have to decide which of the to be ported stuff we want to get over before that. IMHO at least the remaining loaders should make it. Some other parts require more thinking. > 2) Once known major bugs are fixed, create an RC1 branch for > testing. (Mar 13) As of now I will be traveling on the 12th so doing the RC1 on the 13th might be a little tough. I would prefer to try to finish on the 11th. Given that this date is a week away, I'm not really sure if this makes sense but we should at least give it a try. I also loose access to most of my machines after Friday (due to a spatial shift to Germany) so somebody else will have to do the final builds. > I know our group will be willing to provide extensive testing of > this branch and this will provide a stable "release" for the IEEE VR > audience. > 3) Create list of outstanding issues to address (as tickets?). Have > release manager coordinate the issue resolutions. I started this for the to be ported things (wiki) and I started to sort through the open tickets. I try to go through my internal list and see what is in there. > 4) Burn down list of issues. If major issues found then create new > RC2, etc for testing. > 5) Target release of OpenSG 2.0 by May 1st. the 4)/5) time-line is in general fine with me (as of now). > As Patrick said earlier, he is able to help support and coordinate > this as needed. I am also willing to provide other engineers to test > the system, provide feedback on documentation, and run down any issues > encountered. If possible, we will help fix the issue, but from > previous experience I know this may take GV or CN to do the real fix. I'm fine with spending time either fixing things or at least providing help to track them down and find a solution. kind regards, gerrit ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Opensg-core mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-core
