FlightGear Git: splitting FGData: Difference between revisions

FlightGear Git: splitting FGData (view source)

464 bytes added , 16 October 2011

159

edits

@@ Line 48: / Line 48: @@
 == Step 2: Remove all aircraft from fgdata ==
-Fgdata will be renamed, so we can keep it for some time until we're sure everything is safe. We can then put the "new" fgdata (without all the aircraft data) up.
+Fgdata is frozen, all commit privileges revoked. Meanwhile, a new fgdata repository is created and tested.
+== Step 3: Switch fgdata ==
+Once tests show that the new repository is working fine and no data has been lost, the repositories will be switched.
+The exisiting repository is renamed, and the new repository takes its place and access to the new repository is setup.
+The historic fgdata is kept but stays frozen, at least until we're sure everything is safe. It may also be a good idea to keep the existing repo, since it contains release branches - which are not part of the new repository and would be lost otherwise.
 {{Appendix}}