eZ Community » Forums » Discussions » An explosive cocktail : Symfony and...
expandshrink

Monday 02 July 2012 12:05:25 pm - 68 replies

» Read full blog post

Introduction

Ever dreamt of an even more powerful eZ Publish?
Ever dreamt of an even more flexible eZ Publish?
Ever dreamt of an even easier to learn eZ Publish?

 
Well...you’d better read on.

 

Friday 06 July 2012 1:03:36 pm

Quote from Geoff Bentley :
Quote from Karnichi Mohamed :

Great news ...For symfony developpers.It s Time for me to switch to another business... I spent a long time to master the intricacies of this cms.

@Karnichi Mohamed:  I feel your pain of having invested a lot of time into something, and then feel like your skills will become obsolete.

I don't think switching CMSes is the solution though - I can't think of a CMS which doesn't have this problem - just ask Drupal developers, who will be using Symfony in Drupal 8!  

Change is a constant for web developers - and if you're not constantly learning, your skills are going to quickly become obsolete.  The only difference is the rate of change - standards take a long time to evolve, with good reason; whereas applications & technologies built on top are constantly evolving.

I'm stoked to have an excuse to start working with Symfony, as this makes me more valuable as a programmer; moderately excited about learning the eZ Publish REST & Public APIs; and sad for the eventual depreciation in usefulness of the eZP knowledge I've built up over the last 5 years.

But, 4.x will be around for a while, and there is plenty of time to learn & transition.

@Geoff BentleyI am talking here about business, not about cms. Please stop to see things from a developer's perspective. But I will still talk to you as a developer so that you can understand :

I have no problem learning a new framework, i already mastered two: yii and zend. it's not a question of framework, it is a matter of choice. the problem here is that we impose. I prefere to have the choice.

From the perspective of an entrepreneur, we invested much effort in order to provide our customers the best of ezpublish. I can not imagine the transition, also the time it takes for the new version reaches a level of stability.

Today there are many self-proclaimed ezpublish experts, just because they attended from near and far to one or two projects. Tomorrow there will be many at once, just because they have the label of SF developers ... And I don't feel comfortable with this.

Modified on Friday 06 July 2012 1:05:51 pm by Karnichi Mohamed

Friday 06 July 2012 1:24:11 pm

Quote from Karnichi Mohamed :
Quote from Geoff Bentley :
Quote from Karnichi Mohamed :

Great news ...For symfony developpers.It s Time for me to switch to another business... I spent a long time to master the intricacies of this cms.

@Karnichi Mohamed:  I feel your pain of having invested a lot of time into something, and then feel like your skills will become obsolete.

I don't think switching CMSes is the solution though - I can't think of a CMS which doesn't have this problem - just ask Drupal developers, who will be using Symfony in Drupal 8!  

Change is a constant for web developers - and if you're not constantly learning, your skills are going to quickly become obsolete.  The only difference is the rate of change - standards take a long time to evolve, with good reason; whereas applications & technologies built on top are constantly evolving.

I'm stoked to have an excuse to start working with Symfony, as this makes me more valuable as a programmer; moderately excited about learning the eZ Publish REST & Public APIs; and sad for the eventual depreciation in usefulness of the eZP knowledge I've built up over the last 5 years.

But, 4.x will be around for a while, and there is plenty of time to learn & transition.

@Geoff BentleyI am talking here about business, not about cms. Please stop to see things from a developer's perspective. But I will still talk to you as a developer so that you can understand :

@Karnichi Mohamed - I run my own business, and have done for years.  In your initial post you were talking about the CMS, so I assumed your concern was development-related.  Upgrading software is an important part of any IT strategy (are you still running Windows 95?), and my clients know that.  Please see David's post above for the type of business analysis that should be done.  There is no silver bullet here - each client will be different, depending on their needs and your support agreement.

Friday 06 July 2012 1:35:19 pm

@Mohamed: So you're talking about competition here aren't you happy.gif Emoticon ?

