Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!mips!smsc.sony.com!dce From: dce@smsc.sony.com (David Elliott) Newsgroups: comp.windows.x Subject: How long a release takes (Re: xlock patch for R4.) Message-ID: <1989Dec20.041406.26272@smsc.sony.com> Date: 20 Dec 89 04:14:06 GMT References: <129433@sun.Eng.Sun.COM> Reply-To: dce@Sony.COM (David Elliott) Organization: Sony Microsystems Corp. Lines: 29 In article hogan@csl.sri.com (Emmett Hogan) writes: > >>>>>> On 19 Dec 89 20:43:18 GMT, naughton@wind.Sun.COM (Patrick Naughton) said: > >Patrick> When you receive X11R4 (this decadeish) xlock will not work. > >Is it just me or does this sound ridiculous ? Patches for unreleased >software, why not just fix it before it is released ? It's just you. Typically, a commercial release of a size close to what X11R4 is would require a functionality freeze around 10 weeks before shipment. 4-6 weeks later would be the final freeze for shipment, after which final tapes are made and the QA group would do a final set of tests. X11R4 is supposed to be released this year, which means in the next two weeks. If the folks finishing up the release put in every fix they get over the last few weeks, they won't be able to even see if the things compile, let alone take a few days off for the holiday season. I think it's fairly reasonable of Patrick to expect that his patches might not make it into the final release, given how recently this problem was found. -- David Elliott dce@smsc.sony.com | ...!{uunet,mips}!sonyusa!dce | (408)944-4073 "As I never read this newsgroup or my email, please send replies via carrier pigeon."