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, April the 2nd.


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-620 - Getting issue details... STATUS Planned end: Jan/15/2020
  • RFC-674 - Getting issue details... STATUS Planned end: Mar/17/2020
  • RFC-689 - Getting issue details... STATUS Planned end: Apr/24/2020
  • RFC-620: Leanne says that it should be almost there
    • Board Recommend.
  • RFC-674: work ongoing
  • RFC-689: 
    • Tim Jenness suggested we can do the release and get a report on what the problems are, in order to get some better idea of how the problem is.
    • Gabriele Comoretto remembers that any improvement in the release process shall start from DMTN-106 and DMTN-110 unless somebody else has better proposals.
    • DMCCB outcome
      • board recommend the RFC
      • no community post
      • due date next week, including a report on what done
      • next ccb to evaluate the situation
Board Recommended RFCs



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: Apr/28/2020
  • RFC-688 - Getting issue details... STATUS Planned end: Apr/23/2020
  • RFC-687 - Getting issue details... STATUS Planned end: Apr/22/2020
  • RFC-686 - Getting issue details... STATUS Planned end: Apr/15/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-662 - Getting issue details... STATUS Planned end: Mar/26/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
  • RFC-686: Bvan should adopt it
  • RFC-682: seems OK, board recommend

Adopted RFCs without Triggering issues

(to create implementing DM issues)



Adopted RFCs with all triggered work COMPLETED

(to set status as 'IMPLEMENTED')

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

RFCs adopted since last CCB

(to review, no action required)



RFCs implemented (or withdraw) since last CCB

(to review, no action required)



Releases

  • Planned
  • Changes to the release schedule
  • Next planned major release 20.0.0
    • Planned for Spring 2020
      DM-20564 - Getting issue details... STATUS

    • Blocking issues open:
      • DM-20565 - Getting issue details... STATUS
      • DM-20573 - Getting issue details... STATUS
      • DM-21711 - Getting issue details... STATUS
      • DM-22192 - Getting issue details... STATUS
      • DM-22233 - Getting issue details... STATUS
      • DM-22578 - Getting issue details... STATUS
      • DM-23076 - Getting issue details... STATUS
        • This issue will become obsolete assuming RFC-687 passes.
      • DM-23343 - Getting issue details... STATUS
      • DM-23369 - Getting issue details... STATUS
      • DM-23374 - Getting issue details... STATUS
        • This is blocking on DM-24439 (effectively, removing lsst.daf.persistence.DbAuth). We've not had feedback from the Sims team about how much of a problem that would be for them.
      • DM-23380 - Getting issue details... STATUS
      • DM-23651 - Getting issue details... STATUS
  • Community post in preparation for the release:  https://community.lsst.org/t/in-preparation-of-20-0-0-release/4031
  • Tim Jenness Some of the blocking tickets may be moved to the  n ext major release.
  • John Swinbank will go through the list and resolve the ones that are trivial
  • Colin Slater has been working on the new stack demo
  • Tim Jenness  we shall start May the 4th, the first Monday of May.


Monitor Jira issues status:

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

Support to J. Swinbank monitoring activity.

  1. DM-5236 - Getting issue details... STATUS
  2. DM-5234 - Getting issue details... STATUS
  3. DM-6539 - Getting issue details... STATUS
  4. DM-5225 - Getting issue details... STATUS
  5. DM-8250 - Getting issue details... STATUS
  6. DM-8262 - Getting issue details... STATUS
  7. DM-8198 - Getting issue details... STATUS
  8. DM-8218 - Getting issue details... STATUS
  9. DM-8257 - Getting issue details... STATUS
  10. DM-8269 - Getting issue details... STATUS

3967 unresolved issues (3984 on April the 15th)

  • DM-5225: Frossie has commented; still an active issue.
  • DM-8262: Legit feature request. Not clear we actually want to act on it. Tim & John have both commented.
  • Everything else is now closed.
Open Actions

AOB

Next DM-CCB April the 29th


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