I believe the general solution to that is having more "robust" sites (as I mentioned before on the mailing list). Also staging and deploying require different mvn commands so we have to ask / document folks to be a little (more?) aware.
And I wasn't thinking about adding it to any profile. In fact, the more I look at the parent pom, I don't think the distributionManagement sections should be in profiles at all
Since I haven't followed m2 discussions lately, I followed the profiles through the archives. They came to life in r439540:
The release profile's original purpose was to deploy to the rsync repo. This is not of interest anymore. This point, as it happens, has been raised before
We should move the distributionManagement section out of profiles, see said section in this pom, for example:
Lets suspend this for a few, and I will post a process-level email to the dev list first.