)]}'
{"releasenotes/config.yaml":[{"author":{"_account_id":14525,"name":"Vasyl Saienko","email":"vsaienko@mirantis.com","username":"vsaienko"},"change_message_id":"f38955482d72d6bdaf36af184c481e1cf557881b","unresolved":true,"context_lines":[{"line_number":3,"context_line":"collapse_pre_releases: false"},{"line_number":4,"context_line":"stop_at_branch_base: true"},{"line_number":5,"context_line":"sections:"},{"line_number":6,"context_line":"  - [ca-issuer, ca-issuer Chart]"},{"line_number":7,"context_line":"  - [calico, calico Chart]"},{"line_number":8,"context_line":"  - [ceph-client, ceph-client Chart]"},{"line_number":9,"context_line":"  - [ceph-mon, ceph-mon Chart]"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"4e455553_aac1d8e8","line":6,"range":{"start_line":6,"start_character":4,"end_line":6,"end_character":5},"updated":"2025-01-15 11:36:30.000000000","message":"I think we need also use subsections here https://docs.openstack.org/reno/latest/user/usage.html which will represent what exactly was done like:\n- features\n- issues\n- fixes","commit_id":"7ef00681be101353c0aacc5d90b1a98c30abc60f"},{"author":{"_account_id":3009,"name":"Vladimir Kozhukalov","email":"kozhukalov@gmail.com","username":"kozhukalov"},"change_message_id":"fcfd29162bd5fb68f1411374ddea5314a6e5100a","unresolved":true,"context_lines":[{"line_number":3,"context_line":"collapse_pre_releases: false"},{"line_number":4,"context_line":"stop_at_branch_base: true"},{"line_number":5,"context_line":"sections:"},{"line_number":6,"context_line":"  - [ca-issuer, ca-issuer Chart]"},{"line_number":7,"context_line":"  - [calico, calico Chart]"},{"line_number":8,"context_line":"  - [ceph-client, ceph-client Chart]"},{"line_number":9,"context_line":"  - [ceph-mon, ceph-mon Chart]"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"fb1376b8_d78523ef","line":6,"range":{"start_line":6,"start_character":4,"end_line":6,"end_character":5},"in_reply_to":"4e455553_aac1d8e8","updated":"2025-01-15 14:16:22.000000000","message":"This is good when the git repo is used for one project. In our case we have many charts that barely intersect with each other. IMO it is enough to have a list of short descriptions for changes for every chart whether they are fixes or features. \n\nAlso reno subsection functionality is not flexible. It requires subsections to be defined after sections where they should appear. And if you define them twice after for example chart1 and chart2 then in the report they will appear twice.\n\nAnyway features, issues, fixes, etc. are defined as sections (not subsections) and one can use them if necessary. Those notes will appear as a separate section.","commit_id":"7ef00681be101353c0aacc5d90b1a98c30abc60f"},{"author":{"_account_id":3009,"name":"Vladimir Kozhukalov","email":"kozhukalov@gmail.com","username":"kozhukalov"},"change_message_id":"0c96fde8a31880e7480d9c2495f691b01b4f9354","unresolved":true,"context_lines":[{"line_number":3,"context_line":"collapse_pre_releases: false"},{"line_number":4,"context_line":"stop_at_branch_base: true"},{"line_number":5,"context_line":"sections:"},{"line_number":6,"context_line":"  - [ca-issuer, ca-issuer Chart]"},{"line_number":7,"context_line":"  - [calico, calico Chart]"},{"line_number":8,"context_line":"  - [ceph-client, ceph-client Chart]"},{"line_number":9,"context_line":"  - [ceph-mon, ceph-mon Chart]"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"2d4b1eb8_8b2e6cdd","line":6,"range":{"start_line":6,"start_character":4,"end_line":6,"end_character":5},"in_reply_to":"fb1376b8_d78523ef","updated":"2025-01-15 14:22:09.000000000","message":"I would even remove features, issues, etc. sections here https://opendev.org/openstack/openstack-helm-infra/src/branch/master/releasenotes/config.yaml#L57-L62 because we are going to generate reports and put them to charts. Every chart is going to have its own CHANGELOG.md.","commit_id":"7ef00681be101353c0aacc5d90b1a98c30abc60f"}]}