Did anything ever get decided?
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.
- 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.
2) Once known major bugs are fixed, create an RC1 branch for
testing. (Mar 13)
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.
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.
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.
What do y'all think, is this possible?
-Allen
On Thu, Feb 19, 2009 at 1:44 AM, Gerrit Voss <[email protected]> wrote:
>
> Hi Allen,,
>
> sorry for the delay I was slightly distracted by other things.
>
> On Mon, 2009-02-16 at 08:00 -0600, Allen Bierbaum wrote:
>> Hello all:
>>
>> I am writing to ask what the roadmap to 2.0 release looks like.
>>
>> We create a stable branch of OpenSG in June of 2007 to use temporarily
>> while OpenSG 2.0 was ironed out. This branch has worked *very* well
>> for us which I think speaks volumes to the OpenSG 2.0 code.
>> Unfortunately, we planned to use this for 3-4 months, but have been
>> using it for much longer. We would like to get back to using the head
>> since it has a number of performance improvements and 1.5 years of
>> development, but I must make sure we can count on a stable
>> release/branch for code that we deploy. We can help out with pushing
>> 2.0 out the door, but I don't know what the current plan is.
>>
>> For example:
>>
>> - How close are we to 2.0?
>
> actually I'm already in the middle of what I thought would go into
> 2.1, e.g. I'm about to restructure the materials, the way materials
> are stored, and chunks so that they can change according to the
> requirements/properties of the current segment of the render traversal.
>
>> - What features/capabilities are left to implement?
>
> The biggest issue I see is documentation. I can walk through 1.x
> and open tickets for missing pieces.
>
>> - What will the release process look like (RC's, betas, etc)?
>
> I left that one a little bit to Dirk ;-) (yes, I know it's not nice ;-))
> I'm fine to go into release mode and walk thought the track tickets. As
> we have a tutorial at IEEE VR coming up we have to look into this
> anyway, so hopefully we at least a beta out of it ;-)
>
> I'm not sure how much would we have to merge back from your branch,
> IIRC Carsten looked into a some time ago.
>
>
> Other opinions ??
>
>
> 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
>
------------------------------------------------------------------------------
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
