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, October the 21st.


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-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: Oct/30/2020
  • RFC-709
    • Leanne agrees to board recommend it.
  • RFC-699 and RFC-695 due end of the month
Board Recommended RFCs

Adopted but not implemented LDM RFCs (only document RFCs)
  • RFC-710 - Getting issue details... STATUS
    • waiting for LCR-2643 to finish
  • LCR-2643 approved now, work can move forward on RFC-710
    • it requires implementation issues

Proposed RFCs

(to review, do not require DMCCB approval)

  • RFC-733 - Getting issue details... STATUS Planned end: Oct/22/2020
  • RFC-732 - Getting issue details... STATUS Planned end: Oct/22/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-733 to flag
    • Tim agreed with its implementation
    • Escalated and then board recommended
  • RFC-732
    • should be almost done
    • Tim suggests waiting until next week to approve it.
  • RFC-727 and RFC-726: not relevant for DMCCB
  • RFC-723 should be done

Adopted RFCs without Triggering issues

(to create implementing DM issues)

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

Adopted RFCs with all triggered work COMPLETED

(to set status as 'IMPLEMENTED')

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

RFCs adopted since the last DMCCB

(to review, no action required)

  • RFC-730 - Getting issue details... STATUS
  • RFC-731 - Getting issue details... STATUS

RFCs implemented (or withdraw) since the last DMCCB

(to review, no action required)

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


Releases

  • Planned
  • Changes to the release schedule
  • Next planned Release 21.0.0
    • DM-22815 - Getting issue details... STATUS
    • Tentative schedule:
      • start: November 2nd
      • release available: November 20th
    • Pending blocking issues:
    • Is python 3.8 still blocked on pybind11?
  • python 3.8 will not go in the next 21.0.0 release
    • we should have a rubinenv with python 3.7
  • Blocking tickets to the resolved before the release or removed from the list
    • Yusra looking at them

Monitor Jira issues status:

  • the most forgotten 10 DM issues
    • (resolution = Unresolved ORDER by updated asc)
  1. DM-571 - Getting issue details... STATUS
  2. DM-638 - Getting issue details... STATUS
  3. DM-4852 - Getting issue details... STATUS
  4. DM-4452 - Getting issue details... STATUS
  5. DM-4040 - Getting issue details... STATUS
  6. DM-4046 - Getting issue details... STATUS
  7. DM-693 - Getting issue details... STATUS
  8. DM-5063 - Getting issue details... STATUS
  9. DM-5971 - Getting issue details... STATUS
  10. DM-9819 - Getting issue details... STATUS

3938 unresolved issues (3938 on October the 7th)

DM-638: won't fix since now doing MagicDraw VEs→Jira.

  • DM-571 won't fix


Discussion on eups:

  • we should get rid of eups
  • Jim pointed out that we need a completely new workflow
  • Tim suggests having a mixed solution
    • develop with eups
    • distribute with conda
  • Jim is skeptic
  • WOM assays we need to bring developers to a more standard solution
  • We need a story to get a practical proposal
Open Actions

AOB



Next DM-CCB October 28th.


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
  • Tim Jenness investigate astropy warnings filter for tests.
05 Oct 2022Tim JennessDMCCB#142 (2022 - 09 - 28)
  • Tim Jenness  to write a policy on how external code written by DM shall be handled.
Tim JennessDMCCB#51 (2020 - 05 - 27)



  • No labels