Difference between revisions of "Infra/tickets"
From fd.io
(→New Services Requests) |
(→Prioritization Heuristic) |
||
Line 11: | Line 11: | ||
# Release - Things needed to facilitate immanent release | # Release - Things needed to facilitate immanent release | ||
# Broken - Fixing other breakage | # Broken - Fixing other breakage | ||
+ | # Jira Workflow Changes | ||
# New Services Requested - requests for new services, like OpenGrok | # New Services Requested - requests for new services, like OpenGrok | ||
Revision as of 18:16, 5 May 2016
Contents
[hide]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
There are currently no blocking tickets
New Projects
Release
Broken
Broken:
- DPDK bundles incorrectly put up on nexus
- Unable to open log and report html files in jenkins
- jenkins job csit-vpp-master-verify-weekly - taqgging still not working