With today’s rapid product release cycles, localization processes have to support multiple development branches simultaneously. Many teams are also moving to agile processes, where large epics are broken down into smaller feature stories, each with their own branch. Over the last few years at Adobe, we’ve devised various methods to address these problems. Some projects used a single super-dictionary, while others needed one dictionary per branch. There isn’t a one-size-fits-all solution because each project has its own unique requirements. During this session we will discuss five different methods along with their pros, cons and how they can be improved.
Localization Strategies to Support Multi-branch Development