What we usually do is add a compatibility name to older release branches
so the next release there can read both, the new name and the old name,
but continues to write the old name so earlier releases of the same
(usually two) branches are not affected.
Then for the next release branch (now master) switch from writing the old
name to writing the new name, but still accept the old name "forever".
You can find examples of that in sc/source/core/tool/compiler.cxx
ScCompiler::IsOpCode() in aOdffAliases.
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.