Translations for trunk and 1.0.X branch
Malcolm Tredinnick
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
Nicola Larosa
> 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.
What about commit privileges on that branch? Are they the same as the
trunk ones, so that we maintainers may avoid going back to submitting
patches?
--
Nicola Larosa - http://www.tekNico.net/
Rails, Django, Symfony, Pylons, TurboGears, Seaside... any of these
tools represent a major improvement over the CGI/PHP model of web
development. If you're still writing web sites the way you did five
years ago, you're missing out. - Jacob Kaplan-Moss, May 2008
Malcolm Tredinnick
On Sun, 2008-10-05 at 06:39 +0200, Nicola Larosa wrote:
> Malcolm Tredinnick wrote:
> > 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.
>
> What about commit privileges on that branch? Are they the same as the
> trunk ones, so that we maintainers may avoid going back to submitting
> patches?
They might not be at the moment, but I'll make sure they are set so that
you can commit directly.
Remember that when committing to a branch, you must prefix the commit
message with the branch name ([1.0.X] in this case) so that we can tell
easily in the timeline which commits are going to a branch.
Regards,
Malcolm
Malcolm Tredinnick
On Sun, 2008-10-05 at 16:01 +1100, Malcolm Tredinnick wrote:
>
> On Sun, 2008-10-05 at 06:39 +0200, Nicola Larosa wrote:
> > What about commit privileges on that branch? Are they the same as the
> > trunk ones, so that we maintainers may avoid going back to submitting
> > patches?
>
> They might not be at the moment, but I'll make sure they are set so that
> you can commit directly.
Jacob has now set this up. All translators who have direct commit
privileges to django/conf/locale/* can now commit to the same
directories on the 1.0.X branch.