OOh very interesting use cases. I have had the same thoughts in regards to changing content (as far as actual content is concerned), though I do think changes in due dates are good to have communicated as it helps to manage expectations.
The one I hadn't heard of before is creating easter eggs. That is rather interesting, and I could see as very valid for wanting to have a 'publish without notify' flag.
The only other thing I could suggest while revising content is to unpublish, make all your revisions and republish the item. That would allow you to make numerous revisions and only have the one republish notification go out for the item.
[Edit: *** As @James pointed out, I stand corrected, this out of the box suggestion only works if you haven't graded something yet***] Having said that, thinking outside the box, I can make one other suggestion. Disclaimer: 'Here be dragons'. There are most certainly pros and cons with this one, and I think in many circumstances it would not suit, but, it came to my mind so will throw it out there. You could tell your students your course has a 'maintenance window' for a short period each week. You could unpublish the course, make all your changes, and republish the course. That would stop any notifications going out for the content changes, however would mean the student's wouldn't see the course on their dashboard for the period you are maintaining it. As I said, a plethora of issues doing this, but if you have very specific circumstances and your institution supports this, then it is another available option. I would ensure you communicate this extremely well and make sure institution support is there, because it will be confusing for student's if they log in at a time you are doing maintenance on it, and their subject simply isn't there (like they have been unenrolled).
This discussion post is outdated and has been archived. Please use the Community question forums and official documentation for the most current and accurate information.