Date: Tue, 12 Jun 2001 09:29:35 -0700 From: "Bruce A. Mah" <bmah@FreeBSD.ORG> To: "Antoine Beaupre (LMC)" <Antoine.Beaupre@ericsson.ca> Cc: Kenneth W Cochran <kwc@world.std.com>, freebsd-stable@FreeBSD.ORG Subject: Re: RELNOTESng problems Message-ID: <200106121629.f5CGTZF27955@bmah-freebsd-0.cisco.com> In-Reply-To: <3B2637CA.9050803@lmc.ericsson.se> References: <200106121443.KAA18844@world.std.com> <3B2637CA.9050803@lmc.ericsson.se>
next in thread | previous in thread | raw e-mail | index | archive | help
--==_Exmh_1895071772P Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit If memory serves me right, "Antoine Beaupre (LMC)" wrote: > IIRC, to build the relnotes now, you need to build a release, which is > something I haven't had the resources (drive space and man-hours) to do > since 2.2.6, which is when I discovered fbsd. :) You don't need to make a release. Please see the README file (which you quoted below). > I totally agree with Kenneth here. > > I think that we should keep the rendered .TXT files in the cvs > repository. Even if they're not exactly up to date, it's better than > having nothing at all, or needing megabytes of third-party text > processing code, just to have *text-only* release notes. How does the Web-available versions differ from putting the TXT rendering in the repository? The Web versions will (once the Web Gods make a couple of commits) get built as frequently as the Web site is. In the meantime, you can look at the version on my Web page. They're updated pretty often, on an unofficial basis. > Come on people, it can't be so hard to keep a copy of the rendered > versions in the cvs? Asami does it for /usr/ports/INDEX, iirc. And no > one complains if it's out of date. > > We just have to plaster a big WARNING in the readme saying that the > files are not necessarly up to date... Release notes that are that far out of date aren't useful. (No slam intended on asami...I don't think we need an INDEX file that tracks the ports collection as closely as we need release notes that track the source. Especially not with origin-aware ports.) > > Additionally, I "question" the necessity of requiring tools > > "outside" the base-OS solely for reading the relevant release > > notes/errata. > > > Again, I agree here. Having these release notes is a pretty good hint of > what's new or MFC'd in current or stable. I often use it to tell myself > running -current is a good thing. (joking) ;) If you depend on the release notes to know what's new, you'd want them to be up-to-date wouldn't you? > I don't want to hit on anyone's head with this, and I think that the > move to relnotesNG is a really good one, cleanly accomplished. Thanks. > I just think having the .txt files rendered is a really simple thing to > do for Global User Satisfaction (tm). I'm not opposed to the idea of making the release notes more accessible to people who can't (or don't want to) build the docproj tools. This isn't a problem. That's why we put versions on the Web (granted it could be a little better integrated, we're working on that). I just don't see the point of bloating the repository with the rendered versions. Bruce. --==_Exmh_1895071772P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: Exmh version 2.3.1+ 05/14/2001 iD8DBQE7JkNv2MoxcVugUsMRAmaWAJ48I4CV3EUW/7d4w98wd3rnVcMrWgCg3h8N vkzsbvL2PSfwMOsMxVlB+Kc= =0Rpy -----END PGP SIGNATURE----- --==_Exmh_1895071772P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200106121629.f5CGTZF27955>