)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"6778c30cfdc00dd136d7f7d82712868bcbff4372","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"b10a56f2_a1943d8d","updated":"2022-09-12 07:05:33.000000000","message":"+1 while i read over the tc discusssion","commit_id":"3dccbe512ddce4b122bb8ae4e6e36c3692102193"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"bae7e75490c7527201bc8a85f64a6d31cc442fe3","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"2bddfa83_6410fd68","updated":"2022-09-10 17:13:54.000000000","message":"In Zed cycle, TC agree to use the unversioned template - https://etherpad.opendev.org/p/tc-zed-ptg#L360\n\nI am preparing it in https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/856903\n\nAlso the release script - https://review.opendev.org/c/openstack/project-config/+/856904\n\nLet\u0027s wait for them to merge and we can update this patch manually. Until then -1.","commit_id":"3dccbe512ddce4b122bb8ae4e6e36c3692102193"},{"author":{"_account_id":7634,"name":"Takashi Natsume","email":"takanattie@gmail.com","username":"natsumet"},"change_message_id":"e920f3adfa041c48167c4b4fd003804bdfd4e78d","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"7391d8aa_23aacd0a","updated":"2022-09-10 00:31:03.000000000","message":"recheck timeout","commit_id":"3dccbe512ddce4b122bb8ae4e6e36c3692102193"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"6778c30cfdc00dd136d7f7d82712868bcbff4372","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"84c99f08_136570f1","in_reply_to":"2bddfa83_6410fd68","updated":"2022-09-12 07:05:33.000000000","message":"thats not really a tc discision its a per project one.\nill read over it but im not sure i agree with that unless\nyou are saying there wil be no versioned ones any more.\n\nwhile os-vif is not release in dependet i want it to use the same deffiniton as nova","commit_id":"3dccbe512ddce4b122bb8ae4e6e36c3692102193"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"c9b56ea5e378f83d67b7368aac5680c46dd86a6a","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"fa055be9_3bea9450","in_reply_to":"84c99f08_136570f1","updated":"2022-09-12 07:55:21.000000000","message":"i assume you means this\n\n\n    (gmann) Should we remove the release specific job template for testing runtime?\n\n    Details in http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027713.html\n\n    Example: https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/833892\n\n    communcate it well as it trigger all projects to move to new py version testing. like we do for distro upgrade approach. \n\n    One thing this doesn\u0027t solve is branchless projects needing to test across a broad range of python versions to support stable branches and master. But the number of these is small and we can solve that separately\n\n    AGREE:\n\n    Yes we can do it but with proper communication to all the projects and give some window to test/fix them\n\n    key point is that jobs in the template may start as non-voting during a cycle, but may become voting (so you need to pay attention!)\n    \n    \n From my point of view this has not been communicated to projects at all.\n at least its teh first time im hearaing about it so looping back to my question\n will we apply the same non version config to nova\n \n if so then im fine with that otherwise i woudl want os-vif to all be versioned","commit_id":"3dccbe512ddce4b122bb8ae4e6e36c3692102193"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"8ef5b516360d2146564f6a434d1ef3b88ff56c68","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"3979aa90_6232d49b","in_reply_to":"932264fa_92ae2edd","updated":"2022-09-14 11:41:07.000000000","message":"yes, we willbe using the branche variant on jobs in the same template. We cannot use the branch variant in template but we can use in job. Example: https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/856903/2/zuul.d/project-templates.yaml#1600","commit_id":"3dccbe512ddce4b122bb8ae4e6e36c3692102193"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"fff18fca6d8a03071f3d0e4f45c6eab090c4eb57","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"fe45ed2a_e748f396","in_reply_to":"fa055be9_3bea9450","updated":"2022-09-12 08:45:53.000000000","message":"Basically this one https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/856903\n\nwhere name of template will not be versioned to release and a generic name template will be used so that we donot need to update all repo like this patch. \n\nAnd there is no difference in running jobs it is how we handle the updates in template either by updating all the repo every times (current way) or update it at central place only (new way 856903).\n\nAnd this is same as any other template in any projects or jobs.","commit_id":"3dccbe512ddce4b122bb8ae4e6e36c3692102193"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"3aaeaa39501922e15ae5bfebb78fdf8e5c4c262c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"932264fa_92ae2edd","in_reply_to":"fe45ed2a_e748f396","updated":"2022-09-12 10:51:02.000000000","message":"sure i understand how we could do this centrally but without using the branches\nkeyword in the openstack-python3-jobs definition \ni dont see how you plan to make sure that it does not change after we do the release. for A\n\nis the intent to duplciat the job for B because we dont rewally wany to change the set of jobs that are run via that template after we cut the stabel branch.","commit_id":"3dccbe512ddce4b122bb8ae4e6e36c3692102193"}]}