Re: api docs for unreleased packages
| From: | Martin Jansen | Date: | Wed, 27 Apr 2005 14:57:11 +0000 |
| Subject: | Re: api docs for unreleased packages | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-37430@lists.php.net to get a copy of this message | ||
On Wed Apr 27, 2005 at 09:5422AM -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.
> >
> >Because the API docs are generated on each release.
>
> Why can't they be generated by cron from the CVS repository?
Because we'd then need to keep track of usernames and passwords to
check out from these repositories, make sure that we generate docs
from the right branch, support Subversion and CVS, etc etc.
It's not that there are not enough resources for doing this (even if
Helgi thinks so), but it's more a logistical problem, and in my book
we don't get enough in return by shouldering this.
- Martin