| fungi | __ministry: i've been trying to help the mistral developers find time to triage an existing private report about that bug, but perhaps it's best if we switch it to public now that it's been disclosed in a public irc channel | 19:18 |
|---|---|---|
| fungi | apetrich: ^ see comments from __ministry around 02:00 utc tuesday: https://meetings.opendev.org/irclogs/%23openstack-mistral/%23openstack-mistral.2021-06-29.log.html | 19:21 |
| apetrich | fungi, I dunno. I'm trying to get a sensible solution for it, but besides removing the feature I don't really see how. | 20:49 |
| apetrich | fungi, tomorrow I will talk to a colleague and if we don't get good ideas we might just remove the feature and then I'm fine to go public, if you don't mind | 20:51 |
| apetrich | I will ping you either way | 20:51 |
| fungi | apetrich: sure, but i mean, it's already public now. it's been laid out by a user in this irc channel as of tuesday, in logs published to a place indexed by web search engines | 20:51 |
| fungi | so i'm really just questioning the utility (or futility) of leaving the bug report private at this point | 20:52 |
| fungi | i don't think that should necessarily impact your timeline for devising a fix | 20:52 |
| fungi | it's more just about accepting that this defect is publicly known | 20:53 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!