Here a simplified mini-summary of the SRU [1] process steps to understand where things are.
Generally states are tracked per target release
1. Bug is filed and discussed (states: new, confirmed, triaged)
examples see all early comments <=#45
2. A fix is prepared and uploaded to -unapproved [2]
example see comment #48
3. The SRU team does an extra review and accepts it to proposed (state: Fix committed)
examples see comment #49, #57, #58
From this moment the package is available for testing from -proposed
4. The new build is verified in -proposed where is now available
and the per release tags marked as verification-done
examples see comments #52 #64 and #65
5. Once a bug is verified for a given release and aged (usually min 7 days)
without finding regressions it is released by an SRU member
and thereby landing in -updates
(State: "Fix Released")
example see comment #75
The per release bug states reflect which stage you are in all the time.
Additionally if you are curious there is also global of all ongoing SRUs [3].
Now after that short summary I hope the following makes sense:
"For this case Focal and Jammy are currently in -proposed, already verified and reached >=7 days aging just a few hours ago. So I expect it to be released very soon by the person being on today's SRU duty"
@XanderCDN
Just like Focal/Jammy it is also on its way to ESM in e.g. Bionic, yet not as visible as for the more recent releases. I see you already used the PPA version and helped checking for regressions - thanks!
I sadly do not have an exact timing on for you, but I agree it a) didn't release yet but b) should happen soon.
@ krbvroc1 / Emilian
Here a simplified mini-summary of the SRU [1] process steps to understand where things are.
Generally states are tracked per target release
1. Bug is filed and discussed (states: new, confirmed, triaged)
examples see all early comments <=#45
2. A fix is prepared and uploaded to -unapproved [2]
example see comment #48
3. The SRU team does an extra review and accepts it to proposed (state: Fix committed)
examples see comment #49, #57, #58
From this moment the package is available for testing from -proposed
4. The new build is verified in -proposed where is now available
and the per release tags marked as verification-done
examples see comments #52 #64 and #65
5. Once a bug is verified for a given release and aged (usually min 7 days)
without finding regressions it is released by an SRU member
and thereby landing in -updates
(State: "Fix Released")
example see comment #75
The per release bug states reflect which stage you are in all the time.
Additionally if you are curious there is also global of all ongoing SRUs [3].
Now after that short summary I hope the following makes sense:
"For this case Focal and Jammy are currently in -proposed, already verified and reached >=7 days aging just a few hours ago. So I expect it to be released very soon by the person being on today's SRU duty"
@XanderCDN
Just like Focal/Jammy it is also on its way to ESM in e.g. Bionic, yet not as visible as for the more recent releases. I see you already used the PPA version and helped checking for regressions - thanks!
I sadly do not have an exact timing on for you, but I agree it a) didn't release yet but b) should happen soon.
[1]: https:/ /wiki.ubuntu. com/StableRelea seUpdates /launchpad. net/ubuntu/ jammy/+ queue?queue_ state=1& queue_text= /ubuntu- archive- team.ubuntu. com/pending- sru.html
[2]: https:/
[3]: https:/