sentinel-minipot: release with new message types (v2.2.0)

Part of turris/sentinel/sentinel#24

Minipots are going to provide new message types to server and fix a lot of problems on server that way.

related:

• turris/sentinel/minipot!9 (merged)
• turris/sentinel/minipot!10 (merged)
• turris/sentinel/minipot!11 (merged)
• turris/sentinel/minipot!13 (merged)
• turris/sentinel/minipot#56 (closed)

related to server components:

• turris/ansible!357

changed milestone to %Turris OS 5.3.0

added Backlog label

changed the description

changed the description

added Blocked label and removed Backlog label

changed the description

added To Do label

changed the description

changed the description

changed the description

changed the description

marked this issue as related to turris/sentinel/minipot#56 (closed)

marked the checklist item turris/sentinel/minipot!11 (merged) as completed

changed the description

marked the checklist item turris/sentinel/minipot!13 (merged) as completed

marked the checklist item turris/sentinel/minipot#56 (closed) as completed

assigned to @kkoci and unassigned @mhanak

added Sentinel label

changed the description

added Review label and removed To Do label

This is going to be moved to Turris OS 6.0. It seems like all the stuff is prepared and done, but it is not part of our distribution, which is not a big deal, but there are some changes which require to be done on the server-side, and I am afraid that's too late to get it into Turris OS 5.2.

No way! This is crucial part of %Turris OS 5.3.0

Sentinel team counts with that AFAIK

@jschlehofer I totally agree with @vmyslivec. This move would cost lives since many server components are prepared for this and progress is stalled.

My bad I was ill a week ago so I was not able to react immediately.

In that case, I was told something different. Now, I wonder, why minipot is not updated in our distribution? Whom should I urge about that?

Maybe @kkoci since he replaced the To Do tag with Review (so there should be theoretically some MR somewhere)?? Definitely someone from the distribution team.

Maybe there was a lack of communication form our side. But we discussed this in person, you also took part in the internal discussion about it and this issue was clearly marked with %Turris OS 5.3.0 milestone.. so if there was something we did wrong, let's tell us so we can do better next time

The version 2.2.0 is now released (thansk to @jschlehofer) so most of this issue is resolved. The only thing missing is turris/ansible!357 and so I am passing this to author of changes in that merge request.

linked merge request is a server update that would be merged along with the final %Turris OS 5.3.0 release. On top of that, I am not aware that @ljelinek is the author of any commit there

Oh.. sory. It was all you and Martin so you should be the owner.

I closed it already as it was updated by @jschlehofer

One tick was missing.. so I removed it..

changed milestone to %Turris OS 6.0

changed milestone to %Turris OS 5.3.0

mentioned in merge request !819 (merged)

assigned to @ljelinek and unassigned @kkoci

closed

assigned to @kkoci and unassigned @ljelinek

assigned to @vmyslivec and unassigned @kkoci

removed Review label

assigned to @jschlehofer and unassigned @vmyslivec

removed Blocked label

changed the description