Flagged RFCs
(To be approved by the DMCCB)
Planned end: Jan/15/2020
Planned end: Mar/17/2020
Planned end: Apr/07/2020
- RFC-620: no updates
- Leanne Guy to follow up on RFC-620
- RFC-674: comments agreed, waiting for some external review before moving forward
- RFC-681:
- Leanne Guy reviewed it, is good to go
- There may be some need for adjust the title
- RFC-671: WOM to put the document in Docushare - done https://docushare.lsstcorp.org/docushare/dsweb/Get/Version-64884/20200217%20LDM-142%20LSST%20Networks%20BL%20and%20Plan(1).xlsx
Proposed RFCs
(to review, do not require DMCCB approval)
Planned end: Apr/10/2020
Planned end: Apr/08/2020
Planned end: Apr/07/2020
Planned end: Apr/03/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: Mar/31/2020
- RFC-685:
- Kian-Tat Lim looking at it
- John Swinbank Merlin just points out that we could simplify the approach to have less work
- RFC-684
- should be fine
- RFC-683
- John Swinbank Merlin should retire the RFC
- a better solution should be proposed
- RFC-682
- it should not be problematic
- RFC-680
- also should be adopted
- RFC-675
- should be withdrawn and the requested library added to nublado
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
- Still no reaction
- DM-22578 Colin Slater is going to look this week
- we should not be updating the demo constantly
- The deprecation issues can be done at the last minute
- Early May remains the date to start the release
- Unknown User (gcomoretto) to create the release issues for 20.0.0
Monitor Jira issues status:
- the most forgotten 10 DM issues
- (resolution = Unresolved ORDER by updated asc)
Support to J. Swinbank monitoring activity.
3999 unresolved issues (3884 on March the 11th)
2296: Still relevant; low priority
2311: Still relevant; low priority
2378: Awaiting comment by John Gates
2860: Still relevant; moved to S20 query coverage epic
- new cfitsio requires an RFC
- John Swinbank the process should be agreed
- Kian-Tat Lim is not a change to the API, but how the API is used, no way to put deprecation
- Tim Jenness it is still a backward incompatibility, we should be able to notify this as a deprecation
- Kian-Tat Lim is worried about adding a cycle delay in this type of changes
- An RFC may collect feedbacks if we need to deprecate the change, or just
