Sharing details page: automatic synchronization detection needs to be aware of LP usage
Bug #775701 reported by
Henning Eggers
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
With upstream translations sharing, if an upstream project is hosted in Launchpad, it does not need to import translations from anywhere in order for upstream translation sharing setup to be considered "complete". The checklist on the +sharing-details page should accept the following combinations as "configured correctly":
"Hosted in Launchpad" and "Synchronize templates (or both)"
"Hosted externally" and "Synchronize templates and translations."
Revision history for this message
| Francis J. Lacoste (flacoste) wrote | #1 |
Revision history for this message
| Robert Collins (lifeless) wrote | #2 |
| Changed in launchpad: | |
| importance: | High → Low |
To post a comment you must log in.
dpm's rationale for High:
We want this feature to be used for both external projects and for projects hosted in Launchpad. Right now projects in Launchpad are expected to do automatic imports of both translations and templates to use the feature, where it should be possible for them to just import templates to do upstream sharing. Importing both templates and translations is not only a bit of a waste, but unless the maintainers are really active in fetching translations from Ubuntu -which is not generally the case-, it can lead to overwriting new translation data with old one. A common example is the case where translations are automatically imported, but out of sync with newer translations from Ubuntu: in that case upstream imports have got precedence and will overwrite newer Ubuntu translations.