A user recently commented to me that immediately after updating today they received a page telling them at they are now out of date. It would appear they went from 3.16.13 to 3.16.14, and then needed to update to 3.16.15. A screen shot of what they saw was attached. So the bug (or perhaps question), is how can we get them them from 3.16.13 to 3.16.15 without them having to do two manual updates. Having the user opt in to a lengthy process and then telling them that they failed is of course going to be frustrating for them, in addition to the fact that we aren't always getting users on the most secure version.

Here's what the user sees after updating. Double update... what does it mean? so intense. If we ship 3.16.16 it could almost be a triple update.

Shouldn't the 3.16.13 User be offered a Full MAR Update to .15 instead of the partial one to .14?

If they have already started the download from 3.6.13 to 3.6.14 then we don't try to stop the current download of 3.6.14 which is bug 353804 and with releases this is an extremely rare occurrence (in this case due to a firedrill release). If they updated from 3.6.13 to 3.6.14 and then we released 3.6.15 this would be expected behavior even though annoying (caused by the fact that we had to do a firedrill). If they haven't already started the download from 3.6.13 to 3.6.14 then they should be offered 3.6.15... if they are not (I highly suspect they would be) then please file a releng bug since they generate the snippets. The only behavior above that is an app update bug is 353804 so duping.