I’ve done what I suggested, and its what my system is
guiverc@d7050-next:~/uwn/issues/903$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Questing Quokka (development branch)
Release: 25.10
Codename: questing
I’m using Ubuntu questing, which will change its name to Ubuntu 25.10 when it reaches RC (Release Candidate) just prior to release in October. A development OS goes by its codename, with released products using the 25.10 (ie. the Description in that command will change just prior to release when the OS reaches stable, it’s currently in alpha).
You apply normal upgrades just like you would a stable OS, and it’ll upgrade packages normally and you’ll note it switch from questing to Ubuntu 25.10 usually on the weekend prior to release.
It’s NOT a stable OS, so problems can occur, and many sites do not support it; including the Support and Help site here (ie. the Start Here clearly says standard-supported versions of Ubuntu only, ie. no ESM, no development etc).
I watch the development progress, and believe I know how to fix most problems I’ve encountered; whilst problems are rare, I have had this system break twice in the last three cycles; so there is risk involved (and you need to be comfortable in fixing your system when that occurs! having a plan it place as you won’t know when or what may break).
You’ll need more space for updates, and I update my system three times per day, as being on a development release differs to a stable release.
You may find you need to apt full-upgrade a couple of times per cycle; as the apt upgrade can leave packages not upgraded as changes occurs, and your system does have a few extra no longer used files taking space as the cleanup of a development release isn’t the same as a stable system (ie. stuff is changing, and its on you to keep up & fix whatever gets left behind).
This though is no different to other OSes, if you’ve used a rolling system you’ll know of the breakage (it’s not that bad in my experience), and is ~equal to Debian testing in my view.
Do you read all the development updates? To me they do regularly highlight the significant changes that are happening, and that is what can go wrong. Your system won’t have occasional updates, but many updates per day as its not a stable system, and you maybe using different packages to what prior testing was done. A development release is there so bugs can be found, reported, and then fixed PRIOR to normal end-users actually using the system. It’s called unstable for a reason; so don’t forget that (even if it’ll appear stable most of the time).
This site does contain a Pre-Release Discussion area for the development release, and you can learn about what its for by reading here but it’s geared for discussion, and not end-user support, as development users are expected to fix their own problems (it’s unstable don’t forget).