[dev] code upgrade checking

[Eric Rostetter]

Quoting Marko <marko@oblo.com>:

> this idea just came to mind with the recent shares changes... what happenes
> when
> someone is going from current stable to this next stable release which has
> this different share handling?

AFAIK, there was never any share handling in any release version, so the
next release would be the first one, and no "upgrade" would be needed, only
an "addition".

Upgrades are pretty tough, per-user data kind of things.  Additions are
easy, one-time admin kinds of things.  So as long as well tell the admin
to create/modify/whatever the backend data store, it should be painless,
without any real automation needed.

-- 
Eric Rostetter
The Department of Physics
The University of Texas at Austin

Why get even? Get odd!