On Wed, 2006-03-08 at 14:30 +0530, Rahul Sundaram wrote: > Hi > > The network section on the release notes > (http://fedoraproject.org/wiki/Docs/Beats/Networking) documents some of > the major changes between kernel revisions but these are already nicely > documented at http://wiki.kernelnewbies.org/LinuxChanges. I added this > link to the relevant section already but maybe we should not duplicate > this information within the release notes unnecessarily? It is an interesting question that dovetails into something that I was thinking about this morning: How online can we go with our release notes? How far _should_ we go? On-system documentation is very valuable, that is, manual and info pages. What role do the release notes play in on-system documentation? Can/should they be useful in a non-network situation? The release notes can give a location to list bugs fixed, bugs known, and latest information that could not make it into package documentation. Should it do that? A release notes is a snapshot in time of documentation that is about a snapshot in time of code development. It seems to me a natural place to duplicate all manner of external content that pertains to that snapshot. Package change lists, bug reports, and content pulls from various location can be automated. - Karsten -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Content Services Fedora Documentation Project http://www.redhat.com/docs http://fedoraproject.org/wiki/DocsProject
Attachment:
signature.asc
Description: This is a digitally signed message part
-- fedora-docs-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-docs-list
