| vanou | TheJulia: thank you. with such condition required to user, my concern goes away. i overlook that requirements for ironic user. | 01:36 |
|---|---|---|
| vanou | TheJulia: yes. containerization can bypass such concern. i'm happy to know there is a work going to handle this concern. thank you. | 01:39 |
| vanou | I have a question about https://review.opendev.org/c/openstack/ironic/+/826576 | 01:47 |
| vanou | This commit (826576) fixes problem that is introduced by another commit in this yoga development cycle. In this case should i add release note to this commit (826576)? | 01:49 |
| vanou | If these 2 commits (826576 and commit which introduced problem) happen between different release cycle, it's make sense for me to add release note to commit 826576. | 01:51 |
| TheJulia | vanou: generally yes, you should always include release notes | 20:17 |
| TheJulia | since we also release multiple times during an openstack development cycle | 20:18 |
| vanou | TheJulia: thank you. now i understand policy of release note inclusion in commit. i'll add asap | 21:52 |
| janders | good morning Ironic o/ | 23:20 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!