Location
Browser | Room System | Phone Dial-in |
---|
https://bluejeans.com/761546516/ | - Dial: 199.48.152.152 or bjn.vc
- Enter Meeting ID: 761546516 -or- use the pairing code
| Dial-in numbers: - +1 408 740 7256
- +1 888 240 2560 (US Toll-Free)
- +1 408 317 9253 (Alternate Number)
Meeting ID: 761546516 |
(Back to the DMCCB page)
Time
From 9.00 to 09.30 PT, Wednesday, April the 17th.
Attendees
Regrets
DMCCB Meeting Goals
- See DMCCB responsibilities listed in LDM-294 section 7.4
Discussion Items
Item | Description | CCB Notes |
---|
Flagged RFCs (To be approved by the DMCCB) |
RFC-581
-
Getting issue details...
STATUS
RFC-592
-
Getting issue details...
STATUS
| - RFC-581 still pending
- RFC-592 trivial changes
- CCB agreed to board recommend
|
Proposed RFCs (to review, do not require DMCCB approval) |
RFC-591
-
Getting issue details...
STATUS
RFC-585
-
Getting issue details...
STATUS
| - RFC-591 is on T&S
- Tim added the correct component
- This should be ignored by DMCCB
- RFC-585
- to handle via community post
- John Swinbank suggested to ask Jim Bosch to prepare a full proposal, instead of many small RFCs
|
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 since last CCB (to review, no action required) |
RFC-574
-
Getting issue details...
STATUS
RFC-589
-
Getting issue details...
STATUS
RFC-583
-
Getting issue details...
STATUS
RFC-575
-
Getting issue details...
STATUS
RFC-549
-
Getting issue details...
STATUS
RFC-573
-
Getting issue details...
STATUS
|
|
Changes to the planned releases | - 18.0 Release to be planned (no changes since last DMCCB)
| - SW release to be done by the end of the cycle
- SW release to be done for the test
- Release policy to be sorted out as soon as possible: LDM-672
|
Monitor Jira issues status: - the most forgotten 10 DM issues
- (resolution = Unresolved ORDER by updated asc)
| Support to J. Swinbank monitoring activity -
DM-1898
-
Getting issue details...
STATUS
-
DM-3202
-
Getting issue details...
STATUS
-
DM-1866
-
Getting issue details...
STATUS
-
DM-3348
-
Getting issue details...
STATUS
-
DM-3424
-
Getting issue details...
STATUS
-
DM-3487
-
Getting issue details...
STATUS
-
DM-917
-
Getting issue details...
STATUS
-
DM-809
-
Getting issue details...
STATUS
-
DM-3476
-
Getting issue details...
STATUS
-
DM-3430
-
Getting issue details...
STATUS
4169 unresolved issues (3927 on April the 3rd)
| Pre-meeting notes & suggestions from John Swinbank: - DM-1898 — Check with Fritz.
- DM-3202 — Seems like a valid request. Action on John Swinbank to ring this to the attention of Pipelines science leads.
- DM-1866 — This (and its parent epic) seem obsolete. Suggest we just shut them all down.
- DM-3348 — Probably obsolete in light of SDM-standardization. Action John Swinbank to chat with Jim Bosch& Yusra AlSayyadto make sure that they agree.
- DM-3424 — Obsolete, since we no longer use HipChat. Shut it down.
- DM-3487 — Obsolete. Shut it down.
- DM-917 — Seems like a legit request, but low priority.
- DM-809 — Not sure if this is still an issue. Certainly, it's not my impression that log4cxx has been a regular cause of build failures in the last several years; maybe we can just close this down unless it is still causing problems for Fabrice.
- DM-3476 — I'm sure this is still an issue, but it's low priority and unlikely to be scheduled any time soon..
- DM-3430 — This issue seems to basically boil down to EUPS not being resistant to a determined attempt to break it. Which is probably true, but not something I think we should spend effort on. I suggest we "Won't Fix" this.
On the DMCCB: |
AOB | | |
Pending Flagged RFCs
Pending Proposed RFCs
Oldest issues
Meeting outcome
Pending DMCCB Actions
Task report
Looking good, no incomplete tasks.