Hi Olli, > that's not an upgrade path but a clean install. This is a _very alarming_ > piece of news if this indeed is the case. :( If there is no upgrade path we > can't ever go to production and we're stuck on just small pilots with our MH > setups.
If there were no upgrade path, that would indeed be alarming. However, there *is* an upgrade path, it has simply not been implemented so far due to a lack of interest (the need for an update path has been discussed at developer meetings, but should definitely happen on list as well). What needs to be done is write a database script to adjust the tables and field names (we did a refactoring of the naming of tables and fields) and add those fields that are new with matching default values. Search indexes for workflow, series and scheduling can simply be removed and will be recreated from the database (as always, back up your data prior to doing this). In other words, if there is interest from your side in a migration path, please make yourself heard and - if possible - put resources on it. The community will without a doubt be there to support you. If you are not able to help with resources, it may be that update scripts and instructions are available only *after* the release. > In Wordpress, Moodle and many other OS products the upgrades are nowadays > pretty frequent. I'm not saying that frequent updates are nice, but the > ability to upgrade is. For example both Moodle and Wordpress have had several > XSS vulnerabilities lately and if we were unable to upgrade our Moodle / > Wordpress installations, we would be running systems filled with security > holes. That's why I think the upgrade path ability is an extremely critical > part of every production system: running a production environtment is not > possible if there is no upgrade path. :/ I think all of us are on the same page here, there is no question if an upgrade path is necessary or not. The question simply is who is going to put resources forward to make it happen. Thank you for your clear and direct comments, Tobias _______________________________________________ Matterhorn-users mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
