Some Midgard roadmapping

cover image for Some Midgard roadmapping

There has been some discussion on how the different items in the Midgard roadmap fit together. Here is my company's view on how we see ourselves proceeding.

Baseline: Midgard 1.8, MidCOM 2.8 and PHP 5.2

At least in our company we're trying to consolidate all customers to these version numbers. MidCOM 2.8 is a very capable (if heavy) platform that we will be able to support for a long time. It is also important, as...

Next step: Midgard 1.9, MidCOM 2.9 and PHP 5.2

Having consolidated sites to MidCOM 2.8 and PHP 5.2, it will be very easy to migrate to Midgard 1.9 (PHP4 not supported). While Midgard API changes somewhat (Exceptions, Midgard_Connection) between 1.8 and 1.9, MidCOM 2.9 (currently called "trunk") is able to hide that from site builders.

Mid-term: Midgard 1.9, MidCOM 3.0 and PHP 5.2

The main reasons to switch from Midgard 1.8 to Midgard 1.9 are performance, new installer and the ability to run MidCOM 3 alongside MidCOM 2.8. While MidCOM 3 requires complete site rewrite from 2.8/2.9, this phase makes migrations and running sites with both versions on same server possible.

Long-term: Midgard 2.0, MidCOM 3.0 and PHP 6

Once a server has completely migrated from MidCOM 2.x sites onwards, it will be possible to make the final jump to the full new generation Midgard platform.

Technorati Tags: midcom, midgard, php

Read more Midgard posts.