Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-5278

Write guide on developing long-running branches

    XMLWordPrintable

    Details

    • Type: Documentation
    • Status: Open
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: None
    • Labels:
      None

      Description

      I think it'd be valuable to have a Wiki page outlining best practices on how we should develop on long-running feature branches such as those that we have in the durable history project. Some things I'd like to see documented:

      • The preferred way to disable make check and Python tests (discussed in BUILD-9262).
      • A method of tracking failures in a feature branch. Include a template on what information to include (name, description, backtrace, error output, etc).

        Attachments

          Activity

            People

            • Assignee:
              backlog-server-storage-engines Backlog - Storage Engines Team
              Reporter:
              alex.cameron Alex Cameron
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: