)]}'
{"reference/projects.yaml":[{"author":{"_account_id":9656,"name":"Ihar Hrachyshka","email":"ihrachys@redhat.com","username":"ihrachys","status":"Red Hat Networking Systems Engineer"},"change_message_id":"31203e8fb4f57986f5064e4c6dea42d4e9b244fd","unresolved":false,"context_lines":[{"line_number":2476,"context_line":"        - release:cycle-with-intermediary"},{"line_number":2477,"context_line":"        - stable:follows-policy"},{"line_number":2478,"context_line":"        - type:service"},{"line_number":2479,"context_line":"        - starter-kit:compute"},{"line_number":2480,"context_line":"        - vulnerability:managed"},{"line_number":2481,"context_line":"        - assert:follows-standard-deprecation"},{"line_number":2482,"context_line":"    neutron-lbaas:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"9abb7d3a_17017c06","line":2479,"updated":"2016-06-01 09:17:24.000000000","message":"now that we are in the business of dropping tags from *aas subprojects, I think it\u0027s wise to drop starter-kit too since those plugins are not essential for a cloud that is used to \"put a persistent VM on the network\" [1], neither they prove upgradability.\n\n[1] https://governance.openstack.org/reference/tags/starter-kit_compute.html","commit_id":"3055818232dc4094218486c5b0bb23e19ec689e0"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"c552a9e6cc0de5e75da47b1780e3eef727623195","unresolved":false,"context_lines":[{"line_number":2476,"context_line":"        - release:cycle-with-intermediary"},{"line_number":2477,"context_line":"        - stable:follows-policy"},{"line_number":2478,"context_line":"        - type:service"},{"line_number":2479,"context_line":"        - starter-kit:compute"},{"line_number":2480,"context_line":"        - vulnerability:managed"},{"line_number":2481,"context_line":"        - assert:follows-standard-deprecation"},{"line_number":2482,"context_line":"    neutron-lbaas:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"9abb7d3a_5c4dca98","line":2479,"in_reply_to":"9abb7d3a_17017c06","updated":"2016-06-01 16:49:38.000000000","message":"I thought about it but I didn\u0027t want to conflate too many changes in one patch. The upgrade ones seems the least controversial because of lack of empirical evidence the drop is impossible to argue against.","commit_id":"3055818232dc4094218486c5b0bb23e19ec689e0"},{"author":{"_account_id":5263,"name":"Jeremy Stanley","display_name":"fungi","email":"fungi@yuggoth.org","username":"fungi","status":"missing, presumed fed"},"change_message_id":"d9ca0405a5055e1af5ad36fee705e84b9ff0b251","unresolved":false,"context_lines":[{"line_number":2477,"context_line":"        - stable:follows-policy"},{"line_number":2478,"context_line":"        - type:service"},{"line_number":2479,"context_line":"        - starter-kit:compute"},{"line_number":2480,"context_line":"        - vulnerability:managed"},{"line_number":2481,"context_line":"        - assert:follows-standard-deprecation"},{"line_number":2482,"context_line":"    neutron-lbaas:"},{"line_number":2483,"context_line":"      repos:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"9abb7d3a_f68dba31","line":2480,"updated":"2016-06-01 17:29:35.000000000","message":"Armando: I\u0027m unsure what \"contract\" you\u0027re referring to, but the VMT were not consulted on change I2aa729d1b4278743a5e99b41178dc2d11b3e1348 which applied vulnerability management to additional Neutron project repos besides openstack/neutron and openstack/python-neutronclient (though I did speak out against the change in subsequent TC meetings after it merged). The VMT has been trying to decide between a resolution reintroducing repo-specific tags or proposing splitting the neutron deliverable into multiple deliverables so that we can get back to the original vulnerability:managed coverage intent. Since this change is already proposing the latter, it seemed appropriate to include the vulnerability management coverage difference as well to give it further weight.\n\nWhile the VMT may have been consulted on a neutron-lbaas suspected vulnerability report, we haven\u0027t to date issued any official security advisories for vulnerabilities in it or the other Neutron advanced services repos and have conveniently not needed to directly address the difference between this governance implementation detail and reality up to now. In retrospect it would have probably been better to just state outright that openstack/neutron-lbaas wasn\u0027t intended to have VMT coverage in https://launchpad.net/bugs/1549981 where instead we focused on the technical reasons why it wouldn\u0027t qualify for an advisory, so I\u0027m sorry if that gave a false impression of coverage for the repo itself.","commit_id":"3055818232dc4094218486c5b0bb23e19ec689e0"},{"author":{"_account_id":5263,"name":"Jeremy Stanley","display_name":"fungi","email":"fungi@yuggoth.org","username":"fungi","status":"missing, presumed fed"},"change_message_id":"3d5e10992fa51bd16b0741e7e274694c5a059e98","unresolved":false,"context_lines":[{"line_number":2477,"context_line":"        - stable:follows-policy"},{"line_number":2478,"context_line":"        - type:service"},{"line_number":2479,"context_line":"        - starter-kit:compute"},{"line_number":2480,"context_line":"        - vulnerability:managed"},{"line_number":2481,"context_line":"        - assert:follows-standard-deprecation"},{"line_number":2482,"context_line":"    neutron-lbaas:"},{"line_number":2483,"context_line":"      repos:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"9abb7d3a_7eaa4b86","line":2480,"updated":"2016-06-01 14:52:17.000000000","message":"Oh, I probably should cite I1260839b50b6a5ff57a6649e419094f2d4f7f877 and I2aa729d1b4278743a5e99b41178dc2d11b3e1348 for relevant historical evidence of this too.","commit_id":"3055818232dc4094218486c5b0bb23e19ec689e0"},{"author":{"_account_id":5263,"name":"Jeremy Stanley","display_name":"fungi","email":"fungi@yuggoth.org","username":"fungi","status":"missing, presumed fed"},"change_message_id":"8733000df8e834b48b31a612d6bcafdee32ffd7a","unresolved":false,"context_lines":[{"line_number":2477,"context_line":"        - stable:follows-policy"},{"line_number":2478,"context_line":"        - type:service"},{"line_number":2479,"context_line":"        - starter-kit:compute"},{"line_number":2480,"context_line":"        - vulnerability:managed"},{"line_number":2481,"context_line":"        - assert:follows-standard-deprecation"},{"line_number":2482,"context_line":"    neutron-lbaas:"},{"line_number":2483,"context_line":"      repos:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"9abb7d3a_384d7b9a","line":2480,"updated":"2016-06-01 14:32:20.000000000","message":"While this hasn\u0027t come up yet officially (mainly because no security vulnerabilities have been reported for the Neutron \"advanced services\"), the vulnerability:managed tag started out as a per-repo tag applied only to the openstack/neutron repo. When the TC moved to create the concept of deliverables and make tags deliverable-specific, this had the net effect of applying vulnerability:managed to additional repos beyond the original intended scope. Now that these other repos are being split back out of the deliverable, I think this is an appropriate opportunity to make it clearer that the VMT was only intending to handle reported vulnerabilities for the openstack/neutron repo.","commit_id":"3055818232dc4094218486c5b0bb23e19ec689e0"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"7d70aa50bfd375a66c76914ac476f8c51ad03f8d","unresolved":false,"context_lines":[{"line_number":2477,"context_line":"        - stable:follows-policy"},{"line_number":2478,"context_line":"        - type:service"},{"line_number":2479,"context_line":"        - starter-kit:compute"},{"line_number":2480,"context_line":"        - vulnerability:managed"},{"line_number":2481,"context_line":"        - assert:follows-standard-deprecation"},{"line_number":2482,"context_line":"    neutron-lbaas:"},{"line_number":2483,"context_line":"      repos:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"9abb7d3a_c37a84bc","line":2480,"in_reply_to":"9abb7d3a_384d7b9a","updated":"2016-06-01 14:46:14.000000000","message":"As someone who gets to wear both TC and VMT hats here. I agree with this. If we are expanding what the VMT is expected to handle here with neutron, I would like to see a bit more conversation happen first. I do not feel comfortable adding all of the \"advanced services\" in explicitly at this point with the previous intention.","commit_id":"3055818232dc4094218486c5b0bb23e19ec689e0"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"2be372a46cd512903702cdc50218f62033111ee5","unresolved":false,"context_lines":[{"line_number":2477,"context_line":"        - stable:follows-policy"},{"line_number":2478,"context_line":"        - type:service"},{"line_number":2479,"context_line":"        - starter-kit:compute"},{"line_number":2480,"context_line":"        - vulnerability:managed"},{"line_number":2481,"context_line":"        - assert:follows-standard-deprecation"},{"line_number":2482,"context_line":"    neutron-lbaas:"},{"line_number":2483,"context_line":"      repos:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"9abb7d3a_7cb24ee6","line":2480,"in_reply_to":"9abb7d3a_7eaa4b86","updated":"2016-06-01 16:42:55.000000000","message":"As stated in the commit message, it was not my intention to alter the way we handle vulnerabilities. In fact I recall at least one vulnerability that came for LBaaS that we vetted.\n\nI wanted the team to continue to honor the contract, after all these projects are supposed to be managed by the same Neutron team. Isn\u0027t this the point of having neutron as top level node?","commit_id":"3055818232dc4094218486c5b0bb23e19ec689e0"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"2292f430ade3b2154c246350b251776177ea0ebb","unresolved":false,"context_lines":[{"line_number":2477,"context_line":"        - stable:follows-policy"},{"line_number":2478,"context_line":"        - type:service"},{"line_number":2479,"context_line":"        - starter-kit:compute"},{"line_number":2480,"context_line":"        - vulnerability:managed"},{"line_number":2481,"context_line":"        - assert:follows-standard-deprecation"},{"line_number":2482,"context_line":"    neutron-lbaas:"},{"line_number":2483,"context_line":"      repos:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"9abb7d3a_b0fc763f","line":2480,"in_reply_to":"9abb7d3a_ae1c696a","updated":"2016-06-03 07:12:21.000000000","message":"Ok, I think this is a reasonable path forward, thanks!","commit_id":"3055818232dc4094218486c5b0bb23e19ec689e0"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"7fea1c76cf36337bdfd364c5574dcff5c7fee52e","unresolved":false,"context_lines":[{"line_number":2477,"context_line":"        - stable:follows-policy"},{"line_number":2478,"context_line":"        - type:service"},{"line_number":2479,"context_line":"        - starter-kit:compute"},{"line_number":2480,"context_line":"        - vulnerability:managed"},{"line_number":2481,"context_line":"        - assert:follows-standard-deprecation"},{"line_number":2482,"context_line":"    neutron-lbaas:"},{"line_number":2483,"context_line":"      repos:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"9abb7d3a_ae1c696a","line":2480,"in_reply_to":"9abb7d3a_c8456f43","updated":"2016-06-02 00:04:14.000000000","message":"In this case I advocate dropping them and adding them individually (especially here). In short, my -1RC is very much that this \"inheriting\" was not the intent of the tag. We should take the time and fix it appropriately.\n\nMy suggestion: \n\n* Do not apply the vulnerability flags to the split out projects (update this review)\n\n* Move the flag for neutron to neutron\u0027s repo (I am unsure of the state of dynamic-routing) [Followup review to this one]\n\n* Fix any other instance of such flags being applied to a bulk of projects at once instead of individually. [Separate from the above reviews]\n\n* Look at re-applying vulnerability:managed for the *aaS advanced services as is seen fit (we can discuss this specific addition as we look at the individual services having the tag applied). [Each with their own review and following the proper process].\n\n\nThis might feel a bit unfair to the \"advanced services\", but in reality this is reflecting the actual coverage for the VMT wrt the neutron repositories. I think we have been mis-advertising this coverage based upon the supplied links and general discussion around this tag.\n\n\nMost of all, thanks for being patient with us here. It isn\u0027t that we want to avoid covering projects with the vulerability:managed tag, we want to make sure we have a clear view of what we are covering. This is also somewhat related to the updates to the vulnerability:managed tag that steven dake is proposing for us so that the rules of how projects receive the tag (and the steps needed before hand) are well defined.","commit_id":"3055818232dc4094218486c5b0bb23e19ec689e0"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"38da557b0e23206f8fa1a544c50debf6a2c125f4","unresolved":false,"context_lines":[{"line_number":2477,"context_line":"        - stable:follows-policy"},{"line_number":2478,"context_line":"        - type:service"},{"line_number":2479,"context_line":"        - starter-kit:compute"},{"line_number":2480,"context_line":"        - vulnerability:managed"},{"line_number":2481,"context_line":"        - assert:follows-standard-deprecation"},{"line_number":2482,"context_line":"    neutron-lbaas:"},{"line_number":2483,"context_line":"      repos:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"9abb7d3a_c8456f43","line":2480,"in_reply_to":"9abb7d3a_f68dba31","updated":"2016-06-01 19:20:45.000000000","message":"Jeremy, I tend to agree that having tags applied to deliverable as a whole may be problematic in some cases, whether it is security related or upgrade related. When I read [1], I felt that the *-aas were still reasonably eligible to inherit the tag, and thus I decided to include it. If this change has opened up the opportunity to revise whether a single repo is eligible to earn a tag, I am not sure we can do that in the context of a single patch, but I am open to suggestions, i.e. a) we can drop them all and add tags individually; or b) keep them all and prune them afterwards. \n\n[1] https://governance.openstack.org/reference/tags/vulnerability_managed.html","commit_id":"3055818232dc4094218486c5b0bb23e19ec689e0"},{"author":{"_account_id":9656,"name":"Ihar Hrachyshka","email":"ihrachys@redhat.com","username":"ihrachys","status":"Red Hat Networking Systems Engineer"},"change_message_id":"16ae7a4a40db71092d44998b4bee6e33b0177426","unresolved":false,"context_lines":[{"line_number":2495,"context_line":"      repos:"},{"line_number":2496,"context_line":"        - openstack/neutron"},{"line_number":2497,"context_line":"      tags:"},{"line_number":2498,"context_line":"        - tc-approved-release"},{"line_number":2499,"context_line":"        - release:managed"},{"line_number":2500,"context_line":"        - release:cycle-with-milestones"},{"line_number":2501,"context_line":"        - stable:follows-policy"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"7aa08908_3fd49e1e","line":2498,"range":{"start_line":2498,"start_character":10,"end_line":2498,"end_character":29},"updated":"2016-06-07 13:23:39.000000000","message":"You effectively remove the tag for *aas. It seems like only DefCore and TC are to decide what\u0027s tagged with it though.","commit_id":"aaa3c15fc373d401c124e1d4ad58bfe3f0a16934"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"ee25b356cba28979476a1e2976cb474b0a5471b2","unresolved":false,"context_lines":[{"line_number":2495,"context_line":"      repos:"},{"line_number":2496,"context_line":"        - openstack/neutron"},{"line_number":2497,"context_line":"      tags:"},{"line_number":2498,"context_line":"        - tc-approved-release"},{"line_number":2499,"context_line":"        - release:managed"},{"line_number":2500,"context_line":"        - release:cycle-with-milestones"},{"line_number":2501,"context_line":"        - stable:follows-policy"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"7aa08908_ad01793a","line":2498,"range":{"start_line":2498,"start_character":10,"end_line":2498,"end_character":29},"in_reply_to":"7aa08908_3fd49e1e","updated":"2016-06-07 16:05:44.000000000","message":"I followed ttx\u0027s suggestion.","commit_id":"aaa3c15fc373d401c124e1d4ad58bfe3f0a16934"},{"author":{"_account_id":9656,"name":"Ihar Hrachyshka","email":"ihrachys@redhat.com","username":"ihrachys","status":"Red Hat Networking Systems Engineer"},"change_message_id":"16ae7a4a40db71092d44998b4bee6e33b0177426","unresolved":false,"context_lines":[{"line_number":2499,"context_line":"        - release:managed"},{"line_number":2500,"context_line":"        - release:cycle-with-milestones"},{"line_number":2501,"context_line":"        - stable:follows-policy"},{"line_number":2502,"context_line":"        - type:service"},{"line_number":2503,"context_line":"        - starter-kit:compute"},{"line_number":2504,"context_line":"        - vulnerability:managed"},{"line_number":2505,"context_line":"        - assert:follows-standard-deprecation"},{"line_number":2506,"context_line":"        - assert:supports-upgrade"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"7aa08908_5fb88ae5","line":2503,"range":{"start_line":2502,"start_character":10,"end_line":2503,"end_character":29},"updated":"2016-06-07 13:23:39.000000000","message":"Would be nice to see explanation of why we remove those tags for *aas, in the commit message.","commit_id":"aaa3c15fc373d401c124e1d4ad58bfe3f0a16934"},{"author":{"_account_id":9656,"name":"Ihar Hrachyshka","email":"ihrachys@redhat.com","username":"ihrachys","status":"Red Hat Networking Systems Engineer"},"change_message_id":"16ae7a4a40db71092d44998b4bee6e33b0177426","unresolved":false,"context_lines":[{"line_number":2501,"context_line":"        - stable:follows-policy"},{"line_number":2502,"context_line":"        - type:service"},{"line_number":2503,"context_line":"        - starter-kit:compute"},{"line_number":2504,"context_line":"        - vulnerability:managed"},{"line_number":2505,"context_line":"        - assert:follows-standard-deprecation"},{"line_number":2506,"context_line":"        - assert:supports-upgrade"},{"line_number":2507,"context_line":"        - assert:supports-rolling-upgrade"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"7aa08908_3fa2deae","line":2504,"range":{"start_line":2504,"start_character":10,"end_line":2504,"end_character":31},"updated":"2016-06-07 13:23:39.000000000","message":"ditto: some rationale behind removing that one would help.","commit_id":"aaa3c15fc373d401c124e1d4ad58bfe3f0a16934"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"ee25b356cba28979476a1e2976cb474b0a5471b2","unresolved":false,"context_lines":[{"line_number":2501,"context_line":"        - stable:follows-policy"},{"line_number":2502,"context_line":"        - type:service"},{"line_number":2503,"context_line":"        - starter-kit:compute"},{"line_number":2504,"context_line":"        - vulnerability:managed"},{"line_number":2505,"context_line":"        - assert:follows-standard-deprecation"},{"line_number":2506,"context_line":"        - assert:supports-upgrade"},{"line_number":2507,"context_line":"        - assert:supports-rolling-upgrade"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"7aa08908_2d6aa9ee","line":2504,"range":{"start_line":2504,"start_character":10,"end_line":2504,"end_character":31},"in_reply_to":"7aa08908_3fa2deae","updated":"2016-06-07 16:05:44.000000000","message":"I thought the patch history would suffice, I\u0027ll elaborate further to clear any doubt.","commit_id":"aaa3c15fc373d401c124e1d4ad58bfe3f0a16934"},{"author":{"_account_id":9656,"name":"Ihar Hrachyshka","email":"ihrachys@redhat.com","username":"ihrachys","status":"Red Hat Networking Systems Engineer"},"change_message_id":"16ae7a4a40db71092d44998b4bee6e33b0177426","unresolved":false,"context_lines":[{"line_number":2509,"context_line":"      repos:"},{"line_number":2510,"context_line":"        - openstack/neutron-dynamic-routing"},{"line_number":2511,"context_line":"      tags:"},{"line_number":2512,"context_line":"        - release:managed"},{"line_number":2513,"context_line":"        - release:cycle-with-milestones"},{"line_number":2514,"context_line":"    neutron-lib:"},{"line_number":2515,"context_line":"      repos:"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"7aa08908_df511ada","line":2512,"updated":"2016-06-07 13:23:39.000000000","message":"For stable:follows-policy, I am not sure: stable/mitaka for neutron is effectively the stable branch for the repo. All backports go into neutron before Newton. Doesn\u0027t it imply that the deliverable follows the policy?","commit_id":"aaa3c15fc373d401c124e1d4ad58bfe3f0a16934"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"ee25b356cba28979476a1e2976cb474b0a5471b2","unresolved":false,"context_lines":[{"line_number":2509,"context_line":"      repos:"},{"line_number":2510,"context_line":"        - openstack/neutron-dynamic-routing"},{"line_number":2511,"context_line":"      tags:"},{"line_number":2512,"context_line":"        - release:managed"},{"line_number":2513,"context_line":"        - release:cycle-with-milestones"},{"line_number":2514,"context_line":"    neutron-lib:"},{"line_number":2515,"context_line":"      repos:"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"7aa08908_ed01c107","line":2512,"in_reply_to":"7aa08908_df511ada","updated":"2016-06-07 16:05:44.000000000","message":"Since the repo has no stable branch, I figured we\u0027d start fresh, however since we\u0027re still in charge of this repo, I suppose we can assume that indeed we follow stable policy.","commit_id":"aaa3c15fc373d401c124e1d4ad58bfe3f0a16934"}]}
