Hi, First of all, thanks. And second, to leave a clear statement about the main point: I agree with your proposed time frame for the string freeze, October 26th (freeze) to 29th (release).
zimoun <zimon.touto...@gmail.com> writes: > Maybe I am missing something. Probably this context helps: I've already uploaded to TP the translation for the manual, so I can compare the "old" pot (the one uploaded to TP) with the "new" one (the one I generated today on my machine). > Now the translation 1.2.0-pre1 is open, so it is almost 3 weeks (even > if I know it is maybe not enough, well we have to fix some deadlines > somehow :-)). Nobody likes deadlines---at least not me, hehe---but I believe they can be really useful sometimes. :-) > The last week, we could string freeze for polishing and not run after > an always moving target. Yup, that's the main advantage of freezing: you can focus as much as possible on the little and not so little details, like bug hunting. > From my point view, a longer freeze would not help to have the work > done. I do not know. What do you think it could be better? I agree that a longer string freeze wouldn't a big difference, and even may hurt. At least the manual is a huge work that probably cannot be done in weeks from scratch, so I'm not thinking about the string freeze as "the time frame to perform the translation" but "a time frame to check the translation already done and fix last minute issues/features". Besides, sorry if the word 'tight' sounded as a complaint meaning protest, if so it'd really be a complaint meaning grief for my schedule, as I'm unable to dedicate much time on working days. Happy hacking and translation too! Miguel