I understand your concern as I worked in web agencies before where I saw those self-proclaimed eZ Publish experts you mention. However, I think you're missing a point here. From a business POV, using Symfony, it not only opens eZ Publish to Symfony developers, it also opens a wider range of potential new businesses!

I already talked with several people who were not using eZ Publish but Symfony for their business, an now that we say that eZ will from now on be built on top of Symfony, they seriously consider using it while they didn't want before!

What I'm saying here is that yes, eZ Publish will be open to more developers that already know Symfony (and that was a target to address since we seriously lack of eZ developers) but:

  • It also opens to new potential businesses
  • They of course still need to learn the eZ API

Friday 06 July 2012 1:46:20 pm

Quote from S V :

Another question: with regards to extension development (new/existing), what's the best approach at this point? Continue in 4.x, rework in 5 or temp freeze?

I think the wiser approach is to continue in 4.x for now, but with forward compatibility in mind, with separation of concerns, like I explained in my blog post.

Of course there are several places where it would not be entirely possible, but separation of concern + dependency injection will definitely help you when jumping into 5.x happy.gif Emoticon.

Friday 06 July 2012 1:57:09 pm

Quote from Geoff Bentley :
Quote from Karnichi Mohamed :
Quote from Geoff Bentley :
Quote from Karnichi Mohamed :

Great news ...For symfony developpers.It s Time for me to switch to another business... I spent a long time to master the intricacies of this cms.

@Karnichi Mohamed:  I feel your pain of having invested a lot of time into something, and then feel like your skills will become obsolete.

I don't think switching CMSes is the solution though - I can't think of a CMS which doesn't have this problem - just ask Drupal developers, who will be using Symfony in Drupal 8!  

Change is a constant for web developers - and if you're not constantly learning, your skills are going to quickly become obsolete.  The only difference is the rate of change - standards take a long time to evolve, with good reason; whereas applications & technologies built on top are constantly evolving.

I'm stoked to have an excuse to start working with Symfony, as this makes me more valuable as a programmer; moderately excited about learning the eZ Publish REST & Public APIs; and sad for the eventual depreciation in usefulness of the eZP knowledge I've built up over the last 5 years.

But, 4.x will be around for a while, and there is plenty of time to learn & transition.

@Geoff BentleyI am talking here about business, not about cms. Please stop to see things from a developer's perspective. But I will still talk to you as a developer so that you can understand :

@Karnichi Mohamed - I run my own business, and have done for years.  In your initial post you were talking about the CMS, so I assumed your concern was development-related.  Upgrading software is an important part of any IT strategy (are you still running Windows 95?), and my clients know that.  Please see David's post above for the type of business analysis that should be done.  There is no silver bullet here - each client will be different, depending on their needs and your support agreement.

(Joint moderation with author.)

Modified on Wednesday 01 August 2012 12:30:27 pm by Nicolas Pastorino

Friday 06 July 2012 2:15:08 pm

Quote from Geoff Bentley :
  • keep 4.x rolling on smoothly
  • help ease the process of change to eZP5.

Geoff

Hi all! 

This has become an interesting discussion, one where I understand all parties. I seriously like the idea of a CMS built on top of Symfony, the eZ way (as a developer).

But as pointed out by different members already, I'm also a bit concerned about the implications this will have (from a business point of view). It seems if eZ Publish 5 is becoming a whole new shiny CMS built on top of Symfony, and maybe that's exactly what was needed in the current CMS landscape. But it also means that experienced companies that have a track record in building and supporting eZ Publish websites are forced into this new direction, with indeed a lot of competition. For every partner there are different reasons to either support the new approach, or dislike the new approach.

