Bug 1331358

Summary:	please pull translations on 2016/05/02
Product:	[Fedora] Fedora	Reporter:	jibecfed <jean-baptiste>
Component:	comps	Assignee:	Stephen Gallagher <sgallagh>
Status:	CLOSED RAWHIDE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	24	CC:	kevin, piotrdrag, vpavlin
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-04 20:13:12 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description jibecfed 2016-04-28 11:06:58 UTC

Comps' strings where updated on Zanata on "21/04/16 18:32 by nirik"

According to schedule, the software string freeze is on "2016-03-08" : https://fedoraproject.org/wiki/Releases/24/Schedule

I informed teams so they can have a look and correct strings.
More than 2000 words where translated, so the amount of changes is now significant enough to ask you if it is possible rebuild comps to include it.

Would you please pull translations next Monday and rebuild Comps so user have the correct translations ?

If for some reason you have to change strings after deadline, please inform trans team through the mailing list.

Thanks by advance for your help and your understanding

Comment 1 Kevin Fenzi 2016-04-29 16:05:01 UTC

Sure. The reason things are behind here is that comps was only recently migrated from transifex. ;( 

Happy to pull on monday and update things. Or more often until we have better translations. Just let me know.

Comment 2 Kevin Fenzi 2016-05-02 14:26:46 UTC

I just pulled translations and updated comps. 

https://git.fedorahosted.org/cgit/comps.git/commit/?id=f34330c8e5b545e3cd7f8079d71a4570ea02a538

I'm happy to update things periodically as we go forward. 

Note also that comps only has a master branch, so we need to update it for rawhide from time to time anyhow, and I am not sure how it could fit into the string freeze. ;( 

Shall we close this now? Or is there anything further to do here?

Comment 3 jibecfed 2016-05-03 11:58:38 UTC

thanks for you work. If translated strings are included in Comps and everything is fine for final release, everything is good.

About branches :
If strings changes between branches : as comps looks like to be release-focused, I think it would be better to have the same branches in git and in Zanata.

We have a good translation memory in Zanata, if you add a string in different branches, we'll translate it only once and we will manually update the other branches.
Just remember to lock the old branches.

Comment 4 Kevin Fenzi 2016-05-03 15:08:58 UTC

Currently comps does not use or have any branches. All work is done in master. 

Which is why string freeze doesn't make much sense for it, as new rawhide strings can appear at any time. ;(

Comment 5 jibecfed 2016-05-04 19:57:59 UTC

ok, we can close then, thanks for your help