I am still seeing the behavior today. Basically, as noted in comment #2, we think this is related to the language timestamps not updating, even though the underlying strings are. For example, at the time of this writing, compare "tpac" timestamp here:
(Right now they are about an hour apart, but that is just from me fiddling. If we do nothing else, the 3.0 timestamp just gets further and further behind, though the strings inside do reflect the updates.)
I am still seeing the behavior today. Basically, as noted in comment #2, we think this is related to the language timestamps not updating, even though the underlying strings are. For example, at the time of this writing, compare "tpac" timestamp here:
https:/ /translations. launchpad. net/evergreen/ master/ +lang/es
vs here:
https:/ /translations. launchpad. net/evergreen/ 3.0/+lang/ es
(Right now they are about an hour apart, but that is just from me fiddling. If we do nothing else, the 3.0 timestamp just gets further and further behind, though the strings inside do reflect the updates.)