From owner-freebsd-doc@FreeBSD.ORG Sat Jan 24 21:45:36 2004 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B71EE16A4CE; Sat, 24 Jan 2004 21:45:36 -0800 (PST) Received: from b.mail.sonic.net (b.mail.sonic.net [64.142.19.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6BBE243D3F; Sat, 24 Jan 2004 21:45:35 -0800 (PST) (envelope-from bmah@intruder.kitchenlab.org) Received: from intruder.kitchenlab.org (adsl-64-142-31-106.sonic.net [64.142.31.106]) by b.mail.sonic.net (8.12.10/8.12.7) with ESMTP id i0P5jYhj015566 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sat, 24 Jan 2004 21:45:35 -0800 Received: from intruder.kitchenlab.org (bmah@localhost [127.0.0.1]) i0P5jYpW074876; Sat, 24 Jan 2004 21:45:34 -0800 (PST) (envelope-from bmah@intruder.kitchenlab.org) Received: (from bmah@localhost) by intruder.kitchenlab.org (8.12.10/8.12.10/Submit) id i0P5jYrN074875; Sat, 24 Jan 2004 21:45:34 -0800 (PST) (envelope-from bmah) Date: Sat, 24 Jan 2004 21:45:34 -0800 From: "Bruce A. Mah" To: freebsd-doc@freebsd.org Message-ID: <20040125054534.GA74806@intruder.kitchenlab.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Q68bSM7Ycu6FN28Q" Content-Disposition: inline User-Agent: Mutt/1.4.1i X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-url: http://www.employees.org/~bmah/ cc: bmah@freebsd.org Subject: HEADSUP: doc/ tagging for 5.2.1-RELEASE X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jan 2004 05:45:36 -0000 --Q68bSM7Ycu6FN28Q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline As some of you might already be aware, the RE team is strongly considering cutting a 5.2.1-RELEASE to fix several specific issues in 5.2-RELEASE. Although none of these involve the doc/ subtree, we do need to lay down a RELEASE_5_2_1 tag. Because doc/ is (almost) always buildable, I would like to tag the head of the doc/ tree for the new release to pick up new work that has been committed since the last tagging. The release schedule for 5.2.1-RELEASE hasn't been completely determined yet, but it will be an extremely short release cycle, lasting about a week. I'd expect to lay down a tag for doc/ sometime about the middle of this week (about 28 January). Due to the short release cycle, we're not going to do the doc/ slush thing. I'm just going to request that people be really gentle to the doc/ tree over the next week or so. I will be updating the release notes to produce a document that can be used for 5.2.1-RELEASE. I'm going to use the same basic model that I did for the 4.6.2-RELEASE documentation, as soon as I figure out what I did before. :-) I'll give more details as I learn more. Thanks! Bruce. --Q68bSM7Ycu6FN28Q Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFAE1f+2MoxcVugUsMRAvsaAKDWxMV0t5rlydaMDhSDH+1aw2pzCACeLMSc nqBtd3PVZi+WyOhx2AzA1Ws= =fasN -----END PGP SIGNATURE----- --Q68bSM7Ycu6FN28Q--