On 10/25/11 12:54 PM, William Stein wrote:
I'm personally not super comfortable with this, especially if I have to have to be the one responsible for fixing things when they inevitably break and cause trouble. From the second I switched back to the old version until now, I haven't had any complaints about any *.sagenb.org's not working, and haven't had to restart them, etc. So I'm only OK with this if you're 100% on deck, and I don't have to do anything, and you switch it all back as soon as you can.
I agree in that I'm not super comfortable with this either. And I agree that the right solution is to write stress-testing code. Let's see: Rado had something that was stress-testing things back in March. Rado: if you have time, can you try hammering test.sagenb.org with that test suite?
I won't do the sagenb.org test until I have time to deal with whatever comes up from it.
Thanks, Jason -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
