Hey Stan,

Awesome approach. Structure wise looks great. Just one thought — Creating a child for each version in the production tree would increase the db a lot with each update. Also, there are updates wherein you don’t change any strings as such. How about we maintain a different version code for this localisation? Just like how we maintain seperate schema code for any local database in app. We would change this only when there’s any change in any of the label files. I think the tree would be shorter and optimised with this. What do you think?