Bug 32684 – Multiple changelog entries per bug for UCS-3.2-0

Bug 32684 - Multiple changelog entries per bug for UCS-3.2-0


Summary:	Multiple changelog entries per bug for UCS-3.2-0

Status:	CLOSED FIXED

Product:	UCS manual
Classification:	Unclassified
Component:	Release Notes
Version:	unspecified
Hardware:	All Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS 3.2
Assigned To:	Moritz Muehlenhoff
QA Contact:	Philipp Hahn

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-09-24 17:53 CEST by Philipp Hahn
Modified:	2015-04-01 13:50 CEST (History)
CC List:	2 users (show)

See Also:
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
proposed diff (5.33 KB, patch) 2013-09-25 11:24 CEST, Philipp Hahn	Details \| Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Philipp Hahn

2013-09-24 17:53:53 CEST

There are several cases, where one bug has multiple changelog entries.
# grep -P --only '(?<=&ucsbug;)[0-9]+' changelog-3.2.xml | sort -n | uniq -d
1156
10962 duplicate?
19441
19753 merge candidates
24442
27786
29399 duplicate?
30779
30943
30944
30946
30948
30949
31094 two bugs?
31256
31281
31437
31658
31698
32011
32389
32394
32412
32455

Comment 1 Moritz Muehlenhoff

2013-09-25 07:30:38 CEST

That is by design. It helps people to only review the changes for a certain functionality.

Comment 2 Philipp Hahn

2013-09-25 11:24:50 CEST

Created attachment 5469 [details]
proposed diff

(In reply to Moritz Muehlenhoff from comment #1)
> That is by design. It helps people to only review the changes for a certain
> functionality.

Mostly I with you and support the idea, on the other hand I find the ChnageLog already huge enough and reading the same bug/change again and again distracts from the real important changes.

19753 describes two very similar functions in the same library.
The two entries for 29399 are very similar and overlap in their description.
31094 seems to be used twice for completely unrelated bugs; one is probably wrong.
31658 is used twice in the same description.

Write "Python" with an upper-case 'P'.

Comment 3 Moritz Muehlenhoff

2013-10-11 14:54:35 CEST

(In reply to Philipp Hahn from comment #2)
> Created attachment 5469 [details]
> proposed diff

Thanks, merged in revision 44998

> (In reply to Moritz Muehlenhoff from comment #1)
> > That is by design. It helps people to only review the changes for a certain
> > functionality.
> 
> Mostly I with you and support the idea, on the other hand I find the
> ChnageLog already huge enough and reading the same bug/change again and
> again distracts from the real important changes.

For the big picture we have the release highlights releases (of which the changelog is a part).

I don't think anyone reads the full changelog. While in that case there's some repitition the splitting helps people who're only interested in some components. Hardly any customer has everything installed.

Comment 4 Stefan Gohmann

2013-10-11 15:46:55 CEST

(In reply to Moritz Muehlenhoff from comment #3)
> I don't think anyone reads the full changelog.

No, I know customers reading the full changelog.

Comment 5 Philipp Hahn

2013-10-11 17:03:23 CEST

OK: r44998