)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":6786,"name":"Sergey Lukjanov","email":"me@slukjanov.name","username":"slukjanov"},"change_message_id":"1eaa6cd332ea861f6087efe803115d777f044753","unresolved":false,"context_lines":[{"line_number":15,"context_line":""},{"line_number":16,"context_line":"  3) Python client library - seems to be an unstated requirement"},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"  4) Heat integration - most controversial, but is it that different"},{"line_number":19,"context_line":"     from the client lib requirement? Do we want Heat to end up"},{"line_number":20,"context_line":"     with support for only some projects?"},{"line_number":21,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":3,"id":"AAAAUH%2F9hSg%3D","line":18,"updated":"2014-02-06 10:46:42.000000000","message":"Looks like you should remove #4 and #5 from the commit message.","commit_id":"9224c6c91070a7e605a48cdafdbfddb145e8e3e8"}],"reference/incubation-integration-requirements":[{"author":{"_account_id":2750,"name":"Sean Dague","email":"sean@dague.net","username":"sdague"},"change_message_id":"c94083078980369bef1c8d3e2507611d63aa3278","unresolved":false,"context_lines":[{"line_number":81,"context_line":"** Project must have a REST API with at least a JSON entity representation"},{"line_number":82,"context_line":"** The REST API must be declared stable and the project must commit to"},{"line_number":83,"context_line":"   maintaining backwards compatibility"},{"line_number":84,"context_line":"** Project must have a Python client library for its REST API"},{"line_number":85,"context_line":"** Project must have Heat integration such that its resource can be provisioned"},{"line_number":86,"context_line":"   via a Heat template"},{"line_number":87,"context_line":"** Project must be usable via the Horizon dashboard"}],"source_content_type":"application/octet-stream","patch_set":2,"id":"AAAAUH%2F%2BhHY%3D","line":84,"updated":"2014-01-24 20:46:27.000000000","message":"I\u0027m not so sure we want to codify this now, especially with SDK possibly going in a different set of projects.","commit_id":"fd1389a51d5f38c1dd3055836f555856e5a20f66"},{"author":{"_account_id":1247,"name":"Mark McLoughlin","email":"markmc@redhat.com","username":"markmc"},"change_message_id":"395b4ceeb710d36f0258a4cd7f435b21ec349a8a","unresolved":false,"context_lines":[{"line_number":81,"context_line":"** Project must have a REST API with at least a JSON entity representation"},{"line_number":82,"context_line":"** The REST API must be declared stable and the project must commit to"},{"line_number":83,"context_line":"   maintaining backwards compatibility"},{"line_number":84,"context_line":"** Project must have a Python client library for its REST API"},{"line_number":85,"context_line":"** Project must have Heat integration such that its resource can be provisioned"},{"line_number":86,"context_line":"   via a Heat template"},{"line_number":87,"context_line":"** Project must be usable via the Horizon dashboard"}],"source_content_type":"application/octet-stream","patch_set":2,"id":"AAAAUH%2F9hhw%3D","line":84,"in_reply_to":"AAAAUH%2F%2BhHY%3D","updated":"2014-02-06 10:21:27.000000000","message":"Technically speaking, it just says *a* client library - it doesn\u0027t have to be python-fooclient\n\nThat said, if a project wanted to graduate now and it just had additions to python-openstacksdk, I don\u0027t think we\u0027d consider that enough\n\nIOW, the path is pretty obvious for new projects now, but it may evolve - the key requirement is that there is a python binding available","commit_id":"fd1389a51d5f38c1dd3055836f555856e5a20f66"},{"author":{"_account_id":2750,"name":"Sean Dague","email":"sean@dague.net","username":"sdague"},"change_message_id":"c94083078980369bef1c8d3e2507611d63aa3278","unresolved":false,"context_lines":[{"line_number":82,"context_line":"** The REST API must be declared stable and the project must commit to"},{"line_number":83,"context_line":"   maintaining backwards compatibility"},{"line_number":84,"context_line":"** Project must have a Python client library for its REST API"},{"line_number":85,"context_line":"** Project must have Heat integration such that its resource can be provisioned"},{"line_number":86,"context_line":"   via a Heat template"},{"line_number":87,"context_line":"** Project must be usable via the Horizon dashboard"},{"line_number":88,"context_line":""}],"source_content_type":"application/octet-stream","patch_set":2,"id":"AAAAUH%2F%2BhHk%3D","line":85,"updated":"2014-01-24 20:46:27.000000000","message":"Heat isn\u0027t yet really in the integrated gate (it\u0027s there in such a light way that it shipped a broken i2 release). Until that time requiring Heat is way beyond scope.","commit_id":"fd1389a51d5f38c1dd3055836f555856e5a20f66"},{"author":{"_account_id":6786,"name":"Sergey Lukjanov","email":"me@slukjanov.name","username":"slukjanov"},"change_message_id":"110a202f688461fffa0650373ac385bd2c9c7cec","unresolved":false,"context_lines":[{"line_number":82,"context_line":"** The REST API must be declared stable and the project must commit to"},{"line_number":83,"context_line":"   maintaining backwards compatibility"},{"line_number":84,"context_line":"** Project must have a Python client library for its REST API"},{"line_number":85,"context_line":"** Project must have Heat integration such that its resource can be provisioned"},{"line_number":86,"context_line":"   via a Heat template"},{"line_number":87,"context_line":"** Project must be usable via the Horizon dashboard"},{"line_number":88,"context_line":""}],"source_content_type":"application/octet-stream","patch_set":2,"id":"AAAAUH%2F%2Bzho%3D","line":85,"updated":"2014-01-21 22:31:34.000000000","message":"It looks like we\u0027re hitting the egg-checken problem here again. It\u0027ll be really strange for Heat and Horizon to depend on non-integrated projects.","commit_id":"fd1389a51d5f38c1dd3055836f555856e5a20f66"},{"author":{"_account_id":4257,"name":"Zane Bitter","email":"zbitter@redhat.com","username":"zaneb"},"change_message_id":"f0bddd50f20ccf53499c981363aaaae159594ea3","unresolved":false,"context_lines":[{"line_number":82,"context_line":"** The REST API must be declared stable and the project must commit to"},{"line_number":83,"context_line":"   maintaining backwards compatibility"},{"line_number":84,"context_line":"** Project must have a Python client library for its REST API"},{"line_number":85,"context_line":"** Project must have Heat integration such that its resource can be provisioned"},{"line_number":86,"context_line":"   via a Heat template"},{"line_number":87,"context_line":"** Project must be usable via the Horizon dashboard"},{"line_number":88,"context_line":""}],"source_content_type":"application/octet-stream","patch_set":2,"id":"AAAAVn%2F%2Fpfs%3D","line":85,"in_reply_to":"AAAAUH%2F%2BhHk%3D","updated":"2014-03-04 21:28:07.000000000","message":"FWIW I don\u0027t think there is a chicken-and-egg issue here. Heat can load plugins from anywhere (AAUI so can Horizon), and in fact there is a /contrib directory in Heat repo for _exactly_ this purpose, to allow unit tests to run on them and Heat folks to generally help maintain them in an unbroken state without causing a hard dependency.\n\nI also think the gating thing is a red herring. You don\u0027t need a working Heat to write a plugin for it, and the plugin would be in the Heat repo anyway, not in some other repo relying on Heat to work in it\u0027s own gate. (i.e. the plugin could be well tested by the Heat gate\u0027s unit tests.)\n\nIt\u0027s really easy to accidentally write an API that\u0027s _terrible_ for orchestration - and BTW APIs that are terrible for orchestration are also hard for ordinary users to use in very subtle ways. If new projects had a step in their checklists to implement a Heat resource and get it reviewed by the Heat core team (TBH I don\u0027t even care if it works, just that the model is sensible), it would help to surface any issues much sooner, while they still have time to fix the API. The later they uncover it, the more difficult it is for them to fix. You can say \"No, Heat once had a bug and therefore must be Punished\", but that just leaves everybody worse off - the incubated project and its users worst of all.","commit_id":"fd1389a51d5f38c1dd3055836f555856e5a20f66"},{"author":{"_account_id":1247,"name":"Mark McLoughlin","email":"markmc@redhat.com","username":"markmc"},"change_message_id":"395b4ceeb710d36f0258a4cd7f435b21ec349a8a","unresolved":false,"context_lines":[{"line_number":82,"context_line":"** The REST API must be declared stable and the project must commit to"},{"line_number":83,"context_line":"   maintaining backwards compatibility"},{"line_number":84,"context_line":"** Project must have a Python client library for its REST API"},{"line_number":85,"context_line":"** Project must have Heat integration such that its resource can be provisioned"},{"line_number":86,"context_line":"   via a Heat template"},{"line_number":87,"context_line":"** Project must be usable via the Horizon dashboard"},{"line_number":88,"context_line":""}],"source_content_type":"application/octet-stream","patch_set":2,"id":"AAAAUH%2F9hgU%3D","line":85,"in_reply_to":"AAAAUH%2F%2Bk7I%3D","updated":"2014-02-06 10:21:27.000000000","message":"Yeah - we probably should have a \"first dev cycle\" section ... I don\u0027t particularly want to be driving the inevitable \"what happens if projects don\u0027t complete that list\" discussion though :)","commit_id":"fd1389a51d5f38c1dd3055836f555856e5a20f66"},{"author":{"_account_id":1247,"name":"Mark McLoughlin","email":"markmc@redhat.com","username":"markmc"},"change_message_id":"395b4ceeb710d36f0258a4cd7f435b21ec349a8a","unresolved":false,"context_lines":[{"line_number":82,"context_line":"** The REST API must be declared stable and the project must commit to"},{"line_number":83,"context_line":"   maintaining backwards compatibility"},{"line_number":84,"context_line":"** Project must have a Python client library for its REST API"},{"line_number":85,"context_line":"** Project must have Heat integration such that its resource can be provisioned"},{"line_number":86,"context_line":"   via a Heat template"},{"line_number":87,"context_line":"** Project must be usable via the Horizon dashboard"},{"line_number":88,"context_line":""}],"source_content_type":"application/octet-stream","patch_set":2,"id":"AAAAUH%2F9hhY%3D","line":85,"in_reply_to":"AAAAUH%2F%2BmM0%3D","updated":"2014-02-06 10:21:27.000000000","message":"Got it, will drop Heat and Horizon from the list","commit_id":"fd1389a51d5f38c1dd3055836f555856e5a20f66"},{"author":{"_account_id":6786,"name":"Sergey Lukjanov","email":"me@slukjanov.name","username":"slukjanov"},"change_message_id":"5a183ec0f817234e8801e0a05a0d92031f123c07","unresolved":false,"context_lines":[{"line_number":82,"context_line":"** The REST API must be declared stable and the project must commit to"},{"line_number":83,"context_line":"   maintaining backwards compatibility"},{"line_number":84,"context_line":"** Project must have a Python client library for its REST API"},{"line_number":85,"context_line":"** Project must have Heat integration such that its resource can be provisioned"},{"line_number":86,"context_line":"   via a Heat template"},{"line_number":87,"context_line":"** Project must be usable via the Horizon dashboard"},{"line_number":88,"context_line":""}],"source_content_type":"application/octet-stream","patch_set":2,"id":"AAAAUH%2F%2Bk7I%3D","line":85,"in_reply_to":"AAAAUH%2F%2BmM0%3D","updated":"2014-01-24 08:07:56.000000000","message":"I think that we should move such requirements to the separated section - for the first dev cycle after integration.\n\nProbably sections with the following meanings will be more readable and clear:\n\n* requirements to be incubated\n* what should be done during the incubation \u003d\u003d graduation to integrated\n* what should be done in first dev cycle after graduation.","commit_id":"fd1389a51d5f38c1dd3055836f555856e5a20f66"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"200b86195c4e0507830812143c868e8c730e94ca","unresolved":false,"context_lines":[{"line_number":82,"context_line":"** The REST API must be declared stable and the project must commit to"},{"line_number":83,"context_line":"   maintaining backwards compatibility"},{"line_number":84,"context_line":"** Project must have a Python client library for its REST API"},{"line_number":85,"context_line":"** Project must have Heat integration such that its resource can be provisioned"},{"line_number":86,"context_line":"   via a Heat template"},{"line_number":87,"context_line":"** Project must be usable via the Horizon dashboard"},{"line_number":88,"context_line":""}],"source_content_type":"application/octet-stream","patch_set":2,"id":"AAAAUH%2F%2BmM0%3D","line":85,"in_reply_to":"AAAAUH%2F%2Bzho%3D","updated":"2014-01-24 00:52:13.000000000","message":"I agree with Sergey. Those tasks (Heat and Horizon being able to drive those new resources) were in the past added as part of the full development cycle that they undergo together.","commit_id":"fd1389a51d5f38c1dd3055836f555856e5a20f66"},{"author":{"_account_id":2750,"name":"Sean Dague","email":"sean@dague.net","username":"sdague"},"change_message_id":"e4849d5574951d1562bdbf009a985adbddb3cb6d","unresolved":false,"context_lines":[{"line_number":82,"context_line":"** The REST API must be declared stable and the project must commit to"},{"line_number":83,"context_line":"   maintaining backwards compatibility"},{"line_number":84,"context_line":"** Project must have a Python client library for its REST API"},{"line_number":85,"context_line":"** Project must have Heat integration such that its resource can be provisioned"},{"line_number":86,"context_line":"   via a Heat template"},{"line_number":87,"context_line":"** Project must be usable via the Horizon dashboard"},{"line_number":88,"context_line":""}],"source_content_type":"application/octet-stream","patch_set":2,"id":"AAAAVn%2F%2Fmow%3D","line":85,"in_reply_to":"AAAAVn%2F%2Fpfs%3D","updated":"2014-03-11 18:23:36.000000000","message":"This isn\u0027t about Heat once had a bug. It\u0027s about the fact that 2 full cycles after being part of the integrated release Heat still isn\u0027t part of the integrated gate in any subtantial way. Which means it\u0027s not reasonable to CD in any real way. If heat was coming up for graduation now, it would be rejected on those grounds. The i2 issue was a symptom of this fact.\n\nWe\u0027re asking new projects to hit a substantially higher mark that Heat currently does on being part of the integrated gate. Which means I don\u0027t believe that we should make integrating with Heat a requirement on new projects until Heat actually integrates in the gate in a real way. This is about being symmetric so that all integrated parts of OpenStack are provably working together at all times. Heat doesn\u0027t do that.\n\nI really wish it did. I\u0027ve been asking the question pretty much continuously about when Heat would finally get a gating job that actually does something other than trivial REST calls which test none of the core function of Heat.\n\nSo please realize where this request for balance, and Heat actually being integrated comes from. Because right now everyone is very much worse off that Heat can break at any time because it currently isn\u0027t actually doing the same kinds of testing that Keystone, Nova, Swift, Glance, Cinder, Neutron, or even Savana or Ironic are doing. Rackspace\u0027s Heat CD deployment regularly breaks because of this.\n\nAs soon as Heat is really part of the integrated gate, I withdraw my objections. And I\u0027d love nothing more for it to be that, and be something we could really think of as integrated.","commit_id":"fd1389a51d5f38c1dd3055836f555856e5a20f66"},{"author":{"_account_id":964,"name":"Anne Gentle","email":"annegentle@justwriteclick.com","username":"annegentle"},"change_message_id":"9547ef5cdaa5e2e87cce6ac988693a6ee23fdfcd","unresolved":false,"context_lines":[{"line_number":80,"context_line":"* API"},{"line_number":81,"context_line":"** Project must have a REST API with at least a JSON entity representation"},{"line_number":82,"context_line":"** The REST API must be declared stable and the project must commit to"},{"line_number":83,"context_line":"   maintaining backwards compatibility"},{"line_number":84,"context_line":"** Project must have a Python client library for its REST API"},{"line_number":85,"context_line":""},{"line_number":86,"context_line":"* QA"}],"source_content_type":"application/octet-stream","patch_set":4,"id":"AAAAUX%2F%2FwLg%3D","line":83,"updated":"2014-02-11 01:50:24.000000000","message":"For discussion: \n\n- backwards compatibility maintained for how long? \n- if a project has a REST API version 1, but they want to do some rework and make a v2, does the v2 have to be stable before graduation?","commit_id":"7aca5a38fb6fd5dee66fcbf976ecea3772905ad3"},{"author":{"_account_id":2271,"name":"Michael Still","email":"mikal@stillhq.com","username":"mikalstill"},"change_message_id":"4ee432e068d942b7190f9bb3db960d9fccaf458b","unresolved":false,"context_lines":[{"line_number":82,"context_line":"** The REST API must be declared stable and the project must commit to"},{"line_number":83,"context_line":"   maintaining backwards compatibility"},{"line_number":84,"context_line":"** Project must have a Python client library for its REST API"},{"line_number":85,"context_line":""},{"line_number":86,"context_line":"* QA"},{"line_number":87,"context_line":"** Project must be part of the integrated gate"},{"line_number":88,"context_line":"** Project must have decent unit test and functional tests coverage"}],"source_content_type":"application/octet-stream","patch_set":4,"id":"AAAAUX%2F%2Foo8%3D","line":85,"updated":"2014-02-11 20:54:30.000000000","message":"Can\u0027t we think of a possible future project which has no API?","commit_id":"7aca5a38fb6fd5dee66fcbf976ecea3772905ad3"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"990e691fd0035d3023bdeea04f5251807933e9ae","unresolved":false,"context_lines":[{"line_number":106,"context_line":"\u003d First Integrated Release \u003d"},{"line_number":107,"context_line":""},{"line_number":108,"context_line":"In the release cyle after the project has graduated, the TC expects the project"},{"line_number":109,"context_line":"to have reach a level of maturity for its first integrated release. In order for"},{"line_number":110,"context_line":"the project to graduate, the TC will need to be confident that the project will"},{"line_number":111,"context_line":"reach that level of maturity in the time allowed."},{"line_number":112,"context_line":""}],"source_content_type":"application/octet-stream","patch_set":5,"id":"AAAAWH%2F%2F%2BDo%3D","line":109,"updated":"2014-03-12 16:39:51.000000000","message":"\"to have reached\" or \"to reach\"","commit_id":"b6ea83c7e4cdea9b73bc9b103b8b53d1c245b4b2"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"dbfb94bc433be9d5c3e18dc5be4cca3eda916b87","unresolved":false,"context_lines":[{"line_number":111,"context_line":"reach that level of maturity in the time allowed."},{"line_number":112,"context_line":""},{"line_number":113,"context_line":"* API"},{"line_number":114,"context_line":"** Project must have a REST API with at least a JSON entity representation"},{"line_number":115,"context_line":"** The REST API must be declared stable and the project must commit to"},{"line_number":116,"context_line":"   maintaining backwards compatibility"},{"line_number":117,"context_line":"** Project must have a Python client library API for its REST API"}],"source_content_type":"application/octet-stream","patch_set":5,"id":"AAAAWH%2F%2FWjo%3D","line":114,"updated":"2014-03-18 12:50:31.000000000","message":"Looks like a graduation requirement to me. I would add \"if applicable\" since not all projects will have a REST API.","commit_id":"b6ea83c7e4cdea9b73bc9b103b8b53d1c245b4b2"},{"author":{"_account_id":6786,"name":"Sergey Lukjanov","email":"me@slukjanov.name","username":"slukjanov"},"change_message_id":"f8710444add2459e3e6c856343ccf36210bf70a8","unresolved":false,"context_lines":[{"line_number":111,"context_line":"reach that level of maturity in the time allowed."},{"line_number":112,"context_line":""},{"line_number":113,"context_line":"* API"},{"line_number":114,"context_line":"** Project must have a REST API with at least a JSON entity representation"},{"line_number":115,"context_line":"** The REST API must be declared stable and the project must commit to"},{"line_number":116,"context_line":"   maintaining backwards compatibility"},{"line_number":117,"context_line":"** Project must have a Python client library API for its REST API"}],"source_content_type":"application/octet-stream","patch_set":5,"id":"AAAAWH%2F%2FWfk%3D","line":114,"in_reply_to":"AAAAWH%2F%2FWjo%3D","updated":"2014-03-18 12:59:21.000000000","message":"+1 for both requirement and \"if applicable\" condition.\n\nWe already have incubation requirement \"Project APIs should be reasonably stable\" and API docs requirements in both incubation/graduation requirements, so, IMO it\u0027ll be better to have this requirement for graduation (I think all current projects will pass it).","commit_id":"b6ea83c7e4cdea9b73bc9b103b8b53d1c245b4b2"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"dbfb94bc433be9d5c3e18dc5be4cca3eda916b87","unresolved":false,"context_lines":[{"line_number":114,"context_line":"** Project must have a REST API with at least a JSON entity representation"},{"line_number":115,"context_line":"** The REST API must be declared stable and the project must commit to"},{"line_number":116,"context_line":"   maintaining backwards compatibility"},{"line_number":117,"context_line":"** Project must have a Python client library API for its REST API"},{"line_number":118,"context_line":"** Project must have Heat integration such that its resource can be provisioned"},{"line_number":119,"context_line":"   via a Heat template"},{"line_number":120,"context_line":"** Project must be usable via the Horizon dashboard"}],"source_content_type":"application/octet-stream","patch_set":5,"id":"AAAAWH%2F%2FWjQ%3D","line":117,"updated":"2014-03-18 12:50:31.000000000","message":"Looks like a graduation requirement to me.\nI would add \"if applicable\" since not all projects will have a REST API.","commit_id":"b6ea83c7e4cdea9b73bc9b103b8b53d1c245b4b2"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"990e691fd0035d3023bdeea04f5251807933e9ae","unresolved":false,"context_lines":[{"line_number":115,"context_line":"** The REST API must be declared stable and the project must commit to"},{"line_number":116,"context_line":"   maintaining backwards compatibility"},{"line_number":117,"context_line":"** Project must have a Python client library API for its REST API"},{"line_number":118,"context_line":"** Project must have Heat integration such that its resource can be provisioned"},{"line_number":119,"context_line":"   via a Heat template"},{"line_number":120,"context_line":"** Project must be usable via the Horizon dashboard"}],"source_content_type":"application/octet-stream","patch_set":5,"id":"AAAAWH%2F%2F%2BCM%3D","line":118,"updated":"2014-03-12 16:39:51.000000000","message":"Not all projects will have resources to be provisioned (ceilometer). How about:\n\n  If the project manages resources, it must have have Heat integration for provisioning them via a Heat template.","commit_id":"b6ea83c7e4cdea9b73bc9b103b8b53d1c245b4b2"},{"author":{"_account_id":6786,"name":"Sergey Lukjanov","email":"me@slukjanov.name","username":"slukjanov"},"change_message_id":"f8710444add2459e3e6c856343ccf36210bf70a8","unresolved":false,"context_lines":[{"line_number":117,"context_line":"** Project must have a Python client library API for its REST API"},{"line_number":118,"context_line":"** Project must have Heat integration such that its resource can be provisioned"},{"line_number":119,"context_line":"   via a Heat template"},{"line_number":120,"context_line":"** Project must be usable via the Horizon dashboard"}],"source_content_type":"application/octet-stream","patch_set":5,"id":"AAAAWH%2F%2FWb0%3D","line":120,"updated":"2014-03-18 12:59:21.000000000","message":"Should it be requirement for all projects?\n\nTL;DR\n\nProbably, we should add here some condition too, like \"if applicable\" or \"if useful\". For example, in Ironic it seems like only  admin pages needed after integration with nova (probably, I\u0027m not correct about it). IMO I think that Horizon integration is very important to make end users able to use all projects from one UI, but I\u0027m a bit concerned about applying this requirement to all projects.","commit_id":"b6ea83c7e4cdea9b73bc9b103b8b53d1c245b4b2"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"1ffa3dfbdc59789afe6e02bb911e5628a59a474d","unresolved":false,"context_lines":[{"line_number":109,"context_line":""},{"line_number":110,"context_line":"\u003d First Integrated Cycle Expectations \u003d"},{"line_number":111,"context_line":""},{"line_number":112,"context_line":"In the release cyle after the project has graduated, the TC expects the project"},{"line_number":113,"context_line":"to reach a level of maturity for its first integrated release. In order for the"},{"line_number":114,"context_line":"project to graduate, the TC will need to be confident that the project will"},{"line_number":115,"context_line":"reach that level of maturity in the time allowed."}],"source_content_type":"application/octet-stream","patch_set":6,"id":"AAAAWH%2F%2BktI%3D","line":112,"updated":"2014-03-25 20:02:12.000000000","message":"Typo: cyle -\u003e cycle","commit_id":"d1e346f865658c0a6193bb594f5fbe6d73c8b5a0"},{"author":{"_account_id":1247,"name":"Mark McLoughlin","email":"markmc@redhat.com","username":"markmc"},"change_message_id":"4e256a37b8ebbb3944fa2a842616f24fc773885e","unresolved":false,"context_lines":[{"line_number":109,"context_line":""},{"line_number":110,"context_line":"\u003d First Integrated Cycle Expectations \u003d"},{"line_number":111,"context_line":""},{"line_number":112,"context_line":"In the release cyle after the project has graduated, the TC expects the project"},{"line_number":113,"context_line":"to reach a level of maturity for its first integrated release. In order for the"},{"line_number":114,"context_line":"project to graduate, the TC will need to be confident that the project will"},{"line_number":115,"context_line":"reach that level of maturity in the time allowed."}],"source_content_type":"application/octet-stream","patch_set":6,"id":"AAAAWH%2F%2BMK8%3D","line":112,"in_reply_to":"AAAAWH%2F%2BktI%3D","updated":"2014-04-01 20:43:31.000000000","message":"Thanks, pushed as Ic39ffeb75fe4470e05d28fcf7e0c3d491ad1f270 to avoid making everyone re-vote","commit_id":"d1e346f865658c0a6193bb594f5fbe6d73c8b5a0"}]}