I personally think that the best option for eZ Publish is to refrain from releasing this 'new product' as eZ Publish 5, instead it should have a new branding or name. What about eZ Symfony? This way the eZ Publish range could stay as it is and get a long term support, including enhancements and patches. It would also save the headache of building a complicated new system with an eZ Publish 4 kernel integrated and could simply be marketed as the newest, latest CMS solution out there. eZ Publish business and community partners then have major advantages over the current roadmap eZ is proposing or decided to go with:

  • instead of only eZ Publish, partners can offer the second product if they want to
  • they won't have to disappoint clients who just invested thousands of Euros for a new eZ Publish website
  • they can continue doing what they are best at, serving eZ Publish customers, without having to learn a whole new framework
  • they won't have to tell a story in which they're saying eZ Publish 4 is outdated, not longer meeting international standards, etc. etc. and trying to persuade clients to migrate to eZ Publish 5

Further, for eZ Systems, a second product would not only make eZ Systems look like a bigger and more competitive company, they could also actually benefit from a new branded product:

  1. For all of those customers and developers that considered eZ Publish in the past but didn't choose it, it's a brand new option to go with
  2. All that eZ Systems has learned in the past about do's and don'ts for marketing, they would have a real 2nd change: do it right from the start
  3. New enterprise CMS solutions are scarce, and it would certainly generate a lof of buzz
  4. Introducing a new product would show eZ's respect to its old partners and customers: they don't have to switch but get a clean new option. The old partners and customers are appreciated (as they deserve) and eZ Publish 4 will last and continue to exist.

I hope I still got the opportunity to bring in some fresh ideas about this new approach and our feedback is even considered. I personally think the business partners and community members should always be actively involved in decisions that directly affect their 'business'-strategies. We are the people making or breaking this product, if we don't sell and support it, there is no product.

I really hope the eZ Systems community and management teams are following this discussion actively and are willing to actively participate and respond to the positive and negative feelings living in this forum nowadays.

All of the above is written to contribute to this discussion in a positive way, I'm not trying to blame anyone and whatever will happen, as a business partner we decided to maintain and invest in a long-term relationship with eZ Systems and we hope that feeling is mutual.

All the best,

Terry Duivesteijn - Lead developer Contactivity

Friday 06 July 2012 2:18:58 pm

Quote from Karnichi Mohamed :
Quote from Geoff Bentley :
Quote from Karnichi Mohamed :
Quote from Geoff Bentley :
Quote from Karnichi Mohamed :

Great news ...For symfony developpers.It s Time for me to switch to another business... I spent a long time to master the intricacies of this cms.

@Karnichi Mohamed:  I feel your pain of having invested a lot of time into something, and then feel like your skills will become obsolete.

I don't think switching CMSes is the solution though - I can't think of a CMS which doesn't have this problem - just ask Drupal developers, who will be using Symfony in Drupal 8!  

Change is a constant for web developers - and if you're not constantly learning, your skills are going to quickly become obsolete.  The only difference is the rate of change - standards take a long time to evolve, with good reason; whereas applications & technologies built on top are constantly evolving.

I'm stoked to have an excuse to start working with Symfony, as this makes me more valuable as a programmer; moderately excited about learning the eZ Publish REST & Public APIs; and sad for the eventual depreciation in usefulness of the eZP knowledge I've built up over the last 5 years.

But, 4.x will be around for a while, and there is plenty of time to learn & transition.

@Geoff BentleyI am talking here about business, not about cms. Please stop to see things from a developer's perspective. But I will still talk to you as a developer so that you can understand :

@Karnichi Mohamed - I run my own business, and have done for years.  In your initial post you were talking about the CMS, so I assumed your concern was development-related.  Upgrading software is an important part of any IT strategy (are you still running Windows 95?), and my clients know that.  Please see David's post above for the type of business analysis that should be done.  There is no silver bullet here - each client will be different, depending on their needs and your support agreement.

(Joint moderation with author.)

@Karnichi Mohamed - I use Debian, RHE, Ubuntu, XP, Win7, OSX.  My point was that upgrading software is an important part of any IT strategy.

Modified on Wednesday 01 August 2012 12:31:27 pm by Nicolas Pastorino

Friday 06 July 2012 2:24:14 pm

Quote from Geoff Bentley :
  • keep 4.x rolling on smoothly
  • help ease the process of change to eZP5.

Geoff

