- Add link to the new advisory page into the support sidebar.
- Do not include release info in advisory list as it's not that
interesting in this context.
- Try to make it more clear where to report security issues to.
- Include public key directly on web site instead of referring to FTP
site.
- Remove some stale information.
- Misc minor cleanup.
Reviewed by: cperciva, remko, bz (various versions)
January 2010.
Insert the same date as the estimated EoL for RELENG_6; if there turns
out to be a 6.4-RELEASE at some later date, the EoL for RELENG_6 will
be correspondingly extended, but unless/until the release engineering
team decides that 6.4-RELEASE will happen users should plan on moving
to RELENG_7 before the end of January 2010.
6.2-RELEASE is a "normal" release, and would therefore only be supported
for 12 months normally, we're going to give it an extra 4 months of
support to allow a longer window for people to upgrade to 6.3-RELEASE or
7.0-RELEASE.
be supported by the FreeBSD Security Team.
Due to slippage in the FreeBSD 6.2 release schedule, the FreeBSD 6.0
EoL is being pushed back two months to the end of January 2007, in
order to allow time for users to upgrade once FreeBSD 6.2 is released.
- Move includes.nav*.sgml to share/sgml/navibar.ent and
<lang>/share/sgml/nabibar.l10n.ent.
- Move includes.sgml and includes.xsl to
share/sgml/common.ent, share/sgml/header.ent, <lang>/share/sgml/l10n.ent,
and <lang>?share/sgml/header.l10n.ent.
- Move most of XSLT libraries to share/sgml/*.xsl and
<lang>/share/sgml/*.xsl.
- Move news.xml and other *.xml files for the similar purpose
to share/sgml/*.xml and <lang>/share/sgml/*.xml.
- Switch to use a custom DTD for HTML document. Now we use
"-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension", which is
HTML 4.01 + some entities previously pulled via
"<!ENTITY % includes SYSTEM "includes.sgml"> %includes;" line.
The location of entity file will be resolved by using catalog file.
- Add DOCTYPE declearation to XML documents. This makes the followings
possible:
* Use of &foo; entities for SGML in an XML file instead of defining
{$foo} as the same content.
* &symbolic; entities for Latin characters.
- Duplicated information between SGML and XML, or English and
translated doc, has been removed as much as possible.
auto-responder returned when sending mail to admins@.
On the security page simply remove the email address since it's not
needed, and on the machines page link to the newusers page instead.
* Add entry for RELENG_6_1. This is an Extended branch, and will expire
at the end of May 2008.
* Update EoL of RELENG_6: The branch will be alive at least as long as
RELENG_6_1 (and longer, assuming there are more 6.x releases).
* Extend EoL of RELENG_5_4 to match the EoL of RELENG_5_3 (October 2006).
This will give users of FreeBSD 5.4 more time to upgrade to 5.5 (which
will be released very soon).
* Update EoL of RELENG_5: It will die at the same time as RELENG_5_5,
which will be the end of May 2008.
- Markup a list with <ul> instead of using <br>.
- Use secteam@ instead of security@ as contact address for the FreeBSD
Security Team in the hope of minimizing confusion a bit with which
address goes where.
- Add a link to the contributors article where people can see the current
Security Team member list.
- Tell people the preferred contact is the FreeBSD Security Team.
Note part of this page is still somewhat inconsistent with itself in
some parts, but at least this is a step in the right direction.
cperciva =~ s/Deputy Security Officer/Security Officer/
Jacques is stepping down from the Security Officer role after 43 months
of dedicated service, but he will still be around to make sure I don't
mess things up too badly... :-)
security support, i.e., 12 months.
While I'm here, extend the EoL date for RELENG_5 to now + 24 months,
since the actual date is going to be 24 months after the last 5.x
release.
We now have a Security Officer (nectar), two Deputy Security Officers
(des, cperciva), and one Core Team / Release Engineering / TrustedBSD
Project liaison (rwatson).
1. The security-officer alias goes to three people, not four; there is
one member of the core team on the alias, not two.
2. Our set of close working relationships includes DragonFlyBSD as well
as the older BSDs.
3. We usually commit security fixes to HEAD and the security branches
(nearly) simultaneously; there is no longer a significant lag between
disclosure-via-CVS and the advisory being sent out.
With hat: secteam
Update RELENG_4 EoL to January 31, 2007 -- two years after the
(anticipated) 4.11-RELEASE.
Remove RELENG_5_2 as it has exceeded its lifetime in most of the world.
Time to update those 5.2.1-RELEASE systems to 5.3-RELEASE!
branches. `Early adopter' branches will be supported 6+ months,
`Normal' branches will be supported 12+ months, and `Extended'
branches will be supported 24+ months.
Mark RELENG_4_8 as an `Extended' support branch and extend its
Estimated EoL accordingly.
While here, also extend RELENG_5_2 through the end of 2004.
(I was reminded that RELENG_4_8 had expired a few days ago by
cperciva@.)
