Location
Zoom link available on Slack channel.
(Back to the DMCCB page)
Time
From 9.00 to 09.30 PT, Wednesday, November 24th, 2021.
Attendees
Regrets
DMCCB Meeting Goals
- See DMCCB responsibilities listed in LDM-294 section 7.4
DMCCB Additional Resources
Discussion Items
Item | Description | CCB Notes |
---|
Flagged RFCs (To be approved by the DMCCB) |
RFC-771
-
Getting issue details...
STATUS
Planned end: Apr/21/2021
RFC-783
-
Getting issue details...
STATUS
Planned end: July/31/2021
RFC-804
-
Getting issue details...
STATUS
-
RFC-813
-
Getting issue details...
STATUS
| 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 |
Board Recommended RFCs | -
RFC-802
-
Getting issue details...
STATUS
|
|
| |
|
Proposed RFCs (to review, do not require DMCCB approval) | -
RFC-812
-
Getting issue details...
STATUS
|
|
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) | -
RFC-803
-
Getting issue details...
STATUS
-
RFC-814
-
Getting issue details...
STATUS
-
RFC-811
-
Getting issue details...
STATUS
| |
RFCs implemented (or withdrawn) since the last DMCCB (to review, no action required) | -
RFC-801
-
Getting issue details...
STATUS
-
RFC-245
-
Getting issue details...
STATUS
| |
|
|
|
Releases - Planned
- Changes to the release schedule
| - Next planned Release 23.0.0:
-
DM-29437
-
Getting issue details...
STATUS
- Backport requested for
DM-32649
-
Getting issue details...
STATUS
, 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)
| -
DM-13611
-
Getting issue details...
STATUS
-
DM-13085
-
Getting issue details...
STATUS
-
DM-13695
-
Getting issue details...
STATUS
-
DM-13778
-
Getting issue details...
STATUS
-
DM-13774
-
Getting issue details...
STATUS
-
DM-13802
-
Getting issue details...
STATUS
-
DM-13846
-
Getting issue details...
STATUS
-
DM-9450
-
Getting issue details...
STATUS
-
DM-13968
-
Getting issue details...
STATUS
-
DM-13857
-
Getting issue details...
STATUS
Unresolved issues: 4204 |
|
Open Actions |
|
|
AOB |
|
|
Next DM-CCB | December 8th |
|
Pending Flagged RFCs
Pending Proposed RFCs
Oldest issues
Meeting outcome
Pending DMCCB Actions
Task report
Looking good, no incomplete tasks.