CCB Notes
Flagged RFCs
(To be approved by the DMCCB)
Planned end: Apr/21/2021
Planned end: July/31/2021
804 - awaiting Jim
771 - Awaiting Gregory Dubois-Felsmann
783 - tim working on it - some code to review , backward compatability of property set needs some thought. KT may have counter proposal still
813 - Cristián Silva to comment
Proposed RFCs
(to review, do not require DMCCB approval)
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 the last DMCCB
(to review, no action required)
803 - Friday
RFCs implemented (or withdrawn) since the last DMCCB
(to review, no action required)
Releases
- Planned
- Changes to the release schedule
- Next planned Release 23.0.0:
- Backport requested for
, but it requires a followup ticket for backwards compatibility. (You can't make warps from old calexps if using PsfWcsSelectimagesTask) From a v23 perspective, must backport both or neither. From DP0.2 perspective, if both backported, need only this ticket for step1. DP0.2 plan was to backport this , build rc4 today and kick off pilot runs over the weekend make up time (we are 1 week behind.)
- Release process requires manually tagging ci_*. I went through K-T's list of DM Auxilliaries and looks like I should be manually tagging the ap_verify_* repos (which look like they've have updated after w_2021_40). OK?
One backport needed is not backward compatible - needed for QA .
There will be a compatibility fix next week which will need to be back ported.
All seem to agree this is ok.
This would be an RC5 - but not need a pilot run since. The backward compatibility code should carry a depricate in N years note.
Codekit will not move existing tags it was about to set.
Monitor Jira issues status:
- the most forgotten 10 DM issues
- (resolution = Unresolved ORDER by updated asc)
Unresolved issues: 4204
