)]}'
{"README.rst":[{"author":{"_account_id":5292,"name":"Christopher Yeoh","email":"cbkyeoh@gmail.com","username":"cyeoh-0"},"change_message_id":"8e6e4f36d9f0b5126755d98ea84a7a688fcc65e1","unresolved":false,"context_lines":[{"line_number":183,"context_line":"For new tests being added to Tempest the assumption is that the API being"},{"line_number":184,"context_line":"tested is considered stable and adheres to the OpenStack API stability"},{"line_number":185,"context_line":"guidelines. If an API is still considered experimental or in development then"},{"line_number":186,"context_line":"it should not be tested by Tempest until it is considered stable. "}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_02fb1e47","line":186,"updated":"2014-06-06 07:55:32.000000000","message":"trailing whitespace here.\n\nBut also we\u0027ve been talking in Nova about having ALL new APIs considered to be experimental for one cycle. To make it easier to wriggle out of \"big oops\" scenarios. This would be clearly communicated to users of the API through versioning\n\nHowever I think we\u0027d still want to have tempest tests so we don\u0027t *accidentally* change the API.","commit_id":"728f61988744a2a7e0a7925a57d9db13d65a5e13"},{"author":{"_account_id":5196,"name":"Matthew Treinish","email":"mtreinish@kortar.org","username":"treinish"},"change_message_id":"7f89df51bf751de1eb702c606b1e14d37add86bc","unresolved":false,"context_lines":[{"line_number":183,"context_line":"For new tests being added to Tempest the assumption is that the API being"},{"line_number":184,"context_line":"tested is considered stable and adheres to the OpenStack API stability"},{"line_number":185,"context_line":"guidelines. If an API is still considered experimental or in development then"},{"line_number":186,"context_line":"it should not be tested by Tempest until it is considered stable. "}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_5fcdcf5c","line":186,"in_reply_to":"1ae5cdf2_02fb1e47","updated":"2014-06-08 21:17:25.000000000","message":"I\u0027ll respin this with the whitespace fix.\n\nSo the problem is that because of how we\u0027re gating now with branchless tempest on more than one release we can\u0027t support backwards incompatible changes. (unless a backport is feasible, which isn\u0027t normally the case with experimental apis) \n\nThis actually came up on the v3 tests earlier this cycle and recently with ironic tests. If tests are added to tempest they already have to comply with the api stability guidelines. I\u0027m adding it here to readme so people understand the expectations regarding api stability so we avoid another situation like:\nhttps://review.openstack.org/#/c/95789/\n\nWe also discussed this during the qa meeting and everyone seemed to agree that we need to be documenting this in the readme, because we are already enforcing this.\n\nThere was a good proposal from Maru about doing tempest test development in the project tree for test and api incubation:\n\nhttps://etherpad.openstack.org/p/juno-qa-functional-api\n\nI can definitely understand wanting to wait a cycle or 2 before adhering to the stabiility guidelines to fix mistakes. I think that or something like that is how tempest tests will be developed for experimental apis in the future, and when the api is considered stable we graduate the tests to tempest.","commit_id":"728f61988744a2a7e0a7925a57d9db13d65a5e13"}]}