Hi, Although I would still love to see a snapshot as soon as possible...
It would be great to push visibly to a 1.9 release. You have a nice list formed below of items to be mentioned in release notes. But do we have a burn down list of items that need to be completed. In general, I see there being two fundamental approaches for the approach to the release. First, time based. Target a date and taint that date with a realistic set of hoped for features, what is ready is what is ready. What is not, slips to the next release. Second, feature based. Target a set of features, allowing it to be tainted with a reasonably realistic date. When the features are complete, the release is made. Which is preferred approach for those on the list? Can I suggest a wiki page to provide a focus for burning down issues prior to the release? Regards, Matthew -------- Original Message -------- Subject: [Flightgear-devel] Revision Log / Intended developments From: Durk Talsma <[EMAIL PROTECTED]> To: FlightGear developers discussions <flightgear-devel@lists.sourceforge.net> Date: 05/10/08 04:03 AM > Hi All, > > As mentioned by Curt on previous occasions, one of the more labour intense > parts of managing a release consists of the compilation of a comprehensible > revision log that lists the major changes / improvements to FlightGear. I > would appreciate it if somebody would give a hand in compiling such a list. > Last year, we used the WIKI to host this log. Eventually this page ended up > in > the Developer portal, under the section Done. There is still a "Changes since > 0.9.10 page, and I guess we could add a new "Changes since 1.0.0". Each > revision log typically consists of the sections: "New Features", "Bugfixes", > "Regressions", "New Aircraft", and "Improved Aircraft" > > Also, with the global target set for the release, I'm trying to get an > impression of which projects are still under development, and which would be > nice to have included in the release. Note that this overview implies by no > means a deadline, or anything like it. I'd just like to know what is > currently > going on, so I can get an impression of which projects need some more time, > and when we should set a feature freeze period. Based on my own reading of > the > developers list, I have the following list: > > Ralf Gerlich and Martin Spott: Complete scenery rebuild based on improved > terragear algorithms / object database updates > > James Turner: Refactoring / unification of Airport and runway code and its > ramifications for AI / ATC / Waypoint managment. > > Stuart Buchanan: 3D Clouds. > > Melchior: GUI improvements? > > Myself: Traffic Manager II. > > More aircraft improvements than possibile to mention. :-) > > Anything else? > > > Cheers, > Durk > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
