)]}'
{"specs/kilo/master-policy.rst":[{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"2bc4bf7212e2754b92012b34c86b7fc0e91509cf","unresolved":false,"context_lines":[{"line_number":9,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"The blueprint has been created for puppet-nova, but affects all modules:"},{"line_number":12,"context_line":"https://blueprints.launchpad.net/puppet-nova/+spec/master-policy"},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"Problem description"},{"line_number":15,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":3,"id":"ba3cc151_5ac71945","line":12,"updated":"2015-06-30 20:37:26.000000000","message":"This would probably be a better place to register it https://launchpad.net/puppet-openstack","commit_id":"c9b2b8f4f91f20f6df8f50aa79e72ac5d43ff6c3"},{"author":{"_account_id":3153,"name":"Emilien Macchi","email":"emilien@redhat.com","username":"emilienm"},"change_message_id":"69ab38e32906a53e3926762fbb70937436b1f004","unresolved":false,"context_lines":[{"line_number":9,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"The blueprint has been created for puppet-nova, but affects all modules:"},{"line_number":12,"context_line":"https://blueprints.launchpad.net/puppet-nova/+spec/master-policy"},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"Problem description"},{"line_number":15,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":3,"id":"ba3cc151_4e4d1b3d","line":12,"in_reply_to":"ba3cc151_5ac71945","updated":"2015-06-30 21:38:14.000000000","message":"Done","commit_id":"c9b2b8f4f91f20f6df8f50aa79e72ac5d43ff6c3"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"2bc4bf7212e2754b92012b34c86b7fc0e91509cf","unresolved":false,"context_lines":[{"line_number":37,"context_line":""},{"line_number":38,"context_line":"* Accept that master branch is not supposed to work on stable releases of OpenStack."},{"line_number":39,"context_line":"* Functional testing CI jobs should work on the OpenStack release that comes after the"},{"line_number":40,"context_line":"  latest Puppet OpenStack stable branch."},{"line_number":41,"context_line":"* Submit a feature in master only if it can be tested by functional testing CI jobs."},{"line_number":42,"context_line":"* Help developpers to easily backport patches to stable branches when needed."},{"line_number":43,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"ba3cc151_dac009e3","line":40,"updated":"2015-06-30 20:37:26.000000000","message":"This is a little unclear. Can we change it to:\n\nFunctional testing CI jobs should pass using the latest testing package repositories from the Ubuntu and RHEL distributions.","commit_id":"c9b2b8f4f91f20f6df8f50aa79e72ac5d43ff6c3"},{"author":{"_account_id":3153,"name":"Emilien Macchi","email":"emilien@redhat.com","username":"emilienm"},"change_message_id":"69ab38e32906a53e3926762fbb70937436b1f004","unresolved":false,"context_lines":[{"line_number":37,"context_line":""},{"line_number":38,"context_line":"* Accept that master branch is not supposed to work on stable releases of OpenStack."},{"line_number":39,"context_line":"* Functional testing CI jobs should work on the OpenStack release that comes after the"},{"line_number":40,"context_line":"  latest Puppet OpenStack stable branch."},{"line_number":41,"context_line":"* Submit a feature in master only if it can be tested by functional testing CI jobs."},{"line_number":42,"context_line":"* Help developpers to easily backport patches to stable branches when needed."},{"line_number":43,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"ba3cc151_8e100303","line":40,"in_reply_to":"ba3cc151_dac009e3","updated":"2015-06-30 21:38:14.000000000","message":"Done","commit_id":"c9b2b8f4f91f20f6df8f50aa79e72ac5d43ff6c3"},{"author":{"_account_id":10540,"name":"Clayton O\u0027Neill","email":"clayton.oneill@charter.com","username":"coneill"},"change_message_id":"1349c62fa783a0eecc5f53abef55fd12f4c31bfb","unresolved":false,"context_lines":[{"line_number":39,"context_line":"* Functional testing CI jobs should work on the OpenStack release that comes after the"},{"line_number":40,"context_line":"  latest Puppet OpenStack stable branch."},{"line_number":41,"context_line":"* Submit a feature in master only if it can be tested by functional testing CI jobs."},{"line_number":42,"context_line":"* Help developpers to easily backport patches to stable branches when needed."},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"Alternatives"},{"line_number":45,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"ba3cc151_d086bada","line":42,"updated":"2015-06-30 15:26:17.000000000","message":"Typo","commit_id":"c9b2b8f4f91f20f6df8f50aa79e72ac5d43ff6c3"},{"author":{"_account_id":3153,"name":"Emilien Macchi","email":"emilien@redhat.com","username":"emilienm"},"change_message_id":"69ab38e32906a53e3926762fbb70937436b1f004","unresolved":false,"context_lines":[{"line_number":39,"context_line":"* Functional testing CI jobs should work on the OpenStack release that comes after the"},{"line_number":40,"context_line":"  latest Puppet OpenStack stable branch."},{"line_number":41,"context_line":"* Submit a feature in master only if it can be tested by functional testing CI jobs."},{"line_number":42,"context_line":"* Help developpers to easily backport patches to stable branches when needed."},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"Alternatives"},{"line_number":45,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"ba3cc151_ce5febe3","line":42,"in_reply_to":"ba3cc151_d086bada","updated":"2015-06-30 21:38:14.000000000","message":"Done","commit_id":"c9b2b8f4f91f20f6df8f50aa79e72ac5d43ff6c3"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"2bc4bf7212e2754b92012b34c86b7fc0e91509cf","unresolved":false,"context_lines":[{"line_number":76,"context_line":""},{"line_number":77,"context_line":"Deployers will need to be more careful if they used to run master branches."},{"line_number":78,"context_line":""},{"line_number":79,"context_line":"* use master if they target a deployment with the current developpement version."},{"line_number":80,"context_line":"* use stable branches if they plan to deploy a stable version of OpenStack."},{"line_number":81,"context_line":""},{"line_number":82,"context_line":"Developer impact"}],"source_content_type":"text/x-rst","patch_set":3,"id":"ba3cc151_fa82ad93","line":79,"updated":"2015-06-30 20:37:26.000000000","message":"development not developpement","commit_id":"c9b2b8f4f91f20f6df8f50aa79e72ac5d43ff6c3"},{"author":{"_account_id":3153,"name":"Emilien Macchi","email":"emilien@redhat.com","username":"emilienm"},"change_message_id":"69ab38e32906a53e3926762fbb70937436b1f004","unresolved":false,"context_lines":[{"line_number":76,"context_line":""},{"line_number":77,"context_line":"Deployers will need to be more careful if they used to run master branches."},{"line_number":78,"context_line":""},{"line_number":79,"context_line":"* use master if they target a deployment with the current developpement version."},{"line_number":80,"context_line":"* use stable branches if they plan to deploy a stable version of OpenStack."},{"line_number":81,"context_line":""},{"line_number":82,"context_line":"Developer impact"}],"source_content_type":"text/x-rst","patch_set":3,"id":"ba3cc151_4e743b67","line":79,"in_reply_to":"ba3cc151_fa82ad93","updated":"2015-06-30 21:38:14.000000000","message":"Done","commit_id":"c9b2b8f4f91f20f6df8f50aa79e72ac5d43ff6c3"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"2bc4bf7212e2754b92012b34c86b7fc0e91509cf","unresolved":false,"context_lines":[{"line_number":82,"context_line":"Developer impact"},{"line_number":83,"context_line":"----------------"},{"line_number":84,"context_line":""},{"line_number":85,"context_line":"Developpers will need to figure if their patch can be tested by the current state of master."},{"line_number":86,"context_line":"Also, they will need to be more engaged in backport policy and make sure to cherry-pick interesting"},{"line_number":87,"context_line":"bugfixes and features to the right stable branches."},{"line_number":88,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"ba3cc151_3a601501","line":85,"updated":"2015-06-30 20:37:26.000000000","message":"Developers not Developpers","commit_id":"c9b2b8f4f91f20f6df8f50aa79e72ac5d43ff6c3"},{"author":{"_account_id":3153,"name":"Emilien Macchi","email":"emilien@redhat.com","username":"emilienm"},"change_message_id":"69ab38e32906a53e3926762fbb70937436b1f004","unresolved":false,"context_lines":[{"line_number":82,"context_line":"Developer impact"},{"line_number":83,"context_line":"----------------"},{"line_number":84,"context_line":""},{"line_number":85,"context_line":"Developpers will need to figure if their patch can be tested by the current state of master."},{"line_number":86,"context_line":"Also, they will need to be more engaged in backport policy and make sure to cherry-pick interesting"},{"line_number":87,"context_line":"bugfixes and features to the right stable branches."},{"line_number":88,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"ba3cc151_ae5ce7ed","line":85,"in_reply_to":"ba3cc151_3a601501","updated":"2015-06-30 21:38:14.000000000","message":"Done","commit_id":"c9b2b8f4f91f20f6df8f50aa79e72ac5d43ff6c3"},{"author":{"_account_id":9500,"name":"Matt Fischer","email":"matt@mattfischer.com","username":"mfisch"},"change_message_id":"f5a7ed23aa07adb106ca2a9705fb5a8b925b3a6b","unresolved":false,"context_lines":[{"line_number":20,"context_line":"  release, with all the time backward compatibility support. When using"},{"line_number":21,"context_line":"  deprecated configuration parameters, OpenStack projects uses WARNING level"},{"line_number":22,"context_line":"  in logging files, that warn operators to update configuration files so they"},{"line_number":23,"context_line":"  have the latest options."},{"line_number":24,"context_line":"* Since the beginning of the Puppet modules project, master branch has always been"},{"line_number":25,"context_line":"  the development branch and be used to integrate features from OpenStack master"},{"line_number":26,"context_line":"  or very recent release. Until now, master branch always meant to be used to test"}],"source_content_type":"text/x-rst","patch_set":4,"id":"ba3cc151_fe3de1dd","line":23,"updated":"2015-07-06 22:00:29.000000000","message":"They also only warn once at startup. Not sure if that bears mentioning.","commit_id":"630467fc61f87b289d0133742b741f73490b627f"},{"author":{"_account_id":3153,"name":"Emilien Macchi","email":"emilien@redhat.com","username":"emilienm"},"change_message_id":"d6acd0f0926cc2b3da445179247d4c3f597e4475","unresolved":false,"context_lines":[{"line_number":20,"context_line":"  release, with all the time backward compatibility support. When using"},{"line_number":21,"context_line":"  deprecated configuration parameters, OpenStack projects uses WARNING level"},{"line_number":22,"context_line":"  in logging files, that warn operators to update configuration files so they"},{"line_number":23,"context_line":"  have the latest options."},{"line_number":24,"context_line":"* Since the beginning of the Puppet modules project, master branch has always been"},{"line_number":25,"context_line":"  the development branch and be used to integrate features from OpenStack master"},{"line_number":26,"context_line":"  or very recent release. Until now, master branch always meant to be used to test"}],"source_content_type":"text/x-rst","patch_set":4,"id":"ba3cc151_0e6189d3","line":23,"in_reply_to":"ba3cc151_fe3de1dd","updated":"2015-07-10 20:01:36.000000000","message":"Done","commit_id":"630467fc61f87b289d0133742b741f73490b627f"},{"author":{"_account_id":9500,"name":"Matt Fischer","email":"matt@mattfischer.com","username":"mfisch"},"change_message_id":"f5a7ed23aa07adb106ca2a9705fb5a8b925b3a6b","unresolved":false,"context_lines":[{"line_number":40,"context_line":"  from the Ubuntu and RHEL distributions."},{"line_number":41,"context_line":"* Submit a feature in master only if it can be tested by functional testing CI jobs."},{"line_number":42,"context_line":"* Help developers to easily backport patches to stable branches when needed."},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"Alternatives"},{"line_number":45,"context_line":"------------"},{"line_number":46,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"ba3cc151_e108e42a","line":43,"updated":"2015-07-06 22:00:29.000000000","message":"Do we need to discuss the case of making breaking deprecation fixes? Many times adding support for a new feature is okay but moving config options around for deprecations can break the release.","commit_id":"630467fc61f87b289d0133742b741f73490b627f"},{"author":{"_account_id":3153,"name":"Emilien Macchi","email":"emilien@redhat.com","username":"emilienm"},"change_message_id":"d6acd0f0926cc2b3da445179247d4c3f597e4475","unresolved":false,"context_lines":[{"line_number":40,"context_line":"  from the Ubuntu and RHEL distributions."},{"line_number":41,"context_line":"* Submit a feature in master only if it can be tested by functional testing CI jobs."},{"line_number":42,"context_line":"* Help developers to easily backport patches to stable branches when needed."},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"Alternatives"},{"line_number":45,"context_line":"------------"},{"line_number":46,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"ba3cc151_8ea91993","line":43,"in_reply_to":"ba3cc151_e108e42a","updated":"2015-07-10 20:01:36.000000000","message":"isn\u0027t already the case of my text here?\n\"Accept (...) not supposed (...).\"","commit_id":"630467fc61f87b289d0133742b741f73490b627f"},{"author":{"_account_id":9500,"name":"Matt Fischer","email":"matt@mattfischer.com","username":"mfisch"},"change_message_id":"f5a7ed23aa07adb106ca2a9705fb5a8b925b3a6b","unresolved":false,"context_lines":[{"line_number":84,"context_line":""},{"line_number":85,"context_line":"Developers will need to figure if their patch can be tested by the current state of master."},{"line_number":86,"context_line":"Also, they will need to be more engaged in backport policy and make sure to cherry-pick interesting"},{"line_number":87,"context_line":"bugfixes and features to the right stable branches."},{"line_number":88,"context_line":""},{"line_number":89,"context_line":"Implementation"},{"line_number":90,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":4,"id":"ba3cc151_611db465","line":87,"updated":"2015-07-06 22:00:29.000000000","message":"I\u0027d like backports of all bug fixes to be required.","commit_id":"630467fc61f87b289d0133742b741f73490b627f"},{"author":{"_account_id":3153,"name":"Emilien Macchi","email":"emilien@redhat.com","username":"emilienm"},"change_message_id":"d6acd0f0926cc2b3da445179247d4c3f597e4475","unresolved":false,"context_lines":[{"line_number":84,"context_line":""},{"line_number":85,"context_line":"Developers will need to figure if their patch can be tested by the current state of master."},{"line_number":86,"context_line":"Also, they will need to be more engaged in backport policy and make sure to cherry-pick interesting"},{"line_number":87,"context_line":"bugfixes and features to the right stable branches."},{"line_number":88,"context_line":""},{"line_number":89,"context_line":"Implementation"},{"line_number":90,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":4,"id":"ba3cc151_4e955186","line":87,"in_reply_to":"ba3cc151_611db465","updated":"2015-07-10 20:01:36.000000000","message":"I think this is what my sentence gently says, no?","commit_id":"630467fc61f87b289d0133742b741f73490b627f"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"77cf3c5f72b01cec904d3f48ab92889b72d34e97","unresolved":false,"context_lines":[{"line_number":49,"context_line":""},{"line_number":50,"context_line":"* Another possibility that would help developers but may not help the operators case much"},{"line_number":51,"context_line":"  is to pick a date after which it is okay to start targeting the next release, and"},{"line_number":52,"context_line":"  loudly announce it."},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"Data model impact"},{"line_number":55,"context_line":"-----------------"}],"source_content_type":"text/x-rst","patch_set":5,"id":"9a41bdd9_c0dcb7e6","line":52,"updated":"2015-07-13 14:26:18.000000000","message":"I think making an announcement on the mailing list when we switch functional testing to the next pre-release packages could be part of the solution, rather than an alternative.\n\nI\u0027d suggest removing this bullet point from \"Alternatives\" and expand the second bullet point under \"Proposed change\" to mention making an announcement when we update the repositories for the functional tests.","commit_id":"b3b86be828950192c8b41143638a7af8d9690db0"},{"author":{"_account_id":3153,"name":"Emilien Macchi","email":"emilien@redhat.com","username":"emilienm"},"change_message_id":"a9de851049dc5ddb450f9be935098f39e0d1c882","unresolved":false,"context_lines":[{"line_number":49,"context_line":""},{"line_number":50,"context_line":"* Another possibility that would help developers but may not help the operators case much"},{"line_number":51,"context_line":"  is to pick a date after which it is okay to start targeting the next release, and"},{"line_number":52,"context_line":"  loudly announce it."},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"Data model impact"},{"line_number":55,"context_line":"-----------------"}],"source_content_type":"text/x-rst","patch_set":5,"id":"9a41bdd9_a3517dda","line":52,"in_reply_to":"9a41bdd9_c0dcb7e6","updated":"2015-07-13 14:35:33.000000000","message":"Done","commit_id":"b3b86be828950192c8b41143638a7af8d9690db0"}],"specs/master-policy.rst":[{"author":{"_account_id":9500,"name":"Matt Fischer","email":"matt@mattfischer.com","username":"mfisch"},"change_message_id":"50458a42ae66682ae10313212a373b5d8916eaac","unresolved":false,"context_lines":[{"line_number":18,"context_line":"Here are the problems that lead us to write this blueprint:"},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"* OpenStack projects use to update their configuration files and API every"},{"line_number":21,"context_line":"  release, with most of the time backward compatibility support. When using"},{"line_number":22,"context_line":"  deprecated configuration parameters, OpenStack projects uses WARNING level"},{"line_number":23,"context_line":"  in logging files, that warn operators to update configuration files so they"},{"line_number":24,"context_line":"  have the latest options. This is the problem #1: how to deal with new"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3acd31a7_2ee2bf2f","line":21,"updated":"2015-05-05 17:08:19.000000000","message":"I think it\u0027s all of the time because deprecations are used.","commit_id":"548e5a77e1a2a6e81c69a870e1b38974c25e0f79"},{"author":{"_account_id":3153,"name":"Emilien Macchi","email":"emilien@redhat.com","username":"emilienm"},"change_message_id":"677e3841320edfd863e983de8b0a219020646fed","unresolved":false,"context_lines":[{"line_number":18,"context_line":"Here are the problems that lead us to write this blueprint:"},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"* OpenStack projects use to update their configuration files and API every"},{"line_number":21,"context_line":"  release, with most of the time backward compatibility support. When using"},{"line_number":22,"context_line":"  deprecated configuration parameters, OpenStack projects uses WARNING level"},{"line_number":23,"context_line":"  in logging files, that warn operators to update configuration files so they"},{"line_number":24,"context_line":"  have the latest options. This is the problem #1: how to deal with new"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1aca2d91_2387f110","line":21,"in_reply_to":"3acd31a7_2ee2bf2f","updated":"2015-05-23 18:37:50.000000000","message":"Done","commit_id":"548e5a77e1a2a6e81c69a870e1b38974c25e0f79"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"43d48c2d2b7c54d56f359e42c52c3de6f1ce57d0","unresolved":false,"context_lines":[{"line_number":27,"context_line":"* Since the beginning of the Puppet modules project, master branch has always"},{"line_number":28,"context_line":"  the development branch and used to integrate features from OpenStack master"},{"line_number":29,"context_line":"  or very recent release. That means master branch used to be broken for"},{"line_number":30,"context_line":"  stable releases. This is problem #2: when can we break master?"},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"* Over the time, our community grew and we\u0027ve got some contributions and"},{"line_number":33,"context_line":"  more feedback from operators world that complained master branch was broken"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3acd31a7_02c11254","line":30,"updated":"2015-05-05 19:53:24.000000000","message":"Expanding on Matt\u0027s comment, I think it is worth clarifying what \"break master\" means here. There is \"break\" in the sense that the class or type API changes, and there is \"break\" in the sense that changes specific to the next OpenStack release land that break functionality for the current release.\n\nMy opinion is that it is always okay for master to be unstable in the sense that API compatibility \"breaks\", and that it is otherwise not okay for master to \"break\" in a way that makes it impossible for someone to run it, for example to make changes that only work with packages that aren\u0027t available to me.","commit_id":"548e5a77e1a2a6e81c69a870e1b38974c25e0f79"},{"author":{"_account_id":9500,"name":"Matt Fischer","email":"matt@mattfischer.com","username":"mfisch"},"change_message_id":"50458a42ae66682ae10313212a373b5d8916eaac","unresolved":false,"context_lines":[{"line_number":27,"context_line":"* Since the beginning of the Puppet modules project, master branch has always"},{"line_number":28,"context_line":"  the development branch and used to integrate features from OpenStack master"},{"line_number":29,"context_line":"  or very recent release. That means master branch used to be broken for"},{"line_number":30,"context_line":"  stable releases. This is problem #2: when can we break master?"},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"* Over the time, our community grew and we\u0027ve got some contributions and"},{"line_number":33,"context_line":"  more feedback from operators world that complained master branch was broken"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3acd31a7_2e507fd3","line":30,"updated":"2015-05-05 17:08:19.000000000","message":"when can we break master for the current stable release is the question","commit_id":"548e5a77e1a2a6e81c69a870e1b38974c25e0f79"},{"author":{"_account_id":7156,"name":"Mathieu Gagné","email":"mgagne@calavera.ca","username":"mgagne"},"change_message_id":"58d820485ed1b4f735617dec2a8d407db663b657","unresolved":false,"context_lines":[{"line_number":27,"context_line":"* Since the beginning of the Puppet modules project, master branch has always"},{"line_number":28,"context_line":"  the development branch and used to integrate features from OpenStack master"},{"line_number":29,"context_line":"  or very recent release. That means master branch used to be broken for"},{"line_number":30,"context_line":"  stable releases. This is problem #2: when can we break master?"},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"* Over the time, our community grew and we\u0027ve got some contributions and"},{"line_number":33,"context_line":"  more feedback from operators world that complained master branch was broken"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3acd31a7_bd6f1ffb","line":30,"in_reply_to":"3acd31a7_02c11254","updated":"2015-05-05 20:31:37.000000000","message":"I agree with Colleen that we need to define \"break master\".\n\nHowever I disagree with the statement \u0027My opinion is that it is always okay for master to be unstable in the sense that API compatibility \"breaks\"\u0027. So far, we successfully managed to NOT break backward compatibility when making API (to our Puppet manifests) changes. We should continue our amazing work and I don\u0027t see I compelling reason to change our way of doing.\n\nRegarding \"breaking master\" for stable release installations, it would be wrong to assume that we can \"break master\" as soon as a stable release is cut. We are usually still working on stabilizing the newly released stable version.\n\nSo I think the core of the problem is there: Now that Kilo is released, people will start migrating to Kilo and discover bugs or missing features in our modules for the next ~3 months. So I expect people to start reporting bugs against Kilo installations.\n\nIf we cut a stable branch now, we will have to support both master and stable/kilo branches.  Since we are bad with backports, we should help ourselves. I suggest we wait ~3 months before cutting a stable branch for kilo.\n\nI\u0027m also *strongly* against the concept of future/* branches. We already have the concept of stable branches and the master branch. There is no need to introduce a 3rd type of branch. If we wish to work on liberty support, it should be done in master, not future/liberty. If we wish to support kilo (only), it should be done in stable/kilo. Otherwise we are making things more complicated than they should be for little gain.\n\nSo what\u0027s the correct timeframe to \"break master\" against stable branches? I don\u0027t know. But it shouldn\u0027t be 6 months (3 months look to be reasonable) otherwise we might just block our own efforts to support the next release by fear of breaking previous stable release.\n\nAlso, the only concrete example we had regarding \"breaking master\" was config name changes. This is simple to manage, OpenStack always made it easy for their operators but first deprecating the old config name.\n\nBut what about default config value change, new packages, package renames? Those are examples of changes that we don\u0027t know yet how to make it backward compatible with previous releases without introducing new Puppet parameters.\n\nSo now that Kilo is released, we should start focusing our effort to bugfix Kilo and starting thinking about supporting Liberty, not the 2nd last stable release (Juno).","commit_id":"548e5a77e1a2a6e81c69a870e1b38974c25e0f79"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"43d48c2d2b7c54d56f359e42c52c3de6f1ce57d0","unresolved":false,"context_lines":[{"line_number":28,"context_line":"  the development branch and used to integrate features from OpenStack master"},{"line_number":29,"context_line":"  or very recent release. That means master branch used to be broken for"},{"line_number":30,"context_line":"  stable releases. This is problem #2: when can we break master?"},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"* Over the time, our community grew and we\u0027ve got some contributions and"},{"line_number":33,"context_line":"  more feedback from operators world that complained master branch was broken"},{"line_number":34,"context_line":"  for a recent stable release. This is problem #3: how to warn Operators that"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3acd31a7_425dca13","line":31,"updated":"2015-05-05 19:53:24.000000000","message":"This relates to our new functional testing: up until a certain point beaker must test against the current release because pre-release distro packages for the next release aren\u0027t available yet. Beaker needs to know what repos to install, so we need to decide what those repos are and what date to switch them over.","commit_id":"548e5a77e1a2a6e81c69a870e1b38974c25e0f79"},{"author":{"_account_id":7156,"name":"Mathieu Gagné","email":"mgagne@calavera.ca","username":"mgagne"},"change_message_id":"58d820485ed1b4f735617dec2a8d407db663b657","unresolved":false,"context_lines":[{"line_number":28,"context_line":"  the development branch and used to integrate features from OpenStack master"},{"line_number":29,"context_line":"  or very recent release. That means master branch used to be broken for"},{"line_number":30,"context_line":"  stable releases. This is problem #2: when can we break master?"},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"* Over the time, our community grew and we\u0027ve got some contributions and"},{"line_number":33,"context_line":"  more feedback from operators world that complained master branch was broken"},{"line_number":34,"context_line":"  for a recent stable release. This is problem #3: how to warn Operators that"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3acd31a7_9d60e302","line":31,"in_reply_to":"3acd31a7_425dca13","updated":"2015-05-05 20:31:37.000000000","message":"What\u0027s the timeframe?","commit_id":"548e5a77e1a2a6e81c69a870e1b38974c25e0f79"},{"author":{"_account_id":9500,"name":"Matt Fischer","email":"matt@mattfischer.com","username":"mfisch"},"change_message_id":"50458a42ae66682ae10313212a373b5d8916eaac","unresolved":false,"context_lines":[{"line_number":29,"context_line":"  or very recent release. That means master branch used to be broken for"},{"line_number":30,"context_line":"  stable releases. This is problem #2: when can we break master?"},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"* Over the time, our community grew and we\u0027ve got some contributions and"},{"line_number":33,"context_line":"  more feedback from operators world that complained master branch was broken"},{"line_number":34,"context_line":"  for a recent stable release. This is problem #3: how to warn Operators that"},{"line_number":35,"context_line":"  master is going to be broken?"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3acd31a7_0e2ee342","line":32,"updated":"2015-05-05 17:08:19.000000000","message":"drop the word some","commit_id":"548e5a77e1a2a6e81c69a870e1b38974c25e0f79"},{"author":{"_account_id":3153,"name":"Emilien Macchi","email":"emilien@redhat.com","username":"emilienm"},"change_message_id":"677e3841320edfd863e983de8b0a219020646fed","unresolved":false,"context_lines":[{"line_number":29,"context_line":"  or very recent release. That means master branch used to be broken for"},{"line_number":30,"context_line":"  stable releases. This is problem #2: when can we break master?"},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"* Over the time, our community grew and we\u0027ve got some contributions and"},{"line_number":33,"context_line":"  more feedback from operators world that complained master branch was broken"},{"line_number":34,"context_line":"  for a recent stable release. This is problem #3: how to warn Operators that"},{"line_number":35,"context_line":"  master is going to be broken?"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1aca2d91_63bba9c5","line":32,"in_reply_to":"3acd31a7_0e2ee342","updated":"2015-05-23 18:37:50.000000000","message":"Done","commit_id":"548e5a77e1a2a6e81c69a870e1b38974c25e0f79"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"43d48c2d2b7c54d56f359e42c52c3de6f1ce57d0","unresolved":false,"context_lines":[{"line_number":45,"context_line":""},{"line_number":46,"context_line":"* Problem #1: WIP"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"* Problem #2: WIP"},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"* Problem #3: WIP"},{"line_number":51,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"3acd31a7_62ab2676","line":48,"updated":"2015-05-05 19:53:24.000000000","message":"My first suggestion was described in the etherpad, creating a branch called \u0027future/kilo\u0027 for those changes that would get merged back into master and then into stable/kilo when that branch is created.\n\nAnother possibility that would help my case as a developer but may not help the operator case much is to pick a date after which it is okay to start targeting the next release, and loudly announce it. We have been saying that master targets the next release but the truth is that it doesn\u0027t until some ill-defined point where the next release is packageable. The date would be based on when pre-release repos are publicly available for our supported operating systems -- basically, as soon as we can point beaker at something and have it pass tests. Whatever repos we use for beaker should be documented on our wiki so that developers can use them as well. The date for this cutover should be loudly announced so that developers can switch repos and operators can know that master is not safe anymore.","commit_id":"548e5a77e1a2a6e81c69a870e1b38974c25e0f79"},{"author":{"_account_id":7156,"name":"Mathieu Gagné","email":"mgagne@calavera.ca","username":"mgagne"},"change_message_id":"58d820485ed1b4f735617dec2a8d407db663b657","unresolved":false,"context_lines":[{"line_number":45,"context_line":""},{"line_number":46,"context_line":"* Problem #1: WIP"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"* Problem #2: WIP"},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"* Problem #3: WIP"},{"line_number":51,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"3acd31a7_8f0b0a24","line":48,"in_reply_to":"3acd31a7_62ab2676","updated":"2015-05-05 20:31:37.000000000","message":"As stated previously, I\u0027m against having future/kilo for the reason mentioned above.\n\nYes to have a delayed stable release. How about until \"next\" beta1 is released?","commit_id":"548e5a77e1a2a6e81c69a870e1b38974c25e0f79"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"71fde08edb70f4b66d7fe29d709754c084944055","unresolved":false,"context_lines":[{"line_number":45,"context_line":""},{"line_number":46,"context_line":"* Problem #1: WIP"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"* Problem #2: WIP"},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"* Problem #3: WIP"},{"line_number":51,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"1aca2d91_e7512a10","line":48,"in_reply_to":"3acd31a7_8f0b0a24","updated":"2015-05-06 04:06:19.000000000","message":"\u003e Yes to have a delayed stable release. How about until \"next\" beta1 is released?\n\n+1","commit_id":"548e5a77e1a2a6e81c69a870e1b38974c25e0f79"}]}