[Deploying Sakai] Frequency of updates to production system

Matthew Buckett matthew.buckett at oucs.ox.ac.uk
Tue Nov 3 06:40:08 PST 2009

On 2 Nov 2009, at 12:03, Stephen Marquard wrote:

> I'd be interested to hear your experiences or if you have a regular  
> schedule for software updates (e.g. once a week / month, etc.) and  
> how you manage them.

The release we've made since January 2009 are (tags from our  
repository, so upgrade dates are normally later):

8d77698 2009-03-02 Update version to 2.5-ox3 final build.
beb1378 2009-03-13 Final bugfix build
86203e2 2009-04-20 Final 2.5-ox4 build.
1fe3804 2009-05-12 Making the final 2.5-ox4.2 build
01666e0 2009-06-22 Final 2.5-ox5 release
23655a5 2009-06-29 Final 2.5-ox5.1 build
320509c 2009-07-06 Final 2.5-ox5.2 build.
aac5df7 2009-07-31 Final 2.5-ox5.3 build
6bbe0d4 2009-11-02 Increment build to 2.6-ox1

Generally we try to have a major (eg: 2.5-ox4) release just before the  
start of term and then normally a bugfix (eg: 2.5-ox4.2) a few weeks  
later to catch anything we missed in our testing. We try to avoid  
large feature changes during the middle of term.

We have 3 terms each academic year. (http://www.ox.ac.uk/about_the_university/university_year/dates_of_term.html 

We just upgraded to 2.6-ox1 this morning and so far everything is  
ticking along nicely, but already a few little issues have appeared  
which we will fix over the next few weeks.

Matthew Buckett
VLE Developer, Learning Technologies Group

More information about the production mailing list