summaryrefslogtreecommitdiffstats
path: root/wiki/src/blueprint/GitLab.mdwn
diff options
context:
space:
mode:
authorintrigeri <intrigeri@boum.org>2019-11-18 14:59:09 +0000
committerintrigeri <intrigeri@boum.org>2019-11-18 14:59:09 +0000
commit190e20c8f1c4e9cc1769e66b3f7e0e7d70201650 (patch)
treec8849602babb932e45b307d412a6113cfe95e97e /wiki/src/blueprint/GitLab.mdwn
parent9ffaa50a39d92d0d7602882e94d21bf7fe421e7c (diff)
GitLab: better describe issue ID constraints and random ideas we had
Diffstat (limited to 'wiki/src/blueprint/GitLab.mdwn')
-rw-r--r--wiki/src/blueprint/GitLab.mdwn26
1 files changed, 19 insertions, 7 deletions
diff --git a/wiki/src/blueprint/GitLab.mdwn b/wiki/src/blueprint/GitLab.mdwn
index 1f41025..0c2bafe 100644
--- a/wiki/src/blueprint/GitLab.mdwn
+++ b/wiki/src/blueprint/GitLab.mdwn
@@ -274,19 +274,31 @@ Tails community.
### MUST
-* For every existing Redmine issue, the meaning of `#NNNN` MUST be
- preserved unambiguously. (This probably implies that we can't have
- a GitLab issue with the same ID.)
+* For every existing Redmine issue, the meaning of its `#NNNN` ID MUST
+ be preserved unambiguously. This implies that we can't reuse
+ existing Redmine issue IDs in our main GitLab project, where most
+ issues will live.)
* [[!tails_ticket NNNN]] and
<https://redmine.tails.boum.org/code/issues/NNNN> links MUST point
- or — possibly transitively, via a placeholder issue — redirect to the
- relevant GitLab issue.
+ or — possibly transitively — redirect to the relevant GitLab issue.
+
+ Implementation idea: start with a static web redirector, and then:
+
+ - This is sufficient to solve the problem for issues imported into
+ our main GitLab project, if they have the same ID as they used to.
+
+ - For issues imported into another GitLab project, we either need
+ extra redirection rules based on a mapping from Redmine issue IDs
+ to GitLab (project, issue ID) tuples, or placeholder issues on
+ GitLab that handle a second redirection step (GitLab might handle
+ the redirection iself when an issue is moved from one project to
+ another)
* Preserve issue private/public status. Given GitLab's permissions
model, this implies that some issues MUST be migrated to another
- GitLab sub-project than the default one; for details, see the
- "Private issues" section above.
+ GitLab project than the default one where most of our issues will
+ live; for details, see the "Private issues" section above.
Example: [[!tails_ticket 10346]]