Re: api docs for unreleased packages

Martin Jansen wrote:

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.

Ok, well what if it were only supported for cvs.php.net packages (which is almost all of them, right?)? Then there's no need for usernames & passwords or supporting SVN (though in themselves these things seem rather trivial, although they would require some additional information from project managers). I think it would be quite beneficial, especially for those who want to see what an unreleased package does before deciding whether to check it out from CVS. But it sounds like I'm in the minority on this one :) -Hans