Clarify ownership of GDB pretty printers

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Server Programmability
    • SP Prioritized List
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The ownership model for the pretty printers and their infrastructure is not well-understood or codified correctly in codeowners. For example, the bulk of our custom pretty printers are implemented in buildscripts/gdb/mongo_printers.py which is currently owned by Devprod Build. In reality, while Build should own the infrastructure that is responsible for allowing gdb to load the pretty printers, server teams should be responsible for the correctness of the printers' implementations. .gdbinit is notably unowned as discussed first in SERVER-103201.

      Reorganize the pretty printer implementation files and their codeowners so that each pretty printer is owned by the team that owns the object it prints (e.g. SP for BSONObj, Replication for OplogEntry, etc.). Assign any infrastructural files to appropriate devprod teams.

            Assignee:
            Unassigned
            Reporter:
            James Bronsted
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: