- Remove references to CVS, everything is in Subversion now
- The "mentors" file is used in the ports repo, as well as in src/doc
- Commits to "access" should include the new committer's username
map to point to it.
I'm not particularly happy about linking to the wiki from the main site,
but this change seems like the least-bad option, for now at least.
Discussed with: bcr
Approved by: bcr (mentor)
IE 9+
Fx 4+
Chrome 4+
Safari 5+
Remove Support for
Fx before 4.0
Chrome between 0.2 and 4.0
Safari between 3.0 and 5.0
Of note: in the third hunk the "real" value and the prefixed values
differ.
Tested on Chrome & Firefox 19
Approved by: bcr (mentor)
- FreeBSD 9.0 scheduled to be supported till the end of March, so move
it back to the "Most Recent Releases"
- Mark FreeBSD 8.3 as a legacy release.
- Move FreeBSD 7.4 to the list of unsupported releases.
PR: www/176680
Submitted by: SirDice <sirdice@gmail.com>
Approved by: remko (mentor)
- Stop encouraging people to mirror the FreeBSD web site
- Update the instructions to use csup rather than cvsup
- Remove details for compiling cvsup
- Stop linking to pages which no longer contains info on cvsup
- Fix the instructions
- Remove incorrect info about how often the FreeBSD website updates.
This page can probably just be removed, but until then it can at least be
correct.
Approved by: bcr (mentor)
comp.unix.bsd.freebsd.misc still gets traffic, even if at a reduced
level, and comp.unix.questions is pretty alive too. But instead of
reverting the changes and listing them in two places, one paragraph
now talks about both Usenet groups.
Reviewed by: eadler
Approved by: remko (mentor), gjb (mentor)
Move 7-STABLE and 7.4 to the list of unsupported releases/version.
Releng:
Mention that RELENG_7 is now a maintenance branch, mention that 7.4
is no longer officially supported.
Reviewed by: des,simon
Hat: secteam
- add information related to the documentation slush
- update and comment out the wiki link, there is no wiki page for
8.4-RELEASE yet.
Approved by: gjb (mentor)
These aren't linked to from anywhere yet, as I wanted to open up the review
process more. In one day or so, I plan to have incorporated any reasonable
changes I receive (via email - comments or patches are welcome), and then
complete the rest of the report release process.
Hat: monthly
Approved by: gabor (mentor, this morning - approval for .xml parts only)