From owner-freebsd-www Mon Mar 24 7:10:26 2003 Delivered-To: freebsd-www@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ED79637B405 for ; Mon, 24 Mar 2003 07:10:16 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D4C943F93 for ; Mon, 24 Mar 2003 07:10:15 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.6/8.12.6) with ESMTP id h2OFAFNS015621 for ; Mon, 24 Mar 2003 07:10:15 -0800 (PST) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.6/8.12.6/Submit) id h2OFAFIK015620; Mon, 24 Mar 2003 07:10:15 -0800 (PST) Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3827837B404 for ; Mon, 24 Mar 2003 07:06:12 -0800 (PST) Received: from freebsd.org.ru (sweet.etrust.ru [194.84.67.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88AAB43FDD for ; Mon, 24 Mar 2003 07:06:10 -0800 (PST) (envelope-from osa@freebsd.org.ru) Received: by freebsd.org.ru (Postfix, from userid 1000) id 203051CF; Mon, 24 Mar 2003 18:06:08 +0300 (MSK) Message-Id: <20030324150608.203051CF@freebsd.org.ru> Date: Mon, 24 Mar 2003 18:06:08 +0300 (MSK) From: "Sergey A.Osokin" Reply-To: "Sergey A.Osokin" To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Subject: www/50247: [PATCH] www/en/releases/4.6R/schedule.sgml: cosmetic fix X-Spam-Status: No, hits=-13.6 required=5.0 tests=AWL,HTML_10_20,HTML_MESSAGE,PATCH_UNIFIED_DIFF,RESENT_TO autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) Sender: owner-freebsd-www@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 50247 >Category: www >Synopsis: [PATCH] www/en/releases/4.6R/schedule.sgml: cosmetic fix >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-www >State: open >Quarter: >Keywords: >Date-Required: >Class: update >Submitter-Id: current-users >Arrival-Date: Mon Mar 24 07:10:14 PST 2003 >Closed-Date: >Last-Modified: >Originator: Sergey A. Osokin >Release: FreeBSD 4.8-RC i386 >Organization: n/a >Environment: System: FreeBSD 4.8-RC i386 >Description: www/en/releases/4.6R/schedule.sgml: cosmetic fix >How-To-Repeat: just look at http://www.freebsd.org/releases/4.6R/schedule.sgml >Fix: Index: www/en/releases/4.6R/schedule.sgml =================================================================== RCS file: /home/ncvs/www/en/releases/4.6R/schedule.sgml,v retrieving revision 1.18 diff -u -r1.18 schedule.sgml --- www/en/releases/4.6R/schedule.sgml 17 Jun 2002 21:26:08 -0000 1.18 +++ www/en/releases/4.6R/schedule.sgml 24 Mar 2003 15:03:59 -0000 @@ -18,7 +18,7 @@

General discussions about the release engineering process or quality assurance issues should be sent to the public freebsd-qa mailing list. + href="mailto:FreeBSD-qa@FreeBSD.org">FreeBSD-qa mailing list. MFC requests should be sent to Schedule - - - + + + + + + + + + - + + + - + should be sent to the developers@, stable@ + and qa@ lists. @@ -87,8 +95,8 @@ + freebsd-ports@ and BCC: developers@ to set a date + for the week long ports freeze and tagging of the ports tree. @@ -108,26 +116,25 @@ - + + stable@FreeBSD.org after the snapshot is uploaded. - @@ -139,7 +146,7 @@ + experience with RC1. @@ -164,8 +171,8 @@ - + @@ -177,7 +184,7 @@ popular packages appearing on the first disc. - + @@ -188,7 +195,7 @@ + available from ftp.FreeBSD.org and the mirrors. @@ -202,11 +209,11 @@ - + @@ -214,8 +221,8 @@ + href="&base;/doc/en_US.ISO8859-1/articles/releng/article.html#versionbump">here + are updated to reflect the fact that this is FreeBSD 4.6. @@ -223,13 +230,13 @@ + for the man->web gateway. Also make sure these man pages are + pointed to by docs.sgml. - - + + @@ -246,8 +253,8 @@ + href="mailto:hubs@FreeBSD.org">hubs@FreeBSD.org to give admins + time to prepare for the load spike to come. @@ -262,7 +269,7 @@ + received the bits. @@ -270,8 +277,8 @@ + out, and commits to RELENG_4 no longer require approval. Also + note the policy for commits to the RELENG_4_6 branch. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-www" in the body of the message
ActionExpectedActualDescription
Reminder announcement01 Apr 200209 Apr 2002ActionExpectedActualDescription
Reminder announcement01 Apr 200209 Apr 2002 Release Engineers send announcement email to - developers@FreeBSD.org with a rough schedule for the FreeBSD 4.6 + developers@FreeBSD.org with a rough schedule for the FreeBSD 4.6 release.
4.6-PRERELEASE Testing Guide publishedOngoing--4.6-PRERELEASE Testing Guide publishedOngoing-- A testing guide should be published with information about recent changes and areas of the system that should be thoroughly tested during the @@ -58,13 +66,13 @@ Code freeze begins 01 May 2002 01 May 2002After this date, all commits to the RELENG_4 branch must be approved by re@FreeBSD.org. Certain highly active documentation committers are exempt from this rule for routine man page / release note updates. Heads-up emails - should be sent to the developers@, stable@, and qa@ lists.
15 May 2002 19 May 2002 Someone from portmgr should email - freebsd-ports@ and BCC: developers@ to set a date - for the week long ports freeze and tagging of the ports tree.
The first release candidate for the x86 and Alpha architecture is released. ISO images should be uploaded to ftp-master.freebsd.org and - releng4.freebsd.org. A network install directory should - be uploaded to ftp-master.freebsd.org. The - packages and XF86336 directories may be - symlinked to save space, as long as you're sure to use - relative symlinks. + releng4.freebsd.org. A network install directory should + be uploaded to ftp-master.freebsd.org. The + packages/ and XF86336/ directories may be + symlinked to save space, as long as you're sure to use + relative symlinks.
Heads up to -stableHeads up to -stable 17 May 2002 17 May 2002 A message should be sent to qa@FreeBSD.org and - stable@FreeBSD.org after the snapshot is uploaded.
Package split posted 17 May 2002 --The proposed package split (which packages go on which disc of the 4 CD set) should be posted to qa@FreeBSD.org, ports@FreeBSD.org, and stable@FreeBSD.org.?? May 2002 18 May 2002 Note: the release date of this candidate depends on the user - experience with RC1.
Final package build starts 25 May 2002 --The ports cluster and bento - build final packages.The ports cluster and bento + build final packages.
doc tree tagged.doc/ tree tagged. 27 May 2002 27 May 2002 RELEASE_4_6_0 tag for docs.3 June 2002 6 June 2002 4.6 RC4 for the x86 and Alpha architectures will be made - available from ftp.FreeBSD.org and the mirrors.
Note to freebsd-stable@ 5 June 2002 6 June 2002A note should be sent to the freebsd-stable to let - over-anxious users know that the tags have been created but the - release still isn't ready. Tags may be slid before the - announcement goes out. Point users to freebsd-qa@ for - details.A note should be sent to the freebsd-stable@ to let + over-anxious users know that the tags have been created but the + release still isn't ready. Tags may be slid before the + announcement goes out. Point users to freebsd-qa@ for + details.
5 June 2002 8 June 2002 The files listed here - are updated to reflect the fact that this is FreeBSD 4.6.
6 June 2002 3 June 2002 Make sure the 4.6 manual pages are being displayed by default - for the man->web gateway. Also make sure these man pages are - pointed to by docs.sgml.
src tree tagged.10 June 2002src tree tagged.10 June 2002 10 June 2002 RELENG_4_6_0_RELEASE tag for src.
10 June 2002 11 June 2002 Heads up email to hubs@FreeBSD.org to give admins - time to prepare for the load spike to come.
10 Jun 2002 15 June 2002 Announcement sent out after a majority of the mirrors have - received the bits.
10 June 2002 16 June Announcement to developers@ explaining that the release is - out, and commits to RELENG_4 no longer require approval. Also - note the policy for commits to the RELENG_4_6 branch.