Monday 01 August 2011 12:53:47 pm
Hi Samuel, For you first question, be sure to check http://share.ez.no/community-project/release-policy and also look at the graph in those slides. You should visualize the enterprise and community releases as parallel tracks. 4.5 can be called stable, it had it's regular QA phase. The community release differ mostly in the fact that it lacks the QA phase, and it is released every month to make participation and more important innovation possible. That graph should make things a bit more clear I hope. Question two; upgrade the normal way, you are used to, from 4.3 to 4.4, from 4.4 to 4.5. From there on, you should be able to upgrade to 2011.7. You need to ask yourself the question though, do you want to use the more innovative community release which might have a few more bugs, or do you need a solid and stable and tested (QA phase) release which is the enterprise one. Personally I would not mix them, and stick to one of those releases. Use the upgrade guides on doc.ez.no for the enterprise upgrade cycle. On the download pages on share.ez.no you find upgrade instructions for the community releases. Question 3; as above, for the enterprise release, see doc.ez.no, and for the community release see for example http://share.ez.no/download-develop/downloads/ez-publish-community-project-2011.7/upgrading-from-ez-publish-community-project-2011.6-to-2011.7. Question 4; both should be the same version e.g. code base. Question 5; as far as I know, those extensions should work on the community release also. On a side note; although it looks as if we are now releasing to different packages (enterprise and community), it should still be possible to upgrade/migrate between them without any problem. This was one of the goals we set when we started with the two separate releases. Let me know if you have any further questions. Regards Robin
Board member, eZ Publish Community Project Board - Member of the share.ez.no team - Key values: Openness and Innovation.
LinkedIn: http://nl.linkedin.com/in/robinmuilwijk // Twitter: http://twitter.com/i_robin // Skype: robin.muilwijk
|