[Deploying Sakai] Frequency of updates to production system

[Stephen Marquard]

Hi all,

Small factoid: at UCT, we've deployed 41 software updates to Vula this year. On 2.6, you can get this from the 'server.start' event, provided you have ui.service set to something that reflects software changes (example below - ours is version / Sakai SVN revision / local svn revision).

I'd guess about half of these are due to local code changes (SMS, course evaluations, UCT-specific branches), and half to pick up changes in 2-6-x branches.

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.

Cheers
Stephen

mysql> select distinct REF FROM SAKAI_EVENT_2009 WHERE EVENT='server.start';
+--------------------+
| REF                |
+--------------------+
| 2.6/[r59698-r7060] |
| 2.6/[r59823-r7070] |
| 2.6/[r59978-r7078] |
| 2.6/[r60134-r7109] |
| 2.6/[r60263-r7129] |
| 2.6/[r61141-r7136] |
| 2.6/[r61708-r7153] |
| 2.6/[r61927-r7169] |
| 2.6/[r62169-r7177] |
| 2.6/[r62169-r7183] |
| 2.6/[r62338-r7190] |
| 2.6/[r62432-r7199] |
| 2.6/[r63133-r7239] |
| 2.6/[r63582-r7273] |
| 2.6/[r63618-r7273] |
| 2.6/[r63897-r7302] |
| 2.6/[r64137-r7316] |
| 2.6/[r64214-r7317] |
| 2.6/[r64331-r7324] |
| 2.6/[r64549-r7324] |
| 2.6/[r64593-r7324] |
| 2.6/[r65127-r7329] |
| 2.6/[r65217-r7334] |
| 2.6/[r65247-r7334] |
| 2.6/[r65306-r7342] |
| 2.6/[r65466-r7358] |
| 2.6/[r65825-r7379] |
| 2.6/[r65836-r7382] |
| 2.6/[r65870-r7387] |
| 2.6/[r65992-r7399] |
| 2.6/[r66226-r7420] |
| 2.6/[r66274-r7429] |
| 2.6/[r66390-r7443] |
| 2.6/[r66495-r7460] |
| 2.6/[r66648-r7547] |
| 2.6/[r66668-r7550] |
| 2.6/[r66959-r7577] |
| 2.6/[r67151-r7590] |
| 2.6/[r68066-r7608] |
| 2.6/[r68142-r7641] |
| 2.6/[r68361-r7673] |
+--------------------+
41 rows in set (10 min 6.70 sec)