I personally think that the best option for eZ Publish is to refrain from releasing this 'new product' as eZ Publish 5, instead it should have a new branding or name

Nice lateral thinking Terry!

Friday 06 July 2012 2:45:21 pm

Quote from Geoff Bentley :
Quote from Geoff Bentley :
  • keep 4.x rolling on smoothly
  • help ease the process of change to eZP5.

Geoff

I personally think that the best option for eZ Publish is to refrain from releasing this 'new product' as eZ Publish 5, instead it should have a new branding or name

Nice lateral thinking Terry!

THAT will not happen, eZ publish has been developed since 1999 and they are well known as eZ publish, this brand has a lot of value, I am sure about that, changing it can cost a lot for everybody, specially eZ systems.

@Mohamed Please post where is your eZ publish Expert certification, the last time I checked there is just the eZ Publish Developer Basics Certification, so every eZ publish Expert is, in some degree, self-proclaimed, and in some cases self certified...

Modified on Friday 06 July 2012 2:47:12 pm by Thiago Campos Viana

Friday 06 July 2012 3:13:33 pm

Quote from Karnichi Mohamed :
Quote from Geoff Bentley :
Quote from Karnichi Mohamed :
Quote from Geoff Bentley :
Quote from Karnichi Mohamed :

 

@Geoff BentleyI : I use Linux, this is not your case apparently. this is why you do not understand what I say. And please keep this kind of comments to your girlfriend

@Mohamed : Please make sure you read again the forum guidelines : http://share.ez.no/about/etiquette-blogging-and-usage-guidelines , and watch your tone. Thanks in advance.

Friday 06 July 2012 4:00:17 pm

This is a very interesting change of direction! I've been away from this community since 2009, and just now and then trying to keep a high level overview of what's going on. IMHO this can be the biggest turning point in 3 years and I believe it can potentially give a boost again to the eZ ecosystem.

This can be beneficial for all involved parties, including long-term partners and customers. Thinking loud:

  • if eZ Publish 4 remains part of eZ Publish 5 to maintain BC, then I suppose eZ Systems will do anything to make upgrading as easy as possible, like they've usually done in the past, to increase the adoption of this new major version
  • in that case, I also assume severe or less severe bugs in eZ Publish 4 will get fixes, because it is an integral part of eZ Publish 5, so there is no immediate need to upgrade all your custom code,
  • unless you want to make use of the shiny new APIs of eZ Publish 5
  • where we get to the point that building on top of well-designed, well-documented, popularity-gaining PHP libraries of which further development is assured by both a broader community and another company (Sensio Labs), is both from an economical as well as a technical point of view better than re-inventing the wheel,
  • it finally allows eZ Systems and its technology partners to focus on the CMS functionality,
  • I believe businesses will be able to convince their customers more easily about the continuity of the product, because its fundaments are known by a broader community
  • also I think as a business you can more easily find developers who have some experience with Symfony already, and if not experienced they will be able to learn it much faster because it's well documented
  • this might lead to a market growth of eZ Publish
  • at the end, it's up to you as a business to make the difference in quality, quantity and service you offer, no matter if you are operating in a niche market with a limited amount of competitors or on a bigger market
  • communication could've been better, following this thread it looks to me - considering myself as an outsider these days - that business partners weren't involved enough in the decision making or not informed well on forehand about the final decision before this got publicly announced - putting in question the benefits of their partnership
  • keep friendly to each other, hit the ball and not the heels blunk.gif Emoticon

To end this comment, a disclaimer: these days I am mostly spending my time developing for Drupal, which will have its legacy fundaments replaced by Symfony as well in the next major version.

Friday 06 July 2012 4:04:46 pm

@Nicolas: my bad, I withdraw my last comment. if you can delete it ... do it.

@Nicolas & Jérôme : tanks for your constructive responses. we will wait, see what happens.

@Thiago Campos: there is no certification "ezpublish expert". I passed the same certification that everyone http://auth.ez.no/certification/verify/272595 . Also, there is no relationship between certification and expertise. you should not feel concerned about my speech on the self-proclaimed experts. I would not go further at risk of being misunderstood again.

