Updated: Comment #N
The issue queue used to use the two different tags for classifying issues "Needs change notice" and "Needs change notification" until it was cleaned up (issue). "Needs change notification" was chosen because it was used in the majority of cases. Yet, issues that need a record change start with "Change notice: ..."
The documentation Contributor task: Write up a change record for a Drupal core issue uses both "change record" and "change notification" terms in its alias, title and content.
The list of 'change records' for Drupal core is at https://drupal.org/list-changes (note the alias) and the content type is 'changenotice'.
I find notification a bit odd: we're not sending notifications in this context, we not notifying in the sense "inform (someone) of something, typically in a formal or official manner.". Notice or record sounds more appropriate. I could go with notice since it's used so much in the issue titles.
Standardize on "Change record":
execute changes above
Fixed
3.0
User interface
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
I went through the remaining tasks and all but last issue was not done. I created a MR for remaining task.
Automatically closed - issue fixed for 2 weeks with no activity.