)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":1955,"name":"Alan Pevec","email":"alan.pevec@redhat.com","username":"apevec"},"change_message_id":"f748d85cc4f393b12d5192fd225c24d35395940f","unresolved":false,"context_lines":[{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Bump dogpile.cache lower bound to 0.6.2"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Keystone requires RegionInvalidationStrategy which comes with dogpile 0.6.2"},{"line_number":10,"context_line":"Introduced by https://review.openstack.org/#/c/349704/"},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"Change-Id: I6733cefef90d07330e219591dc3c49e170512b23"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"fa7ab95a_a6c20751","line":9,"range":{"start_line":9,"start_character":51,"end_line":9,"end_character":75},"updated":"2016-08-30 16:37:22.000000000","message":"BTW if it were following semver, new feature should have bumped MINOR and not PATCH version part [1]\n\n[1] http://semver.org/","commit_id":"52e5969f314a9d3e38bb2ef1a00499703b1cb25f"},{"author":{"_account_id":11816,"name":"mike bayer","display_name":"Mike Bayer","email":"mike_mp@zzzcomputing.com","username":"zzzeek","status":"Red Hat"},"change_message_id":"8c95a2f20e5a06f8b1f28d10fdb30d0a8fe4077c","unresolved":false,"context_lines":[{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Bump dogpile.cache lower bound to 0.6.2"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Keystone requires RegionInvalidationStrategy which comes with dogpile 0.6.2"},{"line_number":10,"context_line":"Introduced by https://review.openstack.org/#/c/349704/"},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"Change-Id: I6733cefef90d07330e219591dc3c49e170512b23"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"fa7ab95a_dc1a7e7c","line":9,"range":{"start_line":9,"start_character":51,"end_line":9,"end_character":75},"in_reply_to":"fa7ab95a_a6c20751","updated":"2016-08-30 17:33:22.000000000","message":"concerns I have with semver (besides that I\u0027d have to make a huge change to my versioning model and get all my users to adjust to it) include: \n\n* At the very least, SQLAlchemy would be at version 11 now, and version 1.0 would have been in 2006 when I had only put about six months of work into it, the project was ridiculously immature, and had at least six or seven full-blown refactorings in its future.   I prefer projects to stay in a \"0.x\" status for several years until they\u0027ve gained enough widespread adoption that they are proven for production use.  \"1.0\" means a lot to people and semver forces you into it an order of magnitude too soon.    Semver\u0027s solution of keeping all changes on minor version while you\u0027re in 0.x.y means SQLAlchemy would have made it to 0.103.0, which lacks critical context that we did major API changes in 0.2.x, 0.3.x, 0.4.x, etc.    I\u0027d like that last digit to be available, basically.\n\n* semver has a rigid notion of \"backwards incompatible\" - any change can be backwards-incompatible, esp. if you have a granular API like that of SQLAlchemy or Alembic.  I almost never add truly \"backwards incompatible\" changes to an API, but for a fine-grained API it is unavoidable that a large portion of improvements will affect someone that was relying on previously undefined, broken, or sub-optimal behavior.   Alembic added the feature of being able to compare INTEGER/BIGINT types distinctly, rather than not being able to tell the difference.  In the vast majority of cases, this is a good thing, but Nova had a rigid requirement on this comparison failing: https://review.openstack.org/#/c/253859/ hence that release broke the world.  My projects would all be at version 425.0.0 if i truly had to do this for every feature that could conceivably surprise a project that was relying on things incorrectly.","commit_id":"52e5969f314a9d3e38bb2ef1a00499703b1cb25f"}]}