Saturday 07 July 2012 1:21:39 am

Quote from Kristof Coomans :

This is a very interesting change of direction! I've been away from this community since 2009, and just now and then trying to keep a high level overview of what's going on. IMHO this can be the biggest turning point in 3 years and I believe it can potentially give a boost again to the eZ ecosystem.

(...)

Spot on, we will threat 4.x (referred to as "legacy" in the context of 5.x) as supported part of the product until 6.0, witch might mean 5 years + ee support time. And we will make sure upgrade path is as smooth as always.
The only case where you can not mix and match the two kernels will be if you decide to use a different persistence storage engine then "legacy", as in we plan to have a nosql and potentially a improved rdbms storage engine sometime next year, but they will be all supported. Same goes for IO handler (binary files), if you want to use a potential future S3 handler, then you will need to refactor your code to be on the 5.x stack.

@Terry / @Geoff: Regarding continued innovation in 4.x, this will continue to happen in the form of pull requests, bug fixes and small enhancements.

Final note on expectations:
Transition to a full 5.x stack will take time, our release in November will as mentioned before not contain everything needed to work alone, it will first and formost include the finished Public API, REST API v2 and the 5.x (Symfony) stack, on top of those three components you will find a first edition of Editorial Interface, but certainly not everything we intend with it yet.

Sunday 08 July 2012 12:15:32 pm

Hi all. Yep, i was a bit surprised with the announcement. As someone said, where are the ez components then?. but anyway, i see this as a move and time will say if it's a good or a not so good move happy.gif Emoticon

As a developer i did things in the past that needed to be changed years after. And at that time i was like '"hell, this would be much better if i replace this old library for this another new one". And i think something similar has come to the minds of the ez engineers (ok, at a much bigger level). But it's their decision and i think it's more a technical move than a business move (even at the end they can be related, of course). 

I think ez engineers normally take good decisions, so before being in panic, i'd let them the time to guide us in this process. 

Some other things that have been commented:

About symfony developers

Go back in the past. There are plenty of post talking about problems of eZ Publish. Normally one is always there: Lack of eZ Publish developers and difficult for php developers, even for experienced ones, to start writing code for an eZ Publish app. You can also have a look at the number of members in this community and compare it with the number of drupal accounts... You can also have a look at the irc channels. have a look at the people connected to drupal, wordpress, magento and ezpublish and you'll see what we are talking about. 

So if this move brings more people to ez publish world then welcome them!. is not that what we wanted?

I understand many of us have invest resources and money to be good with eZ Publish. But in my experience, i also think we may have lost some contracts because ez publish is not a widely used product here in Spain. And, in a wrong way, many people thinks "is not widely used => is not a good product". And we and the customers finally going with eZ Publish know this is not entirely true. 

That being said, i still think we, as experienced ez publish developers, have some adventage "vs" the new companies that might be trying eZ for the first time. Recently i started to work Magento. It's Zend based, but i didn't need to worry about it at all. Of course, i needed to learn Magento API, how it can be customized and so on, but Zend was something being there and i didn't even open its folder happy.gif Emoticon

I think something similar will be with Ez Publish. We won't really need to worry about Symfony and we need to focus on the eZ Publish API instead. So, being a Symfony expert won't necessary mean being an eZ Publish expert. 

Reactions

Again, back to the past and think about the reactions, apart from eZ Community itself, that eZ Publish announcements have reached. Yep, we read things about Etna or Fuji in some cms websites, in post similar to the "press note" sent by eZ Systems (hope not being so crude with this sentence).

But for developers this announcemets was like "cool, but still i'm not interested on it". But know "we" are getting attention from people outside ezcommunity itself. Have a look at http://symfony.com/blog/symfony2-meets-ez-publish-5. This post have now more comments that, i would say, a 90% of the posts in this forum happy.gif Emoticon

To finish, i would like to point to the comment #16 in that post. it says:

