Bug 1422792

This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.

Guess it was fixed by reporter.

NO.

I assume this has not changed - so moving this to stay in Rawhide

Hi Igor
We are in F28 cycle. Is this bug to be fixed in F28?

Is this going to be fixed or not? It seems just update??

Currently we update translations periodically, but still manually.

I don't think this process must be automated. It is OK IMHO when it is manual as long as it is launched when needed.

I'd like to show an example how it looks now. DNF version 4.1.0 has been released on February 12. Last time the updated *.pot file has been uploaded to Zanata was February 6 in the morning. After that some messages have been modified and a new *.pot file has *not* been uploaded to Zanata. Translators did not even have a chance to see and translate those new messages. Also, after February 6 no *.po files have been downloaded from Zanata. This means that those messages which had been added or modified shortly before February 6 and translators have translated them in Zanata have not been updated in the source repository.

AFAIK the maintenance scripts upload the *.pot file to Zanata and download *.po files immediately. This is not the best idea because translators should have a chance to translate. But it is fine as it is if the development cycle is similar to that:

* The script is run (Feb 6 in the evening): uploads the new *.pot files to Zanata. No problem if it downloads *.po files at the same time.
* The developers may continue their work but must not add or modify any messages (string freeze period). Translators have a chance to translate. This must take several days.
* The script is run again (Feb 12): downloads the updated *.po files from Zanata. No problem if it uploads the new *.pot file because it is the same content as before.
* DNF is ready for a release.

If it does not have to be automated and everything may remain unchanged then it's difficult to define the criteria which must be met in order for us to call this bug fixed. I suggest to close this bug if:

* The script is run now to upload the *.pot file to Zanata. Today translation sprint starts [1] so it is the last moment to do it. The script may be run from the master branch or from the 4.1.0 branch (there is no such branch now so it would have to be created).
* Developers do not add or modify any message (in the same branch as above) until the end of the sprint which is March 5, 2019.
* The script is run again on March 5 or better March 6. The new *.pot file should be the same as today and *.po files should contain the updated translations.
* The new release is made: this can be 4.1.0-2 if we are working in the stable branch or 4.1.1 if we are working in master.

Igor, I think you were present when we were discussing this issue recently at DevConf.

[1] https://fedorapeople.org/groups/schedule/f-30/f-30-trans-tasks.html

Hi Rafal, I did set up automatic uploading of .pot files to Zanata. Downloading of translated *.po is for now still manual, but the main problem (giving more time to translators for their work) should be solved for now.

Thank you, Marek. You did more than I expected. Is this automatic script visible in the source code repository?

However, lack of translation updates is a problem. I don't mind if it's done manually as long as it is actually done. There have been 2 releases of dnf since March 12 and no translations have been pulled from Zanata.

My suggestion: please add a line to dnf/rel-eng/README explaining how to pull the translations, it should be the first command, and make sure that the right people are actually aware of this change and follow it. Then let's close this bug and call it fixed.