This site has been archived and you can no longer log in or post new messages. For up-to-date community resources please visit ezplatform.com

eZ Community » Forums » Discussions » eZ Publish Community Project 2011.5...
expandshrink

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

» Read full blog post

Introduction

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

Wednesday 18 May 2011 8:44:11 pm

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

Thursday 19 May 2011 12:51:18 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?

Thursday 19 May 2011 11: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 ?

Saturday 21 May 2011 9: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?

Wednesday 25 May 2011 8:07:11 am

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).

Wednesday 27 July 2011 11: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.

expandshrink

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

36 542 Users on board!

Forums menu

Proudly Developed with from