stable release exception for sos

[Arif Ali]

Hi Robie,

That's fine - it's appropriate to treat sos the same as sosreport since
> it's just a rename and there aren't any functional differences. Feel
> free to adjust the wiki accordingly.


Wiki Updated

One thing to consider carefully though is whether it's appropriate to
> attempt to retrospectively follow the rename in existing stable
> releases. That could result in a mess and needs a closer look at the
> packaging implications, I think.
>

This is something I am considering, but still have a few months before that
can actually happen due to how we do the release of sos as a SRU (typically
2 releases a year, and one is currently going through the SRU).

I will prepare the package in a PPA, like I have in the past in the same
minimal change effort, and will seek guidance when the time comes. As I
think we'd probably need to remove the src:sosreport so that src:sos can
migrate (which is what we had to do with plucky). I think in this instance
it won't make sense to change the seeds and would need to promote sos to
main. But agreed it definitely needs a closer look at the implications.

The sosreport and sos-collector command is being removed, and the plan was
to include that as part of the transitional package in stable as well so
that the change would be seamless and cause less user friction with the
command if they're used to using it. Having it split like this would help
wean them off, and plan to drop the transitional package after the next LTS.

Obviously, any advice around this would be awesome, that can help me to
prepare for this transition. There's still plenty of time before I prepare
the next SRU for sos.

Arif
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-release/attachments/20250220/0c2b2e1f/attachment.html>