Re: documentation for the maintenance branch

2002-07-05 Thread J.Pietschmann
Christian Geisert wrote: > Please wait till after the release. Ok, most issues are solved now, I'll commit it to HEAD this weekend, not that the release is out. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For add

Re: documentation for the maintenance branch

2002-06-27 Thread Christian Geisert
Joerg Pietschmann schrieb: [..] > That's exactly what I'm currently doing, the HTML and the > intermediate document-DTD files are produced in the build > directory. Unfortunately, as I already noted, it's an > all-or-nothing thing unless you are comfortable with broken > doc builds for some time

Re: documentation for the maintenance branch

2002-06-27 Thread Christian Geisert
J.Pietschmann schrieb: [..] > The last checkin showed a "generate commit notification mail" > or something, but I didn't get one either. AFAIK your commit mail needs to be approved once. Best thing would be to ask root. > J.Pietschmann Christian -

Re: documentation for the maintenance branch

2002-06-27 Thread Peter B. West
Joerg, Joerg Pietschmann wrote: > "Peter B. West" <[EMAIL PROTECTED]> wrote: > >>Obviously there is a need for some documention with normal releases. We >>don't need the design docs in the user releases, but all of the >>operational material, including the FAQs, is necessary. >> >>If we were

Re: documentation for the maintenance branch

2002-06-27 Thread Keiron Liddle
On Thu, 2002-06-27 at 14:39, Joerg Pietschmann wrote: > +1 on omitting the design doc completely in bin distributions. > Should probably omit skin source and xsl too. +1 also. > I'm not sure about PDF, apparently there are not much requests > for this format. > What's larger: > - PDF > - xdocs +

Re: documentation for the maintenance branch

2002-06-27 Thread Joerg Pietschmann
"Peter B. West" <[EMAIL PROTECTED]> wrote: > Obviously there is a need for some documention with normal releases. We > don't need the design docs in the user releases, but all of the > operational material, including the FAQs, is necessary. > > If we were to do source and compiled releases, th

Re: documentation for the maintenance branch

2002-06-27 Thread Peter B. West
Fopdevs, Obviously there is a need for some documention with normal releases. We don't need the design docs in the user releases, but all of the operational material, including the FAQs, is necessary. If we were to do source and compiled releases, the xml-docs could go into the source releas

Re: documentation for the maintenance branch

2002-06-26 Thread J.Pietschmann
Jeremias Maerki wrote: > We're not really in a hurry, are we? I thought we are... The problem is that DTD and XSL of all documents has to be in sync, a partial commit breaks things :( > If it makes life simpler: +1. The only question arises when we're coming > to the point when we're starting wit