On the Available Updates (admin/reports/updates) page there are links beside each update to download the update and to view its release notes. The release notes link is helpful to see if there are any major changes to note before updating, or any additional steps that need to be performed (e.g. run update.php).
However, consider the following example: You have version 1.x-1.0.0 of a module installed. Version 1.x-1.0.2 is available. You want to update, so you click the link to view the release notes. There's nothing important to note, so you go ahead with the update. But version 1.x-1.0.1 of the module requires additional work in order to update properly. You don't see that however, as you only see the release notes for 1.x-1.0.2...
I propose linking to a page* that shows all of the release notes between the installed version of a project and the version you're updating to. That way you can see all necessary steps/information/notes related to the update you're about to perform.
* I'm not sure if such a page exists in GitHub (at least a quick search didn't show a way to do this automatically)...
Recent comments
We can no longer add contrib projects in the Tugboat sandboxes that we use for core PR's? Can this be fixed or is there a reason for this? We can add contrib projects to demo...
Apr 25th Weekly Meetings
The Mail System and MimeMail modules are now installed. I'll let you know if they solve the problem. Edit: Using Mail System with MimeMail I was able to send plain text emails. There is...
HTML Email treated as plain text
If you haven't already I recommend installing Mail System and MimeMail. The latter will help format emails as HTML and first helps with configuring which module will handle the formatting...
HTML Email treated as plain text