eZ Publish Community Project 2011.5 available now / Discussions / Forums - Share eZ Publish! The eZ Publish Community

Forums / Discussions / eZ Publish Community Project 2011.5 available now

Wednesday 18 May 2011 12:19:16 am - 6 replies

Introduction

The second build of eZ Publish Community Project is now available. Read on for all details.

6 replies

Author	Message
Damien Pobel	Wednesday 18 May 2011 11:44:11 am Small notes to eZ Find users : you may encounter an indexing issue on hidden or invisible objects with eZ Find included in this version. You can manually apply the patch of this commit or retrieve the last version of schema.xml to fix this. Cheers Damien Planet eZ Publish.fr : http://www.planet-ezpublish.fr Certification : http://auth.ez.no/certification/verify/372448 Publications about eZ Publish : http://pwet.fr/tags/keywords/weblog/ez_publish
Geoff Bentley	Thursday 19 May 2011 3:51:18 am Has the naming convention been designed to confuse new users? It bears no relation to the eZ Publish documentation, or the Enterprise version. How on earth is someone supposed to know which documentation they should be reading?
Nicolas Pastorino	Thursday 19 May 2011 2:02:52 pm " Has the naming convention been designed to confuse new users? It bears no relation to the eZ Publish documentation, or the Enterprise version. How on earth is someone supposed to know which documentation they should be reading? " Hi Geoff, good point. We (the Community Project Board) are planning on providing a correspondance map between the Enterprise Edition version and the Community Project version. The primary purpose of this is to show the parallel yet interleaved evolutions of both products. This will, on a side-note, solve the issue you are raising. Thoughts ? -- Nicolas Pastorino Director Community - eZ Member of the Community Project Board eZ Publish Community on twitter: http://twitter.com/ezcommunity t : http://twitter.com/jeanvoye G+ : http://plus.tl/jeanvoye
Geoff Bentley	Saturday 21 May 2011 12:57:20 am " " Has the naming convention been designed to confuse new users? It bears no relation to the eZ Publish documentation, or the Enterprise version. How on earth is someone supposed to know which documentation they should be reading? " Hi Geoff, good point. We (the Community Project Board) are planning on providing a correspondance map between the Enterprise Edition version and the Community Project version. The primary purpose of this is to show the parallel yet interleaved evolutions of both products. This will, on a side-note, solve the issue you are raising. Thoughts ? " If the Community Project is not going to keep its own documentation, and use eZ Systems docs as the canonical, then how will the documentation be accurate as the Community Project releases at a faster rate of knots than the Enterprise? While the mapping will certainly provide clarity, it's an unfortunate obstacle to understanding & developing with eZ Publish. I like the simplicity of the date convention - having a shared convention as a base, say "4.5E" and "4.5C_2011.5" would be fugly, but would negate any need for such a map? Thoughts?
Virgil Ciobanu	Tuesday 24 May 2011 11:07:11 pm Is there any tag or branch on github that point to the 2011.5 release? (Could not find any, seems that last branch connected with release is stable/4.4). visit: http://www.websoftix.com
Ole Marius Smestad	Wednesday 27 July 2011 2:24:00 am " " " If the Community Project is not going to keep its own documentation, and use eZ Systems docs as the canonical, then how will the documentation be accurate as the Community Project releases at a faster rate of knots than the Enterprise? " " While the mapping will certainly provide clarity, it's an unfortunate obstacle to understanding & developing with eZ Publish. I like the simplicity of the date convention - having a shared convention as a base, say "4.5E" and "4.5C_2011.5" would be fugly, but would negate any need for such a map? Thoughts? " Hi Geoff, I don't think the versioning scheme is likely to change. However we are looking at ways to improve the documentation through means of being able to tag articles with their relevant releases. This means that articles which apply for both the enterprise and community release, will be marked as such, whereas documentation on new features only applicable to the community version, would then be labelled accordingly. This way it is possible to use the large body of existing documentation, which is valid for both, and we don't need to duplicate these resources. At the same time it allows for granular differences as needed. Best regards, Ole M. -- Ole Marius Smestad Lead Engineer eZ Publish Member of the Community Project Board

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