Comment 1 for bug 1875522

The way the upgrade process currently works is to examine the meta-release file for the 'Supported' field. In the event that the Supported is set to 0 then everyone is prompted to upgrade. We don't set it to Supported yet deliberately so that we can get these enthusiasts to test the upgrade process for us. Subsequently, while the definition of the '-d' switch is incorrect for a short period of time I think its best that the '-d' switch is scary as setting the meta-release file's 'Supported' filed is an indication that we think it is safe to upgrade for everyone.

I do think the release notes could be better about explaining why the '-d' switch needs to be used for a short period of time after release though.