Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


Hi there,

On Thu, 2011-05-05 at 01:13 -0700, plino wrote:
When you do a code freeze for a Beta (or any) release it means that a branch
is created and to that branch only fixes are added but not new features,
correct?

        Good question - that branch is libreoffice-3-4 and you have it about
right; yes. For new features we need some double (or more) code review
and we use that very sparingly; so far I've only seen one go in (fixing
the document shadows).

Are the fixes to the Beta branch incorporated to the main code (trunk?)?
I.e. the "trunk" contains all the fixes from the Beta branch plus new
features (which probably have other bugs), right?

        That process is a bit slower; some fixes are committed to master, and
then cherry-picked back; but in general fixes go to libreoffice-3-4 and
then are merged back to master (somewhat intermittently). So it is best
to test a libreoffice-3-4 build if possible.

        HTH,

                Michael.

-- 
 michael.meeks@novell.com  <><, Pseudo Engineer, itinerant idiot



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.