Communty version bugs

Next topic

Author	Message
Brendan Pike	Saturday 02 July 2011 6:05:26 pm I'm wondering if there should be an alternative method of flagging bugs for the community versions of eZ Publish. Today I came up against a bug that has existed since 2011.5 but doesn't appear to effect 4.5. http://issues.ez.no/IssueView.php?Id=18373While not a direct security issue I was surprised it had gone unfixed since it essentially disables an administrators ability to restrict create permissions in the admin2 interface.It seems as the community version matures it could benefit from having an additional method of flagging and self-supporting more autonomously since there will be bugs that are in production on community sites that do not yet effect non-community edition sites.To me this also underlines the importance that the community version gets its own git version where fixes can be created and fed back to the community quickly without the need for a full repacked release.I'd be interested to know if the community project board has considered these surrounding issues and what is in the pipe-line. www.dbinformatics.com.au We are always interested in hearing from experienced eZ PHP programmers and eZ template designers interested in contract work.
Robin Muilwijk	Sunday 03 July 2011 1:33:57 am Hi Brendan, have you seen our release policy which was recently published? (http://share.ez.no/community-project/release-policy). With this we actually keep the enterprise and community edition strongly linked, to enable innovation but also migrate-ability between the two versions. So far we re-introduced monthly releases, and are working on introducing nightly builds. We have not discussed patches though. I've brought this topic to the attention of the other board members, and I'm sure we'll discuss this topic, patches. Kind 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

Author

Message

Saturday 02 July 2011 6:05:26 pm

I'm wondering if there should be an alternative method of flagging bugs for the community versions of eZ Publish. Today I came up against a bug that has existed since 2011.5 but doesn't appear to effect 4.5. http://issues.ez.no/IssueView.php?Id=18373While not a direct security issue I was surprised it had gone unfixed since it essentially disables an administrators ability to restrict create permissions in the admin2 interface.It seems as the community version matures it could benefit from having an additional method of flagging and self-supporting more autonomously since there will be bugs that are in production on community sites that do not yet effect non-community edition sites.To me this also underlines the importance that the community version gets its own git version where fixes can be created and fed back to the community quickly without the need for a full repacked release.I'd be interested to know if the community project board has considered these surrounding issues and what is in the pipe-line.

www.dbinformatics.com.au

We are always interested in hearing from experienced eZ PHP programmers and eZ template designers interested in contract work.

Robin Muilwijk

Sunday 03 July 2011 1:33:57 am

Hi Brendan,

have you seen our release policy which was recently published? (http://share.ez.no/community-project/release-policy). With this we actually keep the enterprise and community edition strongly linked, to enable innovation but also migrate-ability between the two versions.

So far we re-introduced monthly releases, and are working on introducing nightly builds. We have not discussed patches though. I've brought this topic to the attention of the other board members, and I'm sure we'll discuss this topic, patches.

Kind 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