Changes between Version 1 and Version 2 of Ticket #5777, comment 10


Ignore:
Timestamp:
09/27/2017 04:36:41 AM (3 years ago)
Author:
sebastian
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #5777, comment 10

    v1 v2  
    1 I am not sure whether it will be worth to share code for the CrowdIn integration between `buildtools` and the `cms`, or whether this will create more problems than it solves. Both systems implement a different workflow. While with our release process and therefore `buildtools` import and upload of translations are separate steps, this is one combined step with the `cms`. Also `buildtools` only uploads source strings and invalidates any translation if the source string has changed. I'm not sure what the behavior of the `cms` is here, but it is likely not the same either. So what remains to be shared wouldn't be much, and probably just results in additional boilerplate just for the matter of making some trivial code reusable, not to mention the problems of dependency management. 
     1I am not sure whether it will be worth to share code for the CrowdIn integration between `buildtools` and the `cms`, or whether this will create more problems than it solves. Both systems implement a different workflow. While with our release process and therefore `buildtools` import and upload of translations are separate steps, this is one combined step with the `cms`. Also `buildtools` only uploads source strings and invalidates any translation if the source string has changed, which differs from the `cms` as well. So what remains to be shared wouldn't be much, and probably just results in additional boilerplate just for the matter of making some trivial code reusable, not to mention the problems of dependency management.