As the poexport script is not running on staging, requesting an export requires a losa to run the export script manually. That in itself could probably be fixed but the other problem is that the queue in the database is usually filled with stuff that is not interesting for the QA at hand and might cause the script run to take too long and not even get to the request in question. Hence it is wise to clear the queue before requesting an export for QA purposes. Today the following conversation occurred on the matter.
henninge> losa ping ;)
<mthaddon> henninge: hi
<henninge> mthaddon: Hi!
<henninge> mthaddon: can you please clear the translations export queue on staging?
<mthaddon> henninge: how do I do that?
<henninge> delete from poexportrequest;
<mthaddon> henninge: is there a bug about needing manual SQL to do this?
<henninge> mthaddon: I am not aware of it but it's a good idea to fix that.
<henninge> mthaddon: would a script be better?
<henninge> or something in the UI?
<henninge> but it's really only ever needed for QA and such.
<mthaddon> henninge: yep - if you can file a bug about it, I'll run the SQL - UI would be best, script (with tests) would be okay
<henninge> mthaddon: will do, thanks
<mthaddon> henninge: running manual SQL is something we want to avoid, even on QA/staging :)
If a UI solution is considred, bug 6082 might be fixed along the way. A four digit bug!