sharpetronics/QGIS
1
0
Fork 0
mirror of https://github.com/qgis/QGIS.git synced 2025-08-11 00:03:56 -04:00
Code Issues Packages Projects Releases Wiki Activity

Updated QGIS Platform migration plan (markdown)

Vincent Picavet 2018-02-23 10:19:44 +01:00
parent 3cb057ed4f
commit 8db739b88b
1 changed files with 36 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

38
QGIS-Platform-migration-plan.md

@ -6,13 +6,46 @@ This draft takes Gitlab as a target.
## Requirements
- Keep backups of our issues, code, PRs
Issue tracker
- migration of issues
- migration of issues trackers
- migration of issues categories
- migration of issues status
- migration of issues assignments
- migration of issues Ids
- migration of issues URL
- migration of issues attachment
- migration of issue creation date
- migration of issue content formatting
- migration of internal linking between issues
- migration of references between issues
- migration of references between issues and PR / commits
- migration of versions / roadmaps in issues
- migration of comments author
- migration of comments dates
- migration of issue creator
- migration of user mapping
- migration of roadmap items ( = milestones)
- migration of notifications parameters for each issue/user
Code tracker
- migration of source code and history ( git repository)
- migration of PRs
- migration of PRs authors
- migration of PRs comments
- migration of code comments in PRs reviews
Various
- Opensource solution
- Allow to backups of our issues, code, PRs
## Actions plan
- Try a migration of issues from Redmine to a Gitlab instance with the requirements above
- Decide between in-house or gitlab.com ( needed for item below)
- Define user mapping between Redmine users and Gitlab
- email users so they create an account on the target platform if they want to have their issues and comments still assigned. Also an opportunity to ask them nicely to clean their issues in redmine.
- email users so they create an account on the target platform if they want to have their issues and comments still assigned.
- Also an opportunity to ask them nicely to clean their issues in redmine.
- Determine how much users kept and lost
- Take the decision to apply the plan
- Make public announcement on the forthcoming change
@ -25,6 +58,7 @@ This draft takes Gitlab as a target.
- Make Github read-only ( Code & PR)
- Import GitHub code and PRs to GitLab
- Switch code and PR references to Gitlab in all documents
- Document how to input a new issue
- Setup a code mirror on GitHub to keep Travis CI happy
- Convert Travis scripts to GitLab CI
- Shutdown Redmine