Re: api docs for unreleased packages
| From: | Hans Lellelid | Date: | Wed, 27 Apr 2005 13:54:22 +0000 |
| Subject: | Re: api docs for unreleased packages | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-37427@lists.php.net to get a copy of this message | ||
Helgi Þormar wrote:
On Wed, 2005-04-27 at 09:25 -0400, Hans Lellelid wrote:Why can't they be generated by cron from the CVS repository? I assume the repository info (even if not cvs.php.net) is stored in a database somewhere for each package? -HansIs there a good reason to not have API docs generated for unreleased packages? If not, is this a system that could be changed? -- I certainly think it makes sense to have different API docs for each release (or at least the most recent one), but it would also be extremely useful to have access to the API docs for CVS versions of packages. Especially pertinent for packages that don't have other end-user documentation but have usage docs in the phpdoc (which I imagine is fairly common since you guys use such a high-cost-of-entry documentation system :)Because the API docs are generated on each release.