@all AOO developers
In order to prevent problems like this ...
"I need to find a specific code change in a commit big like the Mount
Everest"
https://bz.apache.org/ooo/show_bug.cgi?id=124285
... we should agree that commits should not be too large. Then a
regression, missing code part or else is much easier - and faster - to find.
E.g., doing the code changes of this wiki page is one commit should be
prevented but split in reasonable commits:
https://cwiki.apache.org/confluence/display/OOOUSERS/ODF+1.3+Changes
What do you think?
Thanks
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
