Data Management
Space shortcuts
Page tree
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, May 5th 2021.


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-771 - Getting issue details... STATUS Planned end: Apr/21/2021

  • RFC-775 - Getting issue details... STATUS Planned end: Apr/28/2021
  • RFC-779 - Getting issue details... STATUS Planned end: May/5/2021

771: There's a convo on dm-ccb asking Gregory to do something, but clear from just looking at the  comments

Extending 775 out a week

Board recommending 779

Board Recommended RFCs
  • RFC-777 - Getting issue details... STATUS

Adopted but not implemented LDM RFCs (only document RFCs)
  • RFC-769 - Getting issue details... STATUS



Proposed RFCs

(to review, do not require DMCCB approval)

  • RFC-638 - Getting issue details... STATUS Planned end: Jun/7/2021

  • RFC-774 - Getting issue details... STATUS  Planned end: Apr/15/2021
  • RFC-776 - Getting issue details... STATUS  Planned end: May/7/2021

People outside might be transitioning to ipv6 only and need to be able to talk to them.

 Adopted RFCs without Triggering issues

(to create implementing DM issues)



Adopted RFCs with all triggered work COMPLETED

(to set status as 'IMPLEMENTED')



RFCs adopted since the last DMCCB

(to review, no action required)

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

RFCs implemented (or withdrawn) since the last DMCCB

(to review, no action required)






Releases

  • Planned
  • Changes to the release schedule
  • Next planned Release 22.0.0
    • May 2021 / not linked to DP0.2 version
    • Activity has started.
    • Release notes ticket:  DM-29602 - Getting issue details... STATUS
  • Patch releases
    • None requested at the moment
  • Work on this has begun.
    • YA is collecting release notes
    • JC is writing the characterization report

TJ: Did you want to move to w18?

YA: Nope. JFB: If I proposed it, I'm sure negated it  in the same comment. 

TJ: Not that it matters, but why does this take a month?

YA: Takes a month to run an RC2 these days. 

TJ: Would running on the IDF be faster?

Would be faster if we had more nodes available, but not if we moved the to IDF only once every 6mo. Less human time to keep routine. 

TJ: Did I see that we're doing the test plan for v21 now? Do we have to do a test plan for v22?

YA: No, there are only milestones associated with fall releases.

JFB: If there are no milestones, and this spring release is blocked on human time, why are we doing it again?

Monitor Jira issues status:

  • the most forgotten 10 DM issues
    • (resolution = Unresolved ORDER by updated asc)
  1. DM-10836 - Getting issue details... STATUS
  2. DM-11030 - Getting issue details... STATUS
  3. DM-11055 - Getting issue details... STATUS
  4. DM-3494 - Getting issue details... STATUS
  5. DM-11062 - Getting issue details... STATUS
  6. DM-11064 - Getting issue details... STATUS
  7. DM-11063 - Getting issue details... STATUS
  8. DM-11065 - Getting issue details... STATUS
  9. DM-11066 - Getting issue details... STATUS
  10. DM-11092 - Getting issue details... STATUS

Unresolved issues: 3957



Open Actions

AOB




Next DM-CCB May 12th


Pending Flagged RFCs

Key Summary
Refresh

Pending Proposed RFCs

Key Summary
Refresh

Oldest issues

Key Summary
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)