Commit | Line | Data |
---|---|---|
49ebb1a0 GW |
1 | From owner-freebsd-hackers@freefall.cdrom.com Mon Jan 3 02:23:44 1994 |
2 | Status: RO | |
3 | X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] | |
4 | [nil nil nil nil nil nil nil "\"Jordan K. Hubbard\"" "jkh@whisker.lotus.ie" nil nil "1.1 milestone dates and details." "^From:" nil nil nil]) | |
5 | Received: from freefall.cdrom.com by uvm-gen.emba.uvm.edu with SMTP id AA09741 | |
6 | (5.65/1.08); Mon, 3 Jan 94 02:23:43 -0500 | |
7 | Received: from localhost by freefall.cdrom.com (8.3/KAOS-1) | |
8 | id XAA00705; Sun, 2 Jan 1994 23:15:02 -0800 | |
9 | Received: from whisker.lotus.ie by freefall.cdrom.com (8.3/KAOS-1) | |
10 | id XAA00695; Sun, 2 Jan 1994 23:14:50 -0800 | |
11 | Received: from localhost (jkh@localhost) by whisker.lotus.ie (8.6.4/8.6.3) id BAA02386; Mon, 3 Jan 1994 01:45:00 -0800 | |
12 | Message-Id: <199401030945.BAA02386@whisker.lotus.ie> | |
13 | Precedence: bulk | |
14 | From: "Jordan K. Hubbard" <jkh@whisker.lotus.ie> | |
15 | Sender: freebsd-hackers-owner@freefall.cdrom.com | |
16 | To: freebsd-hackers@freefall.cdrom.com | |
17 | Cc: freebsd-admin@freefall.cdrom.com | |
18 | Subject: 1.1 milestone dates and details. | |
19 | Date: Mon, 3 Jan 1994 01:45:00 -0800 | |
20 | ||
21 | Ok, so we're getting closer on putting this all together, and I think | |
22 | that's great. | |
23 | ||
24 | However, I'd like to note that we're already pretty tight on time if we're | |
25 | going to make the March 1st release date (and I believe we should), given | |
26 | some of the many intermediate milestones that we need to hit. | |
27 | ||
28 | Assuming March 1st, the hard part is to now set down some of these more | |
29 | critical intervening dates and do whatever we need to do to ensure | |
30 | that we DO hit them. If we fall down on our BETA test (I think ALPHA is | |
31 | almost out of the question given the time we have), we won't have any hope | |
32 | of making the 1 March target. | |
33 | ||
34 | I'll take this opportunity to fire off a set of hypothetical dates which | |
35 | we can then wrangle over and hopefully ratify. | |
36 | ||
37 | Additionally, it's now a good time to start listing the desired features | |
38 | and make some realistic time estimates for each one to be completed. | |
39 | Please add your items to this list and then we can add 'em up and | |
40 | see which ones for which we have a chance of doing in time, and for which | |
41 | we don't have a hope in hell. | |
42 | ||
43 | ||
44 | --------------------------- cut cut cut cut cut ----------------------------- | |
45 | ||
46 | MILESTONE LIST | |
47 | ||
48 | ||
49 | Date What | |
50 | ----------- ------------------------------------------------------ | |
51 | 30 Jan 1994 FEATURE FREEZE. No additional features added. | |
52 | 05 Feb 1994 Ship BETA set to small test group. | |
53 | 15 Feb 1994 End BETA - initiate CODE FREEZE; critical fixes only | |
54 | 20 Feb 1994 Ship Pre-release to test group for burn-in testing. | |
55 | 25 Feb 1994 Release frozen - begin packaging. | |
56 | 01 Mar 1994 1.1 FCS | |
57 | ||
58 | ||
59 | ||
60 | PLANNED FEATURES AND BUG FIXES LIST | |
61 | ||
62 | Feature/Fix Est Completion Date Who Detail | |
63 | ------------------------------------------------------------------------------ | |
64 | C++ shared lib/debugging support 10 Jan 1994 JKH [1] | |
65 | Shared libraries 05 Jan 1994 JKH | |
66 | /usr/ports cleanup 25 Jan 1994 ALL [2] | |
67 | Integration of `nvi' from K. Bostic 28 Jan 1994 JKH [3] | |
68 | texinfo added to std distribution 15 Jan 1994 JKH [4] | |
69 | ||
70 | .. (add your own entries here) .. | |
71 | ||
72 | ||
73 | ||
74 | Detail | |
75 | ------ | |
76 | ||
77 | [1] Shared C++ libs require /usr/lib/crt1.so target installed, and selective | |
78 | dependency on same. Shared libg++ requires merging with shared curses | |
79 | library for now (may be different ways of doing this, investigating). | |
80 | ||
81 | [2] ports collection requires thinning, rational makefiles, and other changes | |
82 | required to bring into line with /usr/ports/CHECKLIST document. Everyone | |
83 | _must_ pitch in on this or ports will remain in disarray! | |
84 | ||
85 | [3] Keith Bostic's nvi is nearing first release date. If stable, will | |
86 | replace elvis. | |
87 | ||
88 | [4] Several ports require makeinfo, info is already on its way to becoming | |
89 | documentation format of choice (options.texi being one example), and | |
90 | having a default info reader in /usr/bin/info would be a very nice | |
91 | enabling technology for doing more online docs in info format. | |
92 | ||
93 | .. (add your own entries here) .. | |
94 | ||
95 | ------------------------------ cut cut cut cut ------------------------- | |
96 | ||
97 | ||
98 | "Enforcement": | |
99 | ||
100 | Once we've ratified it, we should check a copy of this file into | |
101 | /usr/src somewhere so that it will be more publically accessible | |
102 | during the development cycle. If you put something on this list, | |
103 | expect periodic mail saying "how's it going? Ahem." as your due-date | |
104 | draws near. If you _don't_ put something you want on the list, | |
105 | then you should both not expect to see it in, and you should expect | |
106 | massive hate-mail (and its possible removal) if you come trundling | |
107 | along and suddenly commit it without warning. | |
108 | ||
109 | Does all this sound reasonable to everyone? | |
110 | ||
111 | Jordan | |
112 |