DMCCB#37 (2020 - 01 - 15)

• RFC-620 - Getting issue details... STATUS Planned end: Jan/15/2020

• Leanne Guy : Discussions happened during the last weeks, but still, the new version including the comments is still missing.
• John Swinbank : ask KT and Wil to review the last update, to get a sign off from the sizing team
• Leanne Guy suggest having an additional week for discussion

• RFC-638 - Getting issue details... STATUS Planned end: Jan/31/2020
• RFC-648 - Getting issue details... STATUS Planned end: Dec/13/2019
• RFC-650 - Getting issue details... STATUS Planned end: Dec/13/2019
• RFC-651 - Getting issue details... STATUS Planned end: Jan/22/2020
• RFC-652 - Getting issue details... STATUS Planned end: Jan/22/2020
• RFC-653 - Getting issue details... STATUS Planned end: Jan/08/2020
• RFC-655 - Getting issue details... STATUS Planned end: Jan/17/2020
• RFC-656 - Getting issue details... STATUS Planned end: Jan/16/2020
• RFC-658 - Getting issue details... STATUS Planned end: Jan/20/2020
• RFC-659 - Getting issue details... STATUS Planned end: Jan/22/2020

• Kian-Tat Lim working on RFC-648, RFC-650, and RFC-653
• RFC-651 and RFC-652 will be flagged as soon as a documents are ready to review
  • DMCCB will not be involved until the document to approve 
  • Colin Slater is not in favor of RFC-651
• RFC-655 will probably be withdraw
• RFC-656 no action
• RFC-658 
  • John Swinbank  this package is not of interest of the community, just internal
  • It should not be a lsst_distrib 
  • this should be a deliverable to T&S
  • It would be OK to add to the lsst_ci
  • add the meta package to the Jenkins build like lsst_ts...
    • Tim Jenness to comment on the RFC-658 with the 2 alternatives
• RFC-659
  • The depreciation procedure should be updated. The proposal seems reasonable.
  • Kian-Tat Lim  should give the final sign up.

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

• 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-20572 - Getting issue details... STATUS
    • DM-20573 - Getting issue details... STATUS
    • DM-21207 - Getting issue details... STATUS
    • DM-21711 - Getting issue details... STATUS
    • DM-22114 - Getting issue details... STATUS
    • DM-22192 - Getting issue details... STATUS
    • DM-22233 - Getting issue details... STATUS
    • DM-23076 - Getting issue details... STATUS
• Do we need a 19.0.1 patch?
  • so far no RFC open
    • see   DM-22703 - Getting issue details... STATUS  and related discussion

• Tim Jenness updated the environment
  
  • the lsst_distrib works, but mathplotlib can't be updated
  • Tim Jenness lsst_sims is broken, need to be fixed
  • John Swinbank  says this policy is not written, need to check with Andrew Connolly
    • John Swinbankto talk to Andrew Connolly  on who updates sims
  • Wil O'Mullane  we should ask Chuck, since sims is paid by commissioning team
• 20.0.0 available end of May 2020
  • blockers to be done by the beginning of May
  • new functionalities?
  • John Swinbank releases are not tight to functionalities, but functionalities will be merged when ready
  • Wil O'Mullane which functionalities we need for commissioning at the end of the year? The May release should have enough of Gen3?
  • We can do the May release in any case, and then we do other minors or patch releases as required.
• Potential 19.0.1:
  • it doesn't seem worth.
    • DM-22703 to be closed as won't fix

Support to J. Swinbank monitoring activity

From Previous week:

• DM-6571 - Getting issue details... STATUS  John Swinbank proposes to relate it to next release
• DM-6602 - Getting issue details... STATUS   John Swinbankproposes to close it as "won't fix”, on the basis that LDM-472 is obsolete. We should also officially mark LDM-472 as obsolete. But we should discuss all this with Wil O'Mullane before doing so.

New list:

1. DM-5000 - Getting issue details... STATUS  
2. DM-6146 - Getting issue details... STATUS
3. DM-6632 - Getting issue details... STATUS
4. DM-6075 - Getting issue details... STATUS
5. DM-5067 - Getting issue details... STATUS
6. DM-6649 - Getting issue details... STATUS
7. DM-6386 - Getting issue details... STATUS
8. DM-6659 - Getting issue details... STATUS
9. DM-6355 - Getting issue details... STATUS
10. DM-6664 - Getting issue details... STATUS

3936 unresolved issues (3771 on January the 8th)

• DM-6571
  • just to be mentioned to the release note
    • John Swinbank block release 21 on dm-6571 and ensure there is an appropriate deprecating on release 20
• DM-6602
  • There should be an RFC to make LDM-472 obsolete
    • Wil O'Mullaneto look at LDM-472 to ensure it is really obsolete and open an RFC to mark it as obsolete
• DM-5000, DM-6146: Obsolete → Won't Fix.
• DM-6632: Legit ticket, low priority, added comment.
• DM-6075: Implementation for RFC-183, which is incorrectly marked as done. Given that it's nearly four years old, and that we have to prioritize actually getting things working as opposed to polishing architecture, I (John Swinbank ) don't think we should devote effort to this ticket. However, since the RFC was legitimately adopted, I don't think we can just close this. Added comment.
  • Kian-Tat Lim to assess DM-6075
• DM-5067: Obsolete; closed as Invalid.
• DM-6649: Nice idea, if we had lots of time. As it is, Won't Fix.
• DM-6386: We won't devote resources just to writing unit tests, although obviously we'll add them as appropriate during the course of development. Closing this as Won't Fix.
• DM-6659: This is an installation problem that is 3.5 years old, and hasn't seen further complaints. Closing this as Won't Fix until & unless it causes reproducible problems for somebody this decade.
• DM-6355: Probably still valid. Added a query to the ticket.
• DM-6664: Presumably still valid, but low priority. Added comment.

Leanne Guy  new RFC will be opened on parquet files