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


Hi all,

as promised, we have created a branch for the stabilization of the
3.4.x releases, called 'libreoffice-3-4'. It is based on master, last
pull on April 1, 2011 at about 12am UTC.

The following rules apply:

        + only bugfixes allowed
        + no approval needed during beta phase (two weeks after branch)
        + 1 approval needed during rc phase
        + 2 approvals with different/no affiliation needed for late
          features

Please commit fixes into the branch to make sure that we have them in
the release. All changes will be regularly merged into master, so you
need NOT commit them twice.


The 'master' branch is used for 3.5 development and has the rules:

        + free commit; do your best to do not break build and
          functionality
        + any development allowed


For further information about the roadmap, please check

        http://wiki.documentfoundation.org/ReleasePlan


Now, if you want to switch your clone to the libreoffice-3-4 branch,
do:

./g pull -r
./g checkout -b libreoffice-3-4 origin/libreoffice-3-4

Hopefully it will work for you :-)  Most probably, you will also want to
do (if you haven't done it yet):

git config --global push.default tracking

When you do git push with this, git will push only the branch you are
on; ie. libreoffice-3-4 when you have switched to it.  This will
save you some git shouting at you.

Happy hacking,
Petr


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.