"Now there will be an instant CMS solution for symfony2 available. That's a big step for symfony2 to rule the (php) world."

And this is a really interesting point of view imho... 

Modified on Sunday 08 July 2012 1:37:17 pm by Carlos Revillo

Tuesday 10 July 2012 9:31:28 am

With the Hangout scheduled for this morning, I thought I would post the types of items that I plan on asking for clarity on.  First a small disclaimer:

What this is not:

I personally don't care if the final choice was A, B or C . The rationale of eZ deciding to switch to a framework for future releases is sound enough regardless of which flavour of framework is chosen. This is not a post regarding the suitability of Symphony or an assessment on the direction of eZ Systems with this recent announcement. 

What this is:

Setting aside the above, this is much more a list of questions to further help myself and others understand how to prepare for eZP5 and how it relates to existing large projects with a large amount of custom code and extensions.  The questions may  seem slanted towards eZP4. True - but that is simply because the first thing I need to do is make sure my eZP4 house is in order including all existing clients.  Only after understanding that can I fully start to embrace eZP5.

Question Context - Community

The questions below are specifically geared to the community edition and not enterprise.   Answer stating something like: "will be maintained by eZ Systems according to the terms of our Enterprise offer." are not necessarily the most helpful in relation to the community edition. Therefore, it would be appreciated if answers could also be given in the same (community) context.

______________________________________________________________________

eZP5 Production release
From analyzing the information available to date, it appears that the November release of eZP5 and the releases to follow shortly thereafter represent a product still under final stages of development.

  • Q: Is there an estimate as to when there is expected to be a production-ready version of eZP5?

eZP4 Kernel Clarity (2 versions?)
There have been comments regarding the eZP4 kernel and its inclusion in eZP5 for the dual porposes of (A) Backward Compatability [BC] abd (B) It will still serve an integral part of the early releases of EZP5.  This has made some people infer that updates to eZP5's 4.x kernel(I will call Legacy Kernel for clarity) will have a positive impace on the production tree of eZP4 use in production (currently 4.7 and community 201206).  However, It is my understanding the the Legacy Kernel is a fork of the eZP4 version pre-4.7 and that it is heavily mdodified for use as a freestanding API.

  • Q: If it is correct that it is a fork and has been modified for a different purpose, is there truly any reason for people to assume or expect that updated to the Legacy Kernel of eZP5 will ever make it back into the eZP4 Production Branch?

BC
It is clear that the commendable step of ensuring the use of eZP4 templates in eZP5 will lessen the immediate burden on people during a migration process.  However, little has been mentioned regarding the overall BC of a base system. BC has always been in reference to templates and the Legacy(4) Kernel.  The various posts raise a few items for attention:

  • Q: What it the expected timeframe that BC will be supported.  At the last meetup, a 2-3 year estimate was given.
  • Q: Is it epected that the full 4.x kernel will work along with standard extensions?  As an example: Should I expect to unzip an eZP4.6 install and all base extensions ezwebin and ezpublish, etc and expect it to work? To me, that is a benchmark for the level of BC - a standard install should work - anything after that is a custom coding or 3rd party extension issue.
  • Q: The data storage engine will change over time.  When this happens, would it not be a safe assumption that BC will be at an end if I then switch to the new storage engine?

Upgrade Path:
Regardless of the level of BC, I see the actual upgrade path to be:

  1. Migrate website over and rely on BC for the 'short term' - giving you some time to complete step 2
  2. Refactor/rewrite
    1. Systematically rewrite underlying code (the level of refastoring vaying greatly depnding on how abstract your code already is)
    2. Rewrite all template logic into a combination of controller/model code(php) and new template code

The way I see it is that no matter what level of BC is included, taking into account the fact that soo much logic exists in the templates currently for most eZP users, the ultimate upgrade path is essentially a rewrite of your existing website to a very large degree.

  • Q: I this a wrong assumption or an accurate assessment of the final need to eventually refactor/rewrite most code as the main part of the upgrade path?

