Just to approach the perspective of a new release from a slightly different angle. I would indeed like to start piecing it all together. As I mentioned previously, my last three months have been rather hectic. Starting a new job, moving, and being without an internet connection for nearly two months. But, as I'm settling in into my new job, new home, with my internet connection restored, and with a new FlightGear capable computer almost assembled, it looks like I'm fully in the green to resume my duties as release coordinator.
As far as I can tell, we're in a really good shape right now. Are there any pressing issues that we need to resolve before we can do a major release. If not, I would like to try and roll up a prerelease version of the source and data directory. Even though we are close to being ready to release, it would still be a good thing to take a few weeks to iron out any remaining rough edges. This would also give me an opportunity to finish the remaining issues. In particular, I still need to do the following: - Compile a comprehensive change log - Finish the final selection of aircraft for inclusion in the release - Check any issues that may come up with regard to Scenery - Check how things are proceeding on the windows and Mac front. For this reason, I'm aiming to have everything ready by December 16, or thereabouts. In the mean time, we should probably focus on improving stability instead of adding new features. 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
