HEADS-UP: doc/ tree slushie

[Bruce A. Mah]

If memory serves me right, Ceri Davies wrote:

> Could I throw out the idea of committing the attached diff before that
> happens?  I know that we normally do this after doc/ has been tagged,
> but that has always seemed strange to me, as the documentation tagged
> as 4.9-RELEASE doesn't contain any references to it.
> 
> Of course, the downside is that the website will reflect things that
> don't exist yet.

Well, the way I usually like to do this is to tag first (with the doc/
tree in a usable state), then change certain files that have version
numbers in them, and then slide the tags on those files.  As you
correctly implied, it doesn't always work that way.  :-)

The benefit is that we reduce (OK, just slightly) the amount of time
that the doc tree displayed on the Web site reflects things that don't
exist yet.  On the other hand, I'm not opposed to trying it your way,
especially since we should be branching and going to final builds soon
anyways.  Lemme think about this a bit...my morning (.ca.us time)
caffeine hasn't taken effect yet.

> Index: en_US.ISO8859-1/articles/hubs/article.sgml
> ===================================================================
> RCS file: /home/ncvs/doc/en_US.ISO8859-1/articles/hubs/article.sgml,v
> retrieving revision 1.36
> diff -u -r1.36 article.sgml
> --- en_US.ISO8859-1/articles/hubs/article.sgml	14 Aug 2003 19:54:05 -0000	1.36
> +++ en_US.ISO8859-1/articles/hubs/article.sgml	20 Oct 2003 15:17:52 -0000
> @@ -79,7 +79,7 @@
>          complete. The CVS repository and the web pages should
>          always be mirrored completely. Also note that the
>          numbers stated here are reflecting the current
> -        state (at 4.8-RELEASE/5.1-RELEASE). Further development and
> +        state (at 4.9-RELEASE/5.1-RELEASE). Further development and
>          releases will only increase the required amount.
>          Also make sure to keep some (ca. 10-20%) extra space
>          around just to be sure.

Yeeek, what are those hard-coded version numbers doing in there?!?
Actually...are there some other related constants (i.e. amount of disk
space) that might need to be changed or otherwise track a version
number?  I haven't read the hubs article lately.

Thanks!

Bruce.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031020/c83e20fe/attachment.sig>