@rvolosatovs this is backported but not released. What do we do with this?

@rvolosatovs this is backported but not released. What do we do with this?

Can you clarify this statement? Since it's backported from 3.11, it should be present in both 3.10 and 3.11 minors, what else do we need to release?

@rvolosatovs this is backported but not released. What do we do with this?

Can you clarify this statement?

It's not part of a 3.10 release. The last one here is 3.10.7, and these commits are merged after. So yes, it is backported, but that's it.

If we don't want 3.10 to panic, then we have to release 3.10.8 with this fix. I'd say this definitely deserves to be released, since once this happens for a device - no class A downlinks will go through anymore.

We released 3.11.0 now, so that's ok.

But next time, please file a Release issue so we don't forget about releasing things that we backported.

This is already deployed in TTS v3.10.9. We can make a TTSOS release for completeness.