|
Thursday 25 August 2011 2:46:22 am
Hi Paul, An overview of the build policy for eZ Publish Community Project is given here, as pointed to by Damien. It also shows how it is articulated with the Enterprise Edition. I hope this answers your initial question. Also, as stated in the latest Community Project Board minutes, we will make available a visual map, on the Download page, guiding the version choices. When it comes to upgrading between the Community Project builds, given that the timespan between builds is one month, the upgrade load is small and well documented. The idea of an automated or semi-automated upgrading tool, run every month, is good. I will bring this up in the next Community Project Board meeting. This will not replace, however, a functional tests handbook, run against the upgraded platform upon every upgrade (i know this is a commonplace, but worth mentioning). Did this thread answer your questions Paul ? Cheers,
--
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
|