Perforce no longer provides server binaries for FreeBSD and we haven't
used Perforce for project development in several years.
Reviewed by: bjk (previous version)
Differential Revision: https://reviews.freebsd.org/D15392
Neither modern Firefox nor Chrome supports OpenSearch, at least in the
form as presented. Documentation suggests it might be possible to get
this to work, but remove for now until and unless someone can get them
to work.
These have not worked in some time and no one has complained, so the
value in fixing them is clearly limited as well.
Neither modern Firefox nor Chrome supports OpenSearch so this entire
section will be removed in the next commit. Separate commits for
tracking and clarity.
- make it clear that "ppc" is "powerpc"
- don't repeat "FreeBSD" so much
- xbox support was removed in r325892
- other minor changes
Reviewed by: allanjude
Fix the link for the GUMSTIX image, and comment it as the build
failed.
Comment the BANANAPI link, there was an issue with the image.
Activate the download URLs for 11.2.
Update the releng page to reflect stable/11 is frozen (belatedly).
Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation
mini-FAQ. While volumes could be written about this, keep it breif
and clear at the expense of a few details and irrelvant pedantry.
Approved by: core@ (emaste, jhb)
the base system and we won't add any more files or content, hence there is no
need to keep this policy around any longer.
Reported by: emaste@
Approved by: core@
information that should be reported to the committee. Before, it seemed
confusing so separating these two sentences makes it clear that these are
separate things that do not belong together.
Reported by: jmg@
Approved by: core@
A lot of work by many people went into making this new code better than
the one we had, including: Valerie Aurora, Anne Dickison, Warner Losh,
Colin Percival, Benno Rice, Devin Teske, and Robert Watson.
Approved by: core@
Now that we have report-template.xml to hold a canonical report
template, there is no need to carry this duplicated content around
anymore -- it could only get stale.
It seems this step was inadvertently skipped before the email version
of the report was sent out.
Link from the status report main page and update the next-due date
(including the extension).
Also add a news entry for the report, backdated to the date of the
announcement email.
Reported by: pi
Pointy Hat to: bjk
