Commit policies and autogenerated changes

[Tommi Vainikainen <tvainika niksula cs hut fi>]

Hi,

It is currently bit unclear to me what kind of policies are for
translation maintenance and file touching (soft) permissions.

It seems that in some modules maintainers, when making release, run
"make update-po" and commit after that. However such changes are
autogenerated (anyone can run that "make update-po"), and thus add no
value to cvs history. If translators want to look at history of
translation, there is rather much "released x.y.z" in cvs history
which hides useful content...

Some other module maintainers instead don't commit those changes, and
thus translators can really "own" the translations. This is the way I
think it should be in every module.

Is there any general commit policy regarding this? Is it up to
maintainers of the module or can team leader tell to not to touch
translations under their supervision?

-- 
Tommi Vainikainen