1) Since 4.x, I have never lost configuration, even through major version upgrades.
2) Last I heard, exporting configuration with Dude 4.0b3 could crash the system and wipe out the map.
Now that I'm searching for answers, I'm finding this is happening to many people. The only mention of Dude in the 6.20 release notes was the ability to see & remove the Dude package. I realize this was probably an unknown effect at the time of release, but when a new release is causing widespread destruction, shouldn't MT either a) pull the software; b) release a new version without the problem; or c) contact users to warn them?
As far as I could tell, this was an ordinary release like any other--certainly no risk to a machine running nothing but Dude! Right?
So I upgrade, and now no clients can log in. Then I downgrade, and I'm greeted with a blank map. Just like dozens of others, evidently. There has to be a better policy than caveat emptor
when upgrading ROS.