Re: api docs for unreleased packages

On Wed, 2005-04-27 at 16:57 +0200, 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. Last time I knew the machine almost died a couple of times because of some extra code that was damping everything down, I mean it's not he most powerful machine I've seen :-) And the fact it struggles a bit when bigger packages release, because of the api generation ... Or that was the fact last time I knew. It's also just that I rather want to keep the load down on the server it self, we have good chunk of crons we have to run as is, so if we'd get a spare machine then I'd want to move all the doc generation over to there and then it could be thought about. The tool you mentioned above, checking out of Svn Cvs and so on, it has been in planning for some time, just a lack of time that has been preventing me/the rest of the guys attached to it to start on the project :-) Those that are thinking, it would be some good stuff for the QA to do some checks and fun fun. - Helgi