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.00 to 09.30 PT, Wednesday, February the 12th.
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-666
-
Getting issue details...
STATUS
Planned end: Feb/14/2020
-
RFC-669
-
Getting issue details...
STATUS
Planned end: Feb/14/2020
| - RFC-620 - waiting for Mario to upload final version. Leanne re-pinged him today
- RFC-660
- WOM - added note to this.
- WOM - Is there more to do or do we release this for now ?
- DMCCB agreed to change the status to board Recommend
- RFC-666
- RFC-669
- Acceptance tests for LSE-61
|
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/12/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: Mar/31/2020
| - RFC-665: Leanne Guy will have a look today
- RFC-662: on agenda for face 2 face
- RFC-653: changes are already done in the code
- RFC-638: is quite old
- extended after the algorithm workshop, March 31st.
|
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
| - Still under investigation, if there is some wor to do.
- An open ticket is related to it.
|
RFCs adopted since last CCB (to review, no action required) | -
RFC-664
-
Getting issue details...
STATUS
-
RFC-667
-
Getting issue details...
STATUS
-
RFC-668
-
Getting issue details...
STATUS
|
|
RFCs implemented (or withdraw) since last CCB (to review, no action required) | -
RFC-667
-
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?
| The community post on 20.0.0 should be just to clarify the timeline, and the release community post to be done more close to the start of the activity. |
Monitor Jira issues status: - the most forgotten 10 DM issues
- (resolution = Unresolved ORDER by updated asc)
| Support to J. Swinbank monitoring activity - -
DM-7353
-
Getting issue details...
STATUS
-
DM-7357
-
Getting issue details...
STATUS
-
DM-7440
-
Getting issue details...
STATUS
-
DM-7443
-
Getting issue details...
STATUS
-
DM-7148
-
Getting issue details...
STATUS
-
DM-7475
-
Getting issue details...
STATUS
-
DM-7522
-
Getting issue details...
STATUS
-
DM-7537
-
Getting issue details...
STATUS
-
DM-5461
-
Getting issue details...
STATUS
-
DM-3845
-
Getting issue details...
STATUS
3936 unresolved issues (3931 on February the 12th) | - DM-7440: Still a desirable Qserv change, but low priority.
- DM-7443: Good idea. Low priority.
- DM-7148: Should be an Architecture ticket. Reassigned. Seems low priority.
- DM-5461: A SQuaRE issue. Still seems relevant.
|
Open Actions |
|
|
AOB |
| |
Next DM-CCB | February the 19th(?) | Feb. 19th. |
Pending Flagged RFCs
Pending Proposed RFCs
Oldest issues
Meeting outcome
Pending DMCCB Actions