Not Considering

Branching

Currently, SDL TMS does not support multi branching.

When it comes to approach a localization project that follows Agile methodologies, we lack a solution that helps us monitor a Git/SVN repo to pick from branches new/edited contents.  We need to automate highly-repetitive and low added-value tasks like monitoring the branches, picking up translatable contents, and once translation is complete, putting back the localized files where they belong in the source repo.

Right now, the only solution is to check each branch manually, analyze with Passolo, and if needed, create bundles that we process through TMS. This process is time-consuming and we cannot concentrate on internationalization/globalization questions. 

Parents
  • Hi,

    We agree the agile development is taking more and more space in the industry and the localization process needs to adapt quickly also.

    We are evaluating an integration with different code repositories. As the .Net parser is very popular and this is usually used togheter with Microsoft technologies we were looking at TFS in the first place.

    Can you give us more details

    - on the workflow you are using

    - which steps you find useful to automate between the repository and Passolo

    - how is your development environment set-up i.e. Git with Microsoft Visual Studio?

    Thank you

    Florina

Comment
  • Hi,

    We agree the agile development is taking more and more space in the industry and the localization process needs to adapt quickly also.

    We are evaluating an integration with different code repositories. As the .Net parser is very popular and this is usually used togheter with Microsoft technologies we were looking at TFS in the first place.

    Can you give us more details

    - on the workflow you are using

    - which steps you find useful to automate between the repository and Passolo

    - how is your development environment set-up i.e. Git with Microsoft Visual Studio?

    Thank you

    Florina

Children
No Data