Why is -d still needed on released version?

Here you can see that do-release-upgrade from 19.10 to 20.04 doesn’t see 20.04’s availability without the -d flag.

ian@Ian-Blue:~$ do-release-upgrade -d
Checking for a new Ubuntu release
Get:1 Upgrade tool signature [1,554 B]                                         
Get:2 Upgrade tool [1,344 kB]                                                  
Fetched 1,346 kB in 0s (0 B/s)                                                 
authenticate 'focal.tar.gz' against 'focal.tar.gz.gpg' 
extracting 'focal.tar.gz'
[screen is terminating]

ian@Ian-Blue:~$ do-release-upgrade
Checking for a new Ubuntu release
No new release found.

ian@Ian-Blue:~$ less /etc/update-manager/release-upgrades | grep Prompt
Prompt=normal

We’re running 3-4 days post-release, and a lot of folks in the help forums are asking and we lack a clear answer.

Is this Phased Upgrades?
Or deliberate?
Or an oversight?

We have never switched auto-updates for any LTS on before the .1 release … I doubt it will be different this time.

(and we seem to have that confusion every two years too, I guess the note in the releasenotes that makes this clear should be in written in red between <blink>…</blink> tags :wink: )

EDIT:
The announcement is here: 20.04 Release Announcement

The text in question is:

Users of Ubuntu 19.10 will be offered an automatic upgrade to 20.04 LTS via Update Manager shortly. Users of 18.04 LTS will be offered the automatic upgrade when 20.04.1 LTS is released, which is scheduled for July 23rd.

3 Likes

Indeed. I raised the question because “shortly” for 19.10 users seems vague.

2 Likes