Comment 8 for bug 2061217

Revision history for this message
Christian Ehrhardt  (paelzer) wrote (last edit ):

To update everyone on what makes this case special, we discussed this today in the MIR meeting [1].

While everyone would have appreciated if all of this would just have happened 2 months ago that is not where we are right now and this isn't complaining - in fact we thank Alberto and CPC for picking it up at all. But due to that we are in a special situation where not-accepting it seems worse (due to the old python-boto it replaces being discontinued and outdated and incompatible) than accepting this with the requirements that we can make happen in the next few hours (see the review above).

Due to that, while no one was happy or super satisfied - we voted unanimously to allow this to be promoted in noble to demote python-boto in the same action.

The security review that we require is not expected to fit in the remaining time before the release and much less before RC images. Therefore it will be scheduled as if there would be no special urgency (usually completing in 2-4 weeks). Thereby it will not be a special urgent "change all other priority to complete it before the release" case which also answers @marks comment #6. No need to bring one more hard to deal with issue to Alex in this case.

Waiting with a state-change for the uploads with the tests to be in proposed and then planning a last check with the release team to not interfere with any RC builds (clearing -proposed is always good, but we want to be sure).

[1]: https://ubottu.com/meetingology/logs/ubuntu-meeting/2024/ubuntu-meeting.2024-04-16-14.32.moin.txt