25.10 is not released, so you can upgrade from 25.04 to 25.10 only editing /etc/apt/sources.list.d/ubuntu.sources … but you can use this method if you are experienced enough and don’t have third party software… and want to take a chance.
… sorry i ignored this problem and ignored also do-release-upgrade -d
What you report there is what is supposed to happen. Ubuntu 25.10 isn’t scheduled to be released until mid October 2025, thus error is expected.
The reason for the error is the command checks https://changelogs.ubuntu.com/meta-release to see what is available and supported, and of course 25.10 or questing isn’t there.
If you read the quick reference manual page, ie. man do-release-upgrade you may notice a development option, which will cause a different file to be used, ie.
which DOES INCLUDE details of the development release, ie. questing or 25.10.
You didn’t include the -d option to jump to 25.10. This is what is used when Quality Assurance testing of the release-upgrade process.
The -d option will be required until release of Ubuntu questing as Ubuntu 25.10, in fact is common for it to still be required soon after ISO release, as the meta files are only changed when all QA testing has shown it’s ready for users to release-upgrade from 25.04 to the then released 25.10 (Ubuntu Release team members have a process they follow, and will open it when all requirements have been met; they can also decide to stop usage of the -d at times too having good reasons at specific times in the development cycle so users aren’t breaking their systems)
OK. For some reason, I thought this was supported, or would be soon. What is “questing”?
Maybe this is what I saw, and I missed that distinction.
I don’t run a very complicated system, so I can’t imagine much to go wrong. I just wanted to pick up the improvements with the new Kernel and the new Gnome. If I went to one of these interim 25.10 versions, will it still update to the real version once the “real” 25.10 comes out?
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).
Many are found on this site (and there are many), eg.
but not all are on this site. Many of the teams (eg. kernel, desktop etc) provide their own pages dealing with their own areas of development, on this site.
For a changelog you could always view
which you’ll note get updated somewhat regularly during the cycle (view top right and you can see 24 edits thus far, this history lets you explore further too), but expect that detail to change irregularly whilst we’re still in alpha and become more complete as beta approaches.
Yeah, I think I am all set for now. Can barely make the supported version work, not going into uncharted territory. Nowhere near as smooth as Windows, unfortunately.
I have been using Ubuntu for 17 years now and once I stopped using the development releases and having the proposed repository enabled my system became stable and has been for all these years but I do not experiment with my production machine anymore I only experiment in a virtual environment.