- Add myself as a committer
- Add my PGP public key
- Add my author entity
- Add a news entry
Reviewed by: imp (mentor), ken (mentor)
Approved by: imp (mentor), ken (mentor)
Differential Revision: https://reviews.freebsd.org/D12357
Update the dtd to permit the <p> element to appear within
<category> and update the xsl template to render any paragraph(s)
of such introductory text before the line break that preceeds the
rendering of project entries in the given category.
- Now that we have the 10.4 hardware compatibility list, readme and
release notes since r50848, hook them up to the betarel2 txtdocslist.
Sync the betarel txtdocslist with that of rel, rel0 and rel1 (modulo
readme, see below, and unapplicable stuff like errata.
- Add missing readme links to the txtdocslists of rel, rel0 and rel1.
- Announce 10.4-RC1 and bump betarel2.vers to RC1 accordingly.
Approved by: re (implicit)
- Add myself as a committer
- Add my PGP public key
- Add my author entity
- Add a news entry
Approved by: imp (mentor)
Differential Revision: https://reviews.freebsd.org/D12303
- The 10.4-BETA3 set includes the BEAGLEBONE image again, so uncomment
its betarel2 entry.
- Announce 10.4-BETA3 and bump betarel2.vers to BETA3 accordingly.
Approved by: re (implict)
- It seems that somehone has mislabeld one of the red buttons to read
beta.second instead of beta2.desc, so give that knob a try and let's
see whether it brings the betarel2 bits into where.html.
- The 10.4-BETA2 set includes the RPI-B image again, so uncomment its
betarel2 entry.
- Announce 10.4-BETA2 and bump betarel2.vers to BETA2 accordingly.
- Nuke some trailing spaces while at it.
Approved by: re (implict)
- Belatedly mark the start of 10.4-BETA1 builds as done.
- Update betarel2 arm/armv6 images with reality built for 10.4, but comment
broken and unpublished 10.4-BETA1 BEAGLEBONE, RPI-B and WANDBOARD images.
- Announce 10.4-BETA1.
Approved by: re (implict)
uses the common properties attributes. This also adds the ability to
set rules in the <info> element to select types of elements that should
not be translated. Non-translated text does not appear in PO files and
is not seen by translators, but is included verbatim in the final
translated output document.
The current use case for this is to prevent the PGP keys from being
translated, which makes no sense and introduces duplication.
This work was made possible with assistance by Shaun McCance at the 2017
Open Help Conference.
Sponsored by: iXsystems
- The main link points to a dead site. "Coming soon" since 2013 ...
- The link to the "stuffed daemon" is also dead. Returns a 404 ...
- It did not fit in with the other entries anyway (was the only entry with an image attached).
Note: The linked image (../gifs/plueschtier-tiny.jpg) is still in the repository.
