)]}'
{"goals/stein/python3-first.rst":[{"author":{"_account_id":4257,"name":"Zane Bitter","email":"zbitter@redhat.com","username":"zaneb"},"change_message_id":"8e3e0da7554a25b30628166e82f327965958f4a8","unresolved":false,"context_lines":[{"line_number":354,"context_line":"easier after the Zuul configuration is moved out of the project-config"},{"line_number":355,"context_line":"repository, so this step is left for last. Because adding the test job"},{"line_number":356,"context_line":"may require code changes, it will be up to each project team to take"},{"line_number":357,"context_line":"this step by adding ``openstack-python36-jobs`` to the list of"},{"line_number":358,"context_line":"templates associated with the project on the master branch. The change"},{"line_number":359,"context_line":"will be self-testing, and can either be structured to include the code"},{"line_number":360,"context_line":"changes (if they are trivial) or end a series of patches (if the code"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f79a3b5_5e4e3090","line":357,"range":{"start_line":357,"start_character":20,"end_line":357,"end_character":48},"updated":"2018-10-15 20:49:03.000000000","message":"or openstack-python37-jobs","commit_id":"afa0194cb4b999dd79550f25ee3d7eef02c6567a"},{"author":{"_account_id":10608,"name":"Matthew Edmonds","email":"edmondsw@us.ibm.com","username":"edmondsw"},"change_message_id":"8ff22e2b6104b415cc7f7e9c89434dad8bb4e72c","unresolved":false,"context_lines":[{"line_number":41,"context_line":"   PyPI."},{"line_number":42,"context_line":"6. There are functional test jobs running under python 3."},{"line_number":43,"context_line":"7. The wiki tracking page is up to date for the project."},{"line_number":44,"context_line":"8. Projects are running python 3.6 or python 3.7 unit test jobs."},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"The goal champions will start by preparing the patches for steps"},{"line_number":47,"context_line":"1-5. That will give project teams more time to focus on steps 6-8,"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3f79a3b5_6ce311a2","line":44,"updated":"2018-10-17 19:33:23.000000000","message":"Why aren\u0027t we also mentioning 3.5 here? Don\u0027t we want to support 3.5 as the only 3.x included in Ubuntu 16.04 LTS, which will not reach EOS until 2021? Else when we drop py27 support we\u0027ll effectively be dropping Ubuntu 16.04 LTS support as well.","commit_id":"3ee83dbde6e215d96bc74c75177189a4c05574c6"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"0cc0fc196b1e416735ce130a22ac76447d971eaf","unresolved":false,"context_lines":[{"line_number":41,"context_line":"   PyPI."},{"line_number":42,"context_line":"6. There are functional test jobs running under python 3."},{"line_number":43,"context_line":"7. The wiki tracking page is up to date for the project."},{"line_number":44,"context_line":"8. Projects are running python 3.6 or python 3.7 unit test jobs."},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"The goal champions will start by preparing the patches for steps"},{"line_number":47,"context_line":"1-5. That will give project teams more time to focus on steps 6-8,"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3f79a3b5_f5e920ab","line":44,"in_reply_to":"3f79a3b5_6ce311a2","updated":"2018-10-17 20:46:37.000000000","message":"We can\u0027t do everything. There are limited testing resources so I think we need to make a choice and we should choose the future. See my comments on https://review.openstack.org/#/c/611010/\n\nThe upstream projects do not have the resource to be involved in managing or verifying long term support, especially for distros that lag contemporary versions.\n\nWe need to do python3. If we\u0027re going to recommend a version, it should be _one_ version. If we are recommending one version, it should be the version that will be in common use at the end of the cycle.","commit_id":"3ee83dbde6e215d96bc74c75177189a4c05574c6"},{"author":{"_account_id":4257,"name":"Zane Bitter","email":"zbitter@redhat.com","username":"zaneb"},"change_message_id":"45eea74a530f5b6f311e86047127b43670658e45","unresolved":false,"context_lines":[{"line_number":41,"context_line":"   PyPI."},{"line_number":42,"context_line":"6. There are functional test jobs running under python 3."},{"line_number":43,"context_line":"7. The wiki tracking page is up to date for the project."},{"line_number":44,"context_line":"8. Projects are running python 3.6 or python 3.7 unit test jobs."},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"The goal champions will start by preparing the patches for steps"},{"line_number":47,"context_line":"1-5. That will give project teams more time to focus on steps 6-8,"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3f79a3b5_2d6d102f","line":44,"in_reply_to":"3f79a3b5_75443074","updated":"2018-10-18 00:08:52.000000000","message":"We\u0027re not mentioning 3.5 here because it\u0027s required in the current PTI already. So the goal as written after this patch would be to get to 3.5 + (3.6 or 3.7). The idea of this patch was to allow projects to move ahead with 3.7 support without having to test 3.5 + 3.6 + 3.7 in the gate.\n\nThere are folks who think we should drop 3.5, and even folks like Chris who think we should drop 3.6, but this patch is not proposing that.","commit_id":"3ee83dbde6e215d96bc74c75177189a4c05574c6"},{"author":{"_account_id":10608,"name":"Matthew Edmonds","email":"edmondsw@us.ibm.com","username":"edmondsw"},"change_message_id":"d56e9dd9f14556654c6b1f9c34171c8a8964bcb1","unresolved":false,"context_lines":[{"line_number":41,"context_line":"   PyPI."},{"line_number":42,"context_line":"6. There are functional test jobs running under python 3."},{"line_number":43,"context_line":"7. The wiki tracking page is up to date for the project."},{"line_number":44,"context_line":"8. Projects are running python 3.6 or python 3.7 unit test jobs."},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"The goal champions will start by preparing the patches for steps"},{"line_number":47,"context_line":"1-5. That will give project teams more time to focus on steps 6-8,"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3f79a3b5_75443074","line":44,"in_reply_to":"3f79a3b5_f5e920ab","updated":"2018-10-17 20:57:44.000000000","message":"I understand we can\u0027t test everything on every commit. But we could test more with periodic testing. And we can tell folks not to write code that won\u0027t work on a range of 3.x versions we agree to support, which I am arguing needs to include 3.5 even if that is only validated by periodic testing.","commit_id":"3ee83dbde6e215d96bc74c75177189a4c05574c6"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"0cc0fc196b1e416735ce130a22ac76447d971eaf","unresolved":false,"context_lines":[{"line_number":346,"context_line":"to date with information about blockers, test jobs, etc. as they work"},{"line_number":347,"context_line":"on this goal (and after, ideally)."},{"line_number":348,"context_line":""},{"line_number":349,"context_line":"Python 3.6 or 3.7 Unit Test Jobs"},{"line_number":350,"context_line":"---------------------------------"},{"line_number":351,"context_line":""},{"line_number":352,"context_line":"`On the mailing list`_ Zane proposed updating to test with Python 3.6"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3f79a3b5_b52968f2","line":349,"updated":"2018-10-17 20:46:37.000000000","message":"let\u0027s not be ambiguous","commit_id":"3ee83dbde6e215d96bc74c75177189a4c05574c6"},{"author":{"_account_id":4257,"name":"Zane Bitter","email":"zbitter@redhat.com","username":"zaneb"},"change_message_id":"45eea74a530f5b6f311e86047127b43670658e45","unresolved":false,"context_lines":[{"line_number":346,"context_line":"to date with information about blockers, test jobs, etc. as they work"},{"line_number":347,"context_line":"on this goal (and after, ideally)."},{"line_number":348,"context_line":""},{"line_number":349,"context_line":"Python 3.6 or 3.7 Unit Test Jobs"},{"line_number":350,"context_line":"---------------------------------"},{"line_number":351,"context_line":""},{"line_number":352,"context_line":"`On the mailing list`_ Zane proposed updating to test with Python 3.6"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3f79a3b5_2d4670a9","line":349,"in_reply_to":"3f79a3b5_b52968f2","updated":"2018-10-18 00:08:52.000000000","message":"The point of the change is to be ambiguous, to reduce the number of gate jobs. However, it might pay to update the paragraph below to state that projects should add jobs for the latest version that passes and work toward raising that ceiling to 3.7, so they don\u0027t think they should be tossing a coin or something.","commit_id":"3ee83dbde6e215d96bc74c75177189a4c05574c6"},{"author":{"_account_id":11904,"name":"Sean McGinnis","email":"sean.mcginnis@gmail.com","username":"SeanM"},"change_message_id":"22b4989575a26809cd3e64dec49eb93154d79202","unresolved":false,"context_lines":[{"line_number":361,"context_line":"trivial) or end a series of patches (if the code changes are"},{"line_number":362,"context_line":"significant)."},{"line_number":363,"context_line":""},{"line_number":364,"context_line":".. note::"},{"line_number":365,"context_line":""},{"line_number":366,"context_line":"   We do not plan to update the minimum version of python 3 we support"},{"line_number":367,"context_line":"   as part of this goal. Projects already running python 3.5 jobs"},{"line_number":368,"context_line":"   should continue to do so."},{"line_number":369,"context_line":""},{"line_number":370,"context_line":"References"},{"line_number":371,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3f79a3b5_860b0fd2","line":368,"range":{"start_line":364,"start_character":0,"end_line":368,"end_character":28},"updated":"2018-10-16 13:37:35.000000000","message":"I wonder about this statement now given some of the discussion. We need to either firmly state that we are going to keep 3.5 support through Stein, or we need to declare that as going away and 3.6 and/or 3.7 being the target.","commit_id":"3ee83dbde6e215d96bc74c75177189a4c05574c6"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"0cc0fc196b1e416735ce130a22ac76447d971eaf","unresolved":false,"context_lines":[{"line_number":361,"context_line":"trivial) or end a series of patches (if the code changes are"},{"line_number":362,"context_line":"significant)."},{"line_number":363,"context_line":""},{"line_number":364,"context_line":".. note::"},{"line_number":365,"context_line":""},{"line_number":366,"context_line":"   We do not plan to update the minimum version of python 3 we support"},{"line_number":367,"context_line":"   as part of this goal. Projects already running python 3.5 jobs"},{"line_number":368,"context_line":"   should continue to do so."},{"line_number":369,"context_line":""},{"line_number":370,"context_line":"References"},{"line_number":371,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3f79a3b5_758190c2","line":368,"range":{"start_line":364,"start_character":0,"end_line":368,"end_character":28},"in_reply_to":"3f79a3b5_6c2eb1fa","updated":"2018-10-17 20:46:37.000000000","message":"I don\u0027t think the fact that RHEL might be slow should constrain us, given that we have limited resources.","commit_id":"3ee83dbde6e215d96bc74c75177189a4c05574c6"},{"author":{"_account_id":10608,"name":"Matthew Edmonds","email":"edmondsw@us.ibm.com","username":"edmondsw"},"change_message_id":"d56e9dd9f14556654c6b1f9c34171c8a8964bcb1","unresolved":false,"context_lines":[{"line_number":361,"context_line":"trivial) or end a series of patches (if the code changes are"},{"line_number":362,"context_line":"significant)."},{"line_number":363,"context_line":""},{"line_number":364,"context_line":".. note::"},{"line_number":365,"context_line":""},{"line_number":366,"context_line":"   We do not plan to update the minimum version of python 3 we support"},{"line_number":367,"context_line":"   as part of this goal. Projects already running python 3.5 jobs"},{"line_number":368,"context_line":"   should continue to do so."},{"line_number":369,"context_line":""},{"line_number":370,"context_line":"References"},{"line_number":371,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3f79a3b5_40093427","line":368,"range":{"start_line":364,"start_character":0,"end_line":368,"end_character":28},"in_reply_to":"3f79a3b5_758190c2","updated":"2018-10-17 20:57:44.000000000","message":"Resources addressed above. But we\u0027ve got a bunch of folks in this community that work at Red Hat. Surely one of them can figure out if this will be an issue or not and speak up (even if it\u0027s just a head nod because they can\u0027t tell us specifically what version it will be yet).","commit_id":"3ee83dbde6e215d96bc74c75177189a4c05574c6"},{"author":{"_account_id":10608,"name":"Matthew Edmonds","email":"edmondsw@us.ibm.com","username":"edmondsw"},"change_message_id":"8ff22e2b6104b415cc7f7e9c89434dad8bb4e72c","unresolved":false,"context_lines":[{"line_number":361,"context_line":"trivial) or end a series of patches (if the code changes are"},{"line_number":362,"context_line":"significant)."},{"line_number":363,"context_line":""},{"line_number":364,"context_line":".. note::"},{"line_number":365,"context_line":""},{"line_number":366,"context_line":"   We do not plan to update the minimum version of python 3 we support"},{"line_number":367,"context_line":"   as part of this goal. Projects already running python 3.5 jobs"},{"line_number":368,"context_line":"   should continue to do so."},{"line_number":369,"context_line":""},{"line_number":370,"context_line":"References"},{"line_number":371,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3f79a3b5_6c2eb1fa","line":368,"range":{"start_line":364,"start_character":0,"end_line":368,"end_character":28},"in_reply_to":"3f79a3b5_860b0fd2","updated":"2018-10-17 19:33:23.000000000","message":"I don\u0027t think we can really talk about bumping the 3.x min until we know what 3.x will be in RHEL 8. It would be silly to drop 3.5 and then have to put it back for rhel.","commit_id":"3ee83dbde6e215d96bc74c75177189a4c05574c6"},{"author":{"_account_id":10608,"name":"Matthew Edmonds","email":"edmondsw@us.ibm.com","username":"edmondsw"},"change_message_id":"967e89acc60a1d574f7b03f8f6ad17d3a7fd20e8","unresolved":false,"context_lines":[{"line_number":364,"context_line":""},{"line_number":365,"context_line":".. note::"},{"line_number":366,"context_line":""},{"line_number":367,"context_line":"   We do not plan to update the minimum version of python 3 we support"},{"line_number":368,"context_line":"   as part of this goal. Projects already running python 3.5 jobs"},{"line_number":369,"context_line":"   should continue to do so."},{"line_number":370,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"3f79a3b5_2f28fd82","line":367,"updated":"2018-10-25 22:34:00.000000000","message":"If we don\u0027t ask everyone to support 3.5, why make anyone do so?\n\nI\u0027m also still concerned that this doesn\u0027t say 3.5 is supported (some other resolution could remove it, and indeed that\u0027s proposed: I11b136a9781dd1a77df536f099df10a6dd524e06) but some will read this and assume that it is.","commit_id":"c4b9bad28ae83dda74943fd1d4529a98839e88e8"},{"author":{"_account_id":11805,"name":"Corey Bryant","email":"corey.bryant@canonical.com","username":"coreycb"},"change_message_id":"8188fac2e4a2b70efd22f00bd1b95e25949a2100","unresolved":false,"context_lines":[{"line_number":364,"context_line":""},{"line_number":365,"context_line":".. note::"},{"line_number":366,"context_line":""},{"line_number":367,"context_line":"   We do not plan to update the minimum version of python 3 we support"},{"line_number":368,"context_line":"   as part of this goal. Projects already running python 3.5 jobs"},{"line_number":369,"context_line":"   should continue to do so."},{"line_number":370,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"3f79a3b5_e78c613a","line":367,"in_reply_to":"3f79a3b5_2f28fd82","updated":"2018-10-26 11:59:23.000000000","message":"I don\u0027t know the answers to your questions but they don\u0027t seem to have anything to do with this merge proposal. This merge proposal is just saying that optional py3.7 tests can be added. Would you like to propose another change to the python3-first goal doc with py3.5 specific details that you\u0027d like to see? As an aside I\u0027m curious what distro is going to need 3.5 support for stein+? It seems like an extreme corner case.","commit_id":"c4b9bad28ae83dda74943fd1d4529a98839e88e8"},{"author":{"_account_id":4257,"name":"Zane Bitter","email":"zbitter@redhat.com","username":"zaneb"},"change_message_id":"5b28fd61524c949f473d9829d506dce5c4d25865","unresolved":false,"context_lines":[{"line_number":364,"context_line":""},{"line_number":365,"context_line":".. note::"},{"line_number":366,"context_line":""},{"line_number":367,"context_line":"   We do not plan to update the minimum version of python 3 we support"},{"line_number":368,"context_line":"   as part of this goal. Projects already running python 3.5 jobs"},{"line_number":369,"context_line":"   should continue to do so."},{"line_number":370,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"3f79a3b5_78ec6ebb","line":367,"in_reply_to":"3f79a3b5_2f28fd82","updated":"2018-10-26 14:35:05.000000000","message":"I don\u0027t think there\u0027s any ambiguity here: it says don\u0027t remove your py35 jobs. (\"Projects already running python 3.5 jobs\" encompasses everything that is not Python 2-only.)\n\nThere is ambiguity about what will happen in future (and indeed a further resolution could, in principle, instruct teams to drop 3.5). At some point we\u0027ll have to make a final determination of which versions we intend to support in the release, but I don\u0027t think this goal will be the venue for doing that.","commit_id":"c4b9bad28ae83dda74943fd1d4529a98839e88e8"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"ff9b0c06658558aec0c8b814b1d54e50cf35149b","unresolved":false,"context_lines":[{"line_number":42,"context_line":"6. There are functional test jobs running under python 3."},{"line_number":43,"context_line":"7. The wiki tracking page is up to date for the project."},{"line_number":44,"context_line":"8. Projects are running python 3.6 unit test jobs."},{"line_number":45,"context_line":"9. Projects are running optional python3.7 unit test jobs."},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"The goal champions will start by preparing the patches for steps"},{"line_number":48,"context_line":"1-5. That will give project teams more time to focus on steps 6-8,"}],"source_content_type":"text/x-rst","patch_set":5,"id":"3f79a3b5_2e35c6d3","line":45,"updated":"2018-11-02 19:10:22.000000000","message":"Are you planning on tracking this optional work with an additional task?\n\nThis is my personal opinion, but if this is going to be optional criteria for the goal added *after* the original proposal, then it\u0027s likely going to be hard to find out which projects opted into doing the extra work short of digging into each project individually.","commit_id":"3a1eccbf5e3bb986e8c136e7f244bb5b5a27ccb3"},{"author":{"_account_id":11805,"name":"Corey Bryant","email":"corey.bryant@canonical.com","username":"coreycb"},"change_message_id":"44fb17e98655ca6c0554ccd78f508021dfa76618","unresolved":false,"context_lines":[{"line_number":42,"context_line":"6. There are functional test jobs running under python 3."},{"line_number":43,"context_line":"7. The wiki tracking page is up to date for the project."},{"line_number":44,"context_line":"8. Projects are running python 3.6 unit test jobs."},{"line_number":45,"context_line":"9. Projects are running optional python3.7 unit test jobs."},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"The goal champions will start by preparing the patches for steps"},{"line_number":48,"context_line":"1-5. That will give project teams more time to focus on steps 6-8,"}],"source_content_type":"text/x-rst","patch_set":5,"id":"3f79a3b5_2feda4b7","line":45,"in_reply_to":"3f79a3b5_065a18f4","updated":"2018-11-05 18:02:45.000000000","message":"Yes those are the 2 open questions, where to document and whether to drop py35. There have been a few -1\u0027s to dropping py35, but I don\u0027t think anyone has made a good case for where stein will be run in production on py35 other than venvs on older distros.","commit_id":"3a1eccbf5e3bb986e8c136e7f244bb5b5a27ccb3"},{"author":{"_account_id":11805,"name":"Corey Bryant","email":"corey.bryant@canonical.com","username":"coreycb"},"change_message_id":"694808b5b4a795eb31e89ec09b037d1f35c07c92","unresolved":false,"context_lines":[{"line_number":42,"context_line":"6. There are functional test jobs running under python 3."},{"line_number":43,"context_line":"7. The wiki tracking page is up to date for the project."},{"line_number":44,"context_line":"8. Projects are running python 3.6 unit test jobs."},{"line_number":45,"context_line":"9. Projects are running optional python3.7 unit test jobs."},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"The goal champions will start by preparing the patches for steps"},{"line_number":48,"context_line":"1-5. That will give project teams more time to focus on steps 6-8,"}],"source_content_type":"text/x-rst","patch_set":5,"id":"3f79a3b5_385df3ea","line":45,"in_reply_to":"3f79a3b5_2e35c6d3","updated":"2018-11-05 12:47:14.000000000","message":"I started tracking it here: https://storyboard.openstack.org/#!/story/2004073\n\nI\u0027d consider it a success if we were able to enable a subset of py37 unit tests in stein. Most of the projects that had py37 unit tests proposed were glad to see them. It\u0027s unfortunate that push back by one project stopped everything in its tracks.","commit_id":"3a1eccbf5e3bb986e8c136e7f244bb5b5a27ccb3"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"17ee5b053e4cc712da8eb236c08b9e84ba66d2b1","unresolved":false,"context_lines":[{"line_number":42,"context_line":"6. There are functional test jobs running under python 3."},{"line_number":43,"context_line":"7. The wiki tracking page is up to date for the project."},{"line_number":44,"context_line":"8. Projects are running python 3.6 unit test jobs."},{"line_number":45,"context_line":"9. Projects are running optional python3.7 unit test jobs."},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"The goal champions will start by preparing the patches for steps"},{"line_number":48,"context_line":"1-5. That will give project teams more time to focus on steps 6-8,"}],"source_content_type":"text/x-rst","patch_set":5,"id":"3f79a3b5_4df2686b","line":45,"in_reply_to":"3f79a3b5_2feda4b7","updated":"2018-11-05 19:39:58.000000000","message":"OK, so if you\u0027re most interested in the 3.7 work I would focus on that and not worry about the 3.5 question. You don\u0027t need a governance change to do that, either. There\u0027s already a mailing list thread, so you can refer to that. Teams that want to take the new tests can. Teams that want to drop 3.5 at the same time can. We don\u0027t need everyone to do optional stuff in exactly the same way.","commit_id":"3a1eccbf5e3bb986e8c136e7f244bb5b5a27ccb3"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"b6587191ce1de3ac3f6df6b232c1a02948d198ea","unresolved":false,"context_lines":[{"line_number":42,"context_line":"6. There are functional test jobs running under python 3."},{"line_number":43,"context_line":"7. The wiki tracking page is up to date for the project."},{"line_number":44,"context_line":"8. Projects are running python 3.6 unit test jobs."},{"line_number":45,"context_line":"9. Projects are running optional python3.7 unit test jobs."},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"The goal champions will start by preparing the patches for steps"},{"line_number":48,"context_line":"1-5. That will give project teams more time to focus on steps 6-8,"}],"source_content_type":"text/x-rst","patch_set":5,"id":"3f79a3b5_065a18f4","line":45,"in_reply_to":"3f79a3b5_385df3ea","updated":"2018-11-05 14:09:32.000000000","message":"That pushback indicates that the plan wasn\u0027t completely worked out, since legitimate questions were raised. Let\u0027s get those answers worked out, and then continue.\n\nAre the only open questions about whether to drop 3.5 testing at the same time as adding 3.7 and how exactly to document the desire to add 3.7 support?","commit_id":"3a1eccbf5e3bb986e8c136e7f244bb5b5a27ccb3"},{"author":{"_account_id":11805,"name":"Corey Bryant","email":"corey.bryant@canonical.com","username":"coreycb"},"change_message_id":"511ef55043dc9b9d4b0e906c3b599760476c06c9","unresolved":false,"context_lines":[{"line_number":42,"context_line":"6. There are functional test jobs running under python 3."},{"line_number":43,"context_line":"7. The wiki tracking page is up to date for the project."},{"line_number":44,"context_line":"8. Projects are running python 3.6 unit test jobs."},{"line_number":45,"context_line":"9. Projects are running optional python3.7 unit test jobs."},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"The goal champions will start by preparing the patches for steps"},{"line_number":48,"context_line":"1-5. That will give project teams more time to focus on steps 6-8,"}],"source_content_type":"text/x-rst","patch_set":5,"id":"3f79a3b5_a80d2a41","line":45,"in_reply_to":"3f79a3b5_4df2686b","updated":"2018-11-05 20:27:12.000000000","message":"I\u0027d like to take that route except there\u0027s been push back on dropping py35 tests since the python3-first goal states that \"We do not plan to update the minimum version of python 3 we support as part of this goal. Projects already running python 3.5 jobs should continue to do so.\" \"Should\" isn\u0027t the same as \"Must\" so perhaps it\u0027s ok to drop py35 tests for some projects without a change to the goal wording. Additionally infra can\u0027t run 3 x py3 flavors (3.5, 3.6, and 3.7).","commit_id":"3a1eccbf5e3bb986e8c136e7f244bb5b5a27ccb3"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"52e40c67cf9d78f732bc762dcae40193ff31ce18","unresolved":false,"context_lines":[{"line_number":42,"context_line":"6. There are functional test jobs running under python 3."},{"line_number":43,"context_line":"7. The wiki tracking page is up to date for the project."},{"line_number":44,"context_line":"8. Projects are running python 3.6 unit test jobs."},{"line_number":45,"context_line":"9. Projects are running optional python3.7 unit test jobs."},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"The goal champions will start by preparing the patches for steps"},{"line_number":48,"context_line":"1-5. That will give project teams more time to focus on steps 6-8,"}],"source_content_type":"text/x-rst","patch_set":5,"id":"3f79a3b5_be56c0cc","line":45,"in_reply_to":"3f79a3b5_7e3028eb","updated":"2018-11-05 21:14:55.000000000","message":"\u003e It\u0027s been brought up in a few places starting here:\n \u003e http://lists.openstack.org/pipermail/openstack-dev/2018-October/135632.html\n\nAndreas is concerned about resources. That\u0027s not the same as saying \"infra could not run all 3 flavors\".\n\n \u003e I think that\u0027s also the idea behind focusing on 2 py3 versions (min\n \u003e and max) in Zane\u0027s proposal: https://review.openstack.org/#/c/613145/2/resolutions/20181024-python-update-process.rst\n\nYes, we have several aspects of this in flux at the same time. I\u0027m suggesting that if you want to make progress on the bit you seemed to care about most, you could focus on just adding 3.7 jobs while we deal with the rest of it. Your work doesn\u0027t need to be completely stopped.","commit_id":"3a1eccbf5e3bb986e8c136e7f244bb5b5a27ccb3"},{"author":{"_account_id":11805,"name":"Corey Bryant","email":"corey.bryant@canonical.com","username":"coreycb"},"change_message_id":"1aacf03791cce934e8cec0a233ac30c47677b6c2","unresolved":false,"context_lines":[{"line_number":42,"context_line":"6. There are functional test jobs running under python 3."},{"line_number":43,"context_line":"7. The wiki tracking page is up to date for the project."},{"line_number":44,"context_line":"8. Projects are running python 3.6 unit test jobs."},{"line_number":45,"context_line":"9. Projects are running optional python3.7 unit test jobs."},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"The goal champions will start by preparing the patches for steps"},{"line_number":48,"context_line":"1-5. That will give project teams more time to focus on steps 6-8,"}],"source_content_type":"text/x-rst","patch_set":5,"id":"3f79a3b5_7e3028eb","line":45,"in_reply_to":"3f79a3b5_83892f2a","updated":"2018-11-05 21:06:48.000000000","message":"It\u0027s been brought up in a few places starting here: http://lists.openstack.org/pipermail/openstack-dev/2018-October/135632.html\n\nI think that\u0027s also the idea behind focusing on 2 py3 versions (min and max) in Zane\u0027s proposal: https://review.openstack.org/#/c/613145/2/resolutions/20181024-python-update-process.rst","commit_id":"3a1eccbf5e3bb986e8c136e7f244bb5b5a27ccb3"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"faf98321e1f9804f998386b58a75c8db46086c64","unresolved":false,"context_lines":[{"line_number":42,"context_line":"6. There are functional test jobs running under python 3."},{"line_number":43,"context_line":"7. The wiki tracking page is up to date for the project."},{"line_number":44,"context_line":"8. Projects are running python 3.6 unit test jobs."},{"line_number":45,"context_line":"9. Projects are running optional python3.7 unit test jobs."},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"The goal champions will start by preparing the patches for steps"},{"line_number":48,"context_line":"1-5. That will give project teams more time to focus on steps 6-8,"}],"source_content_type":"text/x-rst","patch_set":5,"id":"3f79a3b5_83892f2a","line":45,"in_reply_to":"3f79a3b5_a80d2a41","updated":"2018-11-05 20:42:05.000000000","message":"I didn\u0027t see anyone say that infra could not run all 3 flavors. Where is that?","commit_id":"3a1eccbf5e3bb986e8c136e7f244bb5b5a27ccb3"},{"author":{"_account_id":11805,"name":"Corey Bryant","email":"corey.bryant@canonical.com","username":"coreycb"},"change_message_id":"0fcc87c4fbac66cbeb49ce6d427f339db79f78ab","unresolved":false,"context_lines":[{"line_number":42,"context_line":"6. There are functional test jobs running under python 3."},{"line_number":43,"context_line":"7. The wiki tracking page is up to date for the project."},{"line_number":44,"context_line":"8. Projects are running python 3.6 unit test jobs."},{"line_number":45,"context_line":"9. Projects are running optional python3.7 unit test jobs."},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"The goal champions will start by preparing the patches for steps"},{"line_number":48,"context_line":"1-5. That will give project teams more time to focus on steps 6-8,"}],"source_content_type":"text/x-rst","patch_set":5,"id":"3f79a3b5_3ea15093","line":45,"in_reply_to":"3f79a3b5_be56c0cc","updated":"2018-11-05 21:25:48.000000000","message":"Thanks Doug. I appreciate the help in trying to move forward on this.\n\n@ajaeger (I will ping Andreas directly for comment too). Any chance of a +1 from you and infra on enabling 3 flavors of py3 unit tests at the same time for stein?","commit_id":"3a1eccbf5e3bb986e8c136e7f244bb5b5a27ccb3"}]}