)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":12898,"name":"Tony Breeds","email":"tony@bakeyournoodle.com","username":"tonyb"},"change_message_id":"9acf1fc6ff9e3c74d0844d409161534ed5454334","unresolved":false,"context_lines":[{"line_number":4,"context_line":"Commit:     Gorka Eguileor \u003cgeguileo@redhat.com\u003e"},{"line_number":5,"context_line":"CommitDate: 2019-04-11 20:01:08 +0200"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Release cinderlib 0.9.0 and cut stein"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"This commit releases cinderlib 0.9.0 as agreed in the Cinder team"},{"line_number":10,"context_line":"meeting to reflect it is a Tech Preview release, but almost ready for"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"3fce034c_3c47724e","line":7,"range":{"start_line":7,"start_character":28,"end_line":7,"end_character":37},"updated":"2019-04-12 22:28:02.000000000","message":"I don\u0027t see this cutting stein.  I was expecting to see a branches stanza or similar (which does really kinda make cycle-trailing make more sense).\n\nIf that\u0027s what you meant we can easily do it in a follow-up","commit_id":"9741228047e2fb0fec63ab2a5ef3391aa41960c0"},{"author":{"_account_id":9535,"name":"Gorka Eguileor","email":"geguileo@redhat.com","username":"Gorka"},"change_message_id":"7849b7cf4e7c31ae66ab71bd666037d0df2fd47a","unresolved":false,"context_lines":[{"line_number":4,"context_line":"Commit:     Gorka Eguileor \u003cgeguileo@redhat.com\u003e"},{"line_number":5,"context_line":"CommitDate: 2019-04-11 20:01:08 +0200"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Release cinderlib 0.9.0 and cut stein"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"This commit releases cinderlib 0.9.0 as agreed in the Cinder team"},{"line_number":10,"context_line":"meeting to reflect it is a Tech Preview release, but almost ready for"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"3fce034c_d81c256c","line":7,"range":{"start_line":7,"start_character":28,"end_line":7,"end_character":37},"in_reply_to":"3fce034c_3c47724e","updated":"2019-04-15 12:17:34.000000000","message":"Sorry, that part of the commit message is a leftover from a patch I didn\u0027t submit where I was cutting the Stein branch in deliverables/stein before realizing I couldn\u0027t do that because the project had been added as independent based on the time moment of the cycle it was added.","commit_id":"9741228047e2fb0fec63ab2a5ef3391aa41960c0"},{"author":{"_account_id":11904,"name":"Sean McGinnis","email":"sean.mcginnis@gmail.com","username":"SeanM"},"change_message_id":"2cc6741adafc55e44da23d9be16bfa948e32ce56","unresolved":false,"context_lines":[{"line_number":10,"context_line":"meeting to reflect it is a Tech Preview release, but almost ready for"},{"line_number":11,"context_line":"production."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Since the cinderlib project has the Cinder project as a dependency, we"},{"line_number":14,"context_line":"release it after it."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"Change-Id: Idc37f4c66f9eb38126bafc49326427db67713503"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"3fce034c_ba884a1f","line":13,"updated":"2019-04-12 16:14:35.000000000","message":"Another option we could consider is have this cycle-based, but use the \"cycle-trailing\" release model to allow time after the official coordinated release to do a final trailing release. That ties it clearly to a release cycle while still allowing us some time to react to last minute changes in the dependent project. It\u0027s usually used for deployment and packaging deliverables, but this would seem to be another type of deliverable that might make sense for that.","commit_id":"9741228047e2fb0fec63ab2a5ef3391aa41960c0"},{"author":{"_account_id":12898,"name":"Tony Breeds","email":"tony@bakeyournoodle.com","username":"tonyb"},"change_message_id":"9acf1fc6ff9e3c74d0844d409161534ed5454334","unresolved":false,"context_lines":[{"line_number":10,"context_line":"meeting to reflect it is a Tech Preview release, but almost ready for"},{"line_number":11,"context_line":"production."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Since the cinderlib project has the Cinder project as a dependency, we"},{"line_number":14,"context_line":"release it after it."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"Change-Id: Idc37f4c66f9eb38126bafc49326427db67713503"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"3fce034c_dc4c2e78","line":13,"range":{"start_line":13,"start_character":36,"end_line":13,"end_character":66},"updated":"2019-04-12 22:28:02.000000000","message":"That seems somewhat strange to me.  I kinda thought cinderlib was like neutron-lib or ironic-lib where core/common code was stored and then consumed by multi projects (server/client etc).\n\n/me clearly needs to understand the cinderlib design goal ... quick to the PTG! ;P","commit_id":"9741228047e2fb0fec63ab2a5ef3391aa41960c0"},{"author":{"_account_id":12898,"name":"Tony Breeds","email":"tony@bakeyournoodle.com","username":"tonyb"},"change_message_id":"9acf1fc6ff9e3c74d0844d409161534ed5454334","unresolved":false,"context_lines":[{"line_number":10,"context_line":"meeting to reflect it is a Tech Preview release, but almost ready for"},{"line_number":11,"context_line":"production."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Since the cinderlib project has the Cinder project as a dependency, we"},{"line_number":14,"context_line":"release it after it."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"Change-Id: Idc37f4c66f9eb38126bafc49326427db67713503"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"3fce034c_dc274eb6","line":13,"in_reply_to":"3fce034c_ba884a1f","updated":"2019-04-12 22:28:02.000000000","message":"I like the idea of cycle-trailing.  We should think about the switch to that.","commit_id":"9741228047e2fb0fec63ab2a5ef3391aa41960c0"},{"author":{"_account_id":9535,"name":"Gorka Eguileor","email":"geguileo@redhat.com","username":"Gorka"},"change_message_id":"7849b7cf4e7c31ae66ab71bd666037d0df2fd47a","unresolved":false,"context_lines":[{"line_number":10,"context_line":"meeting to reflect it is a Tech Preview release, but almost ready for"},{"line_number":11,"context_line":"production."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Since the cinderlib project has the Cinder project as a dependency, we"},{"line_number":14,"context_line":"release it after it."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"Change-Id: Idc37f4c66f9eb38126bafc49326427db67713503"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"3fce034c_1874ed67","line":13,"range":{"start_line":13,"start_character":36,"end_line":13,"end_character":66},"in_reply_to":"3fce034c_dc4c2e78","updated":"2019-04-15 12:17:34.000000000","message":"I agree, \"cycle-trailing\" is the best release model for cinderlib.\n\nIf I understood the docs correctly, we have to release 0.9.0 like this, since it\u0027s an independent project.  Then move it to \"cycle-trailing\" once the \"train\" directory is available under \"releases\".  And then when we release 1.0 on Train, we will cut the stable/train branch.\n\nAm I correct in my assumptions? Or can I cut a stable/stein branch for an independent project?\n\nTony, cinderlib is different.  It is a library that provides an object oriented abstraction of the Cinder drivers for the purpose of consuming them outside of OpenStack, but our priority is still the consumption of the drivers in Cinder, and we don\u0027t want to limit the flexibility of that interface with the more limited external interface.\nIt would also require a big refactoring effort in Cinder that could lead to new bugs.\n\nPS: I\u0027ll update the commit message to remove the mention of the stein cycle.","commit_id":"9741228047e2fb0fec63ab2a5ef3391aa41960c0"}]}