)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":8124,"name":"cbrandily","email":"zzelle@gmail.com","username":"cbrandily"},"change_message_id":"01b5bbbd2c91475fa1995e78dd807536c5de3886","unresolved":false,"context_lines":[{"line_number":10,"context_line":"alone Openstack, is even harder."},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"For this reason, let\u0027s make clear we can only have two buckets"},{"line_number":13,"context_line":"to choose from: High and Low. High priority work items are items"},{"line_number":14,"context_line":"that all core folks collectively should care about because any failure"},{"line_number":15,"context_line":"in achieving result for them make us look bad. Low work items are great"},{"line_number":16,"context_line":"to have, but if they slip, it\u0027s a shame but not the end of the world."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"da85f559_48ae1fe7","line":13,"updated":"2015-11-11 23:16:17.000000000","message":"This (BP) change and parent (RFE) change are inconsistent:\n\n this one allows High/Low as BP Importance, parent one allows Wishlist as RFE Importance","commit_id":"00671b009dbcb63dc0265c319eec4370252d937a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"09efabfb8d904c79918ca056ee9f6f3de0c8d8d6","unresolved":false,"context_lines":[{"line_number":10,"context_line":"alone Openstack, is even harder."},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"For this reason, let\u0027s make clear we can only have two buckets"},{"line_number":13,"context_line":"to choose from: High and Low. High priority work items are items"},{"line_number":14,"context_line":"that all core folks collectively should care about because any failure"},{"line_number":15,"context_line":"in achieving result for them make us look bad. Low work items are great"},{"line_number":16,"context_line":"to have, but if they slip, it\u0027s a shame but not the end of the world."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"da85f559_a8630b41","line":13,"in_reply_to":"da85f559_48ae1fe7","updated":"2015-11-11 23:22:13.000000000","message":"It could look that way but they aren\u0027t (at least it was not my intention). That\u0027s the whole point of my cleanup: Importance !\u003d Priority.","commit_id":"00671b009dbcb63dc0265c319eec4370252d937a"}],"doc/source/policies/blueprints.rst":[{"author":{"_account_id":6524,"name":"Henry Gessau","email":"HenryG@gessau.net","username":"gessau"},"change_message_id":"c6b1557a49c8862c011cf7860f59643ea98033a4","unresolved":false,"context_lines":[{"line_number":79,"context_line":"  blueprint submitter will work with the RFE submitter to identify the"},{"line_number":80,"context_line":"  following:"},{"line_number":81,"context_line":""},{"line_number":82,"context_line":"  * Priority: there will be only two priorities to choose from, High and Low."},{"line_number":83,"context_line":"    High priority is to be chosen for work items that must make substantial"},{"line_number":84,"context_line":"    progress in the span of the targeted release, and address the following"},{"line_number":85,"context_line":"    aspects:"}],"source_content_type":"text/x-rst","patch_set":1,"id":"da85f559_6750e80b","line":82,"updated":"2015-11-12 04:11:59.000000000","message":"Is it worth noting here that Priority !\u003d Importance (Importance is documented below)? It\u0027s Launchpad basics yet many people, including myself, often confuse the two.","commit_id":"00671b009dbcb63dc0265c319eec4370252d937a"},{"author":{"_account_id":11307,"name":"Andreas Scheuring","email":"andreas.scheuring@de.ibm.com","username":"uniqueName"},"change_message_id":"824648d4f34a85885d3fa0f7bc2fc769d19d22de","unresolved":false,"context_lines":[{"line_number":79,"context_line":"  blueprint submitter will work with the RFE submitter to identify the"},{"line_number":80,"context_line":"  following:"},{"line_number":81,"context_line":""},{"line_number":82,"context_line":"  * Priority: there will be only two priorities to choose from, High and Low."},{"line_number":83,"context_line":"    High priority is to be chosen for work items that must make substantial"},{"line_number":84,"context_line":"    progress in the span of the targeted release, and address the following"},{"line_number":85,"context_line":"    aspects:"}],"source_content_type":"text/x-rst","patch_set":1,"id":"da85f559_36b210e6","line":82,"updated":"2015-11-12 07:24:55.000000000","message":"So from the indentation I assume, that those two priorities are only valid for Blueprints? Or will they also be applied on standalone RFEs that don\u0027t require a spec? \n\nAnd I assume that for usual bugs the more fine granular priorities still exist, right?","commit_id":"00671b009dbcb63dc0265c319eec4370252d937a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"7c48b51dac27774304530df5e190d2f7440f6ff9","unresolved":false,"context_lines":[{"line_number":79,"context_line":"  blueprint submitter will work with the RFE submitter to identify the"},{"line_number":80,"context_line":"  following:"},{"line_number":81,"context_line":""},{"line_number":82,"context_line":"  * Priority: there will be only two priorities to choose from, High and Low."},{"line_number":83,"context_line":"    High priority is to be chosen for work items that must make substantial"},{"line_number":84,"context_line":"    progress in the span of the targeted release, and address the following"},{"line_number":85,"context_line":"    aspects:"}],"source_content_type":"text/x-rst","patch_set":1,"id":"da85f559_c05b9184","line":82,"in_reply_to":"da85f559_36b210e6","updated":"2015-11-12 18:19:40.000000000","message":"yes, blueprints only (since they have a priority field).\n\nRFEs that do not require a spec are \u0027effectively\u0027 treated as low priority items. But let me clear: low priority items doesn\u0027t mean that folks should not pay attention.\n\nI\u0027ll rephrase.\n\n\nAs for the usual bugs (actual defects). The importance applied and that should determine the urgency for a fix..","commit_id":"00671b009dbcb63dc0265c319eec4370252d937a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"86f3dd74dd90581b347321f7aa2c021d87535390","unresolved":false,"context_lines":[{"line_number":79,"context_line":"  blueprint submitter will work with the RFE submitter to identify the"},{"line_number":80,"context_line":"  following:"},{"line_number":81,"context_line":""},{"line_number":82,"context_line":"  * Priority: there will be only two priorities to choose from, High and Low."},{"line_number":83,"context_line":"    High priority is to be chosen for work items that must make substantial"},{"line_number":84,"context_line":"    progress in the span of the targeted release, and address the following"},{"line_number":85,"context_line":"    aspects:"}],"source_content_type":"text/x-rst","patch_set":1,"id":"da85f559_f6f7a8d0","line":82,"in_reply_to":"da85f559_6750e80b","updated":"2015-11-12 07:18:21.000000000","message":"yes, I did mentioned it to Cedric\u0027s comment in the commit message.","commit_id":"00671b009dbcb63dc0265c319eec4370252d937a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"29349508c7122819961372360deef00a64af54b5","unresolved":false,"context_lines":[{"line_number":79,"context_line":"  blueprint submitter will work with the RFE submitter to identify the"},{"line_number":80,"context_line":"  following:"},{"line_number":81,"context_line":""},{"line_number":82,"context_line":"  * Priority: there will be only two priorities to choose from, High and Low."},{"line_number":83,"context_line":"    High priority is to be chosen for work items that must make substantial"},{"line_number":84,"context_line":"    progress in the span of the targeted release, and address the following"},{"line_number":85,"context_line":"    aspects:"}],"source_content_type":"text/x-rst","patch_set":1,"id":"da85f559_3d8f1a77","line":82,"in_reply_to":"da85f559_8578322d","updated":"2015-11-12 22:48:38.000000000","message":"I think that\u0027s the implicit assumption here: RFE without a spec are effectively \u0027no-brainers\u0027: they are easy to understand and deal with. They do not require extra scrutiny, extra attention or extra visibility. As such, it seems they are typically not associated to burning issues, and as such I would automatically enclose them in the low priority bucket. That said, they might be easily the ones that are completed first, hence again stressing out the fact that low priority doesn\u0027t mean lack of staffing.","commit_id":"00671b009dbcb63dc0265c319eec4370252d937a"},{"author":{"_account_id":9656,"name":"Ihar Hrachyshka","email":"ihrachys@redhat.com","username":"ihrachys","status":"Red Hat Networking Systems Engineer"},"change_message_id":"e7c2b67a8ded9abec8c43ffe216fa9f129c0dfcf","unresolved":false,"context_lines":[{"line_number":79,"context_line":"  blueprint submitter will work with the RFE submitter to identify the"},{"line_number":80,"context_line":"  following:"},{"line_number":81,"context_line":""},{"line_number":82,"context_line":"  * Priority: there will be only two priorities to choose from, High and Low."},{"line_number":83,"context_line":"    High priority is to be chosen for work items that must make substantial"},{"line_number":84,"context_line":"    progress in the span of the targeted release, and address the following"},{"line_number":85,"context_line":"    aspects:"}],"source_content_type":"text/x-rst","patch_set":1,"id":"da85f559_8578322d","line":82,"in_reply_to":"da85f559_c05b9184","updated":"2015-11-12 21:01:40.000000000","message":"So there is no way for RFE without BP to be considered of High priority since it\u0027s all Wishlist. Seems like we loose some part of language that could be useful in assessing RFE priority in review.\n\nOr do we think RFEs with no BP are always somehow of lower importance? I fail to see the link between having BP and priority of a feature.","commit_id":"00671b009dbcb63dc0265c319eec4370252d937a"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"d4be833d9725df86d849dc19a8bdf2d1c7243b12","unresolved":false,"context_lines":[{"line_number":85,"context_line":"    aspects:"},{"line_number":86,"context_line":""},{"line_number":87,"context_line":"    * OpenStack cross-project interaction and interoperability issues;"},{"line_number":88,"context_line":"    * Issues that severily affect the existing system usability;"},{"line_number":89,"context_line":"    * Stability and testability of the platform;"},{"line_number":90,"context_line":""},{"line_number":91,"context_line":"    Low priority is to be chosen for everything else: work items that, should"}],"source_content_type":"text/x-rst","patch_set":1,"id":"da85f559_5c59098d","line":88,"updated":"2015-11-11 21:34:08.000000000","message":"- \"severely\" instead of \"severily\"\n\n- \"usability\" is a property of \"system\" so it should be written \"the existing system\u0027s usability\" or \"the usability of the existing system\"","commit_id":"00671b009dbcb63dc0265c319eec4370252d937a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"3d18b1a5e393b11c3b532773ba0656748561833b","unresolved":false,"context_lines":[{"line_number":85,"context_line":"    aspects:"},{"line_number":86,"context_line":""},{"line_number":87,"context_line":"    * OpenStack cross-project interaction and interoperability issues;"},{"line_number":88,"context_line":"    * Issues that severily affect the existing system usability;"},{"line_number":89,"context_line":"    * Stability and testability of the platform;"},{"line_number":90,"context_line":""},{"line_number":91,"context_line":"    Low priority is to be chosen for everything else: work items that, should"}],"source_content_type":"text/x-rst","patch_set":1,"id":"da85f559_6d8215ca","line":88,"in_reply_to":"da85f559_5c59098d","updated":"2015-11-11 22:57:28.000000000","message":"Done","commit_id":"00671b009dbcb63dc0265c319eec4370252d937a"},{"author":{"_account_id":841,"name":"Akihiro Motoki","email":"amotoki@gmail.com","username":"amotoki"},"change_message_id":"a3d633d36414efeaf737ff867457b90eed9ce664","unresolved":false,"context_lines":[{"line_number":85,"context_line":"    aspects:"},{"line_number":86,"context_line":""},{"line_number":87,"context_line":"    * OpenStack cross-project interaction and interoperability issues;"},{"line_number":88,"context_line":"    * Issues that severily affect the existing system usability;"},{"line_number":89,"context_line":"    * Stability and testability of the platform;"},{"line_number":90,"context_line":""},{"line_number":91,"context_line":"    Low priority is to be chosen for everything else: work items that, should"}],"source_content_type":"text/x-rst","patch_set":1,"id":"da85f559_9675fc32","line":88,"in_reply_to":"da85f559_6d8215ca","updated":"2015-11-12 07:26:37.000000000","message":"Though we don\u0027t have prioritized items for a specific cycle now, \n\"Prioritized items\" can be categorized into the second item if we have such.","commit_id":"00671b009dbcb63dc0265c319eec4370252d937a"},{"author":{"_account_id":6788,"name":"Rossella Sblendido","email":"rsblendido@suse.com","username":"rossella-o"},"change_message_id":"f596b79b87e02d51e7c8c0bf4b05d4034748677e","unresolved":false,"context_lines":[{"line_number":88,"context_line":"    * Issues that severily affect the existing system usability;"},{"line_number":89,"context_line":"    * Stability and testability of the platform;"},{"line_number":90,"context_line":""},{"line_number":91,"context_line":"    Low priority is to be chosen for everything else: work items that, should"},{"line_number":92,"context_line":"    they not meet the realease deadline, do not lead to catastrophic failure"},{"line_number":93,"context_line":"    of the project."},{"line_number":94,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"da85f559_068d55d5","line":91,"updated":"2015-11-12 10:21:51.000000000","message":"Do low priority blueprints require an approver? If reviews for these blueprint are expected to be on a best effort basis then we probably don\u0027t need somebody dedicated to it.","commit_id":"00671b009dbcb63dc0265c319eec4370252d937a"},{"author":{"_account_id":9656,"name":"Ihar Hrachyshka","email":"ihrachys@redhat.com","username":"ihrachys","status":"Red Hat Networking Systems Engineer"},"change_message_id":"e7c2b67a8ded9abec8c43ffe216fa9f129c0dfcf","unresolved":false,"context_lines":[{"line_number":88,"context_line":"    * Issues that severily affect the existing system usability;"},{"line_number":89,"context_line":"    * Stability and testability of the platform;"},{"line_number":90,"context_line":""},{"line_number":91,"context_line":"    Low priority is to be chosen for everything else: work items that, should"},{"line_number":92,"context_line":"    they not meet the realease deadline, do not lead to catastrophic failure"},{"line_number":93,"context_line":"    of the project."},{"line_number":94,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"da85f559_a533f661","line":91,"in_reply_to":"da85f559_00c2f9e8","updated":"2015-11-12 21:01:40.000000000","message":"Having an approver also indicates to the author of patches on review that someone actually cares, and that that person will be the POI into core team for the author. Otherwise authors won\u0027t know whether it\u0027s worth to spend the effort now if there is high chance no one will dedicate any time slot for the work. Supporting a patch on review for cycles is not fun.\n\nSo + for having approvers nevertheless.","commit_id":"00671b009dbcb63dc0265c319eec4370252d937a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"7c48b51dac27774304530df5e190d2f7440f6ff9","unresolved":false,"context_lines":[{"line_number":88,"context_line":"    * Issues that severily affect the existing system usability;"},{"line_number":89,"context_line":"    * Stability and testability of the platform;"},{"line_number":90,"context_line":""},{"line_number":91,"context_line":"    Low priority is to be chosen for everything else: work items that, should"},{"line_number":92,"context_line":"    they not meet the realease deadline, do not lead to catastrophic failure"},{"line_number":93,"context_line":"    of the project."},{"line_number":94,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"da85f559_00c2f9e8","line":91,"in_reply_to":"da85f559_068d55d5","updated":"2015-11-12 18:19:40.000000000","message":"Of course...they are not 2nd class citizens. The distinction between the two is purely based on the criteria I propose above. I\u0027ll elaborate a bit further.","commit_id":"00671b009dbcb63dc0265c319eec4370252d937a"},{"author":{"_account_id":841,"name":"Akihiro Motoki","email":"amotoki@gmail.com","username":"amotoki"},"change_message_id":"d397549a40de15bc166bb05bc095ecc69d652f97","unresolved":false,"context_lines":[{"line_number":88,"context_line":"    * Issues that severily affect the existing system usability;"},{"line_number":89,"context_line":"    * Stability and testability of the platform;"},{"line_number":90,"context_line":""},{"line_number":91,"context_line":"    Low priority is to be chosen for everything else: work items that, should"},{"line_number":92,"context_line":"    they not meet the realease deadline, do not lead to catastrophic failure"},{"line_number":93,"context_line":"    of the project."},{"line_number":94,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"da85f559_a970d140","line":91,"in_reply_to":"da85f559_068d55d5","updated":"2015-11-12 12:19:06.000000000","message":"Your concern is valid, but I think the new mechanism updated by Armando should address your concern.\n\nAll approved blueprints should have approvers now and they are in charge of spec reviews, code reviews and all related things until codes are merged [1]. In general, most approvers are neutron core, so if the current mechanism works patch submitters can get core devs.\n\n[1] http://docs.openstack.org/developer/neutron/policies/blueprints.html#neutron-request-for-feature-enhancements","commit_id":"00671b009dbcb63dc0265c319eec4370252d937a"},{"author":{"_account_id":8124,"name":"cbrandily","email":"zzelle@gmail.com","username":"cbrandily"},"change_message_id":"01b5bbbd2c91475fa1995e78dd807536c5de3886","unresolved":false,"context_lines":[{"line_number":89,"context_line":"    * Stability and testability of the platform;"},{"line_number":90,"context_line":""},{"line_number":91,"context_line":"    Low priority is to be chosen for everything else: work items that, should"},{"line_number":92,"context_line":"    they not meet the realease deadline, do not lead to catastrophic failure"},{"line_number":93,"context_line":"    of the project."},{"line_number":94,"context_line":""},{"line_number":95,"context_line":"  * Drafter: who is going to submit and iterate on the spec proposal; he/she"}],"source_content_type":"text/x-rst","patch_set":1,"id":"da85f559_cd50e134","line":92,"updated":"2015-11-11 23:16:17.000000000","message":"realease \u003d\u003e release","commit_id":"00671b009dbcb63dc0265c319eec4370252d937a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"09efabfb8d904c79918ca056ee9f6f3de0c8d8d6","unresolved":false,"context_lines":[{"line_number":89,"context_line":"    * Stability and testability of the platform;"},{"line_number":90,"context_line":""},{"line_number":91,"context_line":"    Low priority is to be chosen for everything else: work items that, should"},{"line_number":92,"context_line":"    they not meet the realease deadline, do not lead to catastrophic failure"},{"line_number":93,"context_line":"    of the project."},{"line_number":94,"context_line":""},{"line_number":95,"context_line":"  * Drafter: who is going to submit and iterate on the spec proposal; he/she"}],"source_content_type":"text/x-rst","patch_set":1,"id":"da85f559_6859a38d","line":92,"in_reply_to":"da85f559_cd50e134","updated":"2015-11-11 23:22:13.000000000","message":"Done","commit_id":"00671b009dbcb63dc0265c319eec4370252d937a"},{"author":{"_account_id":7776,"name":"Paul Carver","email":"pcarver@att.com","username":"pcarver"},"change_message_id":"3bfe9fea211b3c7cc8486bd89db34f258e5b04ec","unresolved":false,"context_lines":[{"line_number":62,"context_line":""},{"line_number":63,"context_line":"* The bug is submitted and will by default land in the \"New\" state."},{"line_number":64,"context_line":"* As soon as a member of the neutron-drivers team acknowledges the bug, it will"},{"line_number":65,"context_line":"  be moved into the \"Confirmed\" state. No assignee, importance, or milestone is"},{"line_number":66,"context_line":"  set at this time. At this point, the importance can be set to \u0027Wishlist\u0027 to"},{"line_number":67,"context_line":"  signal the fact that the report is indeed a feature or enhancement and there"},{"line_number":68,"context_line":"  is no severity associated to it."}],"source_content_type":"text/x-rst","patch_set":2,"id":"da85f559_919ee605","line":65,"updated":"2015-11-15 15:23:40.000000000","message":"Remove importance from this sentence to disambiguate.","commit_id":"cfee51e6353730fd9525788acdc3e6701477c80c"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"2c71d7b1dbdcf0d347b16062738ee5d4b2e0d07d","unresolved":false,"context_lines":[{"line_number":62,"context_line":""},{"line_number":63,"context_line":"* The bug is submitted and will by default land in the \"New\" state."},{"line_number":64,"context_line":"* As soon as a member of the neutron-drivers team acknowledges the bug, it will"},{"line_number":65,"context_line":"  be moved into the \"Confirmed\" state. No assignee, importance, or milestone is"},{"line_number":66,"context_line":"  set at this time. At this point, the importance can be set to \u0027Wishlist\u0027 to"},{"line_number":67,"context_line":"  signal the fact that the report is indeed a feature or enhancement and there"},{"line_number":68,"context_line":"  is no severity associated to it."}],"source_content_type":"text/x-rst","patch_set":2,"id":"ba8a016a_ff565605","line":65,"in_reply_to":"ba8a016a_8be2779e","updated":"2015-11-16 16:56:24.000000000","message":"Gotcha, thanks for clearing this out. I\u0027ll comply straight away.","commit_id":"cfee51e6353730fd9525788acdc3e6701477c80c"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"dec9d19e4e829399f7fc2afb83f2d64a012a18ed","unresolved":false,"context_lines":[{"line_number":62,"context_line":""},{"line_number":63,"context_line":"* The bug is submitted and will by default land in the \"New\" state."},{"line_number":64,"context_line":"* As soon as a member of the neutron-drivers team acknowledges the bug, it will"},{"line_number":65,"context_line":"  be moved into the \"Confirmed\" state. No assignee, importance, or milestone is"},{"line_number":66,"context_line":"  set at this time. At this point, the importance can be set to \u0027Wishlist\u0027 to"},{"line_number":67,"context_line":"  signal the fact that the report is indeed a feature or enhancement and there"},{"line_number":68,"context_line":"  is no severity associated to it."}],"source_content_type":"text/x-rst","patch_set":2,"id":"da85f559_ea8e5026","line":65,"in_reply_to":"da85f559_919ee605","updated":"2015-11-16 03:29:33.000000000","message":"\u0027Importance\u0027 is one of the fields that\u0027s available for assignment on the launchpad bug report page. I explained what Importance is, and elaborated on priorities. I don\u0027t understand what you\u0027re \u0027ordering\u0027 me to do. I refuse to comply ;)","commit_id":"cfee51e6353730fd9525788acdc3e6701477c80c"},{"author":{"_account_id":7776,"name":"Paul Carver","email":"pcarver@att.com","username":"pcarver"},"change_message_id":"a755428c55502e1cc402a3ad3245b2b799a84eea","unresolved":false,"context_lines":[{"line_number":62,"context_line":""},{"line_number":63,"context_line":"* The bug is submitted and will by default land in the \"New\" state."},{"line_number":64,"context_line":"* As soon as a member of the neutron-drivers team acknowledges the bug, it will"},{"line_number":65,"context_line":"  be moved into the \"Confirmed\" state. No assignee, importance, or milestone is"},{"line_number":66,"context_line":"  set at this time. At this point, the importance can be set to \u0027Wishlist\u0027 to"},{"line_number":67,"context_line":"  signal the fact that the report is indeed a feature or enhancement and there"},{"line_number":68,"context_line":"  is no severity associated to it."}],"source_content_type":"text/x-rst","patch_set":2,"id":"ba8a016a_8be2779e","line":65,"in_reply_to":"da85f559_ea8e5026","updated":"2015-11-16 15:18:36.000000000","message":"Sorry for the \"order\", I\u0027ve been trying to fight my tendency to write dissertations but I guess I erred on the side of terseness.\n\nMy point is that you\u0027ve got one old sentence and one newly added sentence that say different things. Ignoring assignee and milestone for the moment we\u0027ve got:\n\n\"No importance is set at this time\"\n\nimmediately followed by\n\n\"At this point, the importance can (or will) be set to \u0027Wishlist\u0027\"\n\nSo are \"this time\" and \"this point\" different? I\u0027m reading them as being the same time/point and wondering if I follow the first sentence \"No importance is set\" or the second sentence \"the importance can/will be set to Wishlist\"\n\nIs there a process step in between \"this time\" and \"this point\"? If so, then you could clarify by adding what is the process step that takes us from Importance \u003d None to Importance \u003d Wishlist.","commit_id":"cfee51e6353730fd9525788acdc3e6701477c80c"},{"author":{"_account_id":7776,"name":"Paul Carver","email":"pcarver@att.com","username":"pcarver"},"change_message_id":"3bfe9fea211b3c7cc8486bd89db34f258e5b04ec","unresolved":false,"context_lines":[{"line_number":63,"context_line":"* The bug is submitted and will by default land in the \"New\" state."},{"line_number":64,"context_line":"* As soon as a member of the neutron-drivers team acknowledges the bug, it will"},{"line_number":65,"context_line":"  be moved into the \"Confirmed\" state. No assignee, importance, or milestone is"},{"line_number":66,"context_line":"  set at this time. At this point, the importance can be set to \u0027Wishlist\u0027 to"},{"line_number":67,"context_line":"  signal the fact that the report is indeed a feature or enhancement and there"},{"line_number":68,"context_line":"  is no severity associated to it."},{"line_number":69,"context_line":"* The bug goes into the \"Triaged\" state while the discussion is ongoing."}],"source_content_type":"text/x-rst","patch_set":2,"id":"da85f559_51895ec9","line":66,"updated":"2015-11-15 15:23:40.000000000","message":"Change \"can\" to \"will\" (or else clarify when importance should be unset vs when it should be set to wishlist.)","commit_id":"cfee51e6353730fd9525788acdc3e6701477c80c"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"dec9d19e4e829399f7fc2afb83f2d64a012a18ed","unresolved":false,"context_lines":[{"line_number":63,"context_line":"* The bug is submitted and will by default land in the \"New\" state."},{"line_number":64,"context_line":"* As soon as a member of the neutron-drivers team acknowledges the bug, it will"},{"line_number":65,"context_line":"  be moved into the \"Confirmed\" state. No assignee, importance, or milestone is"},{"line_number":66,"context_line":"  set at this time. At this point, the importance can be set to \u0027Wishlist\u0027 to"},{"line_number":67,"context_line":"  signal the fact that the report is indeed a feature or enhancement and there"},{"line_number":68,"context_line":"  is no severity associated to it."},{"line_number":69,"context_line":"* The bug goes into the \"Triaged\" state while the discussion is ongoing."}],"source_content_type":"text/x-rst","patch_set":2,"id":"da85f559_4aa8bc77","line":66,"in_reply_to":"da85f559_51895ec9","updated":"2015-11-16 03:29:33.000000000","message":"Done","commit_id":"cfee51e6353730fd9525788acdc3e6701477c80c"},{"author":{"_account_id":14957,"name":"Brad Behle","email":"behle@us.ibm.com","username":"behle"},"change_message_id":"684b2b61eb9667c30381d7f76b40a011e8cbfde7","unresolved":false,"context_lines":[{"line_number":83,"context_line":"  following:"},{"line_number":84,"context_line":""},{"line_number":85,"context_line":"  * Priority: there will be only two priorities to choose from, High and Low."},{"line_number":86,"context_line":"    It is worth noting that priority is not to be confused with `importance \u003chttps://wiki.openstack.org/wiki/Bugs#Importance\u003e`_,"},{"line_number":87,"context_line":"    which is a property of actual defects. High priority is to be chosen for"},{"line_number":88,"context_line":"    work items that must make substantial progress in the span of the targeted"},{"line_number":89,"context_line":"    release, and deal with the following aspects:"}],"source_content_type":"text/x-rst","patch_set":2,"id":"ba8a016a_1c26cbba","line":86,"updated":"2015-11-16 15:52:48.000000000","message":"Even after reading this link and these changes, I\u0027m still struggling to understand the differences between priority and importance.  I get some of the differences, but it might be good to include a sentence or two summarizing the critical distinction as you see it.  Maybe it\u0027s because I\u0027m fairly new to Neutron, but something like that would have helped me to better understand the rest of the priority discussion below.","commit_id":"cfee51e6353730fd9525788acdc3e6701477c80c"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"2c71d7b1dbdcf0d347b16062738ee5d4b2e0d07d","unresolved":false,"context_lines":[{"line_number":83,"context_line":"  following:"},{"line_number":84,"context_line":""},{"line_number":85,"context_line":"  * Priority: there will be only two priorities to choose from, High and Low."},{"line_number":86,"context_line":"    It is worth noting that priority is not to be confused with `importance \u003chttps://wiki.openstack.org/wiki/Bugs#Importance\u003e`_,"},{"line_number":87,"context_line":"    which is a property of actual defects. High priority is to be chosen for"},{"line_number":88,"context_line":"    work items that must make substantial progress in the span of the targeted"},{"line_number":89,"context_line":"    release, and deal with the following aspects:"}],"source_content_type":"text/x-rst","patch_set":2,"id":"ba8a016a_5fa0c2f4","line":86,"in_reply_to":"ba8a016a_1c26cbba","updated":"2015-11-16 16:56:24.000000000","message":"Done","commit_id":"cfee51e6353730fd9525788acdc3e6701477c80c"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"086ba540c1dd9fbb4c42cd4ec289063984501d3d","unresolved":false,"context_lines":[{"line_number":92,"context_line":"    * Issues that affect the existing system\u0027s usability;"},{"line_number":93,"context_line":"    * Stability and testability of the platform;"},{"line_number":94,"context_line":"    * Improvements to the appeal of the platform over alternative solutions;"},{"line_number":95,"context_line":"    * Risky implementations;"},{"line_number":96,"context_line":""},{"line_number":97,"context_line":"    Low priority is to be chosen for everything else: work items that are"},{"line_number":98,"context_line":"    typically easier to implement, and should they be deferred, they are not"}],"source_content_type":"text/x-rst","patch_set":2,"id":"da85f559_ee8c4481","line":95,"updated":"2015-11-13 21:01:14.000000000","message":"It\u0027d remove lines 94 and 95, they are to subjective. The other aspects are all rock solid.","commit_id":"cfee51e6353730fd9525788acdc3e6701477c80c"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"2c71d7b1dbdcf0d347b16062738ee5d4b2e0d07d","unresolved":false,"context_lines":[{"line_number":92,"context_line":"    * Issues that affect the existing system\u0027s usability;"},{"line_number":93,"context_line":"    * Stability and testability of the platform;"},{"line_number":94,"context_line":"    * Improvements to the appeal of the platform over alternative solutions;"},{"line_number":95,"context_line":"    * Risky implementations;"},{"line_number":96,"context_line":""},{"line_number":97,"context_line":"    Low priority is to be chosen for everything else: work items that are"},{"line_number":98,"context_line":"    typically easier to implement, and should they be deferred, they are not"}],"source_content_type":"text/x-rst","patch_set":2,"id":"ba8a016a_dfacb2ef","line":95,"in_reply_to":"ba8a016a_31bbb8c6","updated":"2015-11-16 16:56:24.000000000","message":"I will expand on the meaning.","commit_id":"cfee51e6353730fd9525788acdc3e6701477c80c"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"ab7397bdd64559adbf666e0f4576ed7f2b6d1b23","unresolved":false,"context_lines":[{"line_number":92,"context_line":"    * Issues that affect the existing system\u0027s usability;"},{"line_number":93,"context_line":"    * Stability and testability of the platform;"},{"line_number":94,"context_line":"    * Improvements to the appeal of the platform over alternative solutions;"},{"line_number":95,"context_line":"    * Risky implementations;"},{"line_number":96,"context_line":""},{"line_number":97,"context_line":"    Low priority is to be chosen for everything else: work items that are"},{"line_number":98,"context_line":"    typically easier to implement, and should they be deferred, they are not"}],"source_content_type":"text/x-rst","patch_set":2,"id":"da85f559_8926d114","line":95,"in_reply_to":"da85f559_2ecb2c74","updated":"2015-11-13 22:25:19.000000000","message":"We\u0027re the only cloud networking solution for OpenStack, right? Do we think we\u0027ll be a cloud networking stack for something other than OpenStack? If not, 94 should go.\n\nI still think 95 should go as it\u0027s too subjective.","commit_id":"cfee51e6353730fd9525788acdc3e6701477c80c"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"1bc9f1338a23167b7ac0300f6d9acbaa307b7b61","unresolved":false,"context_lines":[{"line_number":92,"context_line":"    * Issues that affect the existing system\u0027s usability;"},{"line_number":93,"context_line":"    * Stability and testability of the platform;"},{"line_number":94,"context_line":"    * Improvements to the appeal of the platform over alternative solutions;"},{"line_number":95,"context_line":"    * Risky implementations;"},{"line_number":96,"context_line":""},{"line_number":97,"context_line":"    Low priority is to be chosen for everything else: work items that are"},{"line_number":98,"context_line":"    typically easier to implement, and should they be deferred, they are not"}],"source_content_type":"text/x-rst","patch_set":2,"id":"da85f559_721b56cb","line":95,"in_reply_to":"da85f559_6c7cdbb5","updated":"2015-11-14 01:27:21.000000000","message":"Risky is highly subjective. If you want to put in \"fundamental changes to an API\", that is not subjective. But I\u0027m willing to concede if you drop line 94, so we\u0027re good.\n\n:)","commit_id":"cfee51e6353730fd9525788acdc3e6701477c80c"},{"author":{"_account_id":14957,"name":"Brad Behle","email":"behle@us.ibm.com","username":"behle"},"change_message_id":"684b2b61eb9667c30381d7f76b40a011e8cbfde7","unresolved":false,"context_lines":[{"line_number":92,"context_line":"    * Issues that affect the existing system\u0027s usability;"},{"line_number":93,"context_line":"    * Stability and testability of the platform;"},{"line_number":94,"context_line":"    * Improvements to the appeal of the platform over alternative solutions;"},{"line_number":95,"context_line":"    * Risky implementations;"},{"line_number":96,"context_line":""},{"line_number":97,"context_line":"    Low priority is to be chosen for everything else: work items that are"},{"line_number":98,"context_line":"    typically easier to implement, and should they be deferred, they are not"}],"source_content_type":"text/x-rst","patch_set":2,"id":"ba8a016a_31bbb8c6","line":95,"in_reply_to":"da85f559_721b56cb","updated":"2015-11-16 15:52:48.000000000","message":"+1 to Kyle\u0027s comment about \"risky\" being too subjective.  I do think it is reasonable to list things like \"fundamental API or model changes\", \"significant changes to complex and fragile code\", etc as additional criteria for the \"High priority\" tag.","commit_id":"cfee51e6353730fd9525788acdc3e6701477c80c"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"c9692b897037fe1633a7f32dfb7cb98858c47fa6","unresolved":false,"context_lines":[{"line_number":92,"context_line":"    * Issues that affect the existing system\u0027s usability;"},{"line_number":93,"context_line":"    * Stability and testability of the platform;"},{"line_number":94,"context_line":"    * Improvements to the appeal of the platform over alternative solutions;"},{"line_number":95,"context_line":"    * Risky implementations;"},{"line_number":96,"context_line":""},{"line_number":97,"context_line":"    Low priority is to be chosen for everything else: work items that are"},{"line_number":98,"context_line":"    typically easier to implement, and should they be deferred, they are not"}],"source_content_type":"text/x-rst","patch_set":2,"id":"da85f559_6c7cdbb5","line":95,"in_reply_to":"da85f559_8926d114","updated":"2015-11-13 23:11:21.000000000","message":"OpenStack is not the only slice of the entire landscape, anyhow that\u0027s fine I can take it out. As for 95, can you tell me why it\u0027s subjective? If a spec proposes to introduce fundamental changes to an API or a model, how can two different people disagree on the risk (or lack thereof) of regression that that may pose?","commit_id":"cfee51e6353730fd9525788acdc3e6701477c80c"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"58a690427a1d8e19c9e47ab4d727e7a57bf502d3","unresolved":false,"context_lines":[{"line_number":92,"context_line":"    * Issues that affect the existing system\u0027s usability;"},{"line_number":93,"context_line":"    * Stability and testability of the platform;"},{"line_number":94,"context_line":"    * Improvements to the appeal of the platform over alternative solutions;"},{"line_number":95,"context_line":"    * Risky implementations;"},{"line_number":96,"context_line":""},{"line_number":97,"context_line":"    Low priority is to be chosen for everything else: work items that are"},{"line_number":98,"context_line":"    typically easier to implement, and should they be deferred, they are not"}],"source_content_type":"text/x-rst","patch_set":2,"id":"da85f559_2ecb2c74","line":95,"in_reply_to":"da85f559_ee8c4481","updated":"2015-11-13 21:10:24.000000000","message":"Risky in the sense that the code can be complex and require drastic changes...read model and API evolutions and the like. What\u0027s subjective about that?\n\nI could get rid of line 94, but neutron is not the only cloud networking solution out there, and we may want to pay attention to effort that makes us still relevant.","commit_id":"cfee51e6353730fd9525788acdc3e6701477c80c"},{"author":{"_account_id":14957,"name":"Brad Behle","email":"behle@us.ibm.com","username":"behle"},"change_message_id":"684b2b61eb9667c30381d7f76b40a011e8cbfde7","unresolved":false,"context_lines":[{"line_number":95,"context_line":"    * Risky implementations;"},{"line_number":96,"context_line":""},{"line_number":97,"context_line":"    Low priority is to be chosen for everything else: work items that are"},{"line_number":98,"context_line":"    typically easier to implement, and should they be deferred, they are not"},{"line_number":99,"context_line":"    going to cause major grief. RFEs without an associated blueprint are effectively"},{"line_number":100,"context_line":"    equivalent to low priority items. Bear in mind that, even though staffing"},{"line_number":101,"context_line":"    should take priorities into account (i.e. by giving more resources to high"}],"source_content_type":"text/x-rst","patch_set":2,"id":"ba8a016a_f15e9075","line":98,"updated":"2015-11-16 15:52:48.000000000","message":"I would remove \"work items that are typically easier to implement\" from here.  I don\u0027t think this should be a criteria for whether something is high or low priority.  Something could be be \"high\" due to one of the criteria listed above, but still be considered \"easier to implement\".  I think it\u0027s more clear to say low priority are just ones that don\u0027t fit the high priority criteria.  I might also remove the \"should they be deferred.... major grief\", but I could see where that distinction could be useful.","commit_id":"cfee51e6353730fd9525788acdc3e6701477c80c"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"2c71d7b1dbdcf0d347b16062738ee5d4b2e0d07d","unresolved":false,"context_lines":[{"line_number":95,"context_line":"    * Risky implementations;"},{"line_number":96,"context_line":""},{"line_number":97,"context_line":"    Low priority is to be chosen for everything else: work items that are"},{"line_number":98,"context_line":"    typically easier to implement, and should they be deferred, they are not"},{"line_number":99,"context_line":"    going to cause major grief. RFEs without an associated blueprint are effectively"},{"line_number":100,"context_line":"    equivalent to low priority items. Bear in mind that, even though staffing"},{"line_number":101,"context_line":"    should take priorities into account (i.e. by giving more resources to high"}],"source_content_type":"text/x-rst","patch_set":2,"id":"ba8a016a_5f876261","line":98,"in_reply_to":"ba8a016a_f15e9075","updated":"2015-11-16 16:56:24.000000000","message":"I\u0027ll rephrase.","commit_id":"cfee51e6353730fd9525788acdc3e6701477c80c"}]}