os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Reflect reality. RELENG_4 is pushing up the daisies, so advise users

Browse source 
to upgrade to RELENG_6.  For those systems where upgrading is not
possible, point users to the RELEASE_4_EOL tag, but discourage usage
as it is not supported nor updated with security fixes.

Reviewed by:	pav, simon, linimon
This commit is contained in:
Erwin Lansing 2007-03-29 15:10:16 +00:00
parent d527384cb6
commit ac9c8768f5
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=29881
1 changed files with 18 additions and 30 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

48
en/portmgr/policies_releng_4.sgml
View file

@ -1,6 +1,6 @@
<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [ <!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [
<!ENTITY base CDATA ".."> <!ENTITY base CDATA "..">
<!ENTITY date "$FreeBSD: www/en/portmgr/policies_releng_4.sgml,v 1.2 2006/05/14 09:33:27 joel Exp $"> <!ENTITY date "$FreeBSD: www/en/portmgr/policies_releng_4.sgml,v 1.3 2006/08/19 21:20:41 hrs Exp $">
<!ENTITY title "EOS/EOL Policies of Ports and Ports Infrastructure on RELENG_4"> <!ENTITY title "EOS/EOL Policies of Ports and Ports Infrastructure on RELENG_4">
<!ENTITY % navinclude.about "INCLUDE"> <!ENTITY % navinclude.about "INCLUDE">
]> ]>
@ -8,36 +8,24 @@
<html> <html>
&header; &header;
<p>While still many people use RELENG_4, it is EOD. Portmgr has set the <p>While still many people use RELENG_4, it is End of Life (EOL) and
following policies with regard to EOL/EOS of this branch and kindly asks End of Support (EOS). We encourage all users and developers to
developers to implement these:</p> migrate to the FreeBSD 6.X branch, which is a stable and mature
platform, and is now the 'reference' FreeBSD branch for the Ports
Collection. The "last known good" tree has been tagged with the
<tt>RELEASE_4_EOL</tt> tag as a convenience to those remaining
users who intend to self-support their own 4.X 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.</p>
<ul> <p>Support for RELENG_4 was removed from the ports infrastructure
<li>We keep building 4.11 packages as long as we have the resources. after the <tt>RELENG_4_EOL</tt> tag and the ports collection can no
4.X package builds will be deprioritised though, meaning they may not be longer be used on that branch. Therefore maintainers are also no
rebuilt as frequently.</li> longer required to provide any form of support for running their
<li>We will continue to support the 4.X infrastructure until RELENG_4 EOL ports on FreeBSD 4.X, and may also remove any legacy support code
(31&nbsp;January&nbsp;2007) by building the INDEX on RELENG_4 for use by at their convenience.</p>
<i>make fetchindex</i>, and making sure that the Ports Collection
infrastructure (bsd.port.mk, etc) continues to function on RELENG_4,
subject to the reduced testing that this branch will receive. This means
that problems may be noticed only after the fact and may require community
support to develop and test fixes.</li>
<li>We do not require committers/maintainers to support 4.X, but ports will
still be required to be marked BROKEN/IGNORE if they do not build/run.</li>
<li>Port maintainers are strongly encouraged to accept patches from the
community that allow their ports to build and run on 4.X. However, since
running on 4.X is no longer a requirement, maintainers may use their
discretion in cases where a proposed patch would be disruptive to other
supported FreeBSD branches, or would unreasonably impede ongoing
maintenance of the port.</li>
<li>We will continue to accept patches for Ports Collection infrastructure
(bsd.port.mk, etc).</li>
<li>We encourage all users and developers to migrate to the FreeBSD 6.X
branch, which is a stable and mature platform, and is now the 'reference'
FreeBSD branch for the Ports Collection.</li>
</ul>
&footer ; &footer;
</body> </body>
</html> </html>