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, January the 1st 2021.


Attendees

Regrets

  • TBD

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-749 - Getting issue details... STATUS Planned end: Jan/08/2021
  • RFC-748 - Getting issue details... STATUS Planned end: Jan/08/2021
  • RFC-747 - Getting issue details... STATUS Planned end: Jan/12/2021
  • RFC-741 - Getting issue details... STATUS Planned end: Nov/25/2020
  • RFC-695 - Getting issue details... STATUS Planned end: Jan/31/2021
  • RFC-749: Board Recommend.
  • RFC-747: seems fine. KT is OK with it.
    • To Board Recommend.
  • RFC-741: waiting to sign up from NCSA
    • End Date to updated
    • Michelle and Jim working on it
  • RFC-695 end of January
  • RFC-748: CCB agreed
    • we could have a 21.1 to deprecate and then remove from the 22.0
    • Jim to comment in it
Board Recommended RFCs
  • RFC-699 - Getting issue details... STATUS
  • RFC-737 - Getting issue details... STATUS

Adopted but not implemented LDM RFCs (only document RFCs)


Proposed RFCs

(to review, do not require DMCCB approval)

  • RFC-746 - Getting issue details... STATUS Planned end: Feb/1/2021
  • RFC-745 - Getting issue details... STATUS Planned end: Jan/6/2021
  • RFC-744 - Getting issue details... STATUS Planned end: Jan/26/2021
  • RFC-638 - Getting issue details... STATUS Planned end: Jun/7/2021
  • RFC-746 is not DM, but DM should comment on it
  • RFC-745: compute budget may be affected
    • Yusra and Jim should comment

Adopted RFCs without Triggering issues

(to create implementing DM issues)

  • RFC-709 - Getting issue details... STATUS
    • Waiting for LCR-2543

RFC-709 will be discussed today at project CCB with the LCR

Adopted RFCs with all triggered work COMPLETED

(to set status as 'IMPLEMENTED')



RFCs adopted since the last DMCCB

(to review, no action required)

  • RFC-743 - Getting issue details... STATUS
  • RFC-742 - Getting issue details... STATUS

RFCs implemented (or withdraw) since the last DMCCB

(to review, no action required)

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


Releases

  • Planned
  • Changes to the release schedule
  • Release 21.0.0
    • Completed
  • Next planned Release 22.0.0
    • Spring 2021
  • Patch releases
    • None requested at the moment
  • 22.0.0 to be planned in May, to start in 3 months (March)
  • 21.1.0 eventually in the context of the filter work (RFC-748). Not a formal request yet.

Monitor Jira issues status:

  • the most forgotten 10 DM issues
    • (resolution = Unresolved ORDER by updated asc)
  1. DM-512 - Getting issue details... STATUS
  2. DM-2085 - Getting issue details... STATUS
  3. DM-2901 - Getting issue details... STATUS
  4. DM-2090 - Getting issue details... STATUS
  5. DM-295 - Getting issue details... STATUS
  6. DM-1747 - Getting issue details... STATUS
  7. DM-4792 - Getting issue details... STATUS
  8. DM-2685 - Getting issue details... STATUS
  9. DM-5136 - Getting issue details... STATUS
  10. DM-736 - Getting issue details... STATUS

4040 unresolved issues (3999 on December the 16th)

5136: Qserv perf. tuning parameter recommendation; to be investigated during scale testing

Open Actions

AOB


Image data to ingest in Gen2 and Gen3 at NCSA.

Next DM-CCB January 13th


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
25 Apr 2024Frossie EconomouDMCCB#197 (2024 - 04 - 14)