)]}'
{"deliverables/rocky/zun-tempest-plugin.yaml":[{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"0ea47ca17e1a18fe14f331cf53f7be76d87d45c4","unresolved":false,"context_lines":[{"line_number":12,"context_line":"  - version: rocky-em"},{"line_number":13,"context_line":"    projects:"},{"line_number":14,"context_line":"      - repo: openstack/zun-tempest-plugin"},{"line_number":15,"context_line":"        hash: fd84e5affdf6c39dad956e0a309bc0237e068e2f"},{"line_number":16,"context_line":"repository-settings:"},{"line_number":17,"context_line":"  openstack/zun-tempest-plugin: {}"},{"line_number":18,"context_line":"team: zun"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"1fa4df85_63ed1e24","line":15,"range":{"start_line":15,"start_character":13,"end_line":15,"end_character":54},"updated":"2020-02-29 04:36:45.000000000","message":"this is old tag of 2.0.0 version. Tempest and plugins support stable branch with master version till they declare the un-support of that stable. and that release of un-support stable tag is used as stable-em tag not the one released during start of support of cycle release.\n\nWe can go with two option here:\n1. use the last compatible commit hash for stable em tag. 0d639a465ea289781d5a3cb96fb283a85a284007 in case of zun-tempest-plugin which is before py2 drop.\n\n2. keep the tempest plugins release same as tempest. Means Tempest or it plugins release the stable branch support and un-support explicitly in separate release once stable is EM or master is not compatible with EM stable anymore.\n\nI prefer the 2nd one to syncup the release of all plugins with Tempest.","commit_id":"9863ec02631a6710b7f850c83df16c300c0b9e64"},{"author":{"_account_id":11904,"name":"Sean McGinnis","email":"sean.mcginnis@gmail.com","username":"SeanM"},"change_message_id":"c82bff8ce981e07c5fafda92b1d7fe1e205a1da6","unresolved":false,"context_lines":[{"line_number":12,"context_line":"  - version: rocky-em"},{"line_number":13,"context_line":"    projects:"},{"line_number":14,"context_line":"      - repo: openstack/zun-tempest-plugin"},{"line_number":15,"context_line":"        hash: fd84e5affdf6c39dad956e0a309bc0237e068e2f"},{"line_number":16,"context_line":"repository-settings:"},{"line_number":17,"context_line":"  openstack/zun-tempest-plugin: {}"},{"line_number":18,"context_line":"team: zun"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"1fa4df85_def4e5d1","line":15,"range":{"start_line":15,"start_character":13,"end_line":15,"end_character":54},"in_reply_to":"1fa4df85_63ed1e24","updated":"2020-02-29 11:43:16.000000000","message":"As the commit message mentions, you or the team would need to do another release if this is not the last point in the stable/rocky branch before going to extended maintenance. Rocky is now past the deadline for transitioning, so we would need that very soon.\n\nThe last point that stable/rocky was released would be the point it gets the rocky-em tag. From that point on, bugfixes may still be merged to the stable/rocky branch, but no more official tagging will be done off of it.\n\nThe team can also decide this branch is no longer going to be maintained and announce that, at which point there will be a six month period before it transitions to the end of life. That is the only point in the stable maintenance period where the latest commit on the branch, not the last release, is given a new tag of rocky-eol.\n\nhttps://docs.openstack.org/project-team-guide/stable-branches.html#maintenance-phases","commit_id":"9863ec02631a6710b7f850c83df16c300c0b9e64"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"7ec99cf07a19921ac3f4b79a98496ab767ebfef9","unresolved":false,"context_lines":[{"line_number":12,"context_line":"  - version: rocky-em"},{"line_number":13,"context_line":"    projects:"},{"line_number":14,"context_line":"      - repo: openstack/zun-tempest-plugin"},{"line_number":15,"context_line":"        hash: fd84e5affdf6c39dad956e0a309bc0237e068e2f"},{"line_number":16,"context_line":"repository-settings:"},{"line_number":17,"context_line":"  openstack/zun-tempest-plugin: {}"},{"line_number":18,"context_line":"team: zun"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"1fa4df85_fe00c169","line":15,"range":{"start_line":15,"start_character":13,"end_line":15,"end_character":54},"in_reply_to":"1fa4df85_def4e5d1","updated":"2020-02-29 13:38:27.000000000","message":"That is true for branched deliverables but Tempest and plugins are brachless. \n\nFor branchless, we release the start of support and end of support of stable release is done separately with the corresponding commit from master not by the old tag done at release time of that stable branch which is nothing but the start of support of that release.  \n\nFor example, End of support of pike in Tempest is this - I971bc29e2ab12999c3384385a8c55a4ed0a3c361\nWhich is from master commit after which Tempest will not support Pike on master code. So pike end of support for Tempest is this tag not the one released at pike release(that was start of support of pike)","commit_id":"9863ec02631a6710b7f850c83df16c300c0b9e64"}]}