)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":8833,"name":"Rabi Mishra","email":"ramishra@redhat.com","username":"rabi"},"change_message_id":"d615af37919f808bbce110bcd77e027e5d648c2f","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"ed60ab4b_040dd892","updated":"2022-10-22 13:53:19.000000000","message":"I don\u0027t think we are ready to do this now, unless forced/mandated for some reason. With TripleO moving to independent release model, we don\u0027t have any official releases yet after wallaby and we won\u0027t want to move wallaby to EM.\n\n@marios please weigh in your his views based on history and past discussions.","commit_id":"2dedb98750055f1800e907741382efd510946bfc"},{"author":{"_account_id":8833,"name":"Rabi Mishra","email":"ramishra@redhat.com","username":"rabi"},"change_message_id":"a44c5783d9ce039d0e616a1d6b286681a6f92841","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"6e9bf3f1_42464e7a","in_reply_to":"2a8cacaa_f51da177","updated":"2022-11-04 14:38:52.000000000","message":"Just following on the irc discussion and ping on this. If \"EM transition is common process\" can we please update https://docs.openstack.org/project-team-guide/stable-branches.html#maintenance-phases which clearly states below?\n\n\"It is not required that all projects for a given branch transition between phases at the same time\" \n\nAnyway, it seems we have not planning to make wallaby release in the near future. If EM transition is a common process, we can do it.","commit_id":"2dedb98750055f1800e907741382efd510946bfc"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"09500abe60bcf0af01f19123919f2ec5026c409a","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"963bc6cf_298adbfa","in_reply_to":"6e9bf3f1_42464e7a","updated":"2022-11-04 17:05:20.000000000","message":"Thanks Rabi for pointing that out as actually our tooling does not allow to mark the series state as \u0027in Extended Maintenance\u0027 while releasing the same time from that series. So the doc should be definitely modified. (Also, considering the release team size, the best is to stick to move the branches to EM at the planned date for every project). On the other hand EOL\u0027ing is not synced, so for that at least the doc is correct o:)\n\nI\u0027ve updated the patch to make the validation pass (tripleo-docs is tagless, so no need to do there anything)","commit_id":"2dedb98750055f1800e907741382efd510946bfc"},{"author":{"_account_id":8833,"name":"Rabi Mishra","email":"ramishra@redhat.com","username":"rabi"},"change_message_id":"e15af5c8a89998fdf2b58b6b5d2939ce6044d0ff","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"2a8cacaa_f51da177","in_reply_to":"b31dd6a0_4c1420cf","updated":"2022-10-24 09:43:45.000000000","message":"\u003eHowever it also doesn\u0027t cause any problems for tripleo. It just means we won\u0027t make any more upstream releases. We can continue to merge backports.\n\nI understand that. However, are we going to be ok to not have any maintained stable branch/release? We\u0027re still backporting features to wallaby and we would do that for downstream OSP 17.1 in the near future. If we still want to do it maybe we cut zed branch before that(?). Also, what\u0027re the issues if we don\u0027t adhere to deadline now that TripleO is using \u0027independent\u0027 release model?","commit_id":"2dedb98750055f1800e907741382efd510946bfc"},{"author":{"_account_id":8449,"name":"Marios Andreou","email":"marios.andreou@gmail.com","username":"marios"},"change_message_id":"e61dc4c450eee7dd2e3bf9c89945590049dd9552","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"b31dd6a0_4c1420cf","in_reply_to":"ed60ab4b_040dd892","updated":"2022-10-24 07:01:01.000000000","message":"hello,\n\nwe have usually adhered to these deadlines and I believe it *is* forced because these transitions are openstack wide (i.e. https://releases.openstack.org/index.html dates here).\n\nHowever it also doesn\u0027t cause any problems for tripleo. It just means we won\u0027t make any more upstream releases. We can continue to merge backports.\n\nNote that train has been in EM for about a year now [1] and that is still an active branch for us. \n\nlets chat more on irc in a bit if you want? I think we\u0027ll want to make a final release for wallaby before it goes em so that patch will have to go before this one (i.e. release then tag em).\n\n\n\n[1] https://opendev.org/openstack/releases/commit/33e27362ff38ae98d14985664d885811f6c6bdb4","commit_id":"2dedb98750055f1800e907741382efd510946bfc"}]}