eZP4 Future
If the above answers are close to what I am inferring now, there are many websites that will not be candidates for upgrading to eZP5.  This means that I may be relying on eZP4 for quite a few years to some.  The few comments to date about the end-of-life of the eZP4 branch have been somewhat vague and non-committal beyond assurances that pull requests from the community will continue.  This is the expected result of the push to eZP5.  However, it does not leave me feeling reassured that there will be much in the way of updates to the eZP4 branch or that there will be an overly enthusiastic approach to incorporating pull requests into future monthly community releases. It appears that in the eyes of eZ systems, The eZP4 'product' is quickly reaching the end of it's lifecycle. However, to me it seems not to be happening in a very defined or organized manner.
Q: Can eZ please give a statement specifically to the end-of-life of eZP4 production branch and what can truly be expected (timeline, expected timeline for update eleases based on pull requests, etc).

Tuesday 10 July 2012 12:05:50 pm

Find the recording of the eZ Publish Show #7 here, a Questions & Answers session on eZ Publish 5.

Thanks Geoff for making these shows happen !

Wednesday 11 July 2012 10:22:24 am

Is there still anybody at the steering wheel setting the course?

Does senior management (CEO) at eZ Systems have a vision or strategy concerning ezpublish 5? I get a feeling this show is run completely run by engineers, who seem to make very ad hoc decisions and prefer to leave things open for discussion as long possible. There is more to the introduction of a new eZ Publish version than technical details alone. The non-commitmental approach, lack of long-term strategy and the very informal and incomplete presentation of the plans for the future does not leave me confident about the future of ezpublish.

I'm not debating the move to Symfony - that sounds like a great plan. But the way this is going, it looks like a mickey mouse operation.

Edit: anyway - this will be my last contribution to this discussion. Will use my valuable time to start learning Symfony.

Modified on Wednesday 11 July 2012 10:28:03 am by S V

Wednesday 11 July 2012 11:12:00 am

Hi Sebastiaan and all,

I understand your questioning about this decision as changes are always a bit scary but this is the result of a discussion between senior management and engineers.  And reading the amount of good, enthusiastic comments all over the web and I think it is the kind of synergy that had been awaited from eZ Publish. 

And for those who want more information on "The "Why" and how BC will not kill you", you will find the new blog from Jérôme here.  

Very nice one, Jérôme, congrats!

Wednesday 11 July 2012 12:03:35 pm

Hello,

I installed eZPublish 5 alpha yesterday and it looks really nice and promising so far. It all seems to work pretty well.

Just one thing about the installation phase, are you planning on adding some new packages here, since I had to comment out the line and replace the old packages by those from ez4.7 to get this working. This would make the installation a little easier.

http://packages.ez.no/ezpublish/

There are also a few issues in the back office but I think you are working on a new admin interface. Any plan on releasing this in a beta phase? 

How about the community version? Yhere was no CE release in june for the first time in a year. Are the CE releases going to continue at least until the release of eZ5?

Thank you

Wednesday 11 July 2012 12:19:47 pm

Quote from Paul Leclercq :

Just one thing about the installation phase, are you planning on adding some new packages here, since I had to comment out the line and replace the old packages by those from ez4.7 to get this working. This would make the installation a little easier.

This should not happen if you use 2012.5, migrated to the ezpublish5-branch like explained in the installation doc. What is your eZ Publish legacy version ? Did you migrate it ?

Quote from Paul Leclercq :

There are also a few issues in the back office but I think you are working on a new admin interface. Any plan on releasing this in a beta phase? 

What kind of issues ?

As for release, we plan to have an alpha in mid-august.

Quote from Paul Leclercq :

How about the community version? Yhere was no CE release in june for the first time in a year. Are the CE releases going to continue at least until the release of eZ5?

As for the June release, this is not related to eZ Publish 5 development. Maybe Nico or Maud can talk about it ?

As far as I know, CP releases will continue before and after the release of eZ Publish 5.

expandshrink

You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu

Proudly Developed with from