Notes from Moodlemoot 2013
Olivier Guillot and Gilles-Philippe Leblanc from Université de Montréal presented
Why:
Bugfixes, security fixes
major improvements
stay close to current to make upgrades easier (ie 2.1 to 2.5 would be hard)
easier on any custom mods
easier to backport critical fixes from upcoming verisoin
avoid pitfall of being too far behind to upgrade
when:
avoid 2.x.0 versions
2.x.1 is usually out in a month with substantial fixes
each version has new improvements that are subject to bugs
january and august upgrade windows for major versions 2.x
how:
get neve version
merge custom code on new
commit sources
insall on devel server first, then road test
do functional testing using browsers
test critical modules (grades assignment forums)
fix/merge theme, fix functional test
backport blocker and critical issues from upcoming versojns
load testing to see if new ver has performance issues
winmerge
3 month testing phase
minor fixes - backoirt security blocker critical
search tracker for updates marked with UI change -> that way you know what to make users aware of
upgrade based on downtime from stats
post on form, post news block on all pages about upcoming downtime
No comments:
Post a Comment