You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 9, 2022. It is now read-only.
Have a special git branch for interacting with Transifex*
We could merge everything to a 'transifex' branch and wait for translations before merging that to the release branch but this causes a delay and introduces coordination difficulties (what if some of the pieces are ready to go but others aren't? what if we need to roll back a piece?).
The text was updated successfully, but these errors were encountered:
I use a transifex branch for my project. Since it is open source, I gave Transifex the URL of the resource on GitHub to update automatically. It points to the transifex branch:
We merge the latest translations into our master branch and update the transifex branch whenever we release a new version or start a 'string freeze'. This way the translators have time to translate a release while the developers keep playing with the master branch.
I guess you can't avoid a translation delay unless you let people translate experimental versions that change all the time. That could be a lot of wasted translator time.
We are still experimenting ourselves. One thought we had is that if you use feature branches (aka Gitflow) you could start translations once each feature gets completed. This potentially allows you to start translating earlier and avoid a big 'string freeze' late in the dev cycle (freezes feel so un-agile).
Have a special git branch for interacting with Transifex*
We could merge everything to a 'transifex' branch and wait for translations before merging that to the release branch but this causes a delay and introduces coordination difficulties (what if some of the pieces are ready to go but others aren't? what if we need to roll back a piece?).
The text was updated successfully, but these errors were encountered: