)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":5202,"name":"Erno Kuvaja","email":"jokke@usr.fi","username":"jokke"},"change_message_id":"fc16ea250e26cc21c577064cb5c9e8f30fb02cb3","unresolved":false,"context_lines":[{"line_number":14,"context_line":"Example:"},{"line_number":15,"context_line":"Neutron now supports OVN backends and complex DPDK environments."},{"line_number":16,"context_line":"Installers have to create automation recipes to deploy these new"},{"line_number":17,"context_line":"environments but can\u0027t really do it before the feature is actually"},{"line_number":18,"context_line":"finished (otherwise it can\u0027t be tested remember). That said, it makes"},{"line_number":19,"context_line":"sense to give an extra-time (Phase I) for them to implement what\u0027s"},{"line_number":20,"context_line":"called \"Features\" in installers, after a stable release."},{"line_number":21,"context_line":"The phases criteria are documented in the patch."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"5f4e5783_23e366db","line":18,"range":{"start_line":17,"start_character":17,"end_line":18,"end_character":48},"updated":"2017-10-17 01:46:14.000000000","message":"This is what the trailing release cycle is for, no?","commit_id":"9dc406e76979d4f6f3827726ce5283270af5a4fb"},{"author":{"_account_id":14985,"name":"Alex Schultz","email":"aschultz@next-development.com","username":"mwhahaha"},"change_message_id":"a7651464dd96509bb138841b5b297c7a4f4833a5","unresolved":false,"context_lines":[{"line_number":14,"context_line":"Example:"},{"line_number":15,"context_line":"Neutron now supports OVN backends and complex DPDK environments."},{"line_number":16,"context_line":"Installers have to create automation recipes to deploy these new"},{"line_number":17,"context_line":"environments but can\u0027t really do it before the feature is actually"},{"line_number":18,"context_line":"finished (otherwise it can\u0027t be tested remember). That said, it makes"},{"line_number":19,"context_line":"sense to give an extra-time (Phase I) for them to implement what\u0027s"},{"line_number":20,"context_line":"called \"Features\" in installers, after a stable release."},{"line_number":21,"context_line":"The phases criteria are documented in the patch."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"5f4e5783_c0f11203","line":18,"range":{"start_line":17,"start_character":17,"end_line":18,"end_character":48},"in_reply_to":"5f4e5783_23e366db","updated":"2017-10-17 16:32:57.000000000","message":"So trailing is at most 2 weeks behind. So no it may not be sufficient to correctly implement all the features depending on what you are supporting. If you\u0027re only supporting the core projects then maybe you can get it, but there are a whole bunch of factors that feeds into can you ensure support all the things with an extra 2 weeks. The problem really seems to be that larger complex deployment support may take another 2 months to get right. I know we regularly struggle to get the Upgrade portion working correctly at the end of the cycle because that\u0027s something you won\u0027t know what is in the final release until the end. And then trying to ensure you can upgrade a complex deployment of additional projects within 2 weeks is not necessarily achievable.","commit_id":"9dc406e76979d4f6f3827726ce5283270af5a4fb"}],"doc/source/stable-branches.rst":[{"author":{"_account_id":14985,"name":"Alex Schultz","email":"aschultz@next-development.com","username":"mwhahaha"},"change_message_id":"d21818e99e8e887191d083ed021a401dca818dea","unresolved":false,"context_lines":[{"line_number":46,"context_line":"   basis."},{"line_number":47,"context_line":""},{"line_number":48,"context_line":""},{"line_number":49,"context_line":".. list-table:: stable-policy-relax"},{"line_number":50,"context_line":"   :header-rows: 1"},{"line_number":51,"context_line":"   :widths: 10 20 20 50"},{"line_number":52,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5f4e5783_039c1d0d","line":49,"range":{"start_line":49,"start_character":30,"end_line":49,"end_character":35},"updated":"2017-10-13 22:36:42.000000000","message":"relaxed","commit_id":"9dc406e76979d4f6f3827726ce5283270af5a4fb"},{"author":{"_account_id":2799,"name":"Andy McCrae","email":"andy.mccrae@googlemail.com","username":"andrew-mccrae"},"change_message_id":"3c53aa10050dc5adce10d7bc9a829999e1599222","unresolved":false,"context_lines":[{"line_number":46,"context_line":"   basis."},{"line_number":47,"context_line":""},{"line_number":48,"context_line":""},{"line_number":49,"context_line":".. list-table:: stable-policy-relax"},{"line_number":50,"context_line":"   :header-rows: 1"},{"line_number":51,"context_line":"   :widths: 10 20 20 50"},{"line_number":52,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5f4e5783_4702003f","line":49,"range":{"start_line":49,"start_character":30,"end_line":49,"end_character":35},"in_reply_to":"5f4e5783_039c1d0d","updated":"2017-10-16 12:38:49.000000000","message":"Probably worth naming \"stable-policy-trailing\" or something along those lines would work better to illustrate its a stable-policy for projects that are cycle-trailing (deployments etc).","commit_id":"9dc406e76979d4f6f3827726ce5283270af5a4fb"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"95156b6912c18f8b86471a4722e71ffe4ddb6279","unresolved":false,"context_lines":[{"line_number":46,"context_line":"   basis."},{"line_number":47,"context_line":""},{"line_number":48,"context_line":""},{"line_number":49,"context_line":".. list-table:: stable-policy-relax"},{"line_number":50,"context_line":"   :header-rows: 1"},{"line_number":51,"context_line":"   :widths: 10 20 20 50"},{"line_number":52,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5f4e5783_94624409","line":49,"range":{"start_line":49,"start_character":30,"end_line":49,"end_character":35},"in_reply_to":"5f4e5783_15f8a578","updated":"2017-10-17 14:30:07.000000000","message":"Having 1 tag represent 2 policies seems like it conveys less information to the consumer of the tag because they have to know enough about the product to understand which set of \"rules\" it claims to follow. For example, reviewers for stable releases for the project need to think \"is this a deployment project that follows the full stable policy, or is it using the more relaxed rules?\" every time a review is done. Having a separate tag name gives us that information immediately.","commit_id":"9dc406e76979d4f6f3827726ce5283270af5a4fb"},{"author":{"_account_id":3153,"name":"Emilien Macchi","email":"emilien@redhat.com","username":"emilienm"},"change_message_id":"f91992c573ac3e97cd1dec14eac73bbb34cb5d14","unresolved":false,"context_lines":[{"line_number":46,"context_line":"   basis."},{"line_number":47,"context_line":""},{"line_number":48,"context_line":""},{"line_number":49,"context_line":".. list-table:: stable-policy-relax"},{"line_number":50,"context_line":"   :header-rows: 1"},{"line_number":51,"context_line":"   :widths: 10 20 20 50"},{"line_number":52,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5f4e5783_15f8a578","line":49,"range":{"start_line":49,"start_character":30,"end_line":49,"end_character":35},"in_reply_to":"5f4e5783_4702003f","updated":"2017-10-16 22:09:11.000000000","message":"Thierry proposed the following:\n\n\"(...) we should consider there is one and only one stable branch policy, with two set of rules depending on whether you are a classic project or a deployment/lifecycle project. That way they can both use the same tag (follows-stable-policy)\"\n\nWhat do you think?","commit_id":"9dc406e76979d4f6f3827726ce5283270af5a4fb"},{"author":{"_account_id":12898,"name":"Tony Breeds","email":"tony@bakeyournoodle.com","username":"tonyb"},"change_message_id":"f6ed17a5b5c995ec7040d2e4cfc5bec0d20dadc8","unresolved":false,"context_lines":[{"line_number":46,"context_line":"   basis."},{"line_number":47,"context_line":""},{"line_number":48,"context_line":""},{"line_number":49,"context_line":".. list-table:: stable-policy-relax"},{"line_number":50,"context_line":"   :header-rows: 1"},{"line_number":51,"context_line":"   :widths: 10 20 20 50"},{"line_number":52,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f4b6375_943ec2be","line":49,"range":{"start_line":49,"start_character":30,"end_line":49,"end_character":35},"in_reply_to":"5f4e5783_94624409","updated":"2017-10-26 06:29:40.000000000","message":"I appreciate the singular place for discussion but I feel like we\u0027re putting the implantation before the analysis here.     There are pros and cons for a new tag vs a single tag.  I see that but for me the deciding factor will be how big the delta is between the existing policy and the end state of the alterations.","commit_id":"9dc406e76979d4f6f3827726ce5283270af5a4fb"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"02f0a9f572661400913dd889972f860b3702b410","unresolved":false,"context_lines":[{"line_number":49,"context_line":".. list-table:: stable-policy-relax"},{"line_number":50,"context_line":"   :header-rows: 1"},{"line_number":51,"context_line":"   :widths: 10 20 20 50"},{"line_number":52,"context_line":""},{"line_number":53,"context_line":"   - * Phase"},{"line_number":54,"context_line":"     * Time frame"},{"line_number":55,"context_line":"     * Summary"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5f4e5783_25127363","line":52,"updated":"2017-10-15 07:59:56.000000000","message":"Allow me to share what we are doing:","commit_id":"9dc406e76979d4f6f3827726ce5283270af5a4fb"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"02f0a9f572661400913dd889972f860b3702b410","unresolved":false,"context_lines":[{"line_number":54,"context_line":"     * Time frame"},{"line_number":55,"context_line":"     * Summary"},{"line_number":56,"context_line":"     * Changes Supported"},{"line_number":57,"context_line":"   - * I"},{"line_number":58,"context_line":"     * First 3 months"},{"line_number":59,"context_line":"     * Latest release"},{"line_number":60,"context_line":"     * All features and bugfixes (that meet the criteria described below) are appropriate"},{"line_number":61,"context_line":"   - * II"},{"line_number":62,"context_line":"     * 3-12 months after release"},{"line_number":63,"context_line":"     * Maintained release"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5f4e5783_40067d1f","line":60,"range":{"start_line":57,"start_character":0,"end_line":60,"end_character":89},"updated":"2017-10-15 07:59:56.000000000","message":"We keep that phase I, and we respect the same conditions you explained below. However that phase I runs for more than 3 months, we even consider keeping that for a whole cycle. This makes it more clear: The first cycle is still getting needed feature backports.\n\nBy being more lenient on the first Phase, you allow more spare room for company policies that want to include features \"last minute\" by basically allowing more \"last minutes\". What I mean here, is we\u0027ve experienced difficulties in the past to align business and release, and anything _could_ happen anytime.\n\nIMO, if we want to follow some kind of stability, we should avoid the anytime part, be clear with what we are doing. And if it\u0027s 3 months I am afraid that would be unfollowed in practice.","commit_id":"9dc406e76979d4f6f3827726ce5283270af5a4fb"},{"author":{"_account_id":13294,"name":"Javier Peña","email":"jpena@redhat.com","username":"jpena"},"change_message_id":"406e390cb7147201c4ccaccee213a7c03522762b","unresolved":false,"context_lines":[{"line_number":54,"context_line":"     * Time frame"},{"line_number":55,"context_line":"     * Summary"},{"line_number":56,"context_line":"     * Changes Supported"},{"line_number":57,"context_line":"   - * I"},{"line_number":58,"context_line":"     * First 3 months"},{"line_number":59,"context_line":"     * Latest release"},{"line_number":60,"context_line":"     * All features and bugfixes (that meet the criteria described below) are appropriate"},{"line_number":61,"context_line":"   - * II"},{"line_number":62,"context_line":"     * 3-12 months after release"},{"line_number":63,"context_line":"     * Maintained release"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5f4e5783_5b2e6292","line":60,"range":{"start_line":57,"start_character":0,"end_line":60,"end_character":89},"in_reply_to":"5f4e5783_40067d1f","updated":"2017-10-16 08:54:11.000000000","message":"I think the first 6 months for Phase I would be appropriate. It gives us a full cycle to backport required functionality, and that\u0027s enough time to be able to stop additional requirements after that cycle.","commit_id":"9dc406e76979d4f6f3827726ce5283270af5a4fb"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"c072d0dd603164a45801038f824c950391c9f301","unresolved":false,"context_lines":[{"line_number":54,"context_line":"     * Time frame"},{"line_number":55,"context_line":"     * Summary"},{"line_number":56,"context_line":"     * Changes Supported"},{"line_number":57,"context_line":"   - * I"},{"line_number":58,"context_line":"     * First 3 months"},{"line_number":59,"context_line":"     * Latest release"},{"line_number":60,"context_line":"     * All features and bugfixes (that meet the criteria described below) are appropriate"},{"line_number":61,"context_line":"   - * II"},{"line_number":62,"context_line":"     * 3-12 months after release"},{"line_number":63,"context_line":"     * Maintained release"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5f4e5783_875eb873","line":60,"range":{"start_line":57,"start_character":0,"end_line":60,"end_character":89},"in_reply_to":"5f4e5783_5b2e6292","updated":"2017-10-16 12:36:01.000000000","message":"On top of that, if you want to have a stricter process internally of 3 months, it\u0027s still possible.","commit_id":"9dc406e76979d4f6f3827726ce5283270af5a4fb"},{"author":{"_account_id":12898,"name":"Tony Breeds","email":"tony@bakeyournoodle.com","username":"tonyb"},"change_message_id":"f6ed17a5b5c995ec7040d2e4cfc5bec0d20dadc8","unresolved":false,"context_lines":[{"line_number":61,"context_line":"   - * II"},{"line_number":62,"context_line":"     * 3-12 months after release"},{"line_number":63,"context_line":"     * Maintained release"},{"line_number":64,"context_line":"     * All bugfixes and security patches (that meet the criteria described below) are"},{"line_number":65,"context_line":"       acceptable"},{"line_number":66,"context_line":"   - * III"},{"line_number":67,"context_line":"     * more than 12 months after release"},{"line_number":68,"context_line":"     * Legacy release"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f4b6375_f48f3627","line":65,"range":{"start_line":64,"start_character":7,"end_line":65,"end_character":17},"updated":"2017-10-26 06:29:40.000000000","message":"While this was fresh one thing I said wasn\u0027t appropriate was[1]  I\u0027m not convinced that this structure alters my appraisal.\n\nHere\u0027s things I see:\n\n* You\u0027re changing a default value and not informing consumers [A release note would fix that]\n* Medium seems to overstate the issue, but Low is clearly wrong :(\n* The bug has no indication that if was seen by a user.  From my read it seems like a developer saw the defaults were sub-optimal and wanted to fix them. [Additional details on the bug would fix that]\n\nI\u0027m not saying that shouldn\u0027t be backported and I\u0027m certainly picking on that developer/change/bug but it seems reasonable to evaluate the proposal against something.  With my reading of this policy and that review I would have at least flagged it as questionable in a review.\n\n[1]https://review.openstack.org/#/c/506330/","commit_id":"9dc406e76979d4f6f3827726ce5283270af5a4fb"},{"author":{"_account_id":14985,"name":"Alex Schultz","email":"aschultz@next-development.com","username":"mwhahaha"},"change_message_id":"fbaacaa98474b1424ff4e2e25bda920fc93cbc86","unresolved":false,"context_lines":[{"line_number":66,"context_line":"   - * III"},{"line_number":67,"context_line":"     * more than 12 months after release"},{"line_number":68,"context_line":"     * Legacy release"},{"line_number":69,"context_line":"     * Only critical bugfixes and security patches are acceptable"},{"line_number":70,"context_line":""},{"line_number":71,"context_line":".. note::"},{"line_number":72,"context_line":"   During Phase 1, features can be backported as long as they meet the following criteria:"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5f4e5783_836b6d1c","line":69,"updated":"2017-10-13 22:30:26.000000000","message":"I like this idea as it\u0027s sort of what we already follow. The issue I really see is this legacy III part as for some projects (tripleo/puppet/etc), there occasionally are things that we need to merge 12 months after for various reasons and the question I have around this (and the other) policy is who deems things as \u0027critical\u0027. \n\nAdditionally it seems that phase III is only a few days before EOL meaning it\u0027s just useless to even define. See https://releases.openstack.org/.  I\u0027ve never understood the point of phase III if it\u0027s only going to be ~3 days. If it was going to be for 3-6 months then maybe it would make sense to define it and continue to use it and for the relaxed one it might make sense to allow high/critical bugfixes.  This would allow a mini-lts for the projects that which to continue to carry this.","commit_id":"9dc406e76979d4f6f3827726ce5283270af5a4fb"},{"author":{"_account_id":12898,"name":"Tony Breeds","email":"tony@bakeyournoodle.com","username":"tonyb"},"change_message_id":"f6ed17a5b5c995ec7040d2e4cfc5bec0d20dadc8","unresolved":false,"context_lines":[{"line_number":66,"context_line":"   - * III"},{"line_number":67,"context_line":"     * more than 12 months after release"},{"line_number":68,"context_line":"     * Legacy release"},{"line_number":69,"context_line":"     * Only critical bugfixes and security patches are acceptable"},{"line_number":70,"context_line":""},{"line_number":71,"context_line":".. note::"},{"line_number":72,"context_line":"   During Phase 1, features can be backported as long as they meet the following criteria:"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f4b6375_d139ecf1","line":69,"in_reply_to":"5f4e5783_000c0539","updated":"2017-10-26 06:29:40.000000000","message":"So that\u0027s come up before, any[1] project is free to opt out of the EOL process.  For OSA, TripleO etc as long as there is gate testing that isn\u0027t burdensome to maintain and the limitations are understood[2]  you don\u0027t need EOL.  nova will EOL so you wont get official bugfixes[3]\n\n\n[1] Okay integrated projects would be really strange but I hope you take my point\n[2] For example openstack/requirements can\u0027t be tagged but it would in fact be EOL\u0027d so any requirements or constraints updates would be on the project\n[3] You could carry patches but that would make me cry[4]\n[4] No really I\u0027d cry :D","commit_id":"9dc406e76979d4f6f3827726ce5283270af5a4fb"},{"author":{"_account_id":12898,"name":"Tony Breeds","email":"tony@bakeyournoodle.com","username":"tonyb"},"change_message_id":"f6ed17a5b5c995ec7040d2e4cfc5bec0d20dadc8","unresolved":false,"context_lines":[{"line_number":66,"context_line":"   - * III"},{"line_number":67,"context_line":"     * more than 12 months after release"},{"line_number":68,"context_line":"     * Legacy release"},{"line_number":69,"context_line":"     * Only critical bugfixes and security patches are acceptable"},{"line_number":70,"context_line":""},{"line_number":71,"context_line":".. note::"},{"line_number":72,"context_line":"   During Phase 1, features can be backported as long as they meet the following criteria:"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f4b6375_d19d6c0a","line":69,"in_reply_to":"5f4e5783_836b6d1c","updated":"2017-10-26 06:29:40.000000000","message":"Addressing the duration of Phase III it was there mostly to handle icehouse which did have a Phase III of 3 months.  It was a terrible mess and wasted a lot of resources.\n\nWe can potentially, with input from infra, extend Phase III for 6 months as the stability of the gate/CI/code is much better now.    One challenge we always have to face is the scenario that $n months after release we discover a massive security issue that for reasons we can\u0027t patch within reasonable bounds of the stable policy.  do we just EOL that release? that (inability to fix) becomes more likely for larger values of $n\n\nThe point of who gets to call something critical has come up before.  And it\u0027s been left a little vague on purpose but basically it it boils down to[1] did someone on the bug team think \"the bug prevents a key feature from working properly (regression) for all users (or without a simple workaround) or result in data loss\"\n\n\n[1] https://wiki.openstack.org/wiki/BugTriage#Task_2:_Prioritize_confirmed_bugs_.28bug_supervisors.29","commit_id":"9dc406e76979d4f6f3827726ce5283270af5a4fb"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"02f0a9f572661400913dd889972f860b3702b410","unresolved":false,"context_lines":[{"line_number":66,"context_line":"   - * III"},{"line_number":67,"context_line":"     * more than 12 months after release"},{"line_number":68,"context_line":"     * Legacy release"},{"line_number":69,"context_line":"     * Only critical bugfixes and security patches are acceptable"},{"line_number":70,"context_line":""},{"line_number":71,"context_line":".. note::"},{"line_number":72,"context_line":"   During Phase 1, features can be backported as long as they meet the following criteria:"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5f4e5783_000c0539","line":69,"in_reply_to":"5f4e5783_836b6d1c","updated":"2017-10-15 07:59:56.000000000","message":"I agree on that part. I think we shouldn\u0027t respect the EOL date, as a deploy project, because we\u0027ll probably need to *consume* the EOL tag of upstream projects, to create our EOL release. As usual, if something was shoved last minute into the project (or any external dependency), we\u0027ll need to fix to have a working EOL release.","commit_id":"9dc406e76979d4f6f3827726ce5283270af5a4fb"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"02f0a9f572661400913dd889972f860b3702b410","unresolved":false,"context_lines":[{"line_number":71,"context_line":".. note::"},{"line_number":72,"context_line":"   During Phase 1, features can be backported as long as they meet the following criteria:"},{"line_number":73,"context_line":""},{"line_number":74,"context_line":"   * The feature has to be documented in the tracker and approved by the PTL on behalf on"},{"line_number":75,"context_line":"     the project team."},{"line_number":76,"context_line":"   * Features should not break anything *outside* of the project (external dependencies)."},{"line_number":77,"context_line":"     For example, if a library used by some other projects in or outside OpenStack,"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5f4e5783_0549b789","line":74,"range":{"start_line":74,"start_character":57,"end_line":74,"end_character":76},"updated":"2017-10-15 07:59:56.000000000","message":"by the PTL and/or eventually the project\u0027s \"stable\" team? This way you can have a team that guarantees the stability.","commit_id":"9dc406e76979d4f6f3827726ce5283270af5a4fb"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"02f0a9f572661400913dd889972f860b3702b410","unresolved":false,"context_lines":[{"line_number":73,"context_line":""},{"line_number":74,"context_line":"   * The feature has to be documented in the tracker and approved by the PTL on behalf on"},{"line_number":75,"context_line":"     the project team."},{"line_number":76,"context_line":"   * Features should not break anything *outside* of the project (external dependencies)."},{"line_number":77,"context_line":"     For example, if a library used by some other projects in or outside OpenStack,"},{"line_number":78,"context_line":"     the feature has to be fully backward compatible and no impact for the operator or"},{"line_number":79,"context_line":"     end-user."},{"line_number":80,"context_line":"   * They are backported because they meet an important use-case and for some reasons,"},{"line_number":81,"context_line":"     the code wasn\u0027t implemented during the latest cycle."},{"line_number":82,"context_line":"   * They can break dependencies that are part of the project, as long as it has been"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5f4e5783_e5269bce","line":79,"range":{"start_line":76,"start_character":5,"end_line":79,"end_character":14},"updated":"2017-10-15 07:59:56.000000000","message":"So this means NEVER have an interface change for the operator.\nIn that case what\u0027s the meaning of minor tags (not patch tags) for releases?\n\nIn our case, it happened once or two times we had to modify the interface for our users, and we documented and issued release notes accordingly. It was a necessary evil (I can\u0027t remember why though), and I think we should still have that opportunity while in Phase I.\n\nPhase II and III don\u0027t deserve that.","commit_id":"9dc406e76979d4f6f3827726ce5283270af5a4fb"},{"author":{"_account_id":12898,"name":"Tony Breeds","email":"tony@bakeyournoodle.com","username":"tonyb"},"change_message_id":"f6ed17a5b5c995ec7040d2e4cfc5bec0d20dadc8","unresolved":false,"context_lines":[{"line_number":92,"context_line":"   can be backported, as long as it\u0027s fully backward compatible and tested."},{"line_number":93,"context_line":""},{"line_number":94,"context_line":"Given that stable branches are created every 6 months, that means that at any"},{"line_number":95,"context_line":"given time, only one branch is in Phase I support and only one branch is in"},{"line_number":96,"context_line":"Phase II support. Depending on how long each branch is supported, there may be"},{"line_number":97,"context_line":"one or more releases in Phase III support."},{"line_number":98,"context_line":""},{"line_number":99,"context_line":"The exact length of any given stable branch life support is discussed amongst"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f4b6375_b115504b","line":96,"range":{"start_line":95,"start_character":54,"end_line":96,"end_character":16},"updated":"2017-10-26 06:29:40.000000000","message":"That\u0027s incorrect and needs to be fixed in a separate patch.  Ocata\u0027s short cycle meant that we had 2 in Phase II (and Phase III)","commit_id":"9dc406e76979d4f6f3827726ce5283270af5a4fb"},{"author":{"_account_id":14985,"name":"Alex Schultz","email":"aschultz@next-development.com","username":"mwhahaha"},"change_message_id":"fbaacaa98474b1424ff4e2e25bda920fc93cbc86","unresolved":false,"context_lines":[{"line_number":94,"context_line":"Given that stable branches are created every 6 months, that means that at any"},{"line_number":95,"context_line":"given time, only one branch is in Phase I support and only one branch is in"},{"line_number":96,"context_line":"Phase II support. Depending on how long each branch is supported, there may be"},{"line_number":97,"context_line":"one or more releases in Phase III support."},{"line_number":98,"context_line":""},{"line_number":99,"context_line":"The exact length of any given stable branch life support is discussed amongst"},{"line_number":100,"context_line":"stable branch maintainers and QA/infrastructure teams at the start of every"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5f4e5783_2364b949","line":97,"updated":"2017-10-13 22:30:26.000000000","message":"Is this bit still correct with both stable policies?","commit_id":"9dc406e76979d4f6f3827726ce5283270af5a4fb"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"02f0a9f572661400913dd889972f860b3702b410","unresolved":false,"context_lines":[{"line_number":94,"context_line":"Given that stable branches are created every 6 months, that means that at any"},{"line_number":95,"context_line":"given time, only one branch is in Phase I support and only one branch is in"},{"line_number":96,"context_line":"Phase II support. Depending on how long each branch is supported, there may be"},{"line_number":97,"context_line":"one or more releases in Phase III support."},{"line_number":98,"context_line":""},{"line_number":99,"context_line":"The exact length of any given stable branch life support is discussed amongst"},{"line_number":100,"context_line":"stable branch maintainers and QA/infrastructure teams at the start of every"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5f4e5783_e03d69c4","line":97,"in_reply_to":"5f4e5783_2364b949","updated":"2017-10-15 07:59:56.000000000","message":"If phase 2 is 3-12 months, you can indeed have 2  branches under that phase.","commit_id":"9dc406e76979d4f6f3827726ce5283270af5a4fb"}]}
