Hi,
When will we stop accepting translation updates for 12.3?
Marguerite
Marguerite Su i@marguerite.su writes:
When will we stop accepting translation updates for 12.3?
I think now with the beta1 release we are in the string freeze period. Developers are now only allowed to change strings if it is needed to fix a "serious" bug. This is somwhow in coolo's schedule (http://turing.suse.de/%7Ecoolo/opensuse_12.3/, linked from en.opensuse.org)--of course, I'm not sure whether all developers are properly aware of it.
I'll now stop overriding desktop files messages with upstream translations and request yast strings for the last time.
On Wed, Jan 30, 2013 at 5:50 PM, Karl Eichwalder ke@suse.de wrote:
Marguerite Su i@marguerite.su writes:
When will we stop accepting translation updates for 12.3?
I think now with the beta1 release we are in the string freeze period. Developers are now only allowed to change strings if it is needed to fix a "serious" bug. This is somwhow in coolo's schedule (http://turing.suse.de/%7Ecoolo/opensuse_12.3/, linked from en.opensuse.org)--of course, I'm not sure whether all developers are properly aware of it.
I'll now stop overriding desktop files messages with upstream translations and request yast strings for the last time.
Hi, Karl,
Sounds like we're in a hurry for this release...in 12.2's time, the translation deadline is Aug. 31th...and on Sep. 5 we're still doing the release notes and websites updates.
As a translator, I tend to start working on the last Milestone...because in the previous ones, hardcore features are not finalized yet, and few new string is filled in. but this time...we freeze at beta...so seems we have to use unreviewed translations this time...
PS:
I found a problem in M2 and Beta.
There's a qt-pkg.mo and a packager.mo in yast2-trans-zh_CN, but yast2-packager still displays English for software management module, all else are Chinese.
Can you please check if the same happens to DE or the language you speak besides English?
It seems to be triggered by potential code changes in yast (libyui didn't seems to exist in previous versions) or a version mismatch (like you pushed trunk but yast developer still use stable interface) to me.
If confirmed, I'll open a bug report.
Thanks
Marguerite
Marguerite
Marguerite Su i@marguerite.su writes:
Sounds like we're in a hurry for this release...in 12.2's time, the translation deadline is Aug. 31th...and on Sep. 5 we're still doing the release notes and websites updates.
I do not understand this completely. But yes, release notes are always late, and we often must update them after the actual release od the distribution because we detect more "issues" as time goes by.
As a translator, I tend to start working on the last Milestone...because in the previous ones, hardcore features are not finalized yet, and few new string is filled in. but this time...we freeze at beta...so seems we have to use unreviewed translations this time...
Hhmm, if needed we can and will still update translations for the next RCs.
There's a qt-pkg.mo and a packager.mo in yast2-trans-zh_CN, but yast2-packager still displays English for software management module, all else are Chinese.
Can you please check if the same happens to DE or the language you speak besides English?
Unfortunately, my test installations (in virtualbox) currently fail completely. I probably must try a physical installation...
It seems to be triggered by potential code changes in yast (libyui didn't seems to exist in previous versions) or a version mismatch (like you pushed trunk but yast developer still use stable interface) to me.
If confirmed, I'll open a bug report.
I'd say, even if unconfirmed for the moment, you'd better open a bug report now.
On Wed, Jan 30, 2013 at 10:18 PM, Karl Eichwalder ke@suse.de wrote:
Marguerite Su i@marguerite.su writes:
Sounds like we're in a hurry for this release...in 12.2's time, the translation deadline is Aug. 31th...and on Sep. 5 we're still doing the release notes and websites updates.
I do not understand this completely. But yes, release notes are always late, and we often must update them after the actual release od the distribution because we detect more "issues" as time goes by.
Sorry I misunderstood.
I meant this:
http://lists.opensuse.org/opensuse-translation/2012-07/msg00000.html
and this:
http://lists.opensuse.org/opensuse-translation/2012-08/msg00048.html
I was about to say, judging by the date, you had at least a month and more to do 12.2 translation. this time we only have a time window between M2 and B1.
Then I find the release date of M2...there's still a month between them too, but because there're Christmas and new year holidays, and office work got full on ordinary days because of the two holidays...so time flew and I missed the time window.
As a translator, I tend to start working on the last Milestone...because in the previous ones, hardcore features are not finalized yet, and few new string is filled in. but this time...we freeze at beta...so seems we have to use unreviewed translations this time...
Hhmm, if needed we can and will still update translations for the next RCs.
Hhmmm, still good news ha...
I'd say, even if unconfirmed for the moment, you'd better open a bug report now.
bnc#801311
Greetings,
Marguerite
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wednesday, 2013-01-30 at 10:50 +0100, Karl Eichwalder wrote:
Marguerite Su <> writes:
When will we stop accepting translation updates for 12.3?
I think now with the beta1 release we are in the string freeze period. Developers are now only allowed to change strings if it is needed to fix a "serious" bug. This is somwhow in coolo's schedule (http://turing.suse.de/%7Ecoolo/opensuse_12.3/, linked from en.opensuse.org)--of course, I'm not sure whether all developers are properly aware of it.
At http://turing.suse.de/~coolo/opensuse_12.3/ there is no mention of the word "translation". Thus it is not clear what window we have for translation.
- -- Cheers, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am 12.02.2013 14:29, schrieb Carlos E. R.:
On Wednesday, 2013-01-30 at 10:50 +0100, Karl Eichwalder wrote:
Marguerite Su <> writes:
When will we stop accepting translation updates for 12.3?
I think now with the beta1 release we are in the string freeze period. Developers are now only allowed to change strings if it is needed to fix a "serious" bug. This is somwhow in coolo's schedule (http://turing.suse.de/%7Ecoolo/opensuse_12.3/, linked from en.opensuse.org)--of course, I'm not sure whether all developers are properly aware of it.
At http://turing.suse.de/~coolo/opensuse_12.3/ there is no mention of the word "translation". Thus it is not clear what window we have for translation.
There is no deadline. You can translate as late as you like and it depends on the PO file and its developerhow late it goes in.
Greetings, Stephan
translation@lists.opensuse.org