lynx-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: LYNX-DEV Old question - 2-4-2 vs 2-4-FM


From: Al Gilman
Subject: Re: LYNX-DEV Old question - 2-4-2 vs 2-4-FM
Date: Thu, 24 Oct 1996 10:49:38 -0400 (EDT)

  From: Wayne Buttles <address@hidden>
  
  If the true answer is a faq, just point me in the right direction.  I have
  seen a lot of talk while searching through the archives, but I could never
  find the answer.  Which came first, lynx 2-4-2 or 2-4-FM?  I am kind of
  cloudy on when `FM' started and if other development stopped or if there
  were two versions in the works for a period of time.
  
There was a lot of concurrency.  Fote did [a lot of] the initial
VMS port.  I don't know when exactly he started using the FM
suffix but it goes back into the time period when there was
material progress still being made at UKans.  But by the time of
2.3.8, we have a Kansas version number which is a relabel of the
-FM version with essentially no local [Kansas] contribution.  So
from some version prior to 2.3.8 onward 'til 2.4.2 you have a
process where development is nominally being pursued on two
concurrent streams which rendezvous for major releases.  But the
deceleration of the Kansas-integrated thread was so marked that
it was not much of a footrace past 2.3.7 or so.  After 2.4.2
Kansas admitted that they were not going forward and 2.4-FM
became the only growth bud on the product.  Eventually Fote
realized that a lot of SysOps would never take a sample of a
daily update sequence and dropped out versions 2.5 and 2.6 for
upload to Kansas so the stable-version-minded among us would have
newer configurations.

Now he has declared himself on vacation from the
one-armed-paper-hanger routine he maintained through the period
from 2.3.? to 2.6, and we are groping our way toward a more
sustainable process model.

Al Gilman

PS: Wayne, while your question may have been frequently asked, it
wasn't usually answered.  Hopefully the wounds are by now closed
and my recap above won't salt them too badly.
;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;



reply via email to

[Prev in Thread] Current Thread [Next in Thread]