Sepherosa Ziehau is switching DragonFly from IPFW1 to IPFW2, which has the same rule syntax. Gergo Szakal helpfully pointed out that the differences between the two versions are listed in the IPFW man page under “IPFW2 ENHANCEMENTS”.
A bug in SMP virtual kernels has been fixed; the side effect is that if you are running bleeding edge code, you will need to recompile any SMP vkernels you are using.
1.10 has been released; check the page describing the release and then please use a mirror when downloading the ISO or updating your sources. The release page also has a list of the many changes in this version. Check the errata, as there’s a few small issues that remain within the installer.
Two warnings: the compatibility slice is changing, and disklabel is going through extensive changes. If you run bleeding-edge code, you will want to do a full rebuild.
Matthew Dillon has done some careful reworking of the disklabel system; it will require a full make buildworld and etc. process if you are running bleeding edge code and want to upgrade. Be careful!
Incidentally, this makes a dynamic /dev possible, for anyone wanting to put it together.  Again, be careful!
Since Matthew Dillon’s working on the disklabel code, be careful if you’re running bleeding edge code in the next few days. Disklabel errors eat data.
If you have a DragonFly system, you should update it now. (Point releases have been rolled for 1.8, 1.6, and even 1.4) Non-DragonFly systems should also be updated, if available.
If you are mirroring Joerg Sonnenberger’s pkgsrc binary archive from its old location at packages.stura.uni-rostock.de, it’s time to switch. He has a new site, and until his bandwidth has stabilized, it’s best to mirror from Simon ‘corecode’ Schubert’s site at chlamydia.fs.ei.tum.de.
The title says it all – visit the download page for 1.8 to get it. Most every mirror appears to have it right now – not just the ones on the 1.8 page.
Note that some sites have an early version of the 1.8.1 release that lacks the installer; that image is ‘dfly-1.8.1.iso.gz’. Instead, be sure to download ‘dfly-1.8.1_REL.iso.gz’, which should be the newer file of the two.
Sepherosa Ziehau warned bleeding-edge users that recent network interface changes will require a rebuild of both kernel and world when next updating. This does not apply to 1.8 users.
DragonFly 1.8.1 will be released this weekend, so if you have something that you need added, speak up! This release will include the rtld fixes that enable parts of KDE to work again, among other things.
You may need to copy in a new /etc/localtime file to account for daylight savings time changes in the U.S. and Canada, especially if you have an older system; Matthew Dillon explains.
www.dragonflybsd.org and leaf.dragonflybsd.org are getting upgraded to 1.8; this may mean some intermittent downtime over the next week.
If you are running a DragonFly system older than version 1.6, and you are in North America using something other than UTC time, you will need to manually update your tzinfo files to reflect the changed (in 2005, taking effect this year) Daylight Savings Time start and stop dates. If you are on UTC or are running 1.6+, you are fine.
Version 1.8 has been released! See the release announcement, or proceed directly to the download page (and errata).
Updated: mentioned on BSDNews, Reddit, and Digg. Download also available as a Metalink. (Description at metalinker.org)
Matthew Dillon reports changes to the kernel configuration file are needed now. Also, if you are running bleeding-edge code, a full buildworld/buildkernel is required on the next upgrade.
Branching for 1.8 will happen very soon; as soon as ACPI is ready. The release date has not slipped.
Matthew Dillon is doing CVS surgery tonight to revert the architecture name changes; if you are using bleeding-edge code, don’t update it until tomorrow.
Simon ‘corecode’ Schubert had some trouble with the changed src layout while working on gcc 4.1. Matthew Dillon is changing it back, Wednesday. (So no commits on Wednesday, please.) This naming issue is apparently not new.
Matthew Dillon is renaming some I/O calls. It shouldn’t cause major problems, but as always, make sure to do a complete buildworld/buildkernel when next upgrading your bleeding-edge system.
Matthew Dillon is making trapframe changes – it will require a complete buildworld if you are following bleeding edge code. Read his post for more details.