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 the 6th.


Attendees

Regrets

DMCCB Meeting Goals

      • See DMCCB responsibilities listed in LDM-294 section 7.4

DMCCB Additional Resources

Discussion Items

ItemDescriptionCCB Notes

Flagged RFCs

(To be approved by the DMCCB)

  • RFC-674 - Getting issue details... STATUS Planned end: Mar/17/2020
  • Changes are done by JeffK and GCM, still to be reviewed before adopting
Board Recommended RFCs
  • RFC-689 - Getting issue details... STATUS
    • see below 19.0.1 status

Adopted but not implemented LDM RFCs (only document RFCs)

Proposed RFCs

(to review, do not require DMCCB approval)

  • RFC-690 - Getting issue details... STATUS Planned end: May/5/2020
  • RFC-688 - Getting issue details... STATUS Planned end: Apr/23/2020
  • RFC-685 - Getting issue details... STATUS Planned end: Apr/10/2020
  • RFC-680 - Getting issue details... STATUS Planned end: Apr/01/2020
  • RFC-675 - Getting issue details... STATUS Planned end: Mar/06/2020
  • RFC-652 - Getting issue details... STATUS Planned end: Jan/22/2020
  • RFC-651 - Getting issue details... STATUS Planned end: Jan/22/2020
  • RFC-638 - Getting issue details... STATUS Planned end: Apr/30/2020
  • 688
    • should result in a deprecation message in 20 release note
  • 685
    • KT
  • RFC-680
  • all other ones are long living RFCs

Adopted RFCs without Triggering issues

(to create implementing DM issues)



Adopted RFCs with all triggered work COMPLETED

(to set status as 'IMPLEMENTED')

  • RFC-682 - Getting issue details... STATUS
  • marked as implemented since it is in the new scipipe-conda-env

RFCs adopted since last CCB

(to review, no action required)

  • RFC-686 - Getting issue details... STATUS
  • RFC-679 - Getting issue details... STATUS
  • RFC-620 - Getting issue details... STATUS

RFCs implemented (or withdraw) since last CCB

(to review, no action required)

  • RFC-691 - Getting issue details... STATUS
  • RFC-687 - Getting issue details... STATUS


Releases

  • Planned
  • Changes to the release schedule
  • 19.0.1
    • is blocked on a review from Adam
  • 20.0.0
    • DM-24712 is blocking
    • if not fixed this week, we will need to wait before starting the release process
    • John Swinbank is relevant to block the release on an OSX Catalina, problem on tests? We should not block the release on this.
      • John Swinbank  check if mathplotlib can be removed from the unit test in order not to block the 20.0.0 release — conclusion is that removing matplotlib would be “a big task”; prefer not to do so if at all possible.
    • Leanne Guy suggests not to put plots in unit tests.
    • Other problems on the environment: mpich and requests for sims
      • Kian-Tat Limfind out what has t be done in order to fix the new scipipe-conda-env for 2.0.0 release (with BVan) and make a ticket

Monitor Jira issues status:

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

Support to J. Swinbank monitoring activity.

  1. DM-7790 - Getting issue details... STATUS
  2. DM-8305 - Getting issue details... STATUS
  3. DM-5459 - Getting issue details... STATUS
  4. DM-6877 - Getting issue details... STATUS
  5. DM-6721 - Getting issue details... STATUS
  6. DM-6599 - Getting issue details... STATUS
  7. DM-1507 - Getting issue details... STATUS
  8. DM-5852 - Getting issue details... STATUS
  9. DM-5853 - Getting issue details... STATUS
  10. DM-926 - Getting issue details... STATUS

3965 unresolved issues (3963 on April the 29th)

  • DM-7790: we shall be done
  • Also all the others
  • John Swinbank will close the obvious ones, and wait for Frossie to follow up.
    • DM-7790: won't fix (obsolete).
    • DM-6721: changed team, added comment.
    • DM-5459: won't fix (obsolete due to change to sphinx)
    • DM-1507: won't fix.
Open Actions

AOB

Next DM-CCB May the 13thMay the 20th.


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)