Date: Mon, 26 Jan 2004 13:11:51 -0800 From: "Bruce A. Mah" <bmah@freebsd.org> To: current@freebsd.org, sagejona@theatre.msu.edu Subject: Re: RFC: Weekly status update 17/01/04-23/01/04 (cvs-src summary) Message-ID: <20040126211151.GB2411@intruder.kitchenlab.org> In-Reply-To: <20040124070846.GA595@omoikane.mb.skyweb.ca> References: <20040124070846.GA595@omoikane.mb.skyweb.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
--XOIedfhf+7KOe/yw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline If memory serves me right, Mark Johnston wrote: > Last week's thread about status reports spurred me to come up with this > in a few idle hours. I've gone through the cvs-src mail from last week > and summarized what looked like the most important commits, along with > some of the longer threads that cropped up. Cool! This seems very much like the process that I use for updating the release notes...the end product is of course different, and has a different audience. If you happen to run across anything you think should be in the release notes, but aren't, please let me know. Whether or not there's demand for a writeup such as this, you've got to agree that there's no better way to learn what's going on in the project, than by having to explain it back to the project. :-) Cheers, Bruce. PS. Someone (des@, I think?) suggested that a team of people working on this would be effective to prevent burn-out...let me echo this comment. (At least with the release notes, if I drop the ball for a couple weeks, I can catch up by the next release.) --XOIedfhf+7KOe/yw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFAFYKX2MoxcVugUsMRAsO7AKDJH9xIpKGddOgpjy5ElLKRGtP9ZgCffUkr wp7uERxaYejX6IkiDyMLBeM= =2PX3 -----END PGP SIGNATURE----- --XOIedfhf+7KOe/yw--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040126211151.GB2411>