Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.See original discussion in #2078085: Determine if change notices should block an 8.0 RC?.
This is a holding issue to track completion of all change notices prior to the release of the first beta. Basically the same as #1393358: [META-12] Review 'revisit before release candidate' tag.
The sole purpose of this issue is so we don't have to individually bump all change notices to critical as we do now.
Contributors can easily mark change notices fixed themselves by writing a change notice, that's not the same for any other critical task in the queue which has to go through full patch/RTBC/commit.
Please don't link to individual change notices here, the 'Missing change record' tag is enough.
When https://drupal.org/project/issues/search?issue_tags=Missing%20change%20r... is empty, we can close this issue.
Comments
Comment #1
YesCT CreditAttribution: YesCT commentedcatch updated https://drupal.org/core-gates#documentation
I updated https://drupal.org/change-records
Comment #2
klonoshttps://drupal.org/change-records
Blame d.o D7 upgrade?
Comment #3
geerlingguy CreditAttribution: geerlingguy commentedLooks like the URL's been changed to https://drupal.org/list-changes - a redirect should probably be added, since a lot of sites were linking to change-records.
Comment #4
catchI think we should probably make this issue a beta blocker for the outstanding change notices (i.e., we'd release a beta with zero outstanding change notices). We can then keep the issue open to do the same for release candidate.
If this ends up being the only issue blocking a beta release that seems fine. Beta's one point where I'd expect more contrib authors to port modules, so having docs at least nominally up to date for that is worth holding it up for.
Comment #5
webchickMakes sense to me.
Comment #6
herom CreditAttribution: herom commentedComment #7
YesCT CreditAttribution: YesCT commented@geerlingguy no, https://drupal.org/change-records went to https://drupal.org/node/1314040 which is not found anymore. It was a page explaining the procedures around change records.
https://drupal.org/list-changes is a listing of change records, not the policies.
and the link to more information from https://drupal.org/core-gates#documentation still point to.. that page, so we cant get more information.
I'd like to get that page back. how?
Comment #8
xjmNB: the "Needs change notification" tag has been renamed to "Needs change record" to be consistent with everything else. I updated the relevant contributor task docs and recent g.d.o core posts, but there might be other references about. Henceforth, that tag may appear on any issue with an API change, now that it is possible to create draft change records
There's a new tag specifically for issues already committed to core but missing their change record:
https://drupal.org/project/issues/search?issue_tags=Missing%20change%20r...
Comment #9
xjmComment #10
jessebeach CreditAttribution: jessebeach commentedNine more to go!
Comment #11
jessebeach CreditAttribution: jessebeach commentedComment #12
jessebeach CreditAttribution: jessebeach commentedComment #13
jessebeach CreditAttribution: jessebeach commentedComment #14
jessebeach CreditAttribution: jessebeach commentedAll outstanding change notices are written.
Comment #15
plachAwesome work!
Comment #16
MixologicIs the existence of change records documented somewhere? It's a wonderful canonical resource of everything that changed - *if you know about it*. It seems like it should be mentioned often and in a lot of places. For example, there's no mention of it here: https://drupal.org/update/modules/7/8.Nevermind. Its pretty clear on the "before you start link"