So I finished merging in the Samigo 2.4 changes to the Rutgers code base yesterday the [instructions in the wiki](http://bugs.sakaiproject.org/confluence/display/SAM/Running+Samigo+2.4+in+Sakai+2.3) were actually very good — one small mis-merge on my part, but aside from the self-imposed pain the merge went quite smoothly.
So far, the defaulting to off of the rich text areas is a *huge* improvement in useability (though, really it would be nice if sakai had a nice “minimal” mode or something) though I wonder if it should be labeled “show toolbar” and hide the switching editor modes from the user?
The “retract now” button is also a nice touch.
At some point, organizing the list of posted tests, and finding someway to hide, move tests that were retracted without anyone taking them would probably be a big plus.
Much of August is likely to be spent load-testing (and creating infrastructure to load-test) to validate performance of the upgrade in the Rutgers environment, but the [results from Michigan/Stanford’s testing](http://bugs.sakaiproject.org/confluence/display/SAM/Samigo+2.4+Performance+Testing) look very promising, and we are planning on being on Samigo 2.4 for the Fall semester.
bolster the possibility of using something like the wiki or other tools as I would expect they could be used.
bolster the possibility of using something like the wiki or other tools as I would expect they could be used.