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

[Noah Botimer]

Also, I should mention that Alan did exactly what we have established  
as practice. He sent a nice email to the QA list saying that he was  
switching qa1-nl  over for a while. I just noticed it more this time  
because two of our very experienced people got snagged and confused.

(Again, "oh, I guess it's down" is much less confounding than "what  
happened to qa1? It was 2.7 last time...")

I didn't imagine that it would be a hassle to come up on a different  
port when switching releases. Different deployment processes could  
make this harder, though, I suppose.

I guess this is an informal suggestion of a process refinement, to be  
considered or rejected by those who do the yeoman's work.

Thanks,
-Noah

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

> Noah Botimer wrote:
>
>> 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 might be reasonable for QA admins to use the MOTD to state the
> version the server is running. Especially if it's different from
> Confluence or the "usual" state. I actually do this locally to
> indicate "No UTF-8" for the database.
>
> Asking people to run multiple servers on multiple ports is, I
> believe, a little much. We have a hard enough time maintaining
> one up-to-date instance per server with our already overworked
> volunteers.
>
> Seth
>
>
>