Re: api docs for unreleased packages

On Wed, 2005-04-27 at 09:54 -0400, Hans Lellelid wrote: > Helgi Þormar wrote: > > On Wed, 2005-04-27 at 09:25 -0400, Hans Lellelid wrote: > > > >>Is 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. > > 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? Because our machine is struggling enough with what it has at the current, it would be too much to do such a thing. Plus even tho we got the url for a outside repos we can't only use that, we lack the usernames and passwords. This might be possible later on but I still don't see the gain in having API docs for CVS :-) If the developer really needs it he/she can just generate it since he/she is knowledgeable enough to check out the code ;) Anyway that's how I look at it since I rather want to spend our spare cycle into something useful :) - Helgi