🚀 go-pugleaf

In article <CPETTERB.91Nov12171546@mickey.glacier.sim.es.com> cpetterb@glacier.sim.es.com (Cary Petterborg) writes:
>I know this comes up every so often and the FSF people post:
>
>        When we have something to tell you, we'll post it.
>
>Well, all I would like to have someone tell me is:
>
>        It won't be ready before DDMMMYY.
>
>That way I will know whether to invest in a new OS or wait a while
>longer.  I don't care if it takes longer than DDMMMYY to be released,
>but a somewhat educated guess would sure help.  If someone knows
>(FSF people apparently don't read this group), please let us know.
>Oh, and by the way, "It won't be ready before 14Nov92" probably won't
>be very helpful, to anyone (unless it WILL be ready by 31Dec91  ;-).

   The reason why the FSF doesn't do this is because it invariably takes
longer than you think to complete a given project.  They don't want the
hassle of people saying "You said X or Y would be done on DDMMYY, and it's
DDMMYY and it's not done yet.  Why not?"

   The truth of the matter is that often, they just don't know.  And they're
more interested in making sure the job is done right than in meeting
arbitrary projected deadlines.  So why make them?

   The best answer to any question of the sort, "when will X be finished?"
is "In the fullness of time."  :-)