not_interested No Versioning
You can use without versioning - just using the default latest set of resources. For smaller projects with continues deployment or no deployment process at all this can be a suitable solution.
wrap_text "Rolling" Versioning
Most bigger projects will do a versioning divided into stages like:
Everytime you want to deploy to next stage you can copy the resources eg. from latest to staging by creating a new version (and retype staging for new version name).
call_split Semantic Versioning
Semantic Versioning can be useful if you deploy an application in different versions and you got no control over the users upgrading (eg. iOS Applications,…).
1.0.1 → minor (feature) → 1.1.0
1.1.0 → major (breaking) → 2.0.0
When deploying - just create a new version based on your lastest version and update your production code to use that new version.
published 1.0.0 → use 1.0.0
published 1.1.0 → use 1.1.0
published 1.1.1 → keep using 1.1.0 if no changes
Most time you won't need to create a new version when doing bugfix.
code Update your code
Update your locizify script to include targeted version:
Update i18next with locize backend:
Have questions? Contact us!