)]}'
{
  "commit": "2a6112ea9ab698714c6b4e92ddb829e2d4574a7c",
  "tree": "c4af3e2df64acb98628af4f675d2160622c21423",
  "parents": [
    "27df725179045a2e91a34eb91e29e52d0fe5f663"
  ],
  "author": {
    "name": "Clark Boylan",
    "email": "clark.boylan@gmail.com",
    "time": "Fri May 12 10:16:33 2017 -0700"
  },
  "committer": {
    "name": "Clark Boylan",
    "email": "clark.boylan@gmail.com",
    "time": "Fri May 12 10:16:33 2017 -0700"
  },
  "message": "Document testing of new devstack features\n\nAt the Boston 2017 Summit I had mentioned that the pattern of using non\nvoting/experimental jobs was not working for getting new features into\nDevstack. It is slow and leads people to being too conservative when it\ncomes to pushing new things in. Instead I suggested that since Devstack\nchanges are self testing we add the features, have change that enables\nthe feature, and if that changes passes we move forward with merging\n(assuming code review is fine and necessary communication is done).\n\nDocument this process in the HACKING file so that we have something we\ncan point to when people want to add a new experimental job for every\nnew little thing (ipv6, tls, systemd, etc).\n\nChange-Id: I5190cc3d3de4e81d52748347306133b5034d5531\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "b76cb6c4a7a9f81f77edb8279b584ea5e5a2bfd4",
      "old_mode": 33188,
      "old_path": "HACKING.rst",
      "new_id": "fc67f09a7b48895e556808e765268f97be502de2",
      "new_mode": 33188,
      "new_path": "HACKING.rst"
    }
  ]
}