Hi everyone, With 1.2.0 almost being out of the door, I wanted to give an update as to what development will be focussing on during the next couple of weeks. Because of the delay that 1.2.0 incurred and the repercussion this has on 1.3.0, as well as a push from the pilot schools to focus on the technical work for 2.0, it's becoming very likely that we'll upfront some of the planned work on performance and scalability and make it the next target.
Initially, this architectural work will mostly focus on modeling, instrumentation, measurement and setting up an environment that allows us to do this continuously, both from a UI and server point of view. We'll then be identifying the biggest bottlenecks and make changes based on that, and will not allow improved or new solutions into master until we've collected evidence that is indeed an improvement. The threads for ideas about experiments and possible solutions have already started on list ... Obviously, a reasonable amount of 1.3.0 work has already happened and we want to use as much of that as possible. Therefore, we'll try to do a smaller 1.3.0 as soon as possible that just includes the work that has already been finished or is close to being finished. At this point, that seems to be CLE tool skinning (finished), editor role and configurable content sharing. Once 1.2.0 is out of the door, we'll try to do a bugbash with this so we can get an idea as to how close we are for that remaining work. In the meantime, at least a part of the team will be focussing on modeling, measurement and instrumentation ... None of this is necessarily set in stone yet, but I thought it was worth keeping the list up-to-date on the current thinking. Hope that helps, Nicolaas _______________________________________________ oae-dev mailing list [email protected] http://collab.sakaiproject.org/mailman/listinfo/oae-dev
