)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":28048,"name":"Will Szumski","email":"will@stackhpc.com","username":"jovial"},"change_message_id":"bb8c1c3c7cdb1111e1f3c53bfe4bafdeb919a3b9","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"27832783_902d91c7","updated":"2026-04-15 16:30:55.000000000","message":"Does it make sense to target 2025.2 initially and then to backport to 2025.1?","commit_id":"0a109a0741d7baead729271e0cb8d826be769654"},{"author":{"_account_id":38873,"name":"Owen Jones","display_name":"Owen Jones","email":"owen@stackhpc.com","username":"owenjones"},"change_message_id":"08be9f5786a41aa5c7e22c257f933e578e879ab6","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"9c598ef4_c83b50cc","updated":"2026-04-16 14:34:01.000000000","message":"OK, we\u0027ll need to be able to set `ipa_build_release` also to control that (or additional logic to force e.g. 10-stream if build_distro is centos, 10 if it\u0027s Rocky) - first option seems better?","commit_id":"0a109a0741d7baead729271e0cb8d826be769654"},{"author":{"_account_id":38873,"name":"Owen Jones","display_name":"Owen Jones","email":"owen@stackhpc.com","username":"owenjones"},"change_message_id":"878a3be1763b65622ca28c398a845801ed514358","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"d969d0a5_2e6b9695","updated":"2026-04-15 16:20:30.000000000","message":"check experimental","commit_id":"0a109a0741d7baead729271e0cb8d826be769654"}],"etc/kayobe/ipa.yml":[{"author":{"_account_id":28048,"name":"Will Szumski","email":"will@stackhpc.com","username":"jovial"},"change_message_id":"4e018fb98a0f4dcffb6f7dcb719b599fc798616a","unresolved":true,"context_lines":[{"line_number":9,"context_line":""},{"line_number":10,"context_line":"# Whether to build IPA images on Rocky whilst using 2025.1/2025.2, to"},{"line_number":11,"context_line":"# support migration to 2026.1."},{"line_number":12,"context_line":"#ipa_build_rocky:"},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"# URL of IPA source repository."},{"line_number":15,"context_line":"#ipa_build_source_url:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"13fd642a_6c50cf19","line":12,"updated":"2026-04-15 16:45:44.000000000","message":"The only slight issue is that this might get left in the kayobe-confg when we merge in 2026.1 since it it hasn\u0027t come through master first. Could we land distro selection on master: \n\n    # CentOS or Rocky. Only Rocky is tested. \n    ipa_build_el_distro: centos\n\non master. Then backport that all the way through? We could even revert that before the gazpacho release.","commit_id":"0a109a0741d7baead729271e0cb8d826be769654"},{"author":{"_account_id":28048,"name":"Will Szumski","email":"will@stackhpc.com","username":"jovial"},"change_message_id":"d2cb76d45a93970b4f2ff268bdf7d2df6600c30e","unresolved":true,"context_lines":[{"line_number":9,"context_line":""},{"line_number":10,"context_line":"# Whether to build IPA images on Rocky whilst using 2025.1/2025.2, to"},{"line_number":11,"context_line":"# support migration to 2026.1."},{"line_number":12,"context_line":"#ipa_build_rocky:"},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"# URL of IPA source repository."},{"line_number":15,"context_line":"#ipa_build_source_url:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"421ed2bc_577b485c","line":12,"in_reply_to":"13fd642a_6c50cf19","updated":"2026-04-16 08:40:22.000000000","message":"Reverting before the release obviously doesn\u0027t work. It needs to make it into kayobe-config...\n\n\nI will look to see if there is a precedent where we\u0027ve added a flag to a stable branch only.","commit_id":"0a109a0741d7baead729271e0cb8d826be769654"},{"author":{"_account_id":28048,"name":"Will Szumski","email":"will@stackhpc.com","username":"jovial"},"change_message_id":"4fcf0498d366e31805a5accf9cba133714056c0c","unresolved":true,"context_lines":[{"line_number":9,"context_line":""},{"line_number":10,"context_line":"# Whether to build IPA images on Rocky whilst using 2025.1/2025.2, to"},{"line_number":11,"context_line":"# support migration to 2026.1."},{"line_number":12,"context_line":"#ipa_build_rocky:"},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"# URL of IPA source repository."},{"line_number":15,"context_line":"#ipa_build_source_url:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"f43f241b_f4f6f2c6","line":12,"in_reply_to":"421ed2bc_577b485c","updated":"2026-04-16 10:57:41.000000000","message":"I couldn\u0027t find an examples of adding a feature flag to an existing release without first coming through master. Sorry, I know I suggested this could work.\n\nI think a nice feature would be able to override the default ipa distro anyway. So what about something like this in master:\n\n     # Default\n     ipa_build_distro: \"{{ os_distribution }}\"\n     # Force centos stream\n     ipa_build_distro: centos\n     # Force ubuntu\n     ipa_build_distro: ubuntu\n     # Force rocky\n     ipa_build_distro: rocky\n\nThen all conditionals use `ipa_build_distro`.\n \nDuring the backport to 2025.2 and 2025.1, we add support for rocky at the same time.","commit_id":"0a109a0741d7baead729271e0cb8d826be769654"}]}