)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":8449,"name":"Marios Andreou","email":"marios.andreou@gmail.com","username":"marios"},"change_message_id":"d7253d7ee68b11295781b49dfca1b1f5cd22b6bc","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"6de65356_b6723954","updated":"2022-04-12 15:34:53.000000000","message":"going to respin this for anything that merged in the last week \n\nhttp://lists.openstack.org/pipermail/openstack-discuss/2022-April/028152.html","commit_id":"789a72ea560293ecf161221d8d35def37d0ce322"},{"author":{"_account_id":8449,"name":"Marios Andreou","email":"marios.andreou@gmail.com","username":"marios"},"change_message_id":"caadcd971a64d0c22c19852afb1d91760a192764","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"f5432c18_2127be32","updated":"2022-03-17 06:03:41.000000000","message":"wf-1 to allow for any discussion/comments before we proceed","commit_id":"789a72ea560293ecf161221d8d35def37d0ce322"},{"author":{"_account_id":8449,"name":"Marios Andreou","email":"marios.andreou@gmail.com","username":"marios"},"change_message_id":"d77b1fd542464e21e36717013b8f0c83ec2c3666","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"27dc48ab_2ca056e8","updated":"2022-04-13 11:08:53.000000000","message":"i closed out all the open ussuri things yesterday fyi http://lists.openstack.org/pipermail/openstack-discuss/2022-April/028152.html ","commit_id":"dfae032000a6595adf3ec722268f73dca14f49f3"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"f34d680532da687c53bb3ba4a875ed1ce81efca8","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"df7e74b0_16efeb4d","in_reply_to":"02a4b1ba_f685ba13","updated":"2022-04-13 13:29:40.000000000","message":"1st issue: ✔\n2nd issue: in the past the stable policy required that branches should be EOL\u0027d branch-by-branch, so that it is clearly visible for a project which branches are open and which are not, thus makes the (branch-by-branch) backporting clear and easy to follow. it could make less easy to follow from user perspective if projects would decide keeping open different stable branches and EOL\u0027ing other branches. for a project that is maintained for multiple project this is trivial, though i understand that TripleO is only (considered to) consumed by Red Hat. Anyway, I don\u0027t want to block it, i only think it\u0027s better to keep things in sync with OpenStack way of working. So if stable/ussuri is going to EOL then so should go stable/train, too, for TripleO.","commit_id":"dfae032000a6595adf3ec722268f73dca14f49f3"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"1b13c117d8867f9e9265e10a3ac97cfef613a699","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"bddab29a_b677b019","in_reply_to":"27dc48ab_2ca056e8","updated":"2022-04-13 13:09:57.000000000","message":"Thanks Marios. Before we continue with this patch, can you confirm that all the unnecessary job definitions were removed from project-config and other repositories (if there were any - based on the eol process 2nd step [1]).\n\nOn the other hand I strongly advise that do not skip any branch from the EOL line, as that could confuse consumers of OpenStack. I understand that TripleO is used by Red Hat only and the team chose to keep open Train as that is the supported branch by Red Hat, though since it\u0027s open source, anyone could use it. Nevertheless, if it is considered Red Hat only, maintained only by Red Hat, then it could be supported via downstream only as well. So I\u0027m rather see either option out of these two:\n\n1. if stable/train is not EOL\u0027d upstream, then keep it open for stable/ussuri as well\n2. if stable/ussuri is EOL\u0027d upstream, then EOL stable/train as well.\n\n\n[1] \u0027Remove any related zuul jobs that are defined in other repositories and not needed anymore.\u0027 -- https://docs.openstack.org/project-team-guide/stable-branches.html#end-of-life","commit_id":"dfae032000a6595adf3ec722268f73dca14f49f3"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"d2e296ca004b38ebd06b633bf318a6465ac23fd5","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"1168e713_f34f15da","in_reply_to":"5e71a7fc_d0224212","updated":"2022-04-13 14:23:06.000000000","message":"yes, I know that, i didn\u0027t even say that tripleo follows it :) anyway, I understand (and understood even before I asked the question) TripleO points, but wanted to call your attention that this is not fortunate and hoped that we could keep things consistent in community o:) If this discussion would come up on a different (core) project, maintained by multiple vendors, then I would strictly say NO and would ask for a wider discussion on the topic... but I don\u0027t want to block this, so I\u0027m also accepting this now for TripleO. Hashes are from the tip of the stable/ussuri branches, patch looks OK to me. Let\u0027s merge this.","commit_id":"dfae032000a6595adf3ec722268f73dca14f49f3"},{"author":{"_account_id":8449,"name":"Marios Andreou","email":"marios.andreou@gmail.com","username":"marios"},"change_message_id":"5af8e30f2f9ff13e2e9743a76f1f3a4a9ec3878f","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"5e71a7fc_d0224212","in_reply_to":"bd7ea7a6_a20096f1","updated":"2022-04-13 13:57:48.000000000","message":"also forgot to note we don\u0027t follow stable policy...","commit_id":"dfae032000a6595adf3ec722268f73dca14f49f3"},{"author":{"_account_id":8449,"name":"Marios Andreou","email":"marios.andreou@gmail.com","username":"marios"},"change_message_id":"dda4d5b8faf00ed7b29817329b8493ab454946b2","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"02a4b1ba_f685ba13","in_reply_to":"bddab29a_b677b019","updated":"2022-04-13 13:16:16.000000000","message":"2 issues \n\n1st is about the job definitions. we don\u0027t have any in project-config as far as i am aware. For our own job definitions in our tripleo repos yeah we already have the patches lined up to remove those (they are blocked on merging this in fact).\n\n2nd issue is about the eol - so are you objecting to this going eol because train is not yet eol? Yes we are keeping train for a little longer.\n\nbut please clarify are you blocking this?","commit_id":"dfae032000a6595adf3ec722268f73dca14f49f3"},{"author":{"_account_id":8449,"name":"Marios Andreou","email":"marios.andreou@gmail.com","username":"marios"},"change_message_id":"11e1108206773d891248d79e0f85f4d07dfdee9f","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"bd7ea7a6_a20096f1","in_reply_to":"df7e74b0_16efeb4d","updated":"2022-04-13 13:55:15.000000000","message":"train is kept around because the current community (basically red hat as you noted) is interested in that. We don\u0027t have the resources to maintain ussuri especially since we aren\u0027t consuming it for our own use cases. These points and more are already discussed in the move to independent release in https://opendev.org/openstack/tripleo-specs/src/branch/master/specs/xena/tripleo-independent-release.rst\n\nIf others are willing and able to step up and provide the resources to maintain the ussuri ci going then that would be a conversation worth having. As things stand I don\u0027t think that is going to happen.","commit_id":"dfae032000a6595adf3ec722268f73dca14f49f3"}]}