Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 26 May 2005 21:30:32 +0200
From:      "Simon L. Nielsen" <simon@FreeBSD.org>
To:        Peter Jeremy <PeterJeremy@optushome.com.au>
Cc:        "Bruce A. Mah" <bmah@freebsd.org>, doc-committers@freebsd.org, cvs-doc@freebsd.org, cvs-all@freebsd.org
Subject:   Re: cvs commit: www/en/releases/5.4R errata.html
Message-ID:  <20050526193032.GE794@zaphod.nitro.dk>
In-Reply-To: <20050526191549.GB17267@cirb503493.alcatel.com.au>
References:  <200505261456.j4QEuh7s088699@repoman.freebsd.org> <1117119937.34783.14.camel@tomcat.kitchenlab.org> <20050526191549.GB17267@cirb503493.alcatel.com.au>

next in thread | previous in thread | raw e-mail | index | archive | help

--OZkY3AIuv2LYvjdk
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On 2005.05.27 05:15:50 +1000, Peter Jeremy wrote:
> On Thu, 2005-May-26 08:05:37 -0700, Bruce A. Mah wrote:
> >If memory serves me right, Bruce A. Mah wrote:
> >> bmah        2005-05-26 14:56:43 UTC
> >>=20
> >>   FreeBSD doc repository
> >>=20
> >>   Modified files:
> >>     en/releases/5.4R     errata.html=20
> >>   Log:
> >>   Somewhat belatedly, regen from errata/article.sgml 1.69.2.20.
> >>  =20
> >>   Revision  Changes    Path
> >>   1.2       +10 -5     www/en/releases/5.4R/errata.html
> >
> >...and my apologies to anyone who was actually expecting the Web site to
> >have the up-to-date 5.4-RELEASE errata.  My release documentation skills
> >are still a bit rusty, it seems.  :-p
>=20
> Do we need a "things to do for a security advisory or errata update"
> document similar to the "things to do during a release" document?

Yes, and actually such a document exists (or at least a draft for
one)...

The current problem, which I was/is planning to take up with the
appropriate people, is that the wording style used in the errata
document is different from the wording style used in the Security
Advisories, so it's not just a simple cut'n'paste.

I haven't really gotten around to looking into what would be a good
solution, but I'm very open to ideas.

--=20
Simon L. Nielsen
With hats: Documentation team and Security team

--OZkY3AIuv2LYvjdk
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (FreeBSD)

iD8DBQFCliPYh9pcDSc1mlERAnWbAJ9d//WcS5GiBdDvlngRxiG8cPqmzwCdGok2
dOiLfC1sSu1MJKjmsHUkh8Q=
=bHM+
-----END PGP SIGNATURE-----

--OZkY3AIuv2LYvjdk--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050526193032.GE794>