|Opened on:||Wednesday, December 17, 2008 - 15:54|
|Last modified:||Monday, March 23, 2009 - 00:02|
I am hoping that you'll consider making a few changes to the update process that may help to minimize problems occurring after a recompile.
1. Make the update process a choice, rather than a mandatory process upon loading foldit. While the user *can press "Skip update check", not selecting it causes an autoupdate. Perhaps using a method of saying "there is an update available (list basic changes)...update?" might be a more efficacious method for ensuring that a user chooses to update... Doing so _after_ the user logs in and has the current build opened might also minimize updating when problems are already discovered within the user community (via chat)
2. Allow the user to archive the old build and provide an automatic archival process, as well as a rollback method locally to that build.
3. Provide change-file.txt to state changes in current build. This does not have to be a book, just a basic listing of the changes one will see when opening the new version.
I realize this requires additional work for the developers, and I realize that there are so many hours in the day. I don't know how to minimize those hours directly, but I do know that when a "bad" build goes out, you guys are forced into an all-nighter situation at times to try to reduce the negative effects when a serious problem is encountered, and you have to endure the virtual wrath of the user community when it happens, which isn't good for anyone including your selves :) ...the changes suggested above are, to some degree, a method by which I believe you can minimize this problem for both the users and yourselves, even if it takes a bit of up front work.
It is even possible that some of the more altruistic and accomplished programming types will consider providing links and information to assist in executing the above suggestions in as efficacious a manner as possible (for instance auto archiving methods, etc.) without the need to suddenly have access to what we all know is proprietary code owned by the University that you attend and represent.
One need only ask. Although some will make complaints about the idea, others will no doubt take the opportunity to assist without need for personal gain, and it is those participants who might be worth considering as sources to help minimize your load.
thanks for listening.
FYI, this is a call to the user community as well.
And remember..save and save often. This *IS a beta application.