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.
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 assume majority of us want to take MH into production sooner or later,
right? At least I really would love to do it. Does anyone know more
about the upgrade path considering Matterhorn's roadmap?
Olli S
On 21.1.2012 21:37, Greg Logan wrote:
And finally, the 'upgrade path' from 1.2 to 1.3 - can we expect any docs or a
short guide?
I'm not 100% sure here, but as far as I know the upgrade path between
the two releases is to delete everything, drop the DB, and start over.
--
Olli Salo
Tietotekniikkakeskus
Helsingin yliopisto
Tel: +358 9 191 21782
Gsm: +358 50 407 5509
Email: [email protected]
_______________________________________________
Matterhorn-users mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
