Hi All, After a period of having been extremely busy at work, following a switch of jobs and moving to a different country, I'm slowly coming back to life. December is already well on it's way, and it would be great if we could manage another major release this year. Behind the scenes, James Turner has been working hard to automize many aspects of the release process, so we should be relatively well off. Currently, there are still a few release blocking bugs, but in general, I think that prospect of a release is pretty good. Nevertheless, there are still a few things that we need to make a decision on.
Firstly, what is the next version number going to be. My initial thought would be 2.1.0, but it also makes sense to call if 2.2.0 (thanks for the suggestion, James), so that we can reserve 2.1.0. for bugfixes on the current version, or at least move toward a versioning system like that (i.e. the next series could be 2.2.0 for stable, and 2.3.0. for development). Seconly, do we want to maintain our current aircraft selection, or do we want to include a (partially) updated selection from our git repository, or -alternatively- do we want to strip the entire selection down to just single aircraft, and make the others downloadable from our main website. I know that James turner is working towards an infrastructure that should enable this, but I'm not sure whether we are already comfortable enough to just use one single aircraft. On a related note, I would consider shipping the base flightgear distribution entirely without the AI directory, and also make that available as a separate distribution. but again, I'm not comfortable about this as long as we don't have an easy, user friendly way of installing these add-ons). In any case, thought, ideas, and suggestions are welcome. Cheers, Durk ------------------------------------------------------------------------------ Oracle to DB2 Conversion Guide: Learn learn about native support for PL/SQL, new data types, scalar functions, improved concurrency, built-in packages, OCI, SQL*Plus, data movement tools, best practices and more. http://p.sf.net/sfu/oracle-sfdev2dev _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
