https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/TSC-119 tsc <p>As noted in <a href="https://lists.opendaylight.org/pipermail/release/2018-June/015341.html" class="external-link" target="_blank" rel="nofollow noopener">this thread</a>, TSDR was slow to sign off on their CSIT failures for Oxygen SR2. It took four business days for the project's PTL to speak up and sign-off. The required response time is two business days.</p> <p>TSDR is not a Managed project, and Oxygen is the last release to not use the Managed Release Model, but we're still filing a grievance to make it easier to track this later.</p> TSC-119

TSDR slow to sign-off CSIT failure for Oxygen SR2

Grievance Low Closed Done Unassigned Daniel Farrell Tue, 12 Jun 2018 21:53:05 +0000 Thu, 5 Jul 2018 16:45:43 +0000 Thu, 5 Jul 2018 16:45:43 +0000 Thu, 5 Jul 2018 00:00:00 +0000 0 2 <p>We had forgotten about the new (newly enforced?)  two day deadline for updating the spreadsheet.  We were working the issues and hoped to have them fixed before we updated the spreadsheet.  If there are other requirements on TSDR in the future we will do our best to meet them.</p> <blockquote><p>Managed Projects should be responsive over email, IRC, Gerrit, Jira and in regular meetings.</p> <p>All committers should be subscribed to their project’s mailing list and the release mailing list.</p> <p>For the following particularly time-sensitive events, an appropriate response is expected within two business days.</p> <ul> <li>RC or SR candidate feedback.</li> <li>Major disruptions to other projects where a Jira weather item was not present and the pending breakage was not reported to the release mailing list.</li> </ul> </blockquote> <p><a href="https://docs.opendaylight.org/en/latest/release-process/managed-release.html#responsiveness" class="external-link" target="_blank" rel="nofollow noopener">https://docs.opendaylight.org/en/latest/release-process/managed-release.html#responsiveness</a></p> <p>No worries, it's newly specific and new that we're tracking it. </p> <p>I just saw Abhijit's email about the Flourine middle checkpoint grievance list.  I have a prior commitment and will not be able to attend the TSC meeting.  Please accept my reasons for our lack of response as stated above.  I will review the meeting minutes and address any issues.  Thanks!</p> <p> </p> <p>No worries <a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=scottmelton" class="user-hover" rel="scottmelton">scottmelton</a>, thanks for letting us know. I think since TSDR is Self-Managed this is more docs than something we really need to do anything substantial about.</p> Development ODL Project tsdr ODL Release Oxygen SR2 Rank 0|i03fl3: