Re: [Flightgear-devel] release warning
Curtis L. Olson schrieb: Carsten Höfer writes: On Mit, 2003-10-15 at 21:44, Curtis L. Olson wrote: As time permits, I might start fiddling around with pre-release work for the next major release, but I'll hold off of an official release for at least a week or two probably. Regards, Curt. Hi, for the new release I've packed the current FlightGear Tutorial. You will find pdf and sources at http://www.carsten-hoefer.privat.t-online.de As always: Comments and help appreciated!!;-) I do not know who is responsible for the doc cvs tree, but can this person replace the existing files with the new ones?? Thank you and enjoy it;-) I have also added this to the documentation - tutorials section of the flightgear web site. Thanks! Curt. Fine, thanks!! ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] release warning
On Mit, 2003-10-15 at 21:44, Curtis L. Olson wrote: As time permits, I might start fiddling around with pre-release work for the next major release, but I'll hold off of an official release for at least a week or two probably. Regards, Curt. Hi, for the new release I've packed the current FlightGear Tutorial. You will find pdf and sources at http://www.carsten-hoefer.privat.t-online.de As always: Comments and help appreciated!!;-) I do not know who is responsible for the doc cvs tree, but can this person replace the existing files with the new ones?? Thank you and enjoy it;-) Carsten ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] release warning
Carsten Höfer writes: On Mit, 2003-10-15 at 21:44, Curtis L. Olson wrote: As time permits, I might start fiddling around with pre-release work for the next major release, but I'll hold off of an official release for at least a week or two probably. Regards, Curt. Hi, for the new release I've packed the current FlightGear Tutorial. You will find pdf and sources at http://www.carsten-hoefer.privat.t-online.de As always: Comments and help appreciated!!;-) I do not know who is responsible for the doc cvs tree, but can this person replace the existing files with the new ones?? Thank you and enjoy it;-) I have also added this to the documentation - tutorials section of the flightgear web site. Thanks! Curt. -- Curtis Olson HumanFIRST Program FlightGear Project Twin Citiescurt 'at' me.umn.edu curt 'at' flightgear.org Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] release warning
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
[Flightgear-devel] release warning
As time permits, I might start fiddling around with pre-release work for the next major release, but I'll hold off of an official release for at least a week or two probably. Regards, Curt. -- Curtis Olson HumanFIRST Program FlightGear Project Twin Citiescurt 'at' me.umn.edu curt 'at' flightgear.org Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] release warning
Curtis L. Olson [EMAIL PROTECTED] wrote: As time permits, I might start fiddling around with pre-release work for the next major release, but I'll hold off of an official release for at least a week or two probably. I'd consider two weeks not to be enough for a release. There are so many details in FlightGear that it's a very time consuming job to figure out how they _should_ work. Things change that fast that they need to settle a bit (and sometime need fixes) before they can find their way into the manual (BTW, I'm on vacation next week so I need some extra time ), 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
Re: [Flightgear-devel] release warning
Martin Spott writes: Curtis L. Olson [EMAIL PROTECTED] wrote: As time permits, I might start fiddling around with pre-release work for the next major release, but I'll hold off of an official release for at least a week or two probably. I'd consider two weeks not to be enough for a release. There are so many details in FlightGear that it's a very time consuming job to figure out how they _should_ work. Things change that fast that they need to settle a bit (and sometime need fixes) before they can find their way into the manual (BTW, I'm on vacation next week so I need some extra time ), 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 ... (?) Part of the problem from a release manager point of view is that if we wait for every loose end to be tidied up, we would never have a release -- not ever. My challenge is to figure out where to draw the line and balance forward motion against ticking some people off. I usually manage to make at least a few people angry, but please know that no offense is intended ... I'm just trying to balance multiple conflicting demands. I also appreciate that not every one will agree with exactly where and when I draw the line, and I guess that's the way it goes. I'm a big target out here so fire away if you must. I usually keep my asbestos gear within reach, but if you hurry you might be able to sneak in a few shots before I get fully zipped up. ;-) Also, I hope people remember that I am doing this in my spare time as a volunteer. I have a full time job and a family so my time is often very limited, and that limits what I can do and how many loose ends I can keep track of myself ... sometimes if I get a spare chunk of time, I just have to go with it because if I wait a week it might be another 2-3 weeks or more before I can get back to something I started. Regards, Curt. -- Curtis Olson HumanFIRST Program FlightGear Project Twin Citiescurt 'at' me.umn.edu curt 'at' flightgear.org Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
