Hi Anjan! So this service pack in it's current form is pretty empty. I thought about pushing it back by 3 weeks, into CW 42. That was before I realized the Sxmo upgrade would go in there anyway, that would be a significant change worth doing the service pack for. What do you think, shall we do one at the end of this week and include the Sxmo 1.11.1 upgrade?
If you are releasing this week or next week, Ill wait till the next service pack.
Why is that, are you expecting to do some fixups?
Must sync release with superd move to stable in aports.
Most of the time for service packs, we just fork all packages we want to upgrade from aports to pmaports and then upgrade them there. This would mean we wouldn't need to worry about backporting superd in sync, we would just include that in the service pack (forked to pmaports) as well. So I'd do that here too unless you have a reason we should do it differently.
Im moving cross country. That will take up this week and weekend. As such, I wont be able to steward an upgrade to sxmo 1.11.1 in stable.
As such, I think it's best if we push this service pack back.
Why is that, are you expecting to do some fixups?
I was expecting fixups but it seems this release is really stable. Ive been using it on pmOS stable since it came out.
Most of the time for service packs, we just fork all packages we want to upgrade from aports to pmaports and then upgrade them there. This would mean we wouldn't need to worry about backporting superd in sync, we would just include that in the service pack (forked to pmaports) as well. So I'd do that here too unless you have a reason we should do it differently.
Ill have more time to discuss how to handle the superd situation at the end of this move. But im willing to do whatever is easier for you and @craftyguy
removed it from the list again as you requested in chat:
hey ollieparanoid, for the next service pack, I think it might be best if we didnt include 1.11.1. We're near the next release of postmarketOS v22.12 anyways heh.
The service pack would be up for next week. But it's still rather empty - doesn't seem worth the effort, so I'll push this one month further into the November timeslot.
backport with a service pack in one week to v22.06
usually we do vulnerability fixes outside of service packs. but given that this requires major kernel upgrades, it makes sense to put it into a service pack and to wait a week in case there's fallout / we'll need a bit to patch all of them anyway.