Date: Mon, 30 May 2005 00:27:50 +0900 (JST) From: Hiroki Sato <hrs@FreeBSD.org> To: bmah@FreeBSD.org Cc: cvs-all@FreeBSD.org, PeterJeremy@optushome.com.au, doc-committers@FreeBSD.org, cvs-doc@FreeBSD.org, simon@FreeBSD.org Subject: Re: cvs commit: www/en/releases/5.4R errata.html Message-ID: <20050530.002750.74719916.hrs@allbsd.org> In-Reply-To: <1117298991.46625.33.camel@tomcat.kitchenlab.org> References: <1117258487.764.14.camel@localhost> <20050528082910.GH787@zaphod.nitro.dk> <1117298991.46625.33.camel@tomcat.kitchenlab.org>
next in thread | previous in thread | raw e-mail | index | archive | help
----Security_Multipart(Mon_May_30_00_27_50_2005_142)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, sorry for my being inactive recently. I was very busy this month but I finally have the time... "Bruce A. Mah" <bmah@freebsd.org> wrote in <1117298991.46625.33.camel@tomcat.kitchenlab.org>: bm> OK. How about something like the following paragraph and table (pretend bm> there is some real DocBook markup in here and don't worry too much about bm> the wording): I like this idea. bm> A related point: The errata document for (for example) 5.3 was bm> maintained on the RELENG_5 branch (and not RELENG_5_3). So right before bm> we branched for 5.4, the 5.3 errata content was purged. Thus, users bm> tracking the 5.3 security fix branch can't count on the errata document bm> being current anymore; they have to go to RELENG_5_3 src/UPDATING to get bm> this information. (It's worked this way all the way back to bm> 4.3-RELEASE. Curiously, nobody has complained to me about it in the bm> past four years. I can't remember why I set it up this way.) Hmm, for this problem I am thinking about using XML databases for errata document. Probably we can agree that we should maintain errata document for a release until its EoL, and duplicated effort should be reduced. For security advisories, VuXML or similar one can be used to put information into the errata page, and by using XSLT, we can easily handle MD/MI separation and output style change. With these databases the errata page can be generated on-the-fly and trimming old items is not always needed. The current structure limits reuse of information, so some sort of improvements are needed. I made several specific implementations and am still wondering where we should put such databases. Anyway, I am planning to change these framework before 6.0R (I will submit the necessary changes to the public mailing-lists for review, of course). -- | Hiroki SATO ----Security_Multipart(Mon_May_30_00_27_50_2005_142)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBCmd94TyzT2CeTzy0RAi9NAJ9gXLNDsq7OoOi6GyPlvH+wXIutbwCfZooX VeSpJYnHHznErVlg1Y0H2l8= =tKnN -----END PGP SIGNATURE----- ----Security_Multipart(Mon_May_30_00_27_50_2005_142)----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050530.002750.74719916.hrs>