Everybody, Last week we created a 1.0.X branch in Django's subversion repository. See here for the announcement and details:
http://groups.google.com/group/django-developers/msg/3e82561146aa7b54 Translations count as bug-fixes (untranslated strings are bugs), so from time to time you should check what the translation status is for your particular language on the 1.0.X branch and update that as well. You may choose to work on both branches at once (submit two patches -- one for the branch and one for trunk) or just update the branch just before a release. Somebody will make an announcement here a couple of weeks before we do a release from the branch (1.0.1, etc) so that people have a chance to update any new strings. Also, now that 1.0 is out the door I am going to much stricter about requiring people to submit patches for translations, not entire files. If you submit a translation and it is not a patch, it will not be committed and you will be asked to create a patch. Creating patches is not that hard ("svn diff" from the top of the source tree) and it helps a lot with the quality-assurance side of things. It doesn't matter how big the patch file is, the difference is only a few hundred bytes in any case and that is nothing. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django I18N" group. To post to this group, send email to Django-I18N@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Django-I18N?hl=en -~----------~----~----~----~------~----~------~--~---
