)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":8064,"name":"Jake Yip","email":"jake.yip@ardc.edu.au","username":"jake"},"change_message_id":"466ebc1e639c6f38dc65be72ace2e6d26b95402a","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"f9bd220d_70b748c2","updated":"2023-03-08 00:30:28.000000000","message":"Hi is there a link on how versioning works for *-tempest-plugin?\n\nAcross this topic, I see changes in major version (this), minor version [1], and patch version [2]. I would like to find out how to determine what version should we increment?\n\n[1] https://review.opendev.org/c/openstack/releases/+/876616\n[2] https://review.opendev.org/c/openstack/releases/+/876607","commit_id":"4317a600931644e82e34d04b056e8858e4ca82d6"},{"author":{"_account_id":8064,"name":"Jake Yip","email":"jake.yip@ardc.edu.au","username":"jake"},"change_message_id":"0f12cad7f3ad1060a0705ab369f695a78d209a0a","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"ff33bcfc_60b85d40","updated":"2023-03-10 00:10:27.000000000","message":"Thanks Elod for the detailed explanation!\n\nAs Bay/BayModel was a big thing in Magnum (that we have switched away from now), incrementing the MAJOR version in this case is fair to signal the removal.","commit_id":"4317a600931644e82e34d04b056e8858e4ca82d6"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"94d8da1f0930684b90a44b43e4ab9ec78cd44730","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"f48fe92a_22e0229e","in_reply_to":"f9bd220d_70b748c2","updated":"2023-03-08 15:30:18.000000000","message":"Hi Jake, there are two things:\n\n1) in general, release team is following semver rules [1], this is the basic rule:\n   - MAJOR version bump: in case of some backward incompatible change, api change, configuration change\n   - MINOR version bump: in case of new features, dependency changes\n   - PATCH version bump: in case of bug fixes\n2) and there is OpenStack release rules [2], for example cycle-with-intermediary projects need to bump at least a MINOR version between two series (i.e. at the 1st release in a new series), while projects with cycle-with-rc release model need to bump the MAJOR version.\n\nIn case of this patch I\u0027ve proposed the MAJOR version bump due to patch [1] that drops \"Bay and Baymodel\". Though, note, that I\u0027m only proposing this simply by looking at the commit messages. In case, you know that the given patch is not dropping directly support of a feature, not backward incompatible, then you are more then welcome to signal this or update the version bump according to the real code changes.\n\nI hope this explanation helps, but let me know if you have further questions :) And of course, let us know whether the MAJOR bump here is acceptable.\n\nCheers,\nElod\n\n[1] https://semver.org\n[2] https://releases.openstack.org/reference/using.html#using-new-release-command\n[3] https://zuul.opendev.org/t/openstack/build/faf9681662bb40229908b3af12b723de/log/tox/list-changes/list-changes-results.log#245-252","commit_id":"4317a600931644e82e34d04b056e8858e4ca82d6"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"9b482179abce2ff13cbbfce5cabc5748402305f6","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"d976fcea_df9ea84b","in_reply_to":"ff33bcfc_60b85d40","updated":"2023-03-10 12:28:00.000000000","message":"No problem, thanks for the review Jake!","commit_id":"4317a600931644e82e34d04b056e8858e4ca82d6"}]}