chore(i18n): Move 2.0 to its own Transifex project #8022
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We need to do this since there will be backwards incompatible changes to language strings in 2.0 most likely and there is no way to keep Transifex from syncing those changes back to 1.x without creating a new project.
ewinslow
force-pushed
the
i18n-new-transifex-project
branch
from
df5f656
to
d9c26b2
Compare
|
Once nice thing is that the resources from the "elgg-core" project are already set up to auto-update from the 1.x branch, so there's no conflict there. I think we should wait until we create the 2.x branch before we set up any auto-updating for elgg-core-2 strings. Since things will be in flux, we probably don't want translators working on stuff until the string keys are stable. |
9 tasks
|
This seems like a no-brainer unless there's something I'm missing? |
|
LGTM |
ewinslow
added a commit
that referenced
this pull request
Mar 2, 2015
chore(i18n): Move 2.0 to its own Transifex project
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We need to do this since there will be backwards incompatible changes to language strings in 2.0 most likely and there is no way to keep Transifex from syncing those changes back to 1.x without creating a new project.