Hi
I think it kind of misses the point. It should start with:
Changes that make backporting of other fixes to release branch harder
might be only be merged *after creation of the x.y.2 release* and
*before branchoff for the next x.y+1 release*.
I agree with your statement, but new contributors might need a bit more handholding to understand
when/why a patch makes backporting more difficult.
The page groups 3 kind of changes, and only the last kind is real critical timing wise.
I have changed the text a bit based on your suggestion.
thanks
rgds
jan I.
Context
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.