Clarify the order of non-PR Changelog entries
The previous wording would only consider Mantis vs Github. No change entry neededmaster
parent
545aaef50b
commit
a4806d7817
|
@ -169,7 +169,8 @@ Any user-visible change should have a `Changes` entry:
|
||||||
(several numbers separated by commas can be used)
|
(several numbers separated by commas can be used)
|
||||||
|
|
||||||
- maintaining the order: each section lists Mantis PRs first in ascending
|
- maintaining the order: each section lists Mantis PRs first in ascending
|
||||||
numerical order, followed by Github PRs
|
numerical order, followed by Github PRs in ascending numerical order,
|
||||||
|
followed by changes that are not related to a PR.
|
||||||
|
|
||||||
- with a concise readable description of the change (possibly taken
|
- with a concise readable description of the change (possibly taken
|
||||||
from a commit message, but it should make sense to end-users
|
from a commit message, but it should make sense to end-users
|
||||||
|
|
Loading…
Reference in New Issue