Cor Nouws píše v Pá 01. 07. 2011 v 11:16 +0200:
Hi John, Petr,
John LeMoyne Castle wrote (24-06-11 11:38)
The intention is to make as few changes as possible in lo-commit-stat while
getting to where a Weekly Development Summary wiki page is generated easily.
For 'external use' it would be most helpful if there is a output
comparing subsequent releases.
But if In understood the information correctly, that can be easily
accomplished with giving the right parameters?
Yes, the list of changes between releases is easy. You just need to get
the summary between the tags:
bin/lo-commit-stat --log-suffix=release-x.y.z . tag1..tag2
I suggest the following steps:
# make sure that you have all tags
./g fetch --tags
# find the last tags for the release, e.g. 3.4.0 and 3.4.1
git tag | grep libreoffice-3.4.0
git tag | grep libreoffice-3.4.1
# produce the summary
bin/lo-commit-stat --log-suffix=release-3.4.1 .
libreoffice-3.4.0.2..libreoffice-3.4.1.3
It produces log file with plain text. John is working on the wiki
output.
See also bin/lo-commit-stat --help for more details.
Hmm, we might want to create the tag libreoffice-3.4.0-final that will
be identical to the last used rc tag. It would make these queries
easier.
Best Regards,
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.