[LANG-61] Merge separate lang repos into one Created: 17/Nov/16  Updated: 01/Dec/16  Resolved: 23/Nov/16

Status: Closed
Project: Language Bundles
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0.8

Type: Task Priority: Neutral
Reporter: Michael Mühlebach Assignee: Maxime Michel
Resolution: Fixed Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
Relates
Sub-Tasks:
Key
Summary
Type
Status
Assignee
LANG-62 Move lang scripts in reactor to new l... Sub-task Closed Maxime Michel  
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Sprint: Basel 72
Story Points: 2

 Description   

The current split of one separate repository per language generates a lot of overhead for maintaining and especially releasing.

In the unlikely case we want to keep it like this we should generate one JIRA project per language as well otherwise we can not track and manage the different versions & life cycles.



 Comments   
Comment by Philip Mundt [ 18/Nov/16 ]

Currently, the reactor will not be triggered when something changes in one of the lang modules. When a manual trigger is omitted, obvious problems might surface too late.
Going for the one-git-repo will solve this issue.

Comment by Mikaël Geljić [ 18/Nov/16 ]

Yes, JIRA is the current reason we can't release standalone lang updates; git & maven-wise everything was set up towards this.
That said, if that alleviates the current pain of manual releases, I don't mind so much—by the time we add the tooling around to deal with translations proactively.

Comment by Michael Mühlebach [ 28/Nov/16 ]

For QA: Please double check the korean language.

Comment by Philip Mundt [ 01/Dec/16 ]

Move to separate git repository is okay.

However now that the lang modules are in a combined and new git location, they scripts will require adjustment. Will create a followup issue for this.

Generated at Mon Feb 12 02:19:21 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.