Changes between Version 12 and Version 13 of RFC/6_MigrationGitHub

Timestamp:

03/10/19 12:54:02 (6 years ago)

Author:

neteler

Comment:

Note about overlap in time in repos

RFC/6_MigrationGitHub

@@ -26 +26 @@
 Since migration is a huge effort, massive work on converting the existing source code (organized in branches) and the related trac tickets has been done. The main scope of weeks of efforts was to preserve as much information as possible by converting trac/svn references to full URLs pointing to the old system kept available in read-only mode.
 
-The following new !GitHub repositories have been [https://github.com/grass-svn2git created]:
+The following new !GitHub repositories have been [https://github.com/grass-svn2git created]. Note that the "cut-off" date of the main **grass** repository does not correspond to the first upload to CSV which was then migrated to SVN. The repositories **grass** and **grass-legacy** overlap in time since they contain different branches:
 
  * repository **grass**
-   * Source code from 2001 (starting with r31142 - welcome to GRASS 7.0.svn) to present day (SVN-trunk -> git-master)
+   * Source code from 2001 (as the starting commit r31142 was selected, i.e. "Welcome to GRASS 7.0.svn") to present day (SVN-trunk -> git-master)
    * i.e., all 7.x and later release branches + master
  * repository **grass-legacy**
-   * Source code from 1987 - 2018 (r72361 - last commit to releasebranch_6_4)
+   * Source code from 1987 (pre-public internet times; manually reconstructed) - 2018 (r72361 - last commit to releasebranch_6_4)
    * i.e., a separate repository for older GRASS GIS releases (3.2, 4.x, 5.x, 6.x)
  * repository **grass-addons**
-   * repository for addons (in future this will become less relevant as people tend to keep their addons in their own repositories)
+   * repository for addons
    * code re-organized from directory-like layout (grass6, grass7) into branches-like layout (master == grass7, grass6, ...)
  * repository **grass-promo**