I posted this in another thread previously, but it sorta drowned because of a lot of other stuff, so I'll try again with a new thread

Betatesting has been discussed before and this is yet another suggestion

Since it is not really possible to setup a test server so we could test new releases before they were released, I'm thinking of doing it differently. When we change to a new protein, it's possible to upload "old" data for the next 48 hours. Why not use part of that time to beta test?

Besically, it should be possible to set a "beta switch" in the client. If true, the client will load the update right away, if false, the client will continue crunching on the old protein for a little longer - how long I don't know, maybe 12 hours or something?

That would make it possible to report bugs and get them fixed before the majority of the clients is starting to update.

It would also distribute the load on the server, at least a little bit

Stupid idea or?

Ps. Howard, I sent you an email with a link to a broken install. Can I expect to get an email when you've downloaded it?