On Tue, 5 Mar 2019, Ricardo Dias wrote: > Hi Greg, > > I think it makes sense to move messenger tickets to its own project. As you said, it will remove some noise from the RADOS project and it will become much easier to organize messenger issues. > > Therefore, +1 for creating the messenger project in Redmine. I like the idea of being able to find them, but it does mean we'll need to fiddle with queries to see them. I already struggle with having mgr bugs in a separate project (I view core mgr stuff as part of RADOS). Maybe if messenger and mgr are a sub-sub-projects of RADOS or something? Or I can just make a custom query. That's probably the thing to do. sage > > Ricardo Dias > > > On 4 Mar 2019, at 22:19, Gregory Farnum <gfarnum@xxxxxxxxxx> wrote: > > > > In the past, messenger bugs have been shoveled into the catch-all > > RADOS or Ceph project since Sage and I both participated in those. > > > > But at this point, that's often not very true, and the group of people > > working on AsyncMessenger issues is quite different from those working > > on the monitors and OSDs which make up most of the RADOS tickets. > > > > Should we create a new project in Redmine to track issues in the > > messenger implementations? It would make bug scrubbing easier and > > presumably make it simpler to prioritize those issues for the group > > working on them. > > -Greg > > > > >
