This week's BSD Now covers assembly on OpenBSD, games on FreeBSD, and disk space on DragonFly.
I've mentioned it before, but the tool 'synth' is what DragonFly uses to build all the dports binaries - over 30,000 packages, though I'm typing that from memory and not from looking at a tool.  Anyway, the one part of the release process I've never touched was the package building - and now it's documented.  This document is oriented towards DragonFly releases - but if you wanted to create your own package repo with custom options, this is the way to do it.
I uploaded the current 5.4 release candidate - there's an ISO and an IMG file, though your local mirror may be a better place to get it than those links.  Or just wait; I think the release won't be long. Note that I was smart for once and named it 'rc1', so if there's another release candidate, it can be named 'rc2'.  I used 'rc' in previous releases and was never sure if I should name a second candidate rc1, rc2...
Bear with me; this is the history: wpa_supplicant is the program DragonFly uses to connect to most wireless networks.  It's been part of the base system for some time, but if you start it up, you will see a warning (at boot time) about how this version is deprecated.  Installing from dports puts a newer version in place. As is the case with most third-party include in any operating system's base, there's always lag between the newest version of software and what's been included in.  Dependencies creep in, or it's duplicated work between packaging and basic OS maintenance, etc.  (Who here used Perl on FreeBSD 4?  That was frustrating, but a good example here.)  Anyway, the dilemma is that since wpa_supplicant is a program that may be required in order to get online, it must be in the base install.  However, since it has / had vulnerabilities, it must be updated.  The base install doesn't update as fast as the origin of the software, and there's the mismatch. All that's a long explanation as to why network/wpa_supplicant is now on the DragonFly install CD, and gets automatically used if installed.  Thanks for Aaron LI and Matthew Dillon for making it happen.  The base package is still there, in case someone deletes their installed ports and needs to get online before they can reinstall.  This is in master now and will be in the 5.4 release.
A sorta backwards-looking list for you, this week. Unrelated video of the week: Mashups are a mental dead end in most cases, but this "Benny Hill/Slayer Mashup Disaster" tickled me.  (via)
Games are the unofficial accidental theme this week.    
This week's BSD Now (notice I'm spelling it correctly now, with a space) has, along with NetBSD and OpenBSD material, happens to talk about NomadBSD, which I've never really managed to cover.
I tagged the first release candidate for DragonFly 5.4 last night.  The commit message has summary lines from all the commits in this release, if you want to go through them - or wait for the release notes.  I'm happy to see some new-to-me committer names in there, too.
I'm actually surprised this wasn't already there: Aaron Li added terminfo entries for tmux and tmux-256color into DragonFly's terminfo(5) file.  I've been using tmux without issue for some time on DragonFly... but I may not be exercising it as hard as I could.
We're overdue for 5.4 to be released.  New releases are due every 6 months; I lost track!  I plan to work on tagging and building over the U.S. Thanksgiving holiday later this week.
Another cover-all-categories week. Your unrelated music link of the week: A Guide to Breakbeats on Bandcamp.
Still lots of BSD stuff happening.
The movies link should keep you busy.