Mikkel Krøigård <[EMAIL PROTECTED]> writes:
> Martin Geisler <[EMAIL PROTECTED]> writes:
>
>> I have now copied the documentation from the viff.dk repository to
>> the viff repository -- it is currently being built by the buildbot:
>>
>> http://buildbot.viff.dk/builders/Docs/builds/119
>>
>> and
Martin Geisler <[EMAIL PROTECTED]> writes:
> [...] the zipfiles and tarballs now look like this:
>
> viff-x.y/
> viff-x.y/doc/ <-- source files for documentation
> viff-x.y/doc/api/ <-- epydoc API documentation
> viff-x.y/doc/html/<-- Sphinx HTML files
> viff-x.y/apps/
>
> Martin Geisler <[EMAIL PROTECTED]> writes:
>
> > [...] the zipfiles and tarballs now look like this:
> >
> > viff-x.y/
> > viff-x.y/doc/ <-- source files for documentation
> > viff-x.y/doc/api/ <-- epydoc API documentation
> > viff-x.y/doc/html/<-- Sphinx HTML files
> >
Martin Geisler <[EMAIL PROTECTED]> writes:
> The Sphinx generated HTML can be viewed, and searched(!), offline, so
> I think we should include it in the releases. But where to put it and
> where to put the epydoc API docs? How should the zipfile/tarball look
> like when unpacked?
Nobody said anyt
Hi guys and girls!
I leave for a three month stay at IBM Zurich on June 1st and I think
we should do a VIFF 0.6 release before that.
Frist, if you have anything to add to the NEWS, then please do so.
Also, please send me any and all bug fixes you have lying around in
your repository clones.
Last
