I got confirmation[1] in #ubuntu-meeting today (but sadly after the MIR
team meeting ended) that libyang2 has an ACK from MIR:

<ahasenack> hi guys, I missed the meeting, can this also be set to committed? 
https://bugs.launchpad.net/ubuntu/+source/libyang2/+bug/1958293
<ahasenack> I think it's done
<ubottu> Launchpad bug 1958293 in libyang2 (Ubuntu) "[MIR]: libyang2" 
[Critical, In Progress]
<ahasenack> and https://bugs.launchpad.net/ubuntu/+source/frr/+bug/1951834 
which depended on libyang2 being acked
<ubottu> Launchpad bug 1951834 in frr (Ubuntu) "[MIR]: frr" [Critical, In 
Progress]
<ahasenack> sarnold: ^  security was the last step?
<ahasenack> or does it go back to MIR, who then decide if it's done or not?
* didrocks has quit (Quit: WeeChat 3.4)
<slyon> ahasenack: we have MIR team ACK and security team ACK on libyang2, so 
that's done. It can be "In Progress" or "Fix Comitted" depending on the change 
that pulls it into main
<slyon> ahasenack: Both those MIRs are "In Progress" (i.e. ready to be 
promoted). So you could do the seed change for frr and set both bugs to "Fix 
Committed"


Setting the bug to "fix committed".

1. https://irclogs.ubuntu.com/2022/02/22/%23ubuntu-meeting.html#t16:11

** Changed in: libyang2 (Ubuntu)
       Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958293

Title:
  [MIR]: libyang2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libyang2/+bug/1958293/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to