Difference between revisions of "Infra/tickets"
From fd.io
(→Blocking) |
(→Release) |
||
| Line 29: | Line 29: | ||
== Release == | == Release == | ||
# [https://rt.linuxfoundation.org/Ticket/Display.html?id=22183 Create new fd.io.apt.xenial.main repo] | # [https://rt.linuxfoundation.org/Ticket/Display.html?id=22183 Create new fd.io.apt.xenial.main repo] | ||
| + | # [https://rt.linuxfoundation.org/Ticket/Display.html?id=22922 Needed repos for 1606 branch cutting on 2016-05-16] | ||
== Broken == | == Broken == | ||
Revision as of 18:12, 10 May 2016
Contents
Intro
This page is to try to provide some community visibility into infra tickets while we wait to get general visibility. It intrinsically cannot be realtime ( :( ).
Prioritization Heuristic
The initial proposed Prioritization Heuristic is to bucket things into categories (in descending order of priority):
- Blocking - Things which are blocking verify/merge for a project
- New Projects: Provision new project resources, should happen by Monday after their approval
- Release - Things needed to facilitate immanent release
- Broken - Fixing other breakage
- Jira Workflow Changes
- New Services Requested - requests for new services, like OpenGrok
This is a first attempt, and should evolve and improve over time with community input
Tickets
Blocking
-
vpp-csit-verify-* endless loop fix -
JDK 8 missing for HC verify and merge jobs -
vpp-csit-verify-hw-perf-long job not working
New Projects
Release
Broken
Broken:
- Unable to open log and report html files in jenkins
- jenkins job csit-vpp-master-verify-weekly - taqgging still not working
