Flagged RFCs
(To be approved by the DMCCB)
Planned end: Jan/15/2020
Planned end: Mar/17/2020
- RFC-620
- two documents to change
- LCRs
- RFC-
Proposed RFCs
(to review, do not require DMCCB approval)
Planned end: Apr/15/2020
Planned end: Apr/10/2020
Planned end: Apr/01/2020
Planned end: Mar/06/2020
Planned end: Mar/26/2020
Planned end: Jan/22/2020
Planned end: Jan/22/2020
Planned end: Apr/30/2020
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 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
- Blocking issues open:
- Community post in preparation for the release: https://community.lsst.org/t/in-preparation-of-20-0-0-release/4031
- is RFC-686 blocking the release?
- BVan should be able to look into it and do some work before the release
- Other real work
- DM-22578
- DM-23374
- the rest should be just trivial changes that can be done at any moment.
Monitor Jira issues status:
- the most forgotten 10 DM issues
- (resolution = Unresolved ORDER by updated asc)
Support to J. Swinbank monitoring activity.
3984 unresolved issues (3999 on April the 1sr)
- DM-7960 — obsolete in Gen3? If so, let's set to Won't Fix.
- DM-7958 — as above.
- DM-7997 — closing as Won't Fix.
- DM-2996 — pure DAX issue; Fritz Mueller should comment.
- DM-7934 — Won't Fix.
- DM-8089 — Won't Fix.
- DM-8098 — seems valid; low priority; comment on ticket.
- DM-8075 — Tim (rightly) set as Won't Fix.
- DM-8170 — good idea (sufficiently good that I thought we were doing this, but I was confused).
- DM-8219 — Won't Fix, per discussion between Tim & Chris Waters.
