I've pushed Erik's new sound code and my code for effects to the master branch on gitorious and somewhat pompously tagged it as v2.0.0-rc1 i.e., the first candidate for our upcoming release. The home pages for the flightgear and simgear repositories are http://gitorious.org/fg/flightgear and http://gitorious.org/fg/simgear.
There is code in current CVS that isn't in master, and I'll produce a list of those in a separate email. I made this tag with all sorts of reservations: * I'm not sure there's buy-in for making this the source for the release; * There is one known bug in the model effects code (material animations) that will take an evening of work to fix. One could argue that the model effects code should not be in a release candidate; * tagging a release candidate 12 days before the proposed release date is hopelessly optimistic. There is a large list of open bugs and issues, and we need to build releases of this candidate for testing. * The data repository isn't tagged at all. I don't think there's anything magic about 1/1/2010 as a release date, but my sense is that the feature set we have now (and that I've included in the master branch) is what we'd like to have in the release. On the other hand, we don't want to release total crap and have to do a bug fix release right after. We have a large list of bugs from John Denker; some are easy to dismiss, but most are at least worth a look and a response, whether it's WON'T FIX or SHOW STOPPER. Can we get set up on a public bug tracker and get these bugs entered soon? If so, we can converge on a release and have some criteria for when it's ready. We've made noises about this before, but now is really the time. Tim
------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
