Hi all,
there have been created the libreoffice-3-6-1 branch. It will be used
for fine tuning of the 3.6.1 release.
The following rules apply:
+ preferably just translation or blocker fixes
+ only cherry-picking from libreoffice-3-6 branch
+ 2 additional reviews needed; 2nd reviewer pushes
+ no regular merges back to anything
The 'libreoffice-3-6' branch is still active and will be used for the
3.6.2 bugfix release. Please read more at
http://wiki.documentfoundation.org/ReleasePlan
http://wiki.documentfoundation.org/Development/Branches
Now, if you want to switch your clone to the branch, please do:
./g pull -r
./g checkout -b libreoffice-3-6-1 origin/libreoffice-3-6-1
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; e.g. libreoffice-3-6-1 when you have switched to it. This will
save you some git shouting at you.
Happy hacking,
Petr
--
Unsubscribe instructions: E-mail to l10n+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted
Context
- [libreoffice-l10n] [ANNOUNCE] Branch libreoffice-3-6-1 created · Petr Mladek
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.