)]}'
{"features.yaml":[{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"78f61b5ca41d69b4b0077e01316a24d011d54217","unresolved":false,"context_lines":[{"line_number":88,"context_line":""},{"line_number":89,"context_line":"  neutron:"},{"line_number":90,"context_line":"    base:"},{"line_number":91,"context_line":"      services: [quantum, q-svc, q-agt, q-dhcp, q-l3, q-meta, q-lbaas, q-vpn, q-fwaas, q-metering]"},{"line_number":92,"context_line":"      rm-services: [n-net]"},{"line_number":93,"context_line":"    liberty:"},{"line_number":94,"context_line":"      rm-services: [q-vpn]"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"1a4dcd0f_919c110f","line":91,"updated":"2015-08-13 15:28:51.000000000","message":"It would be ideal if services lists are a union between branches so that we can leave q-vpn out of base but then add it for kilo.  I\u0027m not sure how this works though.","commit_id":"4c62cdb5c9dada05c01f2ebce72577a8de725997"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"7bc29a1960d8adfe201c5bbb63dd3799420b8a9c","unresolved":false,"context_lines":[{"line_number":90,"context_line":"    base:"},{"line_number":91,"context_line":"      services: [quantum, q-svc, q-agt, q-dhcp, q-l3, q-meta, q-lbaas, q-fwaas, q-metering]"},{"line_number":92,"context_line":"      rm-services: [n-net]"},{"line_number":93,"context_line":"    kilo:"},{"line_number":94,"context_line":"      services: [q-vpn]"},{"line_number":95,"context_line":""},{"line_number":96,"context_line":"  swift:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"1a4dcd0f_2cc1244e","line":93,"updated":"2015-08-13 15:39:29.000000000","message":"Might need to do this for Juno as well since I don\u0027t see the sswan job filtering out juno in project-config.","commit_id":"626faaee06cc74d6ec17517aaa56c5e51c768350"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"028982e55dfa98480649ae462705d5935655ada7","unresolved":false,"context_lines":[{"line_number":90,"context_line":"    base:"},{"line_number":91,"context_line":"      services: [quantum, q-svc, q-agt, q-dhcp, q-l3, q-meta, q-lbaas, q-fwaas, q-metering]"},{"line_number":92,"context_line":"      rm-services: [n-net]"},{"line_number":93,"context_line":"    kilo:"},{"line_number":94,"context_line":"      services: [q-vpn]"},{"line_number":95,"context_line":""},{"line_number":96,"context_line":"  swift:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"1a4dcd0f_3bbf17ac","line":93,"in_reply_to":"1a4dcd0f_2cc1244e","updated":"2015-08-13 16:12:44.000000000","message":"OK, this isn\u0027t an issue for Juno per-se.  The gate-neutron-vpnaas-dsvm-functional-sswan job is not excluded from stable/juno, but apparently people aren\u0027t supposed to use the stable/juno branch for neutron-vpnaas changes since that service was still a part of neutron in juno, and gate-neutron-vpnaas-dsvm-functional-sswan is only in the experimental queue for neutron in project-config.  So while we should have a project-config change to exclude gate-neutron-vpnaas-dsvm-functional-sswan from running on stable/juno changes since it won\u0027t work, it\u0027s not blocking.","commit_id":"626faaee06cc74d6ec17517aaa56c5e51c768350"}]}