CCB Notes
Flagged RFCs
(To be approved by the DMCCB)
Planned end: Apr/21/2021
Planned end: Apr/28/2021
Planned end: May/21/2021
771 awaiting Gregory.
775 - DRP-AP discussion after this - may be a few minor points after
781 nothign yet
782 - Tim , confusion over c++ layout. KT already ok with this - others no particular opinion -board recomends
Proposed RFCs
(to review, do not require DMCCB approval)
Planned end: Jun/7/2021
Planned end: Apr/15/2021
Planned end: May/7/2021
Planned end: May/21/2021
ipv6 expensive - but entire world is not there . ESNET say 2025 ..
Adopted RFCs without Triggering issues
(to create implementing DM issues)
Adopted RFCs with all triggered work COMPLETED
(to set status as 'IMPLEMENTED')
RFCs adopted since the last DMCCB
(to review, no action required)
RFCs implemented (or withdrawn) since the last DMCCB
(to review, no action required)
Releases
- Planned
- Changes to the release schedule
- Next planned Release 22.0.0
- May 2021 / not linked to DP0.2 version
- Activity has started.
- Release notes ticket:
- Patch releases
- None requested at the moment
- release note draft out
- scarlet and new flags for is primary
- release should be there end of month
- can we update documentaiton post release ?
- docs on a branch (ask Jonathan how to make it appear)
- How to find pending deprecations ?
- e.g. in an RFC, Yusra will check them that seems to be the way.
Monitor Jira issues status:
- the most forgotten 10 DM issues
- (resolution = Unresolved ORDER by updated asc)
Unresolved issues: 3956
Jim looked at some still looking.
external pull request .. merged without ticket and nothing to refer to .. perhaps it should be in the policy (see actions)
Also external forks can not go through jenkins ..
- Kian-Tat LimNote in dev guide that PRs should use ticket branches even from outside contribs
