)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":1,"name":"James E. Blair","email":"jim@acmegating.com","username":"corvus"},"change_message_id":"062dca345085457690171ad8334d6f7cc088382c","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"fa6ac1f1_73656df0","updated":"2024-11-18 21:24:41.000000000","message":"Thanks!\n\nLooking at the first section, it reminds me a lot of the release notes.  We already take a *great* deal of care when writing the release notes to make sure they are short, succinct, and relevant.  I think if we end up doing too much re-writing of them into a quarterly blog post, it\u0027s either a missed opportunity to attract new eyeballs, or unnecessary effort re-editing them.\n\nHow about we aim for something with high level themes and try to draw people to the release notes for details?  Something like this maybe?\n\n```\nOver the past several months, we released Zuul 11.1.0 [0] and Nodepool 11.0.0 [1]. These milestones\nbring many improvements including:\n\n    * Significant performance improvements\n    * New configuration options supporting large project configurations\n    * Better control over job inheritance\n    * More useful error messages reported to users\n\nMany more new features and bugfixes are detailed in the release notes, head over there to see everything that\u0027s new.\n\nWe’re thrilled to see these updates make it out to you via our most recent releases. These performance\nimprovements, features, and bugfixes ensure that Zuul continues to be flexible for all of your continuous\nintegration and continuous deployment needs.\n\n```\n\nAn alternate approach would be to publish the release notes in the blog (basically as an alternative publication channel).  But I don\u0027t like that idea as much.","commit_id":"a914497788aef8385df0ed7943effbf8300473cf"}],"www/blog/index.html":[{"author":{"_account_id":4146,"name":"Clark Boylan","email":"cboylan@sapwetik.org","username":"cboylan"},"change_message_id":"2a8fb73a5cd1249e2a17910c96685173d0947499","unresolved":true,"context_lines":[{"line_number":98,"context_line":"\t\t\u003cp\u003e"},{"line_number":99,"context_line":"\t\tZuul configuration has been made richer in a number of ways:"},{"line_number":100,"context_line":"\t\t\u003ca href\u003d\"https://zuul-ci.org/docs/zuul/latest/tenants.html#attr-tenant.untrusted-projects.%3Cproject%3E.configure-projects\"\u003e"},{"line_number":101,"context_line":"\t\tUntrusted configuration projects\u003c/a\u003e have been added as an"},{"line_number":102,"context_line":"\t\talternative to trusted projects. You can now elect to have"},{"line_number":103,"context_line":"\t\tcentral untrusted projects configure other untrusted projects."},{"line_number":104,"context_line":"\t\tAdditionally, during inheritance you can now control whether"}],"source_content_type":"text/html","patch_set":1,"id":"573b8a79_9bf8af9d","line":101,"updated":"2024-11-18 17:14:36.000000000","message":"I tried using `ul` and `li` tags with the lists here and below and it seems like whatever css theme we\u0027re using doesn\u0027t render lists at all? I suppose we can always edit to fix that in the future but for now the content seems more important.","commit_id":"a914497788aef8385df0ed7943effbf8300473cf"}]}