Hey,
On Freitag, 22. November 2019 17:44:22 CET tails-translations@??? wrote:
> this strings are also stuck: they were fixed in weblate by Muri 23 hours ago:
> > https://translate.tails.boum.org/translate/tails/requirements/de/?checksum
> > =f0082d63109a429
> >
> > https://translate.tails.boum.org/translate/tails/warning/de/?checksum=6f1b
> > efc313f97298#history
> Ok, maybe they were not stuck, simply weblate waits a bit before committing,
> so it was not committing the fixes.
>
> The changes were on weblate interface, but they were not on the repo. So I
> guess that is why it kept complaining.
The issue is caused by the lazy commit feature of Weblate. This feature tries
to reduce the amount of commits by merging several fixes together in one
commit. The downside of this feature is, that Weblate sometimes waits 24h
hours before committing the last state of one file to the repository. I havn't
fully understood the algorithm, when Weblate decides to push directly and when
it waits 24h.
> Maybe those checks should be done in weblate's version of the wiki?
> (BTW, weblate has a very easy to use check framework)
The checks are executed on Jenkins and triggered by any change in the master
branch, that males it possible to check also fixes that were done by Git
directly.
If someone starts implementing those rules in Weblate, than this should help
committing broken stuff in first place. If anyone has a good ruleset from
Weblate, create an issue, so we can can implement them.
>From the Weblate Administrators point of view we first need to upgrade Weblate
2.20 to 3.9.1 before we try to improve things. Because there may be bugs fixed
in meanwhile. The upgrade is scheduled at 10-12. Dec.
hefee
