- Enable the 'download page' URL on the schedule.
- Add arm64/aarch64 virtual machine images and installer image URL.
- Add RPI2 SD card image URL.
- Comment the 12-CURRENT snapshot URLs, no snapshots are available
yet.
Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation
Comment the signatures.html URL for now.
Enable download URLs on where.html for 10.3-BETA1.
Approved by: re (implict)
Sponsored by: The FreeBSD Foundation
to make them a bit easier to find.
Link to a README file within the VM-IMAGES directory which contains
a mapping of disk image format and hypervisor support.
Requested by: gnn
Sponsored by: The FreeBSD Foundation
Improve the text and descriptions around the tables
Make Virtual Machine images easier to find
Differential Revision: https://reviews.freebsd.org/D1102
Reviewed by: gjb, rodrigc, bcr
Approved by: wblock (mentor)
Sponsored by: ScaleEngine Inc.
- 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
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
