Skip to end of metadata
Go to start of metadata

Location

BrowserRoom SystemPhone Dial-in
https://bluejeans.com/761546516/
  1. Dial: 199.48.152.152 or bjn.vc
  2. 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, September the 23rd.


Attendees

Regrets

DMCCB Meeting Goals

  • See DMCCB responsibilities listed in LDM-294 section 7.4

DMCCB Additional Resources

Discussion Items

ItemDescription

CCB Notes

Flagged RFCs

(To be approved by the DMCCB)

  • RFC-709 - Getting issue details... STATUS Planned end Jul/24/2020
  • RFC-699 - Getting issue details... STATUS Planned end: Oct/30/2020
  • RFC-695 - Getting issue details... STATUS Planned end: Sep/30/2020
  • RFC-709
    • Leanne: No progress yet
  • RFC-699, due date in the future
  • RFC-695, due date in the future
Board Recommended RFCs

Adopted but not implemented LDM RFCs (only document RFCs)
  • RFC-710 - Getting issue details... STATUS
    • waiting for LCR-2643 to finish

Proposed RFCs

(to review, do not require DMCCB approval)

  • RFC-729 - Getting issue details... STATUS Planned end: Sep/25/2020
  • RFC-727 - Getting issue details... STATUS Planned end: Sep/30/2020
  • RFC-726 - Getting issue details... STATUS Planned end: Sep/30/2020
  • RFC-723 - Getting issue details... STATUS Planned end: Aug/31/2020
  • RFC-638 - Getting issue details... STATUS Planned end: Jun/7/2021
  • RFC-729: CCB agree to flag it and board recommend  on the due date
  • RFC-727
    • KT comment on it
  • RFC-726
    • due date in the future
  • RFC-723
    • ongoing

Adopted RFCs without Triggering issues

(to create implementing DM issues)

  • RFC-710 - Getting issue details... STATUS (waiting for LCR-2643)
  • RFC-697 - Getting issue details... STATUS

Adopted RFCs with all triggered work COMPLETED

(to set status as 'IMPLEMENTED')



RFCs adopted since the last DMCCB

(to review, no action required)

  • RFC-703 - Getting issue details... STATUS

RFCs implemented (or withdraw) since the last DMCCB

(to review, no action required)

  • RFC-364 - Getting issue details... STATUS
  • RFC-718 - Getting issue details... STATUS


Releases

  • Planned
  • Changes to the release schedule
  • Next planned Release 21.0.0
    • Tentative schedule: November 2020
  • DM-DAX-12 milestone may be on the critical path
    • Leanne Guy  organizing a test plan to test Gen3 availability and announce it in the release. Action from the DMLT vF2F.  DM-26798 - Getting issue details... STATUS
    • John Swinbank should we block the Science Pipeline release if the test plan shows we are not ready?
      • The acceptance test is done after the  release is closed
      • Tim Jenness Gen 3 is going to be in the release, the important thing is what are we communicating to the users: is ready to use or not? The developers are going to use weekly anyway.
      • Leanne Guy Stack CLub is using releases and not weeklies and they will start using Gen3 as soon as it is announced.
    • The release seems to be decoupled from DMX-12. The content of the release note will be accordingly to the available functionality
    • Kian-Tat Lim  are we going to accept Gen2 bugs?
  • Gabriele Comoretto Create community post in preparation for the release and list pending issues to the next DMCCB  

Monitor Jira issues status:

  • the most forgotten 10 DM issues
    • (resolution = Unresolved ORDER by updated asc)

Support to J. Swinbank monitoring activity.

  1. DM-9222 - Getting issue details... STATUS
  2. DM-9221 - Getting issue details... STATUS
  3. DM-9213 - Getting issue details... STATUS
  4. DM-9212 - Getting issue details... STATUS
  5. DM-8651 - Getting issue details... STATUS
  6. DM-8243 - Getting issue details... STATUS
  7. DM-7658 - Getting issue details... STATUS
  8. DM-9878 - Getting issue details... STATUS
  9. DM-9138 - Getting issue details... STATUS
  10. DM-9889 - Getting issue details... STATUS

3954 unresolved issues (3935 on September the 16th)

  • DM-9222: Still an issue. Low priority. Added comment.
  • DM-9221: Still an issue. Low priority. Added comment.
  • DM-9212: Still an issue. Hard to prioritise: important, but never going to be critical. For now, Tim and I both commented, so it'll at least leave the DM-CCB alone.
  • DM-8251: Still an issue. Low priority. Added comment.
  • DM-7658: Still an issue. Low priority. Added comment. 
Open Actions


AOB



Next DM-CCB September 30th.


Pending Flagged RFCs

Key Summary
Loading...
Refresh

Pending Proposed RFCs

Key Summary
Loading...
Refresh

Oldest issues

Key Summary
Loading...
Refresh

Meeting outcome


Pending DMCCB Actions

DescriptionDue dateAssigneeTask appears on
John SwinbankDMCCB#64 (2020 - 09 - 16)
  • John Swinbankwrite a text to clarify when an RFC need to flag (DM-25191)
John SwinbankDMCCB#51 (2020 - 05 - 27)
  • Tim Jenness  to write a policy on how external code written by DM shall be handled.
Tim JennessDMCCB#51 (2020 - 05 - 27)



  • No labels