It would be great is there was a way that module releases would have a method where developers could send a message to the update status system. This message would alert anyone with a Drupal installation who is actively using the update status system if there are any critical changes that may cause an issue with how the module functions. I suspect this information may be drawn directly from the CVS/SVN system but, again, there may be a better way to send such messages.

NOTE: This feature request was spawned from a short discussion on http://drupal.org/node/221927 and, I think, situations like this are going to be more common place in the future as Drupal managers will become more dependent on the update status system rather than checking for updates on each project page. The situation was a message telling people the changes to the module was posted on the project's main page letting all users know there had been a logic change in the module's main function. BUT, a bug report was filed that users reported data was not being collected into the analytics system. It turned out this was not true because the logic change and the module were functioning properly - it was the fact a lot of people didn't see the message on the project page.

Comments

webernet’s picture

I'm tempted to "won't fix" this. Projects should not be making major changes that will potentially break sites on a stable branch. Maintainers should instead be creating a new branch for any major new features or major changes such as those you describe.

dww’s picture

Status: Active » Closed (won't fix)

Update status isn't meant to be a general purpose messaging system, and everything webernet said is true.