On Fri, 13 Feb 2004, Willem Jan Withagen wrote: > From: "Andre Guibert de Bruet" <andy_at_siliconlandmark.com> > > > It'll sound like justifying myself but perhaps the lines on COMMON ITEMS > > > should be the same layout as about 5.x performance. So there's a bigger > > > chance that newbies (or lazies) get to see this part of the file. > > > Or split the file in 2 parts: updating.actuals and updating.common > > > > There's enough troubles trying to get people to read one file, and you > > want to introduce another? :-) > > [I did notice the smiley] > > Let's put it this way: > I've printed the file: 22 pages...... > And only after 3/4 of it, the real general stuff starts. > > I assume most people will give up long before that. > So they never get to the part that they REALLY REALLY should read. > At least I did on the first time, until Ruslan pointed me at it. > > So what about those that are new to FBSD??? I'm running it since 1.1 and > still manage to get into trouble. (Still got the CD :-) ) I'm of the opinion that UPDATING should be shortened for CURRENT. We stopped supporting 5.0-RELEASE, why are we including every change since 4.x? What there should be is an UPGRADING file for users that are running anything other than what's current (5.2-CURRENT as it currently stands) and an UPDATING file for users that don't need the two tons of steps and FYIs. For HEAD, for example, UPDATING would only include the changes since the last release (Currently 5.2-RELEASE, soon 5.2.1). Then again, I'm a nobody and a few bits of wisdom from Warner Losh, which I've CC'ed, could probably help on the matter. :) Regards, Andy > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/ >Received on Fri Feb 13 2004 - 01:24:09 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:42 UTC