diff --git a/en/releases/6.2R/Makefile b/en/releases/6.2R/Makefile new file mode 100644 index 0000000000..bf01f59e7c --- /dev/null +++ b/en/releases/6.2R/Makefile @@ -0,0 +1,51 @@ +# $FreeBSD$ + +.if exists(../Makefile.conf) +.include "../Makefile.conf" +.endif +.if exists(../Makefile.inc) +.include "../Makefile.inc" +.endif + +DOCS= todo.sgml schedule.sgml approvals.sgml +# DOCS+= announce.sgml +# DOCS+= relnotes.sgml +# DOCS+= hardware.sgml +# DOCS+= installation.sgml + +# DATA+= errata.html +# DATA+= hardware-alpha.html +# DATA+= hardware-amd64.html +# DATA+= hardware-ia64.html +# DATA+= hardware-i386.html +# DATA+= hardware-pc98.html +# DATA+= hardware-sparc64.html +# DATA+= installation-alpha.html +# DATA+= installation-amd64.html +# DATA+= installation-ia64.html +# DATA+= installation-i386.html +# DATA+= installation-pc98.html +# DATA+= installation-sparc64.html +# DATA+= readme.html +# DATA+= relnotes-alpha.html +# DATA+= relnotes-amd64.html +# DATA+= relnotes-ia64.html +# DATA+= relnotes-i386.html +# DATA+= relnotes-pc98.html +# DATA+= relnotes-sparc64.html + +FETCHFILE= http://people.freebsd.org/~pho/stress/log/news.rdf +FETCHCMD= /usr/bin/fetch +CLEANFILES+= news.rdf stress.html + +DATA+= docbook.css + +news.rdf: + ${FETCHCMD} ${FETCHFILE} + +stress.html: news.rdf stress.xsl + ${XSLTPROC} stress.xsl news.rdf > stress.html + +todo.html: stress.html + +.include "${WEB_PREFIX}/share/mk/web.site.mk" diff --git a/en/releases/6.2R/approvals.sgml b/en/releases/6.2R/approvals.sgml new file mode 100644 index 0000000000..4208e01c23 --- /dev/null +++ b/en/releases/6.2R/approvals.sgml @@ -0,0 +1,60 @@ + + + + + + + +]> + + + + +&header; + +
The release engineering team utilizes a code freeze to maintain + stability in the period immediately preceding a release. The + developers below have been given explicit approval by re@ to + continue conservative work in a narrowly defined area until the + expiration dates below. All other developers are required to get + approval for each individual change from re@ before committing to + the release branch.
+ +General discussions about the release engineering process or + quality assurance issues should be sent to the public freebsd-qa mailing list. + MFC + requests should be sent to re@FreeBSD.org.
+ +Committer | +Area | +Expiration | +
---|