)]}'
{"doc/source/contributor/contributing.rst":[{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"3c4c5e97fef9d465a8221b25570ca262b2f7b10b","unresolved":false,"context_lines":[{"line_number":57,"context_line":"       maintenance or other development lifecycle issues that are not otherwise"},{"line_number":58,"context_line":"       a bug or feature."},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"When a story has been completed it can be removed from the list by being tagged"},{"line_number":61,"context_line":"with ``fixed``."},{"line_number":62,"context_line":""},{"line_number":63,"context_line":".. note::"},{"line_number":64,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"3fce034c_a3575a58","line":61,"range":{"start_line":60,"start_character":0,"end_line":61,"end_character":15},"updated":"2019-04-18 18:42:32.000000000","message":"Yet another reason I don\u0027t like storyboard, you have to manually manage bugs with tags, even when they are closed. Seems like a worklist should be able to have some kind of filter on overall status of a story, i.e. if all tasks in the story are merged then the story is no longer active and for bugs we could consider that \u0027fixed\u0027 automatically rather than manually needing to change the tag.","commit_id":"1b5710db74151307e95e1102a510f76739f2e00c"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"3c4c5e97fef9d465a8221b25570ca262b2f7b10b","unresolved":false,"context_lines":[{"line_number":85,"context_line":"* The operating system(s) on which the placement is running."},{"line_number":86,"context_line":"* The version(s) of Python being used."},{"line_number":87,"context_line":""},{"line_number":88,"context_line":"Tag the story with ``bug``."},{"line_number":89,"context_line":""},{"line_number":90,"context_line":".. _triage:"},{"line_number":91,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"3fce034c_43f79660","line":88,"range":{"start_line":88,"start_character":0,"end_line":88,"end_character":27},"updated":"2019-04-18 18:42:32.000000000","message":"✓","commit_id":"1b5710db74151307e95e1102a510f76739f2e00c"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"3c4c5e97fef9d465a8221b25570ca262b2f7b10b","unresolved":false,"context_lines":[{"line_number":256,"context_line":"openstack-discuss_ list, and in IRC."},{"line_number":257,"context_line":""},{"line_number":258,"context_line":"Once there is a clear need for a change, a story should be created in"},{"line_number":259,"context_line":"StoryBoard_ with a tag of ``rfe``. Placement team members will evaluate the"},{"line_number":260,"context_line":"story to determine if a :doc:`spec \u003c/specs/index\u003e` is required. If it is, a"},{"line_number":261,"context_line":"task to create the spec will be added to the story. At this time there are no"},{"line_number":262,"context_line":"hard and fast rules on what will require a spec. If the implementation is well"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3fce034c_2397eaee","line":259,"range":{"start_line":259,"start_character":12,"end_line":259,"end_character":33},"updated":"2019-04-18 18:42:32.000000000","message":"✓","commit_id":"1b5710db74151307e95e1102a510f76739f2e00c"}]}