- Set the release month and year for 9.3-RELEASE.
- Remove 9.3-RELEASE from the releng page.
- Add the 9.3-RELEASE EoL to the security page.
- Set beta.testing to IGNORE since images are not yet
built.
Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation
- Set beta2 macros to 10.1-R, and enable the beta2.upcoming
text.
- Connect the 10.1R directory to the build.
Approved by: re (implicit), doceng (implicit)
Sponsored by: The FreeBSD Foundation
handbook fail to build on the cluster with no CVSup mirrors listed. I
can't recreate this locally, but for now, add back a single mirror
(cvsup.freebsd.org, which is under clusteradm control). Hopefully
that should be sufficient to allow the build to complete.
Noticed by: wblock
Pointy hat to: gavin
them from the mirror list source.
Many thanks to all of the people who have have maintained these systems
over the years (sometimes more than 10!). You have helped FreeBSD grow
to what it is today, and your contribution is very much appreciated.
The date on the actual notice is correct (2014-06-03) but the date in
doc/head/share/xml/notices.xml wass incorrectly entered as 2014-05-03 in
rD45000
PR: 190628
Approved by: wblock (mentor)
Fix sendmail improper close-on-exec flag handling. [SA-14:11]
Fix ktrace memory disclosure. [SA-14:12]
Fix incorrect error handling in PAM policy parser. [SA-14:13]
Fix triple-fault when executing from a threaded process. [EN-14:06]
that we will be soon entering the release cycle. As such, we are
not able to easily link to the upcoming release schedule.html page
from the index page unless we already have BETA release builds on
the FTP mirrors.
Implement some evil to eliminate this limitation:
- In share/xml/release.l10n.ent, move reusable text from the
'helptest' header, and into a beta.helptest macro, and include
the new macro in beta.desc.
- Add a new entity, beta.local.where, which is ignored by default.
When enabled in the schedule.xml for the upcoming release, it
prints information about where to download the testing builds.
- Add two new entities, beta.upcoming and beta2.upcoming, which
are used in index.xsl, and when set, direct the URL to the
upcoming release schedule.html page instead of directly to
where.html. With this change, we can advertise that a release
cycle is about to start, and not need downloadable images yet.
Sponsored by: The FreeBSD Foundation
