So when the upgrade from Vivid to Wily is performed, we download the version of ubuntu-release-upgrader from wily. Subsequently, the fix only needs to appear in the release to which the upgrade is being performed.
Having said that it's likely Vivid does need a fix for upgrades from Trusty, but this is currently untestable because of bug 1497688.
The way the release upgrade process works is that it downloads a tarball from the next release we can see this in the meta-release file.
Dist: wily archive. ubuntu. com/ubuntu/ dists/wily/ Release archive. ubuntu. com/ubuntu/ dists/wily- updates/ main/dist- upgrader- all/current/ ReleaseAnnounce ment archive. ubuntu. com/ubuntu/ dists/wily- updates/ main/dist- upgrader- all/current/ ReleaseAnnounce ment.html archive. ubuntu. com/ubuntu/ dists/wily- updates/ main/dist- upgrader- all/current/ wily.tar. gz ature: http:// archive. ubuntu. com/ubuntu/ dists/wily- updates/ main/dist- upgrader- all/current/ wily.tar. gz.gpg
Name: Wily Werewolf
Version: 15.10
Date: Thu, 22 October 2015 15:10:00 UTC
Supported: 1
Description: This is the 15.10 release
Release-File: http://
ReleaseNotes: http://
ReleaseNotesHtml: http://
UpgradeTool: http://
UpgradeToolSign
So when the upgrade from Vivid to Wily is performed, we download the version of ubuntu- release- upgrader from wily. Subsequently, the fix only needs to appear in the release to which the upgrade is being performed.
Having said that it's likely Vivid does need a fix for upgrades from Trusty, but this is currently untestable because of bug 1497688.