Create coder updates (when APIs change) as part of the development process [#827578]

Spinoff from #648218: Make API changes in Drupal core be nodes.

When APIs change, there should be a way either to provide the changes to Coder directly, or at least provide notification in the coder queue. Perhaps this means that an issue should be spun off to the Coder queue, or ... But we need to make sure that every API change causes the corresponding change in Coder.

Comments

Comment #1

David_Rothstein commented 15 June 2010 at 17:04

Yeah, probably a good idea to split this off from the other issue - even regardless of how that one winds up being addressed, the Coder module concerns are somewhat separate.

Is there a reason that simple issue tags couldn't be used to solve this problem? In other words, every time a patch that changes the API is committed, some conscientious person (e.g., the core committers) could add an "affects Coder module" tag to the core issue, which would then be removed by whoever creates a followup issue in the Coder module queue.

Or were you thinking of something more automated?

(Regarding providing the change to Coder directly, I mentioned in the other issue the possible long-term Drupal 8 idea of including Coder upgrade rules themselves as part of the core API change documentation, if we go that route, but I don't know if that would really be a good idea or not.)