----- Original Message ----- From: "Gianluca Cecchi" <gianluca.cecchi@gmail.com> Sent: Wednesday, May 14, 2014 4:35:57 AM
On Tue, May 13, 2014 at 6:44 PM, Einav Cohen <ecohen@redhat.com> wrote:
we are typically not updating translations for versions that were already GA'd (3.4), therefore I recommend to concentrate at this point only on the 'master' version (which is currently tracking the ovirt-engine-3.5 translations, practically).
once we will branch the ovirt-engine-3.5 code out of the 'master' code branch, I will create an 'ovirt-3.5' version in Zanata, to track the ovirt-engine-3.5 translations. the 'master' version will remain the translation tracker for the 'master' code branch [which would practically become the baseline for the next ovirt-engine planned release (ovirt-3.6?)].
As I see from today message that 3.5 alpha is going to be composed, is there a needed percentage to cover before the language can be inserted between the available ones?
[apologies for the extremely late response] we never discussed this before, I assume that a language should be at least in ~70/75% completion in order to justify its introduction into the product (need ack/nack from others on that number?) right now Italian stands on 1.22% translation completion in the 'master' version of the 'oVirt' project in Zanata, so I don't think that it justifies introducing it into oVirt at the moment. Gianluca: do you have an ETA for completion of at least ~70/75% of the Italian translation? if it would be early enough, we can definitely consider adding it to oVirt 3.5 (we obviously missed the ovirt-3.5 alpha milestones, but we can try and introduce it in later ovirt-3.5 milestones).
Any chance to see it in 3.5 alpha?
Gianluca