I'm wondering, what is the best practice for deploying the site for the next version of a plugin on mojo.
I know that is always annoys me when I see the next -SNAPSHOT build as the site with some cool new feature and I give it a whirl only to find that it does not work (because it's a -SNAPSHOT version and has not been pushed to central) So, while working on some cool new features for versions-maven-plugin, what _should_ I do with regard to pushing the site? This is also really a question when it comes to calling for a vote to release the next version as we don't really seem to stage plugin releases on mojo (or maybe we do and I just don't know about it)... since it would seem that we just blast the current site with the next version and if the vote fails we've not really got a good way to roll back. -Stephen
