Monday 07 November 2011 10:28:42 pm - 4 replies
Introduction
On http://pubsvn.ez.no, developers can find automatically-generated documentation of the php-level API for the current version of eZ Publish - and for many historic versions too.
With the exponential growth of versions due to the monthly release schedule, it's time to think again at what documentation to build and how. Read on for a proposal...
Monday 23 January 2012 6:49:17 am
Hello Gaetano, eZ Community Board and eZ Community!
@Gaetano
Thank you for your detailed blog post here in the share.ez.no blogs!
I post today in responce to your request in http://issues.ez.no/18884
to continue my comments here in this blog post as well.
It's been a few months now since I posted the above issue originally and since your replies in the issue and here in this blog post. It seems that http://pubsvn.ez.no still does not make mention to 4.5 or 4.6 (yes, trunk (aka master) but not 4.5 specifically) 
So I ask: What kind of realistic time line is in the works for improvements requested here in this issue ticket to even begin to land in pubsvn?
I only ask as a reminder that these resources make an impact in regular users compared to the exchange of the time required to provide them.
Also it continues to frustrate that the class 'eZPublishSDK' is not generated for all versions of the provided documentation on pubsvn.
Thank you for your continued support!
Respectfully,
Heath
Tuesday 24 January 2012 2:39:07 pm
As promised, the http://pubsvn.ez.no page has been updated.
Changes:
- updated the version of all the tools used in generating documentation (docblox, doxygen, phpdoc)
- for all versions except trunk, documentation is generated from the latest stable release, not from the branch head in github
- added documentation for eZP versions 4.5 and 4.6
- all php files from the eZP sources are now documented (a few were missing previously)
- added a page listing version history of eZP: http://pubsvn.ez.no/ezpublish_version_history/index.php
I hope these will benefit everybody in the community. Happy coding!
You must be logged in to post messages in this topic!