Changes between Version 1 and Version 2 of RFC/6_MigrationGitHub
- Timestamp:
- 03/05/19 14:01:52 (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
RFC/6_MigrationGitHub
v1 v2 2 2 = RFC 6: Migration from SVN to !GitHub = 3 3 4 Author of the first draft: Markus Neteler, Martin Landa4 Authors of the first draft: Markus Neteler, Martin Landa 5 5 6 6 Status: Draft (05 Mar 2019) … … 12 12 The centralized source code management system Subversion (SVN) has served the GRASS GIS project very well since 2007. The project has established routines and infrastructure (code repository, ticketing system, developer wiki) connected to SVN. However, with an increasing number of Open Source developers using git (and here especially the success of !GitHub), time has come to migrate the source code base from SVN kindly hosted by OSGeo to !GitHub.com, a widely adopted development platform. 13 13 14 == Background information of discussions==14 == Background information of git migration == 15 15 16 * For Background and aims, see16 * For background and aims, see 17 17 * https://trac.osgeo.org/grass/wiki/GitMigration 18 18 * Results of a survey performed in early 2019: … … 21 21 * svn -> git test migration ongoing, see #3722 22 22 23 == New Github repositories ==23 == New !GitHub repositories == 24 24 25 25 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. 26 26 27 The following new !GitHub repositories have been created:27 The following new !GitHub repositories have been [https://github.com/grass-svn2git created]: 28 28 29 29 * repository **grass** 30 30 * Source code from 1999 to present day (SVN-trunk -> git-master) 31 * i.e., all 7.x release branches31 * i.e., all 7.x and later release branches + master 32 32 * repository **grass-legacy** 33 33 * Source code from 1987 - 1999 34 34 * i.e., a separate repository for older GRASS GIS releases (3.2, 4.x, 5.x, 6.x) 35 35 * repository **grass-addons** 36 * repository for addons ( this will become less relevant as people tend to keep their addons inown repositories)36 * repository for addons (in future this will become less relevant as people tend to keep their addons in their own repositories) 37 37 * repository **grass-promo** 38 38 * repository for promotional material … … 44 44 == Authorship and SVN user name mapping to !GitHub == 45 45 46 Given GRASS GIS’ history of 35+ years we had to invest major effort in identifying and mapping user names throughout the decades . The following circumstances could be identified:46 Given GRASS GIS’ history of 35+ years we had to invest major effort in identifying and mapping user names throughout the decades (CVS was used from 1999 to 2007; SVN has been used since 2007). 47 47 48 * user present in CSV but not in SVN 49 * user present in SVN but not in CSV 48 The following circumstances could be identified: 49 50 * user present in CVS but not in SVN 51 * user present in SVN but not in CVS 50 52 * user present in both with identical name 51 53 * user present in both with different name as some were changed in the CVS to SVN migration in 2007, leading to colliding user names … … 56 58 == Activating the !GitHub issue tracker == 57 59 58 As the date for the trac migration we selected 2007-12-09 (r25479) as it was the first SVN commit (after the years in CVS).60 As the cut-off date for the trac migration we selected 2007-12-09 (r25479) as it was the first SVN commit (after the years in CVS). 59 61 60 62 The tickets migrated from trac to !GitHub contain updated links in the ticket texts:
