Community
Participate
Working Groups
RFC 165 is proposing a set of enhancements to configuraiton admin. These enhancements depend on the coodinator being proposed in RFC 160 (bug 329685).
Assigning to John, Marking for M5. Not sure this will make it in time for M4.
Out of plan, RFC is delayed.
Do we need a separate bug for RFC 144 or should we simply roll that up into this one and do them both at the same time?
(In reply to comment #3) > Do we need a separate bug for RFC 144 or should we simply roll that up into > this one and do them both at the same time? A new bug should be opened for RFC 144. RFC 144 is getting stable and is a smaller change which we should do separately from the RFC 165 changes.
RFC 165 has not been approved and will not be included in the R4.3 compendium release. Consequently, this will not be in Juno. I will leave this open for possible inclusion in a future release.
A new implementation of CM has been released to master that implements the CM version 1.5 specification. This includes RFC 165.