On Sun, 21 Aug 2011, Torsten Dreyer wrote: > I just merged the release/2.4.0 branches up to tag version/2.4.0-final > into the master branch of SimGear and FlightGear. > The intention for the master branch of the two code repositories is to > always hold the current version. > > For consistency, I'd like to have the same strategy on fgdata sometime > in the future. Once we have this established, people are pushing to a > to-be-created 'next' branch and no longer 'master'. > > I don't have a good idea about how to make the move and how to make sure > all the fgdata commiters will be using a new branch from a specific time > on. Does anybody out there has one?
Hi, Perhaps we could start up next as a post aircraft split-off branch? That is, only containing core data and possibly the base package aircraft. (I'm not sure if those should be in there or kept separate like any other aircraft. Uniformity suggest the latter and would maybe suggest a composite base package repro similar to fg-meta.) Cheers, Anders -- --------------------------------------------------------------------------- Anders Gidenstam WWW: http://www.gidenstam.org/FlightGear/ ------------------------------------------------------------------------------ Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration. Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
