On Wednesday, July 16, 2014 12:29:43 PM UTC-7, cboos wrote: > > On 2014-07-09 9:54 AM, falkb wrote: > > > > > > Am Sonntag, 15. Dezember 2013 10:30:58 UTC+1 schrieb cboos: > > > > > > As I see it, the main issue here would be the translations. There's > a > > great amount of new or updated translations on Transifex, but they > > haven't been integrated yet. > > > > > > What does "integration" mean here? What is actually to do? I'm actually > > a Qt programmer and there we have just .ts files for each language > > containing the translated texts (edit with Qt Linguist app by the > > translators), they are converted to a binary .qm file, and those .qm > > files are loaded by class QTranslator at runtime. What is the mechanism > > of Trac that got out of control? > > > > What's got out of control is that the current workflow as described in > [1] is way too complicated. I could barely keep up when I was more > involved in Trac, now with some distance I see that it's flawed, we need > to simplify and automate more. The main flaw was that I assumed that > after some time, we'll have an active committer and a team coordinator > for each language (the group 1) and that hasn't happened and won't. > > At this point, I think it's safer to assume that the translators will > prefer to work on Transifex, so that this should become our primary > source. We should have a mostly automated way to download everything > from there (synchronisation point), and commit the result, possibly > after the fixes done after checking the translations for > well-formedness. If such fixes are needed, we should then push them back > to Transifex (possibly overwriting edits done there since the > synchronisation point). > > That's the rough picture. The other idea was to merge all the catalogs > for a language in a single one so that we avoid the problems related to > repeated work and with the merges [2]. > > I'll resume work on that soon, but that shouldn't hold on the imminent > release... > > Speaking about that (0.12.6 / 1.0.2 / 1.1.2), I'm ready to give any > advice or even build the Windows parts, if needed. So Ryan, Jun and > Peter, don't hesitate to ask me if you need anything.
Thanks! It would be great to get a release out. I currently have about a half dozen tickets in progress. What I'm thinking is: - Close out those tickets by Friday 07/25 - Spend the next few days reviewing the tickets that were closed in the release, testing, trying to catch anything that may have been overlooked initially. String freeze on Monday 07/28. - Allow the two weeks for translators to update the catalogs. - Prepare the release on 08/08 or later. How does that sound to the other devs? -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/d/optout.
