Your comments about trusting the updater module are right on the money, and will be addressed in the next major update, v2.4. The ability to inform the user about the motivation and extent of the changes is currently stubbed in within the Updater module - as a result of you taking the time to speak your mind, it's now at the top of the list of v2.4's new features. Personally, I'm fond of Firefox's update process, which links to a web page that allows you to drill down to see what is the motivation for the update before proceeding. I envision doing something similar to this. For the record, most incremental updates only touch two jar files in the installation directory: the main VaultletSuite jar, and the translation jar. The two of these files amount to about 300K, and are simply swapped with the outdated jars as the Updater finishes up. Of course, without being notified, you wouldn't know that, so I can definitely empathize with your position. Concerning "medium sized" updates (as the Updater module describes 3-4 MB downloads to users), the changes slated to be made to the Updater module for v2.4 will require that the outdated Updater download a partial installation utility similar to (but significantly smaller than) the original installer which will then autorun, but still allow you to exit from the process if you wish. After that, future "medium sized" updates will contain an option to manually download and install them yourself too. I'll make sure that everybody's advised of the 2.4 release before it takes place, so that it's not a surprise. Between now and then, there may be a couple of patches released that deal with improvements to the new account wizard and bug patches, but I don't envision them being obligatory (since the bugs fixed don't jeopardize security or have destructive effects), so you can skip them until v2.4 is released. Thanks again for your feedback. As a result, everybody benefits |