Sage server machines
Just gathering what has been discussed on the mailing list: https://groups.google.com/forum/#!topic/sage-devel/Jot2ydQjIhk
possible tools to manage (ie create/launch/control) the VM:
kubernetes: does not seem not very cross platform
Xen: hypervisor
shinken: monitoring
Docker: container
Building/Testing
hosting the patchbot
random testing : the current random doctests uses a single seed, so we do not get any more information when the doctests are run. We could also have some truly random tests that, for example, test the associativity in groups from random_elements. The more they are run, the stronger Sage is. Then we could have som VM that only runs those random tests while changing the seed each time.
deploy builder virtual machines for more distros/architectures as i did for Debian/Ubuntu. We can think of something cleaner than http://sagebuilder.metelu.net/ for example something based on vagrant.
explicit the release tests, and implement them as scripts, for example (some release ideas come from a discussion with Jeroen):
Sage must build and pass tests on a particular set of configurations
try various combinations of optional packages
compile Sage with some user and run it from some other user
check the permissions of the files
check if the source code has some bare 'except:' statements
compile the pdf documentation to discover ill-formatted LaTeX formulas
check if openssl is up-to-date (before each official realease)
...
more generaly, write a test script for each problem that once appeared on sage-release
patchbot with more distributions dedicated to test optional packages