"Curtis L. Olson" <[EMAIL PROTECTED]> wrote: > I'm going to push forward with some "pre" releases. I very much > appreciate the documentation issues. Perhaps in a week or two or > three if we are ready for an official release and the documentation > isn't quite there, we could go ahead anyway, and then do a 0.9.3b > release with updated documentation ... (?)
That's o.k. for me. I'll spend some time on the manual during vacation next week - as long as my 'cohabitee' doesn't hurt me :-) > Part of the problem from a release manager point of view is that if we > wait for every loose end to be tidied up, [...] The problem with writing documentation is _not_ the necessity to have all ends fixed but to know about their current state. I usually spend many hours to figure out how some feature is _supposed_ to work and how it really works on different platforms. Not until I know what's the case I can document this feature. In many cases this involves questions to the developers on the list (and dozends of rebuilds), for example when features behave different on different platforms and/or with different settings. Curt, I don't want to shoot at you, I just want to make clear that it's nearly impossible to document a moving targed at a level that I expect documentation to be written. Probably Michael did a better job at this because he found a pragmatic way between quality and measure of the written manual, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -------------------------------------------------------------------------- _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
