Now that we have a couple of development branches, it's time to plan how to better provide QA support for them.
Basically there are 3 possibilities:
We do nothing and just keep master as only QA site This seems to be discarded because we are going to need a site for the next release (3.10, in November) QA cycle.
b) We only keep ONE QA site, for the very next version to be released (3.10 right now).
c) We keep QA sites for ALL development versions (3.10 and 4.0 right now, with the former becoming 3.11 after November).
Whichever is the decided approach the sites will need to be created (public and master), documented and so on, this issue is about that.