Hi, Though I prefer an official release, I can live with beta release so we can avoid killing Durk ;-) I guess it is a good to have a release (in either official or beta) since we can have lots of feedback reports that will improve the quality of FG for the scheduled release in the next Christmas. I also want to add that we have enough features and bug-fixes for beta release. Shader effects and generic input device are in progress, but I guess we can improve these by FSWeekend (or Christmas).
I get lots of feedback reports from Mac users on every official release, but I have less than ten for every snapshot release. So cutting a release is more effective on Mac platform in terms of collecting feedback reports. By the way, is the version number going to be 1.9.2? I think it should be 1.10.0 since it is not a maintenance release. If we are going to have shadow effect working by Christmas, then we could go to 2.0.0. Best, Tat On Sep 6, 2009, at 9:36 PM, Tim Moore wrote: > On 09/06/2009 08:13 AM, Durk Talsma wrote: >> Hi James, >> >> I'm certainly open to the idea, but I don't think I'm able to manage that, >> since I'm both primarily responsible for organizing FSWeekend, and have been >> coordinating the releases in the last few years as well. Having two >> deadlines >> come up at the same time, in addition to teaching four courses (of which two >> are new -> lots of preparation), a deadline for a grant proposal, and a >> major >> review paper (both Sept 30), as well as serving on a PhD defense committee >> and >> preparing a symposium talk (Nov 2 and 3 respectively), I'm not sure whether >> I'm alive by the start of FSWeekend. :-) >> >> For this reason, my personal preference would be to continue regular >> development until FSWeekend, than allow us a few weeks for bugfixing and >> Beta >> testing. That would put the release around christmas time, which would be a >> lot more of an easy time for me. >> >> I agree with Heiko (see earlier post in this thread) that we should have a >> more careful beta testing period. Last year we had a few last minute >> check-ins >> that turned out to bite us. Let's try to circumvent that. >> > I'd prefer to shoot for having a strong beta to show at FSWeekend, then do a > release > around Christmas. I suppose this implies a "feature freeze" in the release > around the > 1st of October. My preference would be to do the release like we did the > maintenance > release -- from a git branch that contains only selected patch sets from CVS. > > In order to get users to actually test the beta, do we need to essentially > cut a release? > > Tim > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
