Following from #1957148: Replace entity_query() with Drupal::entityQuery()

The 'entity_query()' function was replace and old change notices are updated but contributors that not involved in the issue have no way to be informed about the change.

Suppose we need to file change notices to make re-roll of current patches easily

Comments

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented
Category: bug » task
Priority: Major » Normal

I don't see why this is a major bug.

Generally, we don't do HEAD -> HEAD change notices. Change notices (like upgrade paths) are generally for 7 -> 8. Otherwise, there's an incredible amount of crap to sift through for the 100,000s of people reading these after Drupal 8 is shipped (as opposed to the 10s of people reading them right now).

There's a Twitter account somewhere that tweets things tagged "API change" (I think), so one thing we could do is try and be more consistent about tagging things that way, so at least there'd be a feed that people who are actively developing on D8 right now could follow. This would also help find issues that need to be bumped to D9 post-July 1.

andypost’s picture

andypost
he/him
Primary language Russian
commented

Tagged pointed issue.
Anyway, a handbook page needs to figure it out somehow.

jhodgdon’s picture

jhodgdon
she/her
Primary language English
commented
Status: Active » Postponed (maintainer needs more info)

We already have a list of issue tags (the link is below the Tags field on the issue). "API change" is listed in the "Special issue tags" section:
http://drupal.org/node/1207020

I'm not sure what more we need to document?

jhodgdon’s picture

jhodgdon
she/her
Primary language English
commented
Issue summary: View changes
Status: Postponed (maintainer needs more info) » Closed (works as designed)

These policies were long since decided on, closing this issue.