Location
Browser | Room System | Phone Dial-in |
---|
https://bluejeans.com/761546516/ | - Dial: 199.48.152.152 or bjn.vc
- Enter Meeting ID: 761546516 -or- use the pairing code
| Dial-in numbers: - +1 408 740 7256
- +1 888 240 2560 (US Toll-Free)
- +1 408 317 9253 (Alternate Number)
Meeting ID: 761546516 |
(Back to the DMCCB page)
Time
From 9.05 to 09.35 PT, Wednesday, February the 5th.
Attendees
Regrets
DMCCB Meeting Goals
- See DMCCB responsibilities listed in LDM-294 section 7.4
DMCCB Additional Resources
Discussion Items
Item | Description | CCB Notes |
---|
Flagged RFCs (To be approved by the DMCCB) | -
RFC-620
-
Getting issue details...
STATUS
Planned end: Jan/15/2020
-
RFC-660
-
Getting issue details...
STATUS
Planned end: Jan/24/2020
-
RFC-664
-
Getting issue details...
STATUS
Planned end: Feb/05/2020
-
RFC-666
-
Getting issue details...
STATUS
Planned end: Feb/14/2020
-
RFC-667
-
Getting issue details...
STATUS
Planned end: Feb/07/2020
| - RFC-620:
- Leanne Guy waiting from Mario to have more feedbacks
- Tim Jenness remembers that in order to change the requirements we need a very good reason. Trivial changes shall be addressed using VerificationElements
- Kian-Tat Lim sizing model needs to check also.
- Still requires some discussion, can't be approved
- RFC-660
- Approved.
- Tim Jenness following the approval of RFC-660 , deprecate LDM-472
- RFC-664
- DMCCB agrees with the new environment
- matplotlib will not be updated
- RFC-666
- few comments to be addressed before approving
- RFC-667
- DMCCB agrees that LDM-612 is approved
|
Board Recommended RFCs |
|
|
Adopted but not implemented LDM RFCs (only document RFCs) |
|
|
Proposed RFCs (to review, do not require DMCCB approval) | -
RFC-665
-
Getting issue details...
STATUS
Planned end: Feb/06/2020
-
RFC-663
-
Getting issue details...
STATUS
Planned end: Feb/03/2020
-
RFC-662
-
Getting issue details...
STATUS
Planned end: Feb/26/2020
-
RFC-653
-
Getting issue details...
STATUS
Planned end: Jan/08/2020
-
RFC-652
-
Getting issue details...
STATUS
Planned end: Jan/22/2020
-
RFC-651
-
Getting issue details...
STATUS
Planned end: Jan/22/2020
-
RFC-648
-
Getting issue details...
STATUS
Planned end: Dec/13/2019
-
RFC-638
-
Getting issue details...
STATUS
Planned end: Jan/31/2020
| Following RFC - RFC-648
- different ways to approach the problems.
- Tim Jenness will comment
- RFC-662
|
Adopted RFCs without Triggering issues (to create implementing DM issues) |
|
|
Adopted RFCs with all triggered work COMPLETED (to set status as 'IMPLEMENTED') | -
RFC-243
-
Getting issue details...
STATUS
|
|
RFCs adopted since last CCB (to review, no action required) | -
RFC-659
-
Getting issue details...
STATUS
-
RFC-656
-
Getting issue details...
STATUS
-
RFC-661
-
Getting issue details...
STATUS
|
|
RFCs implemented (or withdraw) since last CCB (to review, no action required) | -
RFC-656
-
Getting issue details...
STATUS
|
|
Releases - Planned
- Changes to the release schedule
| - Next planned major release 20.0.0
- Do we need a patch or unscheduled release?
| - Proposed start time beginning of May and have 20.0.0 available 15 of May (aprox)
- Kian-Tat Lim commissioning unlikely to use official releases.
|
Monitor Jira issues status: - the most forgotten 10 DM issues
- (resolution = Unresolved ORDER by updated asc)
| Support to J. Swinbank monitoring activity - From previous DMCCB#38 (canceled): -
DM-6573
-
Getting issue details...
STATUS
-
DM-5212
-
Getting issue details...
STATUS
-
DM-2126
-
Getting issue details...
STATUS
-
DM-6943
-
Getting issue details...
STATUS
-
DM-6946
-
Getting issue details...
STATUS
New: -
DM-7037
-
Getting issue details...
STATUS
-
DM-7003
-
Getting issue details...
STATUS
-
DM-6891
-
Getting issue details...
STATUS
-
DM-7181
-
Getting issue details...
STATUS
-
DM-7222
-
Getting issue details...
STATUS
-
DM-7197
-
Getting issue details...
STATUS
-
DM-7382
-
Getting issue details...
STATUS
-
DM-7361
-
Getting issue details...
STATUS
-
DM-7389
-
Getting issue details...
STATUS
-
DM-7400
-
Getting issue details...
STATUS
3931 unresolved issues (3930 on January the 29th) | - DM-6573: Still relevant, low priority, added comment.
- DM-5212: Still relevant, added comment.
- DM-6943: Won't Fix.
- DM-6946: John Gates to investigate and comment if fixed or still relevant.
- DM-7037: Still relevant, added comment.
- DM-7003: Won't Fix.
- DM-6891: Probably still relevant, added comment.
- DM-7181: Won't Fix.
- DM-7222: Won't Fix.
- DM-7197: Won't Fix.
- DM-7382: Won't Fix.
- DM-7361: Won't Fix.
- DM-7389: Still relevant, added comment.
- DM-7400: Still relevant, added comment.
Unknown User (gcomoretto) to comment on the remaining issues. |
Open Actions |
|
|
AOB |
| |
Next DM-CCB | February the 12th(?) |
|
Pending Flagged RFCs
Pending Proposed RFCs
Oldest issues
Meeting outcome
Pending DMCCB Actions
Task report
Looking good, no incomplete tasks.