-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear Translators et al,
before the 2.0.0 release we had a particular "String Freeze" period. This was a time when all strings were fixed. It was guaranteed that no string changes occur. This should help to offer complete translations at the 2.0.0 release, and several languages reached this challenging mark! Congrats. Now 2.0.0 is out. We *could* have a string freeze for even some more releases, but actually I think this isn't really necessary. Instead, I propose the developers should now be allowed to make all queued string changes (e.g. http://svn.gnucash.org/trac/changeset/14493 and http://svn.gnucash.org/trac/changeset/14546 ) iff these changes went through the normal backporting audit. http://wiki.gnucash.org/wiki/Development_Process We *could* have some particular 2.0.x releases which have a string freeze beforehand, and others without it, but I think the minimal amount of string changes don't justify this additional bookkeeping overhead. So I simply propose an end to the string freeze. Other ideas? Proposals? I've updated http://wiki.gnucash.org/wiki/Translation_Status accordingly. Christian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBRL+aKGXAi+BfhivFAQJ4mgP9GOTxQmpPsok2lq1KuNYlO/udEcQMaonr rt3z/Bl4xD1YyU8Z5xNnQNCxZpJZn4hvYcWR1lYE5fc7BDsd8EpltZAcik1VI57b LkByDC/Kh1TknpctG4uvHVdSAbZUvpKrh4L01ZqAhtGvxRicEr8hS7e7D/Re63/6 stApgHX9PJ4= =iBCy -----END PGP SIGNATURE----- _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
