Danilo needs to fix the issue in Rosetta (few days), then we might be lucky and the strings don't need to get reimported into Rosetta (otherwise that would be another 2 days or so), then the updated packages have to be exported and uploaded (1 day) and then they usually stay in a special repository for about a week until it's proven that they actually fix the issue (and don't cause regressions) following which they will be moved to the actual updates repository.
So I guess we are facing anything between a couple of days and 2 weeks.
Is a bug report about the KTurtle issues around? I'd like to find out if the bug triage squad may have messed up, because a broken KTurtle would certainly have forced us to choose a more reliable translation approach.
Danilo needs to fix the issue in Rosetta (few days), then we might be lucky and the strings don't need to get reimported into Rosetta (otherwise that would be another 2 days or so), then the updated packages have to be exported and uploaded (1 day) and then they usually stay in a special repository for about a week until it's proven that they actually fix the issue (and don't cause regressions) following which they will be moved to the actual updates repository.
So I guess we are facing anything between a couple of days and 2 weeks.
Is a bug report about the KTurtle issues around? I'd like to find out if the bug triage squad may have messed up, because a broken KTurtle would certainly have forced us to choose a more reliable translation approach.