)]}'
{"deliverables/stein/oslo.config.yaml":[{"author":{"_account_id":11904,"name":"Sean McGinnis","email":"sean.mcginnis@gmail.com","username":"SeanM"},"change_message_id":"f84725b251b588ffe9517194691cf00494df16de","unresolved":false,"context_lines":[{"line_number":7,"context_line":"repository-settings:"},{"line_number":8,"context_line":"  openstack/oslo.config: {}"},{"line_number":9,"context_line":"cycle-highlights:"},{"line_number":10,"context_line":"  - Added a Castellan config driver that allows secrets to be moved from"},{"line_number":11,"context_line":"    on-disk config files to any Castellan-compatible keystore. This driver"},{"line_number":12,"context_line":"    lives in the Castellan project, so Castellan must be installed in order to"},{"line_number":13,"context_line":"    use it."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"5fc1f717_dd164ea8","line":10,"updated":"2019-03-21 19:36:10.000000000","message":"This look good, but I\u0027m afraid they will lose important context.\n\nThe cycle highlights are per-team, so all of these will show up as highlights for Oslo. These all do mention \"config\", so it should be easy enough to infer that they are for oslo.config. But along with everything else, it might be better to limit things to 1 or 2 highlights for each oslo deliverable so that the combined output has overall important updates rather than release notes for each library.","commit_id":"2c6558ad270342387770cbf7cab89b318df835fe"},{"author":{"_account_id":6928,"name":"Ben Nemec","email":"openstack@nemebean.com","username":"bnemec"},"change_message_id":"84bcc0ff8d033cb960c00b5020d2ed9b41147006","unresolved":false,"context_lines":[{"line_number":7,"context_line":"repository-settings:"},{"line_number":8,"context_line":"  openstack/oslo.config: {}"},{"line_number":9,"context_line":"cycle-highlights:"},{"line_number":10,"context_line":"  - Added a Castellan config driver that allows secrets to be moved from"},{"line_number":11,"context_line":"    on-disk config files to any Castellan-compatible keystore. This driver"},{"line_number":12,"context_line":"    lives in the Castellan project, so Castellan must be installed in order to"},{"line_number":13,"context_line":"    use it."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"5fc1f717_f83478e0","line":10,"in_reply_to":"5fc1f717_dd164ea8","updated":"2019-03-21 19:52:23.000000000","message":"These are the only highlights I was planning for Oslo. The other major work we did wasn\u0027t user-visible so there\u0027s no reason to call it out in cycle highlights.\n\nI realize it feels a little weird to have all the highlights come from one library out of 40, but all of these features were enabling significant use cases that users seem to care about: removing secrets from config files, containerization, and config validation (something people have wanted for years). I could add something to the env driver one to call out why it\u0027s a significant feature (I should have done that anyway), but otherwise these are the marketable things that happened in Oslo this cycle.","commit_id":"2c6558ad270342387770cbf7cab89b318df835fe"},{"author":{"_account_id":11904,"name":"Sean McGinnis","email":"sean.mcginnis@gmail.com","username":"SeanM"},"change_message_id":"b75ca1079c4b2ea02bbc742965c1b1e823811f94","unresolved":false,"context_lines":[{"line_number":7,"context_line":"repository-settings:"},{"line_number":8,"context_line":"  openstack/oslo.config: {}"},{"line_number":9,"context_line":"cycle-highlights:"},{"line_number":10,"context_line":"  - Added a Castellan config driver that allows secrets to be moved from"},{"line_number":11,"context_line":"    on-disk config files to any Castellan-compatible keystore. This driver"},{"line_number":12,"context_line":"    lives in the Castellan project, so Castellan must be installed in order to"},{"line_number":13,"context_line":"    use it."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"5fc1f717_18baa409","line":10,"in_reply_to":"5fc1f717_f83478e0","updated":"2019-03-21 19:57:54.000000000","message":"OK, makes sense. Thanks! If you want to expand on the env driver, we can do that as a follow up, but based on this, I think this is good enough to go.","commit_id":"2c6558ad270342387770cbf7cab89b318df835fe"}]}