changelog generation sorting changes by tag incorrectly
Bug #1308774 reported by
Doug Hellmann
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
PBR |
Confirmed
|
Medium
|
Unassigned |
Bug Description
The generated ChangeLog for the master HEAD of oslosphinx lists 2 changes under release 2.1.0 that were not in that package. They were committed before the tag, but they were *merged after* the tag.
http://
shows "Add Python 3 trove classifiers" and "Prevent left sidebar text overflow" merging after 2.1.0 was tagged.
Changed in pbr: | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in pbr: | |
importance: | Medium → Low |
status: | Triaged → Confirmed |
To post a comment you must log in.
We had a similar issue in reno that we were able to fix using git's topological sorting, which ensures that a patch does not appear in the log output until the point where it is actually merged.