Hi Ingmar,

I can appreciate your optimism on this point, however, this path has already be traveled. Joomla and Drupal users are caught in a giant vice between releases (Drupal is horrible in this respect). New features being added to the latest release, while the old release is slowly withering away - and users crunched as they consider the costs and unpredictability of migration. I would not call it legal torture, but it is pretty close.

For this reason, I have a concern about migration paths, which it seems like I will have to deal with. Since there is no timeframe for the new release, it makes the issue particularly difficult to deal with, but that is business.

Thanks for your help.

Rich

Hi Derek,

Can you amplify on this? For example, an update between versions in Wordpress usually consists of:

1) Uploading new files.
2) Checking whether the new version breaks the theme in any way (very common for more complicated themes).
3) Checking which add-ons are broken.

Not very pretty, but something that I have learned to deal with, and probably the best of what I have seen in the open source world. Are you objectives similar?

Thanks for the additional info.

Rich

I’m not sure what you’re asking Rich, if you want to restate I’ll be happy to add a bit more information where I can. If you’re asking what the update steps will be specifically, they will be very similar to the current version update instructions.

Hi,

Thanks for getting back to me.

What I am asking, is what the upgrade instructions will look like when the new release will become available. Will it be something like I described for Wordpress - in other words a
upgrading by simply uploading the new files, and then customers testing out third-party add-ons, modules, themes revisions, etc. and fixing as necessary? Are there particular add-ons that you are testing to ensure that they will continue work in the new version? I am assuming you have a target that you are testing for and attempting to achieve in regards to upgrading. If there is such a target, it would make it easier to build a system now, since I will understand the impact later on, as I seek to upgrade.

Thanks again for your help.

Rich

What I am asking, is what the upgrade instructions will look like when the new release will become available.

Ah good, I did understand. Answered above.

To the second part of your question, the developer preview is our attempt to reach out to third party developers - most of the popular add ons are included, but a specific list is not available at this time.

You may also find these useful.
- EE2 FAQ
- Preparing for ExpressionEngine 2.0
- ExpressionEngine 2.0: fully CodeIgnited

Thanks for the additional information and links.

Rich

The reason I’m considering waiting for EE2 on some projects is the fact that I want to work with CI rather than the existing code base when it comes to extending core functionality.