diff --git a/en/portmgr/Makefile b/en/portmgr/Makefile index da4e75270e..be98864414 100644 --- a/en/portmgr/Makefile +++ b/en/portmgr/Makefile @@ -1,4 +1,4 @@ -# $FreeBSD: www/en/portmgr/Makefile,v 1.3 2006/05/11 22:58:42 pav Exp $ +# $FreeBSD: www/en/portmgr/Makefile,v 1.4 2010/09/17 13:29:46 tabthorpe Exp $ .if exists(../Makefile.conf) .include "../Makefile.conf" @@ -13,7 +13,7 @@ DOCS+= implementation.sgml DOCS+= policies.sgml DOCS+= policies_committing.sgml DOCS+= policies_contributors.sgml -DOCS+= policies_releng_6.sgml +DOCS+= policies_eol.sgml DOCS+= qa.sgml .include "${WEB_PREFIX}/share/mk/web.site.mk" diff --git a/en/portmgr/index.sgml b/en/portmgr/index.sgml index 990933805f..56e316c9df 100644 --- a/en/portmgr/index.sgml +++ b/en/portmgr/index.sgml @@ -1,6 +1,6 @@ - + @@ -15,7 +15,7 @@
The FreeBSD Ports Management Team (also known as portmgr due to its email alias) is responsible for issues relating to the - FreeBSD Ports Collection.
+ FreeBSD Ports Collection.EOS/EOL Policies of Ports and Ports - Intrastructure on RELENG_6
+EOL Policies of Ports and Ports + Intrastructure
Support of FreeBSD releases by ports and the ports infrastructure + matches the policies + set out by the FreeBSD Security Officer. Once a major branch X + reaches its EOL date, the "last known good" ports tree will be tagged + with the RELEASE_X_EOL tag as a convenience to those + remaining users who intend to self-support their installations. + This tag is not supported in any way and security fixes will not be + applied. Usage is therefore highly discouraged and should only be + used as a last resort.
+ +For all supported major src branches, all ports will be included in + an automated quality assurance procedure which will build, install, + package, and deinstall each port on all + Tier 1 platforms. Maintainers and committers are notified of + failures detected during testing. Ports that are known not to build + or run on a given supported branch or platform will be marked as + such.
+ +Prebuilt binary packages will also be provided for all major branches + and Tier 1 platforms and will be made available via anonymous FTP + from + a worldwide set of mirror sites. Package builds will use the + oldest supported minor release within each major branch to ensure + ABI and KBI backwards compatability within each major branch, and + support all minor versions of each major branch, including + -RELEASE and -STABLE.
+ +The current package sets and estimated lifetimes of the currently + supported branches are given below. The Estimated EoL + (end-of-life) column gives the earliest date on which that + branch is likely to be dropped.
+ +| Branch | +Release | +Package Branch | +Package Set | +Estimated EoL | +
|---|---|---|---|---|
| RELENG_7 | +n/a/ | +RELENG_7_3 | +packages-7-stable | +February 28, 2013 | +
| RELENG_7_3 | +7.3-RELEASE | +RELENG_7_3 | +packages-7-stable | +March 31, 2012 | +
| RELENG_7_4 | +7.4-RELEASE | +RELENG_7_3 | +packages-7-stable | +February 28, 2013 | +
| RELENG_8 | +n/a | +RELENG_8_1 | +packages-8-stable | +laste release + 2 years | +
| RELENG_8_1 | +8.1-RELEASE | +RELENG_8_1 | +packages-8-stable | +July 31, 2012 | +
| RELENG_8_2 | +8.2-RELEASE | +RELENG_8_1 | +packages-8-stable | +February 29, 2012 | +
| HEAD | +n/a/ | +HEAD | +packages-9-current | +Best Effort | +
Older releases are not maintained, ports and packages may not be able + to install or run. Users are strongly encouraged to upgrade to one of + the supported releases mentioned above.
+ +&footer; + +