Over at http://drupal.org/node/153968#comment-264685, catch asked a good question:

It's possible to disable notifications for individual modules. Does this mean it doesn't check for them at all? In which case you could untick them all one by one and switch off the calling home altogether?

Currently, the answer is 'no'. We fetch the data for every project, and only use the fact we're ignoring a project when figuring out if we're out of date. We should probably change this, so that in update_status_refresh() we also load in the settings and for projects marked as "never warn", we don't bother fetching. Should be about a 5 line diff. ;)

Comments

merlinofchaos’s picture

merlinofchaos commented

I disagree.

Never warn will keep it from turning red when you're out of date; it will not keep it from displaying correct information about Recommended Version, Latest Version and Security Updates.

IMO we must check if there is anything to check.

dww’s picture

dww
we/he/they
commented

Is it desirable to turn of fetching at all? E.g. I know devel never has releases at all, I deploy straight from CVS, and never want to bother fetching the history. Another possible choice in the drop-down, even lower than "Never", called something like "Don't fetch"? Probably too complicated and not worth it. I'm guessing this issue should just go to "won't fix"...

merlinofchaos’s picture

merlinofchaos commented

Devel may never have releases, but the filedate on the -dev tarball will update, and it might be valuable to at least see that information.

And then again, Moshe may surprise you and create a release one day. It'd be nice to have that information available when he does.

dww’s picture

dww
we/he/they
commented
Status: Active » Closed (won't fix)

I'm just thinking about ways to reduce the phone-home expense and give site maintainers some choices (based on feedback in other threads, etc). Devel was only an example. That said, it's probably not worth complicating the UI over this. And we should really come up with better ways to deal with the expense over at http://drupal.org/node/146564, etc. I have some ideas, so I'll drop into IRC and see if we can chat about it briefly.