Always read the upgrade guide before upgrading.
This release only includes changes related to SNMP, which I imagine are irrelevant to most people, though probably exciting for a subset of OpenBSD users. https://www.openbsd.org/faq/upgrade70.html
The upgrade guide for 6.9 gives a better flavor for how OpenBSD handles and documents subsystem and configuration changes: https://www.openbsd.org/faq/upgrade69.html
Notice how succinct and consistent (across decades!) are the upgrade guides. The above have the same basic format and content as this one from 2004: https://www.openbsd.org/faq/upgrade35.html I've been doing remote upgrades of OpenBSD and Linux (mostly Debian, but also occasionally Red Hat derivatives) for over 20 years. While I've fortunately only rarely encountered significant problems with any of them, OpenBSD upgrades are the only ones where I can have any confidence in understanding and tracking how the system evolves across upgrades. Follow the upgrade guide and delete outdated files (much easier since sysclean(8)), and a 10-year-old OpenBSD box can have a filesystem as pristine as a freshly installed system.
I'm not one of those people who wants pristine for the sake of pristine. But pristine is important when you care about security, and maintenance burden is a huge component of security, as are simplicity and transparency.
used it as a webserver and VPN appliance for a couple of years now.
only thing in terms of maintenance is the following when a new release is released.
pkg_add -u ( i usually update extra packages every 6 months, which is mainly lets encrypt). syspatch sysupgrade
reboot:
after reboot
sysmerge to see if i need to do a config diff.
Has been rocksolid and very future rich in base aswell.