[WG: Sakai QA] Sakai QA] QA Server Confusion

[Noah Botimer]

I'm sorry. I meant every time I want to go to a given server. I  
prefer fail-fast to fail-long-and-confusing (maybe burning 30 minutes  
testing something on the wrong version at the same host). A missing  
server is way better than testing on one that silently jumped releases.

For example, people will get in a groove and test multiple hours a  
day for a week on the same server or two. If they have to keep  
checking the statline for release line and version, it burdens the  
process considerably. Checking Confluence regularly to keep the pulse  
is probably even less friendly.

It is *exactly* the right place for the canonical reference, but  
hostnames/ports shouldn't be volatile with respect to which release/ 
config they represent.

Thanks,
-Noah

On Jan 13, 2010, at 10:39 AM, Seth Theriault wrote:

> Noah Botimer wrote:
>
>> Consulting Confluence to figure out what you're going to get is
>> a lot of overhead.
>
> Confluence is the only place where this information has been
> centralized, for better or worse. I am not sure why you believe
> this adds any more overhead than any other "process" in Sakai
> does.
>
> Seth
>
>
>