Sometimes, developers mention other bugs in the body as
related issues.
This might create mislead information in the release notes
E.g: https://wiki.documentfoundation.org/Releases/6.1.1/RC1
* Caolán is mentioned as fixer of i#66963 because the id is in
the body of 9c3d8b1c64
which fixes tdf#98558
* M. Stahl is mentioned as fixer of tdf#112447 because the id is
in the body of 31e66bd07c
This bug was fixed by Bjoern Michaelsen in
ce2fce9a41
Change-Id: I8d0ee038741dbb27364a56a7fa9285f32839c37b
Reviewed-on: https://gerrit.libreoffice.org/69750
Tested-by: Jenkins
Reviewed-by: Andras Timar <andras.timar@collabora.com>
it also doesn't make sense to numerically compare a %hash
enable warnings in the script and remove a duplicated variable (and
some unnecessary hash-declarations)
Change-Id: I0a84dc28f369931ee31a1cf12849fde2b63f1ca2
besides using deprecated syntax – "if (defined %hash)" (or "if (defined
@array)" for that matter) – just using "if (%hash)" (or "if (@array)")
would do, it is also unnecessary to create the hash if it doesn't exist
(autovivification will take care of that)
Change-Id: Ib5704b2d609ae3658f3c166f9e26a051957149f8
Add --bugs-changelog option to print the list of bugs in the style
of SUSE changelog
Optimized the code to check bugzilla only once when you generate
more logs.
Change-Id: I56eeda92628422f1b649c0fd71ae9146aeaa85c9
Add --cherry option that filters commits using the "git cherry" command.
Note that you need to pass git arguments for "git cherry". It means
"old-branch-or-tag" "new-branch-or-tag".
Change-Id: Iea67d0ead205c66112791cb0444fa183c7fa6e9b
It takes ages to get bug summary from bugzilla => it is worh to
generate normal and wiki logs at the same time. Why not produce
all logs with one call
Add --commits option. Also rename --wikibugs to --bugs-wiki.
Use .wiki suffix for wiki logs. Also rename "commit-log" to "commits".
It is enough to use ".log" as the suffix.
Change-Id: I92bbc4d56a0ae9e23401be0677256059c777d712
* some used "resolved" instead of "resolves"
* some didn't have a colon after that
* some inserted a space after bug ID and a separator
* some used a "-" as a separator
Change-Id: Iee6a0f0346a257124e9488fc8f3bbdc59b32cbac
For Example:
* ScConditionalFormat -> no change
* SVG -> no change
* WaE -> no change
* Some -> some
After this change, we now have to sort case-insensitively,
or the lines starting with uppercase will clog up together.
Change-Id: If08cbaa19e6f3496dd1f07920464d16140e2aa3a
+ do not check for "-" in the bug title; it might be also wide character
in some cases
+ show result when looking for bug titles
+ sort bugs when loolking for bug titles and printing bug numbers
Change-Id: I39496f7d0cf5f7a116e7d3c506b76b4a3de1dee1
use "git rev-list --pretty=medium" instead of "git log"
to be able to use origin/libreoffice-3-4 ^origin/libreoffice-3-3
to generate list of changes that are in 3.4 but not in 3.3
use "git rev-list --pretty=medium" instead of "git log"
to be able to use origin/libreoffice-3-4 ^origin/libreoffice-3-3
to generate list of changes that are in 3.4 but not in 3.3
the generated log file name is:
+ commit-log-<branch>-<log-suffix>.log by default
+ bugfixes-<branch>-<suffix>.log with the --bugs option
, where <branch is automatically detected; <suffix> is defined by the
--log-suffix=<suffix> option
Xisco Fauli