Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 14 Jul 2003 10:38:11 -0500
From:      "Jacques A. Vidrine" <nectar@FreeBSD.org>
To:        freebsd-security@FreeBSD.org
Subject:   Security Officer-supported branches update
Message-ID:  <20030714153811.GB78930@madman.celabo.org>

next in thread | raw e-mail | index | archive | help
Hello Everyone,

The branches supported by the FreeBSD Security Officer have been
updated to reflect recent releases and EoL (end-of-life) events.  The
new list is below (and should appear at 
<URL: http://www.freebsd.org/security/ > soon).
In particular, FreeBSD 4.6 and FreeBSD 5.0 have `expired'.  If you wish
to be certain to get critical bug fixes, it is recommended that you
upgrade to one of the newer security branches.

[Excerpt from http://www.freebsd.org/security/]

   The FreeBSD Security Officer provides security advisories for
   several branches of FreeBSD development. These are the -STABLE
   Branches and the Security Branches. (Advisories are not issued for
   the -CURRENT Branch.)

     * There is usually only a single -STABLE branch, although during
       the transition from one major development line to another
       (such as from FreeBSD 4.x to 5.x), there is a time span in
       which there are two -STABLE branches. The -STABLE branch tags
       have names like RELENG_4. The corresponding builds have names
       like FreeBSD 4.6-STABLE.

     * Each FreeBSD Release has an associated Security Branch. The
       Security Branch tags have names like RELENG_4_6. The
       corresponding builds have names like FreeBSD 4.6-RELEASE-p7.

   Each branch is supported by the Security Officer for a limited
   time only, typically through 12 months after the release. The
   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. Please note
   that these dates may be extended into the future, but only
   extenuating circumstances would lead to a branch's support being
   dropped earlier than the date listed.

   +-----------------------------------------+
   |  Branch  |  Release  |  Estimated EoL   |
   |----------+-----------+------------------|
   |RELENG_4  |n/a        |December 31, 2003 |
   |----------+-----------+------------------|
   |RELENG_4_7|4.7-RELEASE|September 30, 2003|
   |----------+-----------+------------------|
   |RELENG_4_8|4.8-RELEASE|March 31, 2004    |
   |----------+-----------+------------------|
   |RELENG_5_1|5.1-RELEASE|December 31, 2003 |
   +-----------------------------------------+

   Older releases are not maintained and users are strongly
   encouraged to upgrade to one of the supported releases mentioned
   above.



Cheers,
-- 
Jacques Vidrine   . NTT/Verio SME      . FreeBSD UNIX       . Heimdal
nectar@celabo.org . jvidrine@verio.net . nectar@freebsd.org . nectar@kth.se


----- Forwarded message from Jacques Vidrine <nectar@FreeBSD.org> -----

Date: Mon, 14 Jul 2003 08:13:43 -0700 (PDT)
From: Jacques Vidrine <nectar@FreeBSD.org>
To: doc-committers@FreeBSD.org, cvs-doc@FreeBSD.org, cvs-all@FreeBSD.org
Subject: cvs commit: www/en/security security.sgml
Message-Id: <200307141513.h6EFDhAI067098@repoman.freebsd.org>

nectar      2003/07/14 08:13:43 PDT

  FreeBSD doc repository

  Modified files:
    en/security          security.sgml 
  Log:
  Security Officer-supported branches updated:
    FreeBSD 4.6, FreeBSD 5.0 removed: they have passed the published EoL.
    FreeBSD 5.1 added.
  
  Revision  Changes    Path
  1.135     +5 -10     www/en/security/security.sgml
http://cvsweb.FreeBSD.org/www/en/security/security.sgml.diff?r1=1.134&r2=1.135&f=c


----- End forwarded message -----



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030714153811.GB78930>