I'd like to see the SceneGraphOrderRenderBin implementation if it could fit in. 
 It was discussed in May.

andy

-----Original Message-----
From: osg-users-boun...@lists.openscenegraph.org 
[mailto:osg-users-boun...@lists.openscenegraph.org] On Behalf Of Robert Osfield
Sent: Saturday, June 20, 2009 6:27 AM
To: OpenSceneGraph Users
Subject: [osg-users] Gearing up for OpenSceneGraph-2.8.2, OpenSceneGraph-2.10 
and VirtualPlanetBuilder-1.0 releases

Hi All,

Over the next six weeks I'd like to push out three stable software
releases, it's not something I can do on my own as testing, bug fixing
and feature refinement all items that community participation are
essential to ensure quality software goes out the door.

-- OpenSceneGaph-2.8.2 release, aiming for end of June (next two weeks)

First up will be another patch release of the OpenSceneGraph-2.8
series.  In theory the 2.8 branch should build and run across without
problems as I generally stick to low risk changes, but... as we found
out with 2.8.1 even changes that look uncontroversial can unwittingly
introduce new bugs break end user applications - testing against a
wide range of applications and platforms is absolutely essential to
catch problems prior to a stable release.  Testing out release
candidates can be pretty dull, but it's crucial so please make the
effort to pull down the rc's and test against your own applications.

As I have two other major releases to get out, it would be very
helpful for driving the 2.8.2 release forward if engineers that have
write access to the OSG-2.8 branch come forward to pick up the batton
and drive the 2.8.2-rc series, both in terms of coordinating with the
community and merging bug fixes.  Volunteers please come forward ;-)

-- OpenSceneGraph-2.10 and VirtualPlanetBuilder-1.0 releases, aiming
for end of July (in time for Siggraph)

The next two releases are VirtualPlanetBuilder-1.0 and
OpenSceneGraph-2.10.  VPB is now broadly feature complete, but in need
of serious testing, debugging, refinement and of course documentation.
 The key feature I have just added was patching of previously built
databases, and support for database revisions.  The database revision
support is something that is part of OSG-svn/trunk, and will be part
of the OSG-2.9.5 that I'll roll out on Monday, so VPB-1.0 will either
have to go out against OSG-2.9.5 or wait for the stable OSG-2.10
release.  The VPB stable release really should go out with stable OSG
release so we should work towards getting OSG-2.10 and VPB-1.0 tested
in parallel and released in quick succession.

In terms of feature for OSG-2.10, it's mostly feature complete but
there are a number of loose ends that need tying up:

    Out of the box audio support for the ffmpeg plugin
    Fix pause and some playback timing issues in the ffmpeg plugin
    Add support for recording movies to osgViewer using ffmpeg plugin.
    Move the xine-lib plugin out into Deprecated.
    Add support for clipping planes to osgVolume.
    Tidy up the Present3D application + plugin and provide online resources.

    Other stuff that I can't think of right now...

    Other stuff that that community needs/would like to tackle for OSG-2.10.

--  Community Coordination

As a general development philosophy note, When it comes to stable
release Quality if King, features are expandable - so please think
like this when considering what extras you are thinking about
contributing over the next month and half, testing and bug fixing and
existing feature refinement are the top priority.

Over the next six weeks I'll be away for weeks family holiday at the
beginning of July, and week training/consultancy on the 3rd week of
July, so the amount of time that I can do coding, testing, bug fixing
and community coordination will have to fitted in to four weeks work.
The community no doubt will also be similarly distracted at various
times, so for us to get everything done will require good coordination
and extra level of effort.   Let me when you available to help out and
when you won't be available.  Also managers of groups that use the OSG
need to think about allotting time for engineers to help out with
testing, as a good quality release that works with your own software
is a real project benefit so well worth investing in.

Many thanks in advance for you help,
Robert.
_______________________________________________
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
_______________________________________________
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Reply via email to