|
|
|
[[_TOC_]]
|
|
|
|
|
|
|
|
# Main Gitlab issue
|
|
|
|
# Overview
|
|
|
|
|
|
|
|
* #768
|
|
|
|
When CiviCRM moved from SVN to Git, the full history of code changes was not imported into Git. By that time, CiviCRM had existed for more than 5 years and had accumulated a lot of changes, but given the fast pace of the project, it was not particularly relevant to import everything.
|
|
|
|
|
|
|
|
# Repos
|
|
|
|
The SVN service was kept alive since then, but has had near 0 activity for the past 2-3 years. However, it still occupies resources on our main hosting server (`svn.civicrm.osuosl.org`, 2 GB ram VPS server), is monitored and requires regular maintenance as any server.
|
|
|
|
|
|
|
|
The server `svn.civicrm.org` hosts these repos:
|
|
|
|
Very occasionally, developers might go back to the SVN archive to check when a feature was introduced (usually by spot-checking branches or tags). The history, while not used often, still provides useful information about the history of the project.
|
|
|
|
|
|
|
|
```
|
|
|
|
# du -sm civicrm extdir hrd php quest sfschool tools
|
|
|
|
1763 civicrm
|
|
|
|
1 extdir
|
|
|
|
2 hrd
|
|
|
|
3 php
|
|
|
|
94 quest
|
|
|
|
11 sfschool
|
|
|
|
168 tools
|
|
|
|
```
|
|
|
|
Around 2017, @xurizaemon, who did want to consult the SVN history, but not bother with using SVN, tested a full SVN to Git migration only for archival purposes. Since it seemed like a viable option to get rid of the SVN service, we then did a few test runs and eventually managed to produce a Git repository for historical purposes that had the full history and all the branches (but not tags).
|
|
|
|
|
|
|
|
# Motivation
|
|
|
|
The new repository is available on Github: https://github.com/civicrm/civicrm-svn
|
|
|
|
|
|
|
|
* The SVN service has near 0 activity for the past 2 years
|
|
|
|
* @xurizaemon has done tests to migrate the SVN repo to a git repo (https://github.com/fuzionnz/civicrm-svn). It does not have the branches, but would be good enough?
|
|
|
|
* (_Comment_ (totten): I don't need to go back to svn often, but when I do... the flow has generally required spot-checking the tags and branches. So I really don't want to lose that info.)
|
|
|
|
* The SVN service is still using a VM with 2 GB ram, which needs to be monitored, upgraded, backed-up, as any production VM.
|
|
|
|
The progress was tracked in Gitlab: #768
|
|
|
|
|
|
|
|
# Roadmap
|
|
|
|
|
| ... | ... | @@ -41,3 +29,20 @@ The server `svn.civicrm.org` hosts these repos: |
|
|
|
* http://savannah.gnu.org/ or http://savannah.nongnu.org/ ([import instructions](http://savannah.gnu.org/maintenance/SvnImportExistingRepo/))
|
|
|
|
* http://www.cloudforge.com/pricing ($2/mo for 2gb quota; [import instructions](https://help.cloudforge.com/hc/en-us/articles/215242503-Importing-an-Existing-Repository-into-CloudForge-Subversion))
|
|
|
|
* http://repositoryhosting.com/features ($6/mo; no mention of quota)
|
|
|
|
|
|
|
|
# Repos
|
|
|
|
|
|
|
|
The server `svn.civicrm.org` hosts these repos:
|
|
|
|
|
|
|
|
```
|
|
|
|
# du -sm civicrm extdir hrd php quest sfschool tools
|
|
|
|
1763 civicrm
|
|
|
|
1 extdir
|
|
|
|
2 hrd
|
|
|
|
3 php
|
|
|
|
94 quest
|
|
|
|
11 sfschool
|
|
|
|
168 tools
|
|
|
|
```
|
|
|
|
|
|
|
|
Only `civicrm` was archived on github. |
|
|
\ No newline at end of file |
