May be beyond the scope of Extended JQuery book but...
I was curious about was revision control of jquery, plugins, extensions, etc of files during deployment (i.e. not how things are saved via version control system like git, svn, etc). How do you deploy the items and make code maintainability for future upgrades easy?
Is it best to keep jquery / jquery ui version file names (jquery-1.8.0.js) to insure the version compatibiltiy is know, which means when you change versions, you have to change ever file with the specific previous version filename?
Do you rename to a non-version specific version filename (jquery-1.8.0.js to jquery.js)? This seems like it could potentially lead to issues later down the line if api or behavior changes.
If an api/plugin change how way to handle this (keep a copy of the old plugin and its required jquery/jquery ui or refactor all the code)? Then you risk having many versions of the same product causing confusion.
I assume good way is to have a "wrapper"/ "adapter" layer to help reduce version dependencies, but that seems like it could also add extra code..
At least jQuery and jQuery UI include version numbers that you can check if necessary - $.fn.jquery and $.ui.version respectively - although testing for the actual function/attribute may be a safer option. Maybe there should be a common mechanism to enquire about the version of a particular plugin. A compatibility wrapper can be useful to help users upgrade to a newer version, and is only required when older (deprecated) functionality is still required. Those users that follow the upgrade path can ignore it.