|
Lines 56-62
Link Here
|
| 56 |
3.<replaceable>X</replaceable> series. Work on 3-CURRENT trudged along |
56 |
3.<replaceable>X</replaceable> series. Work on 3-CURRENT trudged along |
| 57 |
seemingly forever, and finally a cry was made to <quote>just ship it</quote> and |
57 |
seemingly forever, and finally a cry was made to <quote>just ship it</quote> and |
| 58 |
clean up later. This decision resulted in the 3.0 and 3.1 releases |
58 |
clean up later. This decision resulted in the 3.0 and 3.1 releases |
| 59 |
being very unsatisfying for most, and it wasn't until 3.2 that the |
59 |
being very unsatisfying for most, and it was not until 3.2 that the |
| 60 |
series was considered <quote>stable</quote>. To make matters worse, the &t.releng.3; |
60 |
series was considered <quote>stable</quote>. To make matters worse, the &t.releng.3; |
| 61 |
branch was created along with the 3.0 release, and the &t.releng.head; branch was |
61 |
branch was created along with the 3.0 release, and the &t.releng.head; branch was |
| 62 |
allowed to advance immediately towards 4-CURRENT. This resulted in a |
62 |
allowed to advance immediately towards 4-CURRENT. This resulted in a |
|
Lines 64-70
Link Here
|
| 64 |
&t.releng.3; branch very difficult. &os; 2.2.8 was left for quite a while |
64 |
&t.releng.3; branch very difficult. &os; 2.2.8 was left for quite a while |
| 65 |
as the last production-quality version of &os;.</para> |
65 |
as the last production-quality version of &os;.</para> |
| 66 |
|
66 |
|
| 67 |
<para>Our intent is to avoid repeating that scenario with &os; 5.x. |
67 |
<para>Our intent is to avoid repeating that scenario with &os; 5.X. |
| 68 |
Delaying the &t.releng.5; branch until it is stable and production quality |
68 |
Delaying the &t.releng.5; branch until it is stable and production quality |
| 69 |
will ensure that it stays maintainable and provides a compelling reason |
69 |
will ensure that it stays maintainable and provides a compelling reason |
| 70 |
to upgrade from 4.<replaceable>X</replaceable>. To do this, we must |
70 |
to upgrade from 4.<replaceable>X</replaceable>. To do this, we must |
|
Lines 428-434
Link Here
|
| 428 |
|
428 |
|
| 429 |
<listitem> |
429 |
<listitem> |
| 430 |
<para>busdma interface and drivers: architectures like PAE/&i386; and |
430 |
<para>busdma interface and drivers: architectures like PAE/&i386; and |
| 431 |
sparc64 which don't have a direct mapping between host memory |
431 |
sparc64 which do not have a direct mapping between host memory |
| 432 |
address space and expansion bus address space require the |
432 |
address space and expansion bus address space require the |
| 433 |
elimination for vtophys() and friends. The busdma interface was |
433 |
elimination for vtophys() and friends. The busdma interface was |
| 434 |
created to handle exactly this problem, but many drivers do not use |
434 |
created to handle exactly this problem, but many drivers do not use |