[Deploying Sakai] Migrate Sakai 2.5.0 to 2.6.0

Steve Swinsburg steve.swinsburg at gmail.com
Tue Mar 16 21:42:41 PDT 2010

Hi Leonardo,

If you can find out what/if any modifications were made, that will make things easier. If not, then grab a fresh copy of 2.5.0 and diff it against your current version of 2.5.0 and see what changed. Then apply those changes to a 2.6 instance. Bed the code changes down and when ready, it is just a case of upgrading the database and starting up the new code pointing to that database. 

You'll want to do this a few times locally just so you can get the process sorted. 


On 17/03/2010, at 3:07 PM, leonardo jr escorido wrote:

> Hi,
> I am another case of a new guy in the company and new to Sakai :) 
> I need to migrate the production-ready Sakai (2.5.0) used by the client to 2.6.0.
> I am not quite sure but my guess is, the application had changes/customization in the code-level which was done by a third-party (though I am really hoping it isn't).
> Can anyone provide guidelines/online resources on how to do this? I will appreciate it.
> Thanks,
> Leo
> _______________________________________________
> production mailing list
> production at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/production
> TO UNSUBSCRIBE: send email to production-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/production/attachments/20100317/75a9adc1/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3689 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/production/attachments/20100317/75a9adc1/attachment.bin 

More information about the production mailing list