381
edits
FlightGear Git: splitting FGData: Difference between revisions
Jump to navigation
Jump to search
FlightGear Git: splitting FGData (view source)
Revision as of 18:33, 16 October 2011
, 16 October 2011→Reasons to split fgdata
mNo edit summary |
|||
| Line 11: | Line 11: | ||
*** Might be fixed by using Git submodules.<ref>[http://book.git-scm.com/5_submodules.html Git Community Book: Submoduldes]</ref> | *** Might be fixed by using Git submodules.<ref>[http://book.git-scm.com/5_submodules.html Git Community Book: Submoduldes]</ref> | ||
** How to deal with licences? Until now there was a COPYING file in fgdata. When aircraft are split in seperate repositories, they'll likely need to include a license reference themselves. | ** How to deal with licences? Until now there was a COPYING file in fgdata. When aircraft are split in seperate repositories, they'll likely need to include a license reference themselves. | ||
** Need a concept for release management, maintaining version numbers, release branches et. al. | |||
== Starting new aircraft == | == Starting new aircraft == | ||