)]}'
{
  "log": [
    {
      "commit": "739041fb9c0018326baa55098e6d1a381e08c87c",
      "tree": "04a63d0e9fb34277f977db98a3a209078ec20bd4",
      "parents": [
        "58515edc32a704503155b18d5904c6d96261b3d0"
      ],
      "author": {
        "name": "Felipe Monteiro",
        "email": "felipe.monteiro@att.com",
        "time": "Sun Mar 25 00:24:03 2018 -0400"
      },
      "committer": {
        "name": "Felipe Monteiro",
        "email": "felipe.monteiro@att.com",
        "time": "Sat May 19 16:24:33 2018 +0100"
      },
      "message": "feature flag: Policy feature enabled config group\n\nA new configuration group ``[policy_feature_enabled]`` has been added to\nPatrole which will be responsible for collecting the feature flags to be\nused for newly introduced policies or policies that were changed in a\nbackwards-incompatible way.\n\n    * create_port_fixed_ips_ip_address_policy (Neutron)\n    * update_port_fixed_ips_ip_address_policy (Neutron)\n    * limits_extension_used_limits_policy (Cinder)\n    * volume_extension_volume_actions_attach_policy (Cinder)\n    * volume_extension_volume_actions_reserve_policy (Cinder)\n    * volume_extension_volume_actions_unreserve_policy (Cinder)\n\nThese feature flags will be supported until Pike release cycle\nis EOL.\n\nThe motivation behind these feature flags is [0] which adds\nPike/Queens gating to Patrole. However, in Queens, Neutron\nand Cinder renamed or removed a few policies in a backwards-\nincompatible way. These policies can be reviewed here: [1].\n\nThis PS requires another PS [2] in devstack\u0027s lib/tempest\nbecause Patrole, being a branchless project and hosting the\nPatrole devstack plugin itself, must fall back to Tempest\u0027s\ndevstack script to list out the backwards-incompatible\npolicies in Pike.\n\nA documentation update will also come in a follow up with\ninformation on these feature flags.\n\n[0] I76c4a9b8737bf94f230ab141def652b054120f3b\n[1] e.g. http://logs.openstack.org/51/547851/4/check/patrole-member-pike/139c534/job-output.txt.gz#_2018-03-22_21_46_08_392229\n[2] I00bdeff9474c54d38b6d6844a041b305bec01ad8\n\nChange-Id: Ia0d9847908a8e723446c16465d68cd7f622c04cc\n"
    },
    {
      "commit": "4ef7e5309c61583fb2a6e48777188aff06620227",
      "tree": "0a3c947eabf100b82d2b797c4187891efa287ef0",
      "parents": [
        "f1c6757160d89c7115fda36383f2c3846544d04e"
      ],
      "author": {
        "name": "Felipe Monteiro",
        "email": "felipe.monteiro@att.com",
        "time": "Sun Mar 11 07:17:11 2018 -0400"
      },
      "committer": {
        "name": "Felipe Monteiro",
        "email": "felipe.monteiro@att.com",
        "time": "Mon Mar 26 19:44:15 2018 +0100"
      },
      "message": "Remove already-deprecated strict_policy_check option\n\nThe option ``[patrole].strict_policy_check`` was deprecated\nduring the last release cycle (Queens). This was because the\noption could be set to False in order to skip tests which\nmight result in false positives.\n\nThis PS, then, removes strict_policy_check references in the code,\nupdates documentation, and adds a releasenote.\n\nChange-Id: I7f7eda39c0472bd3d70892c801fc4d14db0c0426\n"
    },
    {
      "commit": "b58c1197e9cbedb0713ea2342e8710d9869a1362",
      "tree": "065b7cb38206f89237925f1056c2d6a65ef02c15",
      "parents": [
        "feec999bde210930fe1e8b16bbc60c093927c608"
      ],
      "author": {
        "name": "Felipe Monteiro",
        "email": "felipe.monteiro@att.com",
        "time": "Mon Nov 20 01:50:24 2017 +0000"
      },
      "committer": {
        "name": "Felipe Monteiro",
        "email": "felipe.monteiro@att.com",
        "time": "Mon Nov 27 04:58:28 2017 +0000"
      },
      "message": "Remove deprecrated [rbac] config group\n\nThis PS removes the deprecated [rbac] config group. It was replaced\nlast release cycle with the [patrole] config group, which has\nthe exact same options. This is because [patrole] is more user-friendly\nand congruent with the project name.\n\nChange-Id: Id1a7af0445bd50f44ddcc4277f952391968726b8\n"
    },
    {
      "commit": "098a8cd057a104499bdac26140fc25f8e08e6452",
      "tree": "b316ab179b9ebe77ea14014b9febf8ed99ba8fcf",
      "parents": [
        "bb3c257f77e52bf9da2f0822d40a2a716275bd8f"
      ],
      "author": {
        "name": "Felipe Monteiro",
        "email": "felipe.monteiro@att.com",
        "time": "Wed Sep 20 21:31:27 2017 +0100"
      },
      "committer": {
        "name": "Felipe Monteiro",
        "email": "felipe.monteiro@att.com",
        "time": "Wed Oct 04 01:17:13 2017 +0000"
      },
      "message": "Auto-generate sample config file\n\nThis PS auto-generates the sample config file using\noslo-config-generator which is how every project should reliably\nproduce a config file.\n\nIn addition, the Patrole documentation was updated to link to the\ngenerated config file, so that the documentation accurately\nshows config options.\n\nChange-Id: Ib3c39084b4c2b5a0078d1293d882cf9a9050b29b\nCloses-Bug: #1709490\n"
    }
  ]
}