Ying Chun Guo wrote: > StringFreeze -> Start translation & test -> Report bugs which may cause > string changes -> Cannot fix these bugs because of StringFreeze. > So I'd like to bring this question to dev: when shall we fix these > errors then? > > From my point of view, FeatureFreeze means "not accept new features", > and doesn't mean "cannot fix bugs in features". > StringFreeze should mean "not to add new strings". But we could be able > to improve strings and fix bugs. > I think shipping with incorrect messages is worse than strict string freeze.
First of all, StringFreeze is there to help translators, so we should definitely evolve it if it misses the target :) It was never meant to be strict. My idea was that *if* a string gets changed, we (1) need a good reason for doing so (no cosmetic or gratuitous change) and (2) need a mechanism in place to warn translators about that late change (that could just be a ML post). That way we make sure that if a string gets changed, it's worth the hassle it creates and the relevant people know about it. -- Thierry Carrez (ttx) _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
