)]}'
{"zuul/layout.yaml":[{"author":{"_account_id":4146,"name":"Clark Boylan","email":"cboylan@sapwetik.org","username":"cboylan"},"change_message_id":"5ef634f78ce874ff9aeb07871e13ed441cecdeed","unresolved":false,"context_lines":[{"line_number":95,"context_line":"    trigger:"},{"line_number":96,"context_line":"      gerrit:"},{"line_number":97,"context_line":"        - event: ref-updated"},{"line_number":98,"context_line":"          ref: ^refs/tags/([0-9]+\\.){3}[0-9]*(a|b|rc)[0-9]+$"},{"line_number":99,"context_line":""},{"line_number":100,"context_line":"  - name: release"},{"line_number":101,"context_line":"    description: When a commit is tagged as a release, this pipeline runs jobs that publish archives and documentation."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"1aca2d91_31f97c81","line":98,"updated":"2015-05-06 18:18:33.000000000","message":"What do you think about using the release regex then appending the prerelease stuff to it? makes it a bit more clear what the relationship is between these two regexes.\n\nAlso, pretty sure the trailing \u0027.\u0027 that this new regex requires after the first 3 tuple is not what we want. Using nova\u0027s tags as an example:\n\n  2015.1.0b1\n  2015.1.0b2\n  2015.1.0b3\n  2015.1.0rc1\n  2015.1.0rc2\n  2015.1.0rc3\n\nWhich I think matches up with the below regex too. So we can address readability and correctness together.","commit_id":"993e72c1ec33951c47ef78049f648bfb8f478705"},{"author":{"_account_id":5263,"name":"Jeremy Stanley","display_name":"fungi","email":"fungi@yuggoth.org","username":"fungi","status":"missing, presumed fed"},"change_message_id":"a4eecc3e2f454d39738b070480bb0d2272342a89","unresolved":false,"context_lines":[{"line_number":95,"context_line":"    trigger:"},{"line_number":96,"context_line":"      gerrit:"},{"line_number":97,"context_line":"        - event: ref-updated"},{"line_number":98,"context_line":"          ref: ^refs/tags/([0-9]+\\.){3}[0-9]*(a|b|rc)[0-9]+$"},{"line_number":99,"context_line":""},{"line_number":100,"context_line":"  - name: release"},{"line_number":101,"context_line":"    description: When a commit is tagged as a release, this pipeline runs jobs that publish archives and documentation."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"1aca2d91_acff7300","line":98,"in_reply_to":"1aca2d91_31f97c81","updated":"2015-05-06 18:39:49.000000000","message":"I\u0027m fine refactoring this regex for clarity.\n\nAs to your second point, based on my reading of PBR those will be reinterpreted as e.g. 2015.1.0.b1 instead.","commit_id":"993e72c1ec33951c47ef78049f648bfb8f478705"},{"author":{"_account_id":4146,"name":"Clark Boylan","email":"cboylan@sapwetik.org","username":"cboylan"},"change_message_id":"48bdb75d480fb1ec01c60362408ccea16f690c13","unresolved":false,"context_lines":[{"line_number":95,"context_line":"    trigger:"},{"line_number":96,"context_line":"      gerrit:"},{"line_number":97,"context_line":"        - event: ref-updated"},{"line_number":98,"context_line":"          ref: ^refs/tags/([0-9]+\\.){3}[0-9]*(a|b|rc)[0-9]+$"},{"line_number":99,"context_line":""},{"line_number":100,"context_line":"  - name: release"},{"line_number":101,"context_line":"    description: When a commit is tagged as a release, this pipeline runs jobs that publish archives and documentation."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"1aca2d91_0c00a733","line":98,"in_reply_to":"1aca2d91_acff7300","updated":"2015-05-06 18:46:23.000000000","message":"Built an sdist for nova with latest pbr and actually get 2015.1.0.0b1. So it is normalized according to pep440 (no . between numbers and \u0027b\u0027) but it doesn\u0027t match the tag directly.\n\nWe likely want something like:\n\n  ^refs/tags/([0-9]+\\.){3}[0-9]+(a|b|rc)[0-9]+$\n\nNote the * becomes a +. Though there is some question if we can just hard code that to a 0.","commit_id":"993e72c1ec33951c47ef78049f648bfb8f478705"},{"author":{"_account_id":4190,"name":"lifeless","email":"robertc@robertcollins.net","username":"lifeless"},"change_message_id":"2a8b473091cadb848317a25bfbfafa76927359e6","unresolved":false,"context_lines":[{"line_number":95,"context_line":"    trigger:"},{"line_number":96,"context_line":"      gerrit:"},{"line_number":97,"context_line":"        - event: ref-updated"},{"line_number":98,"context_line":"          ref: ^refs/tags/([0-9]+\\.){3}[0-9]*(a|b|rc)[0-9]+$"},{"line_number":99,"context_line":""},{"line_number":100,"context_line":"  - name: release"},{"line_number":101,"context_line":"    description: When a commit is tagged as a release, this pipeline runs jobs that publish archives and documentation."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"1aca2d91_ece56ba8","line":98,"in_reply_to":"1aca2d91_acff7300","updated":"2015-05-06 18:45:55.000000000","message":"So PBR follows within some limits the generous-on-receipt, strict-on-emission principle. So the following are all the same:\n1.0rc1\n1.rc1\n1.0.0rc1\n1.0.0.0rc1\n\nWhat problem are you trying to solve?","commit_id":"993e72c1ec33951c47ef78049f648bfb8f478705